Defense tech market map

A drone company, a software supplier and a factory can all sell into defense. Their buyers, contracts and cash needs can be very different. We group representative companies by the work they support, the technology they supply and the procurement evidence behind them, so you can compare business models and ask more specific investor questions.

Scope and inclusion criteria

The October 5, 2026 snapshot covers 18 companies founded as startups, including growth-stage businesses. It's US-oriented, with Helsing included as one European/allied example. The sample is representative rather than an exhaustive US or global inventory.

Companies qualify through an active first-party defense offering or a named defense program. Dual-use companies, which serve both civilian and defense customers, need a specific defense role. Enabling suppliers need an identifiable role in delivering or producing defense technology.

We exclude established listed defense primes from the company sample. A prime contractor holds the main customer agreement; a supplier may sell through that prime. Primes appear here only as buyers, integrators or program context.

Inclusion does not establish current ownership, private-company status, early-stage status or investment availability. Dated program examples describe the stage supported by that announcement. They do not establish subsequent deliveries or current revenue.

How to read the map

Each company has one primary category based on a representative offering. That category is an orientation tool, not an official procurement classification or a statement about all company revenue.

  • Mission groups describe the defense work a product supports, such as reconnaissance, ocean surveys or command workflows.
  • Enabling groups describe adoption and supply bottlenecks, such as secure software delivery or manufacturing capacity. They are separate from the seven mission groups.
  • Technology tags identify autonomy, sensors, mission software, secure software or manufacturing. Artificial intelligence (AI) can support several categories; it is not a separate additive market.
  • Commercial lens is our business-model inference, not a verified revenue breakdown, margin estimate or contract term.
  • Diligence question identifies a material uncertainty for an investor. No company is ranked or recommended.

Intelligence, surveillance and reconnaissance (ISR) means collecting information about an operating environment. Uncrewed aircraft systems (UAS) include the aircraft and associated equipment. Counter-UAS products can detect or track aircraft, defeat them, or support another system that does so. Those functions are different.

Evidence labels describe the source and stage of a claim. They do not rate company quality:

  • Government program evidence: a government announcement supports the stated program role or award stage.
  • Company-reported evidence: the company describes an award, integration, deployment or supplier role. The description is a self-report.
  • Planned demonstration: a company announcement describes intended testing. A target date does not establish completion.
  • Marketplace availability: a product has a described purchasing or authorization route. Availability does not establish an order.
  • Product offering only: the offering is documented, but no primary award source is included here. This does not mean the company has no contracts.

All entries share the October 5, 2026 check date. Product pages without a publication date are labeled “date not stated.” Neither evidence labels nor category counts measure market share, market size or investment quality.

Mission map

Air autonomy and tactical ISR

This group covers aircraft and mission-autonomy software for reconnaissance and air missions. Aircraft fleets carry manufacturing and sustainment costs, the maintenance and support needed after delivery. Autonomy software also depends on airframe integration and qualification, the testing and acceptance requirements for its intended use.

  • Shield AI

    Hivemind mission-autonomy software and V-BAT uncrewed aircraft serve military users. The cited US Air Force example concerns the Collaborative Combat Aircraft program. Technology tags: autonomy, mission software, aircraft.

    • Commercial lens: aircraft sales, autonomy licensing, integration and support may have different economics.
    • Company-reported evidence: Shield AI announced a development selection on February 13, 2026. It covers technology maturation, risk reduction and demonstrations, not a fleet production order.
    • Product sources: autonomy software context, September 24, 2026; V-BAT aircraft offering, date not stated. Checked October 5, 2026.
    • Diligence question: which airframe integrations and qualifications convert software development work into repeatable license or production revenue?
  • Skydio

    X10D is a small uncrewed aircraft for tactical reconnaissance. The US Army is the customer named in the cited order announcement. Skydio also serves civilian markets. Technology tags: autonomy, sensors, fleet software.

    • Commercial lens: aircraft, fleet software, accessories, training and support contribute different costs and revenue streams.
    • Company-reported evidence: Skydio announced an Army aircraft order on March 22, 2026. The announcement does not independently reconcile obligated funds, the funds committed to orders, or recognized revenue.
    • Product source: tactical reconnaissance offering, date not stated. Checked October 5, 2026.
    • Diligence question: how much of the economics is repeat procurement and sustainment rather than one hardware order?

Maritime autonomy and ocean intelligence

Autonomous vessels and operated ocean-data missions belong here. A Navy vessel-production agreement and an ocean-survey task order support different business models. A survey order does not establish procurement of a combat vessel.

  • Saildrone

    Surveyor autonomous surface vessels perform ocean surveys for the US Naval Oceanographic Office. Saildrone also serves civilian ocean-data users. Technology tags: autonomy, ocean sensors, data delivery.

    • Commercial lens: operated missions and survey/data delivery depend on vessel ownership, deployment costs and utilization.
    • Company-reported evidence: the survey task order announcement of September 15, 2026 describes Atlantic operations. It supports a service-mission example, not vessel unit sales or earned revenue.
    • Product source: the same September 15, 2026 announcement describes Surveyor. Checked October 5, 2026.
    • Diligence question: who owns the vessels and data, and what happens to margins when deployments, maintenance or weather disrupt utilization?
  • Saronic

    Saronic supplies autonomous surface vessels, including Marauder, and maritime command software. Its cited production customer is the US Navy. Technology tags: autonomy, mission software, shipbuilding.

    • Commercial lens: vessel production, mission integration, software and sustainment create separate capital and delivery obligations.
    • Government program evidence: the Navy's production award announcement, September 29, 2026, names Saronic among three recipients, each with ten medium uncrewed surface vessels. First deliveries were scheduled before the end of fiscal year 2027; the release does not confirm delivery.
    • Product source: surface vessel offering, date not stated. Checked October 5, 2026.
    • Diligence question: can yard capacity, supplier throughput and vessel sustainment meet funded delivery milestones without consuming disproportionate capital?

Ground autonomy and contested logistics

This group covers autonomous ground mobility, vehicle retrofits and military support. Contested logistics means moving supplies or equipment where access and operations can be disrupted. The economics differ between supplying autonomy to a vehicle prime and holding an agreement to produce complete vehicles.

  • Forterra

    AutoDrive supplies ground autonomy; MESA is a separate autonomous vehicle offering. The cited US Marine Corps example concerns AutoDrive integrated into Oshkosh Defense's ROGUE Fires vehicle program. Technology tags: autonomy, vehicle integration, mission software.

    • Commercial lens: supplier-to-prime integration can separate Forterra's contract rights and economics from those of the complete vehicle.
    • Company-reported evidence: the prime integration announcement, January 13, 2025, describes low-rate production orders. It does not establish that Forterra holds the entire government vehicle contract or that those orders cover MESA.
    • Product source: MESA vehicle announcement, April 28, 2026. Checked October 5, 2026.
    • Diligence question: what contract rights, margins and customer concentration sit with Forterra rather than the prime vehicle integrator?
  • Overland AI

    ULTRA vehicles and OverDrive autonomy software support autonomous ground missions. The cited program concerns autonomous support vehicles for the US Marine Corps' mobile air-defense system. Technology tags: autonomy, sensors, vehicle manufacturing.

    • Commercial lens: complete vehicles, autonomy integration and mission software may produce different revenue mixes.
    • Company-reported evidence: a production agreement announcement, June 29, 2026, describes an Accelerate the Procurement and Fielding of Innovative Technologies-supported award. That initiative supplies transition funding; the award authority is a production Other Transaction (OT) agreement. An award does not establish completed fielding.
    • Product source: ground autonomy offering, date not stated. Checked October 5, 2026.
    • Diligence question: how much autonomy performance, safety qualification and manufacturing work remains before funded delivery milestones?

Counter-UAS and air-domain sensing

Radar detects and tracks air threats. Defeat systems act against them. Buyers may need both, with separate integration, acceptance and sustainment requirements.

  • CHAOS Industries

    VANQUISH PRIME is a software-defined fire-control radar for defense air-surveillance and air-defense users. These are intended buyer/use cases, not a named paying customer in this entry. Technology tags: radar sensors, tracking software, integration.

    • Commercial lens: radar systems, integration and software support depend on the direct-customer or integrator channel.
    • Product offering only: no primary award source is included. A possible direct or integrator procurement route is an inference. Sensing is not itself defeat.
    • Product source: VANQUISH PRIME radar, date not stated. Award-source date: not applicable. Checked October 5, 2026.
    • Diligence question: which funded integrators or end users have accepted the system, and how does sensing integrate with the rest of the defense architecture?
  • Epirus

    Epirus supplies high-power microwave counter-UAS systems, including Leonidas and the HAVOC program offering. The cited customer is the US Marine Corps through the Office of Naval Research. Technology tags: directed energy, electronics, system integration.

    • Commercial lens: hardware, integration, training and support depend on production and operating costs.
    • Company-reported evidence: the HAVOC program announcement, August 10, 2026, describes a named contract. It does not establish broad fleet adoption or independently validated effectiveness.
    • Product source: counter-UAS product offering, date not stated. Checked October 5, 2026.
    • Diligence question: what independently accepted test evidence and power, cooling and sustainment requirements govern deployable unit economics?

Space operations and spacecraft platforms

A spacecraft bus supplies core platform functions, such as power and communications, for a payload. Payload supply, launch and mission operations are distinct businesses with different customer and capital dependencies.

  • Apex

    Apex supplies spacecraft buses to payload owners and integrators. Its proposed Orbital Magazine is a defense-relevant host platform, distinct from the hosted interceptor or payload. Technology tags: spacecraft platforms, integration, manufacturing.

    • Commercial lens: bus production may repeat across orders, while configuration, payload integration and qualification add project costs.
    • Planned demonstration: the company announced Project Shadow plans on October 22, 2025, with a June 2026 launch target. That announcement does not establish launch completion, accepted operational capability or a government production order.
    • Product source: spacecraft platform offering, date not stated. Checked October 5, 2026.
    • Diligence question: which spacecraft orders are funded and repeatable, and what hardware, payload and qualification risks remain with the bus supplier?
  • True Anomaly

    Jackal spacecraft and Mosaic mission software support space operations. The cited government example is the US Space Force's VICTUS HAZE mission. Technology tags: spacecraft, mission software, space-domain sensing.

    • Commercial lens: spacecraft and software economics depend on launch, operations and government development work.
    • Government program evidence: Space Systems Command's mission activity announcement, June 22, 2026, describes responsive launch and on-orbit mission activity involving True Anomaly. Demonstration participation does not establish recurring spacecraft production orders.
    • Product source: space operations offering, date not stated. Checked October 5, 2026.
    • Diligence question: what funded follow-on missions justify launch and operations capital beyond a successful demonstration?

Intelligence and command software

This group covers defense mission data, intelligence analysis and command workflows. Software may come with hardware, integration or engineers working alongside the customer. Those costs affect how repeatable the business is.

  • Anduril

    Lattice and Anduril's command/data architecture support US and allied defense users. The selected example is the Army's Next Generation Command and Control program. Anduril also supplies systems across air, maritime, counter-UAS and strike missions. Technology tags: mission software, data integration, hardware integration.

    • Commercial lens: full-stack software, hardware, integration and sustainment cannot be treated as a pure software-subscription business.
    • Government program evidence: the Army program announcement, June 22, 2026, names Anduril to lead the common data baseline as delivery progresses. This role does not classify all company revenue.
    • Product source: command software context, April 10, 2026. Checked October 5, 2026.
    • Diligence question: what is the funded program and software-versus-hardware mix, and which rights or integration costs govern recurring revenue?
  • Vannevar Labs

    Vannevar supplies software and hardware for collecting and analyzing digital information in defense missions. The cited customer path is the Defense Innovation Unit's (DIU) Real-Time Information and Effects program. Technology tags: mission software, data analysis, integration.

    • Commercial lens: licenses may sit alongside customer-specific engineering and integration services.
    • Government program evidence: DIU's production transition announcement, November 18, 2024, describes a production OT following a prototype. The stated agreement ceiling is not obligated funds, revenue or backlog.
    • Product source: mission intelligence offering, date not stated. Checked October 5, 2026.
    • Diligence question: what portion of the ceiling has funded orders, and what data rights, customer concentration and engineering effort support renewals?

Strike systems

This group covers strike platforms and associated mission software. Investor questions concern qualification, customer acceptance, payment milestones and manufacturing yield, the share of output that meets requirements. US and allied procurement systems require separate treatment.

  • Castelion

    Blackbeard is an air-launched hypersonic weapon program with the US Navy as the customer in the cited announcement. Technology tags: strike hardware, manufacturing.

    • Commercial lens: production lots and qualification work create yield, capital and payment-timing dependencies.
    • Company-reported evidence: Castelion's production order announcement, September 14, 2026, describes a Navy delivery order under Small Business Innovation Research (SBIR) Phase III. Its “up to” value does not establish obligations, earned revenue or delivered units.
    • Product source: strike systems offering, date not stated. Checked October 5, 2026.
    • Diligence question: which lot milestones are funded, and how do qualification, manufacturing yield and payment timing affect cash needs?
  • Helsing

    European/allied example. HX-2 is a strike drone integrated with Altra reconnaissance-strike software. European and allied defense users are the intended buyer/use cases in this entry. Technology tags: AI, autonomy, mission software, strike hardware.

    • Commercial lens: hardware and mission software depend on national procurement programs and licensing terms.
    • Product offering only: no primary award source is included. The US procurement routes described below are not assigned to this offering.
    • Product source: HX-2 product offering, date not stated. Award-source date: not applicable. Checked October 5, 2026.
    • Diligence question: which national procurement budgets, export permissions, customer acceptance and human-oversight requirements support adoption?
  • Mach Industries

    Viper and Glide are strike products; Forge is manufacturing infrastructure. Defense strike and protection users are intended buyer/use cases, not a named paying customer in this entry. Technology tags: strike hardware, manufacturing.

    • Commercial lens: development funding, platform production and manufacturing capacity have different economic implications.
    • Product offering only: no primary award source is included. Demonstration-to-production is a possible path. No contract or completed field capability is established here.
    • Product sources: strike product offering, date not stated; Forge manufacturing offering, date not stated. Award-source date: not applicable. Checked October 5, 2026.
    • Diligence question: which products have completed funded qualification and customer acceptance rather than only public tests or announced development?

Enabling layer

These suppliers solve software-adoption and production constraints. Their customers may be software vendors, platform operators or industrial primes. They are separate from the mission map and should not be added to it as another estimate of defense demand.

Software delivery and mission assurance

Secure software delivery helps applications reach government environments. Onboard asset intelligence supports vehicle and aircraft cybersecurity, maintenance and operations. They address different adoption problems.

  • Second Front Systems

    Game Warden supplies secure software delivery for software vendors and US government environments. It combines development, security and operations processes, often called DevSecOps. Technology tags: secure software, cloud deployment, developer infrastructure.

    • Commercial lens: platform subscriptions and deployment services depend on authorization scope and customer-specific work.
    • Marketplace availability: a company announcement of government marketplace availability, February 12, 2026, describes access through Amazon Web Services Marketplace under Joint Warfighting Cloud Capability. This is not a task order, customer adoption or guaranteed authorization for every application.
    • Product source: Game Warden platform, date not stated. Checked October 5, 2026.
    • Diligence question: what authorization is inherited versus application-specific, and who owns residual security, sponsor and procurement responsibilities?
  • Shift5

    Shift5 supplies onboard operational intelligence from vehicle and aircraft data for defense platform operators and commercial transportation users. Technology tags: platform cybersecurity, data analytics, maintenance intelligence.

    • Commercial lens: hardware-enabled analytics may require installation, platform integration and ongoing services.
    • Company-reported evidence: a deployment and financing announcement, September 3, 2025, describes defense deployments. No named primary award is included; financing and deployment assertions do not independently establish a purchase order.
    • Product source: operational intelligence offering, date not stated. Checked October 5, 2026.
    • Diligence question: who has rights to platform data and retrofit access, and what deployment work remains before repeatable fleet-level software margins?

Production capacity

Factory automation and manufacturing services supply other defense businesses. Customer commitments, factory utilization and working capital, the cash needed to fund operations before customers pay, shape the economics. Announced capacity alone does not establish demand.

  • Hadrian

    Hadrian supplies precision-part manufacturing services and Opus factory automation for aerospace and defense primes, suppliers and industrial customers. Technology tags: manufacturing, factory automation.

    • Commercial lens: manufacturing services and capacity commitments depend on utilization, working capital and financing structure.
    • Company-reported evidence: an industrial expansion announcement, July 17, 2025, describes defense manufacturing needs and capacity expansion. This is an industrial supplier example, not evidence of a direct government platform contract. Financing is not backlog, and announced capacity is not operational throughput.
    • Product source: manufacturing services offering, date not stated. Checked October 5, 2026.
    • Diligence question: are expanded factories backed by binding customer commitments, and what utilization and working capital are needed for attractive economics?

Procurement and diligence

A defense use case, a funded development agreement and an accepted production delivery answer different questions. These routes can overlap. They do not form one universal timeline, and none guarantees a long-term funded acquisition program, often called a program of record.

Prototype agreements and follow-on production

A Commercial Solutions Opening is a solicitation approach. An Other Transaction is an agreement authority. DIU principally uses prototype OT agreements and describes the potential for qualifying successful prototypes to move into follow-on production. That potential depends on the applicable requirements and agreement terms; it is not an automatic order. DIU acquisition guidance, publication date not stated; checked October 5, 2026.

Vannevar's dated example supports a prototype-to-production transition. Saronic's supports a production award after testing. The investor question is what funded work follows, who can order it and what delivery milestones remain.

Research phases and commercialization

SBIR and Small Business Technology Transfer (STTR) distinguish Phase I feasibility from Phase II research and development. Phase III covers follow-on commercialization work, which can include production, services or further development, using non-SBIR/STTR funds. A Phase III label alone does not establish repeat production revenue. Official program policies, page publication date not stated; checked October 5, 2026.

Castelion's cited announcement identifies a Phase III production delivery order. Its payment milestones, obligations and accepted deliveries remain separate economic questions. These phase descriptions are not application instructions or a statement that a particular solicitation is open.

Contract ceilings and actual orders

Under the Federal Acquisition Regulation (FAR), an indefinite-delivery, indefinite-quantity (IDIQ) contract has stated limits and a minimum commitment. Individual requirements are purchased through orders. The ceiling, minimum, actual orders, obligated funds, deliveries and recognized revenue are different measures. FAR quantity rules, displayed edition effective March 13, 2026; checked October 5, 2026.

An “up to” announcement is a limit, not proof that the full amount has been ordered or earned. A production agreement can still carry substantial delivery, acceptance and working-capital risk.

Prime and supplier routes

The end user may define the need while a program office owns the budget and a prime contractor holds the agreement. A supplier's customer can be that prime rather than the government.

Forterra's ROGUE Fires example illustrates this distinction. Supplier revenue, renewal rights, data access and bargaining power need their own analysis. The complete vehicle contract cannot be assigned to every contributing supplier.

Marketplace access and cybersecurity authorization

Marketplace listing, eligibility to receive an award, security authorization and funded orders are separate gates. An authorization to operate is permission to use a system within a defined scope. A hosting platform does not automatically authorize every application or supply its customer's budget.

Second Front's example supports an access route. It does not establish sales through that route.

Cybersecurity policy also remains contract-specific. The July 13, 2026 cybersecurity policy announcement suspended Phase II of Cybersecurity Maturity Model Certification (CMMC), while Phase I self-assessment requirements remain. The suspension does not remove underlying cybersecurity duties. Policy status checked October 5, 2026.

Allied and dual-use routes

Helsing's national customer paths cannot be read as US acquisition paths. Dual-use revenue also needs a separate civilian-customer analysis. National eligibility, export permissions, data restrictions and software-control requirements can change the addressable buyer set.

US defense export registration does not itself confer export rights. Federal registration rules distinguish registration from export permission. Current text checked October 5, 2026; these controls require case-specific professional review.

Questions that carry across categories

Our startup investment criteria provide a broader lens for evaluating a business. For defense, the company-specific question should sit alongside these economic and governance questions:

  1. Funded demand: who is the end user, budget owner, integrator and agreement recipient? Which amounts are ordered and obligated, and which remain ceilings or options?
  2. Repeatability: what repeats without another large engineering project? Separate licenses and renewals from hardware lots, surveys, installations and customer-specific services.
  3. Capital intensity: what inventory, tooling, factory, launch or vessel costs arise before payment? How do delivery delays change the cash requirement?
  4. Qualification and acceptance: which tests, approvals and customer-acceptance milestones remain? Who bears rework, warranty and sustainment costs?
  5. Data and intellectual property: who owns the data, software and interfaces? What rights support reuse across customers, and what restrictions limit it?
  6. Integration: who controls access to the platform and who pays for customization? How much customer-site engineering does each deployment require?
  7. Concentration and transition: how dependent is the business on one program, prime or national budget? What happens if prototype work ends without a funded follow-on?
  8. Safety and governance: how are human oversight, lawful use, incident review and customer eligibility handled? Vendor assurances do not substitute for documented responsibilities and accepted evidence.

For example, a recurring software license can still require engineers at each customer site and hardware installation. Compare the cost of serving the next deployment, including those obligations. Our investor diligence checklist connects these questions to the wider company evaluation.

Build your investor judgment

Our angel-investing community, Angel Squad, offers education in Hustle Fund's investing approach and opportunities to learn with peers. It can help you practice evaluating a startup's customers and business model. Inclusion here does not imply that we invested in a company or that members can invest in it.

Explore Angel Squad.

This map is educational research, not an investment recommendation, an offer of securities, or investment, legal, tax, export or procurement advice. It does not establish investor eligibility, allocation availability, company endorsement or independently validated technical performance. Private startup investments are speculative, illiquid and long-term, and you can lose all invested capital. Most startup bets may fail. Seek independent review from qualified legal, tax and other relevant professionals for specific transactions and compliance questions.