Epirus: Leonidas and the counter-drone supplier market
Epirus develops the Leonidas high-power microwave product family. Its public Army contract evidence separates system delivery, testing, support and potential future programme requirements.
Epirus is a US counter-drone technology company whose commercial development can be followed through several distinct records: venture financing, Army equipment contracts, a Navy-supported prototype for Marine Corps experimentation, and partnerships that put its technology into other companies’ platforms. Its Leonidas family is the organising product line. For a business reader, the revealing question is how that family moves between institutional buyers and integrators, and what supporting industrial capacity accompanies it.
The company’s public record is more specific than a general claim to participate in the counter-drone market. It names the government organisations behind particular projects, distinguishes successive versions of its equipment, and identifies partners supplying autonomy and integration. Those relationships explain where Epirus sits in a wider procurement chain, without requiring an assessment of operational performance.
Financing a production business
On 5 March 2025, Epirus announced a $250 million Series D led by 8VC and Washington Harbour Partners. It said cumulative venture funding exceeded $550 million and identified General Dynamics Land Systems among returning strategic investors. The stated uses included production, workforce development and supply-chain processes, alongside international and commercial expansion. This was a financing announcement about the company’s resources and plans. Epirus financing announcement.
The investor mix is commercially relevant because an industrial participant can occupy more than one role. General Dynamics Land Systems subsequently appears in a product integration announcement, giving readers a specific relationship to follow across finance and engineering. The financing disclosure does not publish a complete ownership table, so it cannot establish which shareholders control every corporate decision.
Production funding also changes the questions surrounding the business. A research supplier principally needs to sustain development; a supplier delivering equipment must also manage component availability, acceptance schedules and customer support. Epirus’ stated allocation of capital shows that management was presenting those industrial requirements as part of the growth plan.
What the Army contract actually covers
A 17 July 2025 company release identified a $43,551,060 contract from the US Army’s Rapid Capabilities and Critical Technologies Office. Its base scope comprised two Generation II systems under the Indirect Fire Protection Capability–High-Power Microwave programme, plus associated test events, support equipment and spares. The announcement also described options for additional testing, components and support. Epirus linked the award to four earlier systems it said it had delivered in May 2024. Army contract scope.
That sequence gives the company a more developed public customer history than a single demonstration. Earlier deliveries, a subsequent generation and a priced support package are different commercial milestones. They also show why dividing the headline award by two would produce a misleading equipment price: the contract description includes work and material beyond the two systems themselves.
For a supplier seeking to understand Epirus as a potential partner, the support element matters. Equipment programmes create demand around test participation, logistics and maintained configurations as well as initial manufacture. The published scope provides evidence of those categories, although it does not identify which activities Epirus performs internally or subcontracts.
A separate Navy and Marine Corps pathway
Leonidas Expeditionary has a distinct development history. In September 2024, Epirus described a $5.5 million Office of Naval Research contract associated with the Expeditionary Directed Energy Counter-Swarm project, or ExDECS. The announcement identified cooperation involving ONR, the Marine Corps Warfighting Laboratory and the Joint Counter-small Unmanned Aircraft Systems Office. Expeditionary programme introduction.
On 29 April 2025, the company reported delivery of the prototype to Naval Surface Warfare Center Dahlgren Division in support of the Marine Corps. It described completed government acceptance following factory acceptance activity, with further experimentation ahead. That record places the programme beyond an initial development announcement while retaining its prototype status. ExDECS delivery announcement.
The Army and expeditionary records should be read alongside one another because they reveal separate institutional routes for a related technology family. A company can accumulate experience across those routes, but each customer still has its own programme scope and acceptance process. The public evidence supports a multi-customer development history; it does not provide a consolidated recurring-revenue figure.
Partner roles in a new configuration
On 24 March 2026, Epirus, General Dynamics Land Systems and Kodiak AI introduced Leonidas AGV. Their announcement allocated clear roles: Epirus supplied its technology, Kodiak contributed its autonomous driving system, and General Dynamics Land Systems acted as lead systems integrator on a commercial truck platform. The published event was a product unveiling. Joint integration announcement.
This arrangement illustrates how a specialist can retain an identifiable product family while relying on partners for a larger system. The integrator’s role becomes commercially significant because the customer is evaluating a combined configuration, with responsibilities that extend beyond any single component. A product catalogue alone would not expose that division of work.
The partnership also offers a more useful competitive comparison than treating every counter-drone company as interchangeable. Some businesses supply detection or optical identification, others supply software or integration, and Epirus’ announced role concerns a different part of the system. OpenWorks Engineering’s optical product portfolio provides a neighbouring example of a specialist whose market position depends partly on integration into wider customer systems.
Building a presence around testing and customers
Epirus’ Oklahoma activity adds another dimension. In August 2025 it announced an immersive innovation centre within the FISTA Innovation Park in Lawton, presenting it as a place for education and engagement with government, industry and academic audiences. The facility is evidence of a customer-facing regional presence around the Fort Sill ecosystem. FISTA innovation centre announcement.
A further announcement on 4 August 2026 said Epirus’ radio-frequency test solution had been selected for two FISTA anechoic chambers. The company described a facility available to government-funded research, academia and industry, developed collaboratively and informed by its Torrance testing infrastructure. This is a separate public use of its engineering capabilities in test infrastructure. FISTA test-facility announcement.
Together, those records make the Oklahoma footprint more than an office address. One facility supports engagement; another provides a setting for research and assessment. Neither announcement supplies a complete facility revenue model, but both help explain how Epirus is embedding itself in an ecosystem that can connect technical development with institutional users.
The resulting commercial map has three different counterparties: government organisations buying or evaluating equipment, industrial partners building a combined product, and a regional facility supporting research and engagement. That is a useful way to follow the company because the value created in each relationship is different. A new equipment order would strengthen the customer record; a further integration would broaden the configurations available to buyers; and use of the test facility would deepen an engineering ecosystem. None can stand in for the others when judging which part of the business is developing. Keeping them separate also makes subsequent announcements easier to compare with the existing record.
Reading the next stage
The strongest follow-up evidence would connect these existing strands: completion of the Army base deliveries, any separately documented exercise of options, subsequent customer decisions after expeditionary experimentation, and a buyer-backed programme for the partner-integrated vehicle. Each would answer a different question about adoption. The distinction between a successful prototype and a production business remains useful because Epirus already has examples at several stages.
Epirus therefore belongs in a commercial map of specialist suppliers with documented government programme activity and an expanding partner network. Its public materials establish those relationships and their announced stages. They leave ownership percentages, profitability and independently assessed comparative performance outside the available picture. The company’s progress is best followed through the continuity of named programmes, accepted deliveries and industrial responsibilities that can be checked in subsequent public records.
Sources & evidence
- Epirus Army Generation II contract announcementEpirus · 17 July 2025
- Epirus public newsroomEpirus
- Epirus closes $250 million Series DEpirus · 5 March 2025
- Epirus delivers ExDECS prototype to Navy for Marine CorpsEpirus · 29 April 2025
- Leonidas Expeditionary programme introductionEpirus · 23 September 2024
- Epirus, GDLS and Kodiak introduce autonomous platform integrationEpirus · 24 March 2026
- Epirus RF test solution selected for FISTA chambersEpirus · 4 August 2026
- Epirus opens FISTA innovation centreEpirus · 21 August 2025
Public Epirus release bodies were read, including the exact Army base award and option scope, Series D, prototype acceptance, partner unveiling and FISTA facilities. These are attributed company announcements, not independent performance assessments. Financing disclosures do not establish the complete current ownership table; the vehicle integration announcement is not presented as an awarded procurement.
Suggest a correction