How to invest in defense tech
Learning how to invest in defense tech is mostly a mapping problem: the sector is five distinct layers with different revenue models, and only some of them are reachable from a brokerage account.
Defense tech is five investable layers, not one sector
"Defense tech" is a marketing label stretched across five structurally different businesses, and conflating them is the single most common analytical error in retail coverage. A diversified prime, a listed small-UAS maker, and a private autonomy startup all get filed under the same headline while behaving nothing alike on revenue timing, margin structure, and who actually writes the cheque.
Before you look at any ticker, place it in a layer. The layer tells you what evidence matters: for a prime, segment disclosure; for a pure-play, program concentration; for a software name, whether the defense business is separable from the commercial one at all. The company profiles in our company directory are organised on this logic — pure-play, defense prime, enabler.
The layer map
| Layer | What it is | Retail access | What to verify first |
|---|---|---|---|
| Diversified primes | Large contractors where defense tech is one line inside platforms, services, and sustainment. | Direct | Whether the interesting segment is separately disclosed at all. |
| Mid-tier suppliers | Subsystem, sensor, propulsion, and component vendors selling into multiple platforms. | Direct | Design-in breadth: one airframe or many. |
| Listed pure-plays | Companies whose P&L is dominated by unmanned or autonomous systems — AeroVironment, Kratos, Red Cat, Ondas, Unusual Machines. | Direct | Program concentration and sustainment tail. |
| Dual-use software | Autonomy, data, and mission software sold to both defense and commercial buyers — for example Palantir. | Direct | Whether defense revenue is disclosed separately from commercial. |
| Private and venture-only | Late-stage private defense-tech names such as Anduril and Shield AI. | None | That no listed proxy actually gives you this exposure. |
Defense-tech revenue lags the headline by budget cycles, not quarters
The gap between a defense-tech news story and the revenue it eventually produces is measured in budget cycles. There are four separate events between a capability being demonstrated and a dollar being recognised: authorisation, appropriation, contract award, and delivery against that award. Each has its own calendar, and any one of them can stall the chain without cancelling the story.
The practical consequence is that price action on a demonstration video is trading an event three or four steps upstream of revenue. The non-obvious failure mode is the opposite case: a company whose reported revenue is currently strong because it is delivering against awards made years ago, while its recent award flow has gone quiet. That company looks healthy on the income statement and hollow on the order book. Backlog and new-award disclosure, not trailing revenue, is where you catch it.
Authorisation and appropriation both run through Congress, so the legislative text on Congress.gov is the upstream primary source, and completed award notices appear in the Department of Defense contract announcements.
Program of record versus prototype is the distinction that decides the thesis
A program of record has a named funding line and a production plan; a prototype award is a bounded experiment with no obligation to buy anything afterwards. This is the distinction retail coverage most reliably collapses, because both arrive as a press release containing a government customer and a dollar figure.
Prototype and innovation-pathway awards — the kind routed through the Defense Innovation Unit, DARPA, or the SBIR program — are genuine validation signals. They tell you a service found the capability credible enough to fund a trial. They do not tell you a service has committed to field it at scale. The transition from prototype to production is where most defense-tech equity stories actually fail, and it fails quietly: there is rarely a cancellation announcement, just an award that never gets a follow-on.
When you read a contract announcement, look for three things: the contracting activity, whether the vehicle is a production contract or an other-transaction agreement, and whether the same company appears again on later awards for the same capability. Repetition is the signal. A single award is a data point.
Budget dependency is the sector's real macro factor
Defense-tech demand is set by an appropriations process rather than by consumer or enterprise demand, which changes what macro inputs matter. Rate cuts and consumer sentiment move the multiple; the enacted budget and its account-level detail move the revenue. A continuing resolution — funding at prior-year levels without new starts — is the specific mechanism that hurts emerging defense tech most, because new programs are exactly what cannot start under it. Incumbent primes are relatively insulated; a pure-play waiting on a new production line is not.
This asymmetry is why the same budget headline can be genuinely bullish for a prime and genuinely bearish for a small-cap supplier. Oversight reporting from the Government Accountability Office is the most useful free source for whether a specific program is executing on schedule or slipping, and it is written for a non-industry reader.
A pure policy signal is worth naming separately from a budget line, because it is easy to mistake for one. In August 2026, reporting confirmed by a Department of War spokesperson described a memo from the deputy secretary giving major contractors roughly three weeks to submit plans for faster, more aggressive production and delivery schedules across a named set of programs, citing depleted interceptor stockpiles after sustained use. That memo asks industry to propose capital investment and facility expansion; it is not itself an appropriation, a contract modification, or new money, and the responses were described as feeding a future budget request rather than an immediate order. The screening question is the same one this guide applies to every other headline: has an account been funded, or has a customer only asked a question.
The layer you cannot buy, and the proxies that pretend otherwise
Some of the most consequential defense-tech companies are private, and no listed instrument gives you clean exposure to them. This matters because retail interest in a private name tends to leak into loosely related tickers — a supplier, a former partner, a company in the same category — which then trade on association rather than on their own order book.
The disciplined move is to state plainly what a position actually gives you. If your thesis is "autonomy will reshape procurement," a listed pure-play gives you that thesis plus single-program risk plus small-cap liquidity risk. That may still be a reasonable way to research the theme; it is not the same exposure, and pretending otherwise is how position sizing goes wrong. Our defense startups page tracks which names remain private.
Anduril vs Shield AI: two different private-layer businesses
Anduril and Shield AI get named together often as the two headline private defense-tech names with no listed proxy, but the businesses behind those two names are not the same shape.
| Attribute | Anduril | Shield AI |
|---|---|---|
| Scope | Autonomous defense systems across counter-UAS, loitering munitions, and ground, air, and maritime systems, plus a fighter-class CCA airframe (YFQ-44A). | Aircraft plus the Hivemind autonomy stack, focused on V-BAT, X-BAT, and teaming aircraft rather than a multi-domain product line. |
| Commercial posture | Develops systems on internal funding and sells them as finished products, inverting the traditional cost-plus prime model. | Sells a vehicle plus a software-enabled mission system; the research distinction is whether that is a vehicle sale or a licensable autonomy layer. |
| Named government exposure | Holds a CCA Increment 1 production contract (FQ-44A) and a U.S. Army enterprise IT/software contract with an up-to-$20B ceiling for Lattice counter-UAS work. | V-BAT and X-BAT programs, plus Hivemind integration on partner platforms including a role in the CCA mission-autonomy software pool. |
| What to watch | Whether the Lattice software layer is adopted as the integrating command-and-control system by government customers. | Whether Hivemind is adopted beyond Shield AI's own airframes, which is what would turn it into a software business rather than an aircraft maker. |
Neither company has a ticker, so neither is a research shortcut. Anduril's thesis is a broader, product-first autonomy platform spanning several domains; Shield AI's is narrower and airframe-anchored, with its own autonomy stack as the differentiator. Both require watching contract announcements and any eventual listing filing directly, since no proxy security captures either exposure today.
A screening sequence you can actually run
Work the layers in order rather than starting from a ticker list. The sequence below is deliberately front-loaded with disqualifying checks so you spend research time on fewer names.
- Assign the layer. If you cannot say which of the five layers a company sits in, you do not yet understand the business well enough to hold it.
- Find the disclosure. Pull the latest annual filing on SEC EDGAR and check whether the defense-tech business is a reported segment or buried in "other". If it is buried, the stock cannot be tracked on the thesis you think you hold.
- Separate award flow from revenue. Read backlog and new-award commentary before the revenue line, for the reason described above.
- Test contract type. Fixed-price development work carries execution risk that cost-plus work does not; the contract vehicle is disclosed in filings and award notices, and the standard terms live on Acquisition.gov.
- Check the sustainment tail. Spares, training, and services revenue survives a program's production phase. Hardware-only revenue does not.
Investor read-through
- Strong signal: a named funding line, repeat awards for the same capability, separately disclosed segment revenue, and a services tail behind the hardware.
- Weak signal: a single prototype award, an undisclosed segment, "AI-enabled" language with no contracting activity named, and price moves that track a private company's news.
- Research bridge: continue to defense stocks, drone stocks, small-cap defense stocks, and unmanned systems for the hardware context behind the equity story.
How to invest in defense tech FAQs
How do you invest in defense tech as a retail investor?
You invest in defense tech through the public layers only: diversified primes, mid-tier suppliers, listed pure-plays such as AeroVironment or Kratos, dual-use software names, and defense and drone ETFs. The venture-stage layer is closed to retail.
Why does defense-tech revenue lag the news headlines?
Defense-tech revenue lags headlines because appropriation, contract award, delivery, and revenue recognition are four separate events spread across budget years. A demonstration covered in the press may sit years upstream of any recognised revenue, which you can verify by reading the segment discussion in the company filings on SEC EDGAR.
What is the difference between a program of record and a prototype contract?
A program of record has a funding line inside the enacted budget and a multi-year production plan; a prototype or other-transaction award is a bounded experiment that can end without a production decision. Prototype awards from organisations such as DIU or DARPA are validation signals, not durable revenue.
Is a defense tech ETF better than picking individual stocks?
A defense-tech ETF changes what you are exposed to rather than removing risk, because broad aerospace and defense funds are usually dominated by large primes with limited unmanned-systems weighting. Compare the fund mandate on the issuer page against the thesis you actually hold — see our drone ETF vs stocks comparison.
Is Anduril or Shield AI the better private defense-tech name to research?
Neither has a ticker, so "better" has to mean research priority, not a buy decision. Anduril is the broader thesis: a multi-domain autonomous-systems product company with a CCA production contract and a large Army software ceiling. Shield AI is narrower and airframe-anchored around V-BAT, X-BAT, and its Hivemind autonomy stack. Pick based on which thesis, platform breadth or airframe-plus-autonomy, matches the exposure you actually want, and watch each company's own newsroom for any listing filing.