Implied current valuation 01
61000 USD M [CO006, CO005] Diligence report
Anduril Industries
Vertically integrated autonomous weapons platform with deep DoD relationships; now priced around $61B after the 2026 Series H, but still underpinned by a large defense AI tailwind.
Cover facts
Company profile
Anduril Industries builds autonomous weapons systems and AI-powered defense platforms for the U.S. military and allied governments, led by founder Palmer Luckey and CEO Brian Schimpf.
- Website
- www.anduril.com
- Founded
- 2017-10-01
- Founders
- Palmer Luckey, Brian Schimpf, Matt Grimm, Trae Stephens, Joseph Chen
- Founding location
- Costa Mesa, California, USA
- Headquarters
- Costa Mesa, California, USA
- Product
- Lattice OS (multi-domain AI autonomy platform), Ghost UAS (autonomous surveillance drone), Roadrunner-M (autonomous interceptor), ALTIUS-600M (loitering munition), Fury (strike drone), YFQ-44A (Collaborative Combat Aircraft), Sentry Tower (border surveillance), Dive-LD (underwater UUV), and Arsenal-1 (autonomous weapons manufacturing facility).
- Customers
- U.S. Department of Defense, Customs and Border Protection, SOCOM, U.S. military branches, and allied governments seeking autonomous systems, counter-drone, C2, and defense AI capabilities.
- Business model
- Government defense contracting model combining multi-year program awards, OTA and IDIQ vehicles, hardware systems, and Lattice OS software integration.
- Stage
- late-stage-private
- Funding status
- $11.2B+ raised; $1.5B Series F in August 2024 at $14B post-money, a $2.5B Series G in June 2025 at $30.5B, and a $5B Series H in 2026 at $61B.
Executive summary
Top strengths
- Vertically integrated autonomous weapons platform (Lattice OS + hardware) with no direct peer
- Deep, privileged DoD relationships: SOCOM, CBP, US Army, Air Force, Navy, Space Force, AUKUS
- First-mover moat: Lattice OS deployed across active operations with high switching costs
- Series H at $5B and $61B post-money underscores scarce capital access
- Exceptional founder/CEO team (Palmer Luckey + Brian Schimpf) with government trust and technical credibility
- Structural alignment with $2.2T+ global defense market growing at 7-9% annually
- Replicator and CCA programs represent $5-15B potential program value pipelines
Top risks
- LAWS/CCW treaty risk: binding autonomous weapons restrictions could impair autonomous strike product line
- CCA competition loss to General Atomics: binary outcome with $5-8B valuation impact
- Hardware multiple repricing at IPO: if gross margins reveal hardware-heavy structure, multiple compresses from 23x to 4-5x
- Customer concentration: 3-4 programs (~60-70% revenue) create program-cancellation binary risk
- Capital gap risk: $1.2-1.8B annual burn still requires disciplined execution despite the Series H windfall; market downturn could create funding pressure
- ITAR enforcement exposure: international expansion (AUKUS+) increases compliance complexity and penalty risk
Open gaps
- GAAP financials not disclosed: gross margin, EBITDA, revenue recognition policy, and free cash flow are unavailable; all valuation metrics rely on estimated ARR
- Cap table waterfall unknown: liquidation preferences, anti-dilution ratchets, and participation rights for each round are not public; common stock value at IPO cannot be precisely assessed
- Lattice OS segment revenue not broken out: the software/hardware revenue split that drives multiple is unconfirmed
- No public legal proceedings disclosure: material legal risks (ITAR investigations, DDTC audits, contract disputes) may exist but are not detectable from public sources
Contents
01Company Overview
1.1 Identity and Positioning
Anduril is best understood as a defense technology company that tries to package software, sensors, and autonomous hardware into a single operating system for military and border-security customers. That positioning matters because it is broader than a point-solution drone vendor and narrower than a traditional prime contractor. The business model is anchored in government programs and long sales cycles, but the product story is easier to follow than a typical defense supplier because Lattice, autonomy, and hardware show up as a coherent platform. The company's external messaging consistently emphasizes U.S. and allied missions, which keeps the product set tied to procurement rather than consumer demand.[CO001, CO009, CO010]
| Metric | Value | Evidence |
|---|---|---|
| Founded | 2017 | Company and third-party profile sources |
| Headquarters | Costa Mesa, California | Company and state expansion sources |
| Latest implied valuation | $61B | 2026 Series H and related public coverage |
| Total capital raised | $11.2B+ | Series F plus 2025/2026 rounds |
| Employees | 7,000+ | Public coverage and company hiring footprint |
| Disclosure profile | Private, undisclosed | No public audited financials or cap table |
Headline snapshot uses public sources and derived totals; where the company does not disclose audited numbers, the table intentionally uses the broadest supportable public estimate.
[CO001, CO006, CO007, CO011]Six key milestones from founding through the 2026 Series H and expansion cycle.
2017 founding [CO001]
2019 early deployment [CO010]
2024 Series F [CO004]
2025 valuation step-up [CO005]
2026 Series H [CO006]
2026 expansion [CO008]
1.2 Founders, Leadership, and Control
The founding team combines product credibility, operating discipline, and political signaling. Palmer Luckey remains the public brand face, Brian Schimpf runs the company, and the broader founding group still matters because it links Anduril to Oculus, Palantir, and Founders Fund. That mix helps the company recruit both hardware engineers and software talent while also giving it a narrative that resonates with defense buyers. The main governance question is not whether the founders are visible, but how much of the business remains dependent on a small number of people to win programs, maintain trust, and keep the product cadence moving.[CO002, CO003]
| Person | Role | Background | Strategic importance | Key-person risk |
|---|---|---|---|---|
| Palmer Luckey | Founder / public face | Oculus founder and defense-tech advocate | Brand, mission, external trust | High |
| Brian Schimpf | CEO and co-founder | Runs day-to-day operations | Program delivery and operating cadence | High |
| Trae Stephens | Co-founder / chairman role | Defense investor and operator network | Capital and governance relationships | Medium |
| Matt Grimm | Co-founder | Operations and scaling background | Manufacturing and delivery | Medium |
| Joseph Chen | Co-founder | Technical and product background | Systems and software depth | Medium |
Publicly visible leadership is stable, but the company remains founder-led and therefore still somewhat key-person dependent.
[CO002, CO003]1.3 Funding, Scale, and Milestones
The company's financing path shows clear late-stage scale: a $14B Series F in 2024, a public jump above $30B in 2025, and a $5B Series H in 2026. The new round is the strongest current signal that investors still see room for Anduril to compound into a much larger defense platform. At the same time, the company's growing headcount and Southern California expansion show that capital is being converted into manufacturing, engineering, and program capacity rather than sitting idle. The milestone pattern is therefore a mix of product launches, capital raises, and physical expansion at scale.[CO004, CO005, CO006, CO007, CO008, CO012]
| Stakeholder | Role | Strategic value | Diligence ask |
|---|---|---|---|
| Founders Fund | Lead investor / strategic backer | Deep defense-tech network | Confirm board influence and secondary participation |
| a16z | Growth-stage investor | Talent and platform reach | Clarify follow-on support and valuation discipline |
| 8VC | Defense-tech investor | Operator network and policy access | Confirm current ownership and governance role |
| General Catalyst | Growth investor | Capital and scaling expertise | Check liquidation preferences and ratchets |
| Sands Capital | Series F / growth investor | Long-horizon capital | Confirm post-Series H position and support |
Public investor map is incomplete because exact ownership percentages and board seats are not disclosed.
[CO004, CO005, CO006, CO008]02Market Analysis
2.1 Market Boundary and Buyer Set
Anduril sits in a market that blends defense modernization, autonomy, and command-and-control. The real boundary is not whether the company sells hardware or software, but whether a buyer wants a faster sensor-to-shooter loop and is willing to buy that capability as an integrated program. That framing captures why the company can sell across air, land, sea, and border-security missions without looking like a traditional narrow-point vendor. It also explains why primes, internal government builds, and adjacent software vendors remain relevant substitutes even when Anduril has a strong technology narrative.[CM001, CM002, CM006]
| Segment | Included spend | Excluded spend | Buyer / payer |
|---|---|---|---|
| Autonomy and counter-UAS | ISR, strike, counter-drone, and autonomous control | Consumer drones and unrelated robotics | Defense and homeland-security buyers |
| Sensor-to-shooter software | Command, control, and fusion software | Generic enterprise software | Military program offices |
| Border and perimeter security | Sensing, towers, and integrated response tools | Physical infrastructure with no software layer | Homeland-security agencies |
| Allied defense autonomy | Exportable allied programs and integrations | Unlicensed markets or banned end uses | Allied ministries and primes |
This table intentionally excludes broad defense spend that is unrelated to autonomy or command-and-control software.
[CM001, CM002, CM005]A bottom-up view of the market from broad defense budgets to the smaller subset that Anduril can realistically win.
Layer widths indicate hierarchy, not quantitative proportions.
Defense / homeland-security budgets [CM003]
Autonomy / counter-UAS spend [CM005]
Programs with software integration [CM001, CM009]
Near-term addressable wins [CM004, CM010]
2.2 Sizing Lenses and Growth Drivers
Budget ownership is primarily with defense and homeland-security organizations, plus allied ministries that can buy similar capabilities. The market is attractive because the budget pools are large and the geopolitical backdrop remains supportive, but procurement, export, and security requirements slow conversion from interest to revenue. That combination makes adoption path analysis more important than a single top-down TAM number. In practice, the company wins by tying autonomy to mission outcomes and then expanding across adjacent programs once buyers trust the deployment.[CM003, CM004, CM005, CM010, CM011]
| Lens | Approximate value | Method | Limitation |
|---|---|---|---|
| Global autonomy/counter-UAS demand | $20B-$30B annual range | Directional public-market synthesis | Classified programs not fully visible |
| U.S. near-term addressable spend | High single-digit billions | Defense budget and procurement lens | Program timing uncertain |
| Allied defense autonomy spend | Multi-billion annual adjacency | Exportable allied programs | Policy/export restrictions |
| Anduril reachable share | Too early to pin precisely | Bottom-up from wins and integrations | Depends on execution and trust |
Sizing is directional rather than exact because public budgets mix autonomy with other defense categories.
[CM003, CM004, CM005, CM011]2.3 Adoption Constraints and Momentum Signals
Anduril's hiring and partnership signals show a market still in build mode. The company continues to add technical talent, manufacturing capacity, and customer-facing support, while the General Dynamics relationship shows that ground-force modernization remains an important adjacency. At the same time, the market remains hard to size precisely because many program budgets are fragmented or partially classified. The result is a market that looks large and durable, but one where the pace of adoption is still constrained by institutions rather than by product desirability alone. Procurement timing matters because the strongest market signals do not turn into revenue on the same schedule as software. Buyers may want autonomy immediately, yet they still have to align budgets, test reliability, and often pilot the system before full deployment. That lag is what keeps the market attractive but not frictionless.[CM007, CM008, CM009, CM012]
| Segment | Buyer / user / payer | Adoption trigger | Notes |
|---|---|---|---|
| DoD program office | Buyer and payer | Mission failure or modernization need | Large but slow buying cycle |
| DHS / CBP | Buyer and operator | Border or perimeter security pressure | Visible public-facing use case |
| Allied ministry | Buyer / payer | Interoperable autonomy need | Export and compliance gates |
| Prime contractor partner | Integrator / channel | Need to add autonomy to legacy systems | Can extend distribution |
| Internal build team | Potential substitute | Want to avoid vendor dependence | Important competitive pressure |
The table maps the customer and substitute set because buyer identity materially changes adoption speed.
[CM002, CM004, CM006, CM008]03Competitors
3.1 Competitor Landscape
The competitive set is broad because Anduril is not just selling one product. In any given deal, it can run into a prime contractor, a software platform, a specialized autonomy startup, or an internal government team trying to build the same thing. That breadth matters because the company's best argument is integration: one stack across sensing, autonomy, and command-and-control. It is also a reminder that Anduril does not have the luxury of a simple named-peer comparison; it must win across several different buying criteria at once.[CP001, CP002, CP003, CP004]
| Competitor | Category | Scale / funding | Target segment | Limitation |
|---|---|---|---|---|
| General Atomics | Prime competitor | Large, established | CCA / autonomous aircraft | Legacy prime stack |
| Shield AI | Startup peer | Well-funded | Autonomy and aircraft | Narrower product breadth |
| Palantir | Adjacent software | Large public company | C2 and data fusion | No hardware manufacturing |
| AeroVironment | Drone incumbent | Public defense contractor | Small UAS and loitering systems | Less integrated platform |
| Lockheed Martin | Prime incumbent | Very large public company | Air, space, and missile programs | Slower software cadence |
Peer set mixes direct product rivals with adjacent software and status-quo incumbents because buyers compare across categories.
[CP001, CP002, CP003, CP004, CP005]A qualitative map of scale versus software integration for the most relevant competitors and substitutes.
| Item | X (5–9) | Y (3–8) | Context |
|---|---|---|---|
| 1. Anduril | 8 | 8 | integrated stack |
| 2. General Atomics | 9 | 5 | prime-scale autonomy |
| 3. Shield AI | 6 | 8 | startup autonomy |
| 4. Palantir | 7 | 7 | software adjacency |
| 5. AeroVironment | 7 | 4 | incumbent drone vendor |
| 6. Internal build | 5 | 3 | status quo substitute |
General Atomics [CP002, CP005]
Shield AI [CP003]
Palantir [CP004]
AeroVironment [CP001]
Internal build [CP012]
3.2 Scale, Trust, and Distribution
Scale and trust still favor the biggest incumbents. Legacy primes bring manufacturing depth, certification experience, and long-standing procurement relationships, while startups like Shield AI can be faster or more focused in a narrower slice of autonomy. Anduril tries to sit between those extremes by pairing startup velocity with prime-like delivery. That is a useful position, but it also means the company has to keep proving that its integration layer and software cadence are durable enough to keep larger buyers from simply stitching together their own stack.[CP005, CP008, CP010]
| Buying criterion | Anduril | Prime incumbent | Autonomy startup | Internal build |
|---|---|---|---|---|
| Integrated stack | Strong | Moderate | Moderate | Weak |
| Manufacturing scale | Growing | Strong | Weak | Weak |
| Software cadence | Strong | Weak-to-moderate | Strong | Variable |
| Procurement trust | Growing | Strong | Mixed | Strong |
Ordinal ratings are directional and based on public evidence, not on a formal scored model.
[CP005, CP006, CP007, CP011]3.3 Moat Durability and Price Power
The strongest moat evidence is not a single benchmark score; it is the fact that Anduril keeps showing up in broader partnership and ecosystem conversations. Lattice SDK, prime-adjacent partnerships, and the continued hiring push all suggest a company trying to make its software hard to replace once deployed. But the same market structure that helps Anduril also gives buyers options. Multi-homing remains possible, pricing is usually opaque, and defense buyers can still fall back to status quo suppliers or build in-house if the product path disappoints. This is why the company's moat is best judged as a moving target: every program win can strengthen switching costs, but every competitor can also learn from the last contract and push the comparison back toward price, reliability, and procurement trust. today.[CP006, CP007, CP009, CP011, CP012]
| Model | Anduril position | Competitor pattern | Implication |
|---|---|---|---|
| Platform bundle | Hardware plus software bundle | Often program-specific | Hard to compare list prices |
| Software add-on | Lattice-like integration layer | Standalone software less common | Higher switching cost |
| Program pricing | Bid / award specific | Prime-style negotiated pricing | Opaque margins |
| Support / services | Operational support included | Varies widely | Can hide true unit economics |
Public price lists are generally unavailable, so the table reflects program-level packaging norms rather than a single list price.
[CP006, CP009, CP011]04Financials
4.1 Revenue Streams and Monetization
Anduril's money appears to come from a familiar defense stack: government programs, bundled systems, and recurring support around deployed platforms. That makes the revenue base more durable than a one-off prototype shop, but it also means that line-item pricing is often hidden inside program awards and contract modifications. The company can therefore look like a platform business while still being reported as a set of program wins rather than a clean software subscription model. That distinction is the core reason the financial story is both compelling and hard to benchmark.[CI001, CI002, CI003, CI013]
| Stream | Mechanism | Quality | Diligence ask |
|---|---|---|---|
| Program awards | Government contracts and task orders | High | Clarify backlog and renewal profile |
| Bundled systems | Hardware plus software packages | High | Split software vs hardware attach |
| Support / services | Training, maintenance, and integration | Medium | Quantify recurring portion |
| Partnership programs | Prime-adjacent joint programs | Medium | Map channel economics |
Public revenue is inferred from contracts and product launches because audited statements are not public.
[CI001, CI003, CI013]A qualitative bridge from visible program revenue to the capital required to keep scaling the business.
| Item | Value | Context |
|---|---|---|
| Program revenue | 1000 publicly inferred revenue base | publicly inferred revenue base |
| Software attach | 200 margin upside if reuse expands | margin upside if reuse expands |
| Labor / support cost | -350 headcount and field support burden | headcount and field support burden |
| Manufacturing capex | -250 scale-up investment | scale-up investment |
| Other overhead | -150 program and corporate costs | program and corporate costs |
| Net capital need | 450 continuing funding requirement | continuing funding requirement |
Program revenue [CI001, CI003]
Software attach [CI009]
Labor / support cost [CI007]
Manufacturing capex [CI008]
Other overhead [CI006]
4.2 Margins, Cost Structure, and Capital
Pricing and packaging are mostly program-specific, which is normal for defense but frustrating for investors. Lattice-like software may be embedded inside larger hardware and support bundles, so the visible price on a contract is not the same as the true software attach rate. That creates a margin story that can improve materially if the same software is reused across more deployments, but it also means the company has to prove that repeatability exists. Without that proof, the financial profile can still look like a high-growth hardware business with some software upside rather than a software company with hardware around the edges.[CI006, CI007, CI008, CI009, CI010]
| Item | Public price visibility | Likely model | Implication |
|---|---|---|---|
| Lattice / software | Low | Bundled into programs | Software margin hidden |
| Vehicles / hardware | Low | Program-specific pricing | Unit economics vary |
| Support and training | Low | Service add-on | Can improve recurring mix |
| Partnership deployments | Low | Negotiated per program | Distribution leverage matters |
All pricing is private or program-specific, so the table focuses on model rather than list price.
[CI002, CI009]4.3 Valuation and Financial Verdict
The capital picture is strong but not simple. The 2026 Series H gives Anduril a much larger cushion, yet the company still has to fund labor, manufacturing, and customer support while building a durable margin structure. Because audited financials are not public, every view on runway or profitability is necessarily approximate. That is why the current valuation remains a diligence test: it is plausible if growth stays fast and margins improve, but it is vulnerable if execution slows or if the business proves more hardware-heavy than the market wants. Investors should therefore treat the valuation as a claim on future execution, not as proof that current disclosures already support it. That makes diligence on margins and backlog especially important.[CI004, CI005, CI011, CI012]
| Metric | Current visibility | Why it matters | What closes the gap |
|---|---|---|---|
| Revenue growth | Partial | Shows scale-up speed | Audited financials |
| Gross margin | Not public | Tells software vs hardware mix | Segment disclosure |
| Cash and runway | Not public | Sets financing risk | Balance-sheet disclosure |
| Debt / credit | Not public | Affects leverage risk | Debt covenant disclosure |
| Backlog | Not public | Reveals contracted demand | Customer or IPO disclosure |
The table is intentionally partial because the company does not disclose the underlying statements needed for precision.
[CI006, CI008, CI010, CI012]05Product & Technology
5.1 Product Definition and Workflow
Anduril's product story is easiest to understand as a workflow: detect, decide, and act with software and hardware in the same loop. Lattice sits in the middle, but the company's public product pages make clear that this is not a pure software vendor. The stack spans autonomous aircraft, undersea systems, sensors, and border-security infrastructure, which means the real product is an integrated system rather than any one SKU. That integrated framing matters because it explains why the company keeps selling into mission programs instead of trying to win through a standalone app layer. That is why public product demos alone are not enough.[CE001, CE003, CE010]
| Module / asset | Customer job | Maturity | Diligence gap |
|---|---|---|---|
| Ghost | Persistent ISR and surveillance | Operational | Field reliability data |
| Roadrunner | Counter-air and intercept | Operational / scaling | Unit cost and sortie economics |
| Dive-LD | Undersea autonomy | Early operational | Deployment tempo and support burden |
| Lattice SDK | Integration layer | Platform | Attach rate and third-party use |
The table focuses on the most visible public product lines rather than the entire classified portfolio.
[CE001, CE002, CE003]A layered view of the company's product system from sensors and autonomy to support and manufacturing.
- Support and training
- keeps programs fielded
- Manufacturing and supply chain
- builds the systems
- Command and control
- Lattice and mission software
- Autonomy and sensors
- decision and perception layer
- Mission hardware
- vehicles and towers
- Mission data and analytics
- turns deployments into learning loops
5.2 Modules, Assets, and Architecture
The module map shows how broad the stack has become. Ghost, Roadrunner, Dive-LD, Fury, Sentry, and Lattice SDK are not interchangeable products; they are different slices of the same mission architecture. That breadth creates a stronger story for cross-sell and reuse, but it also makes the company responsible for more of the operational burden. If the field system fails, the software story fails with it. If the manufacturing pipeline slips, the autonomy story loses credibility. Product breadth therefore strengthens the platform narrative only if execution stays tight.[CE002, CE004, CE011]
| User job | Current workflow | Anduril role | Limitation |
|---|---|---|---|
| Find the target | Sensor fusion and tracking | Decision support | Depends on data quality |
| Launch the asset | Human or semi-autonomous control | Autonomy layer | Rules of engagement matter |
| Coordinate the mission | Separate command systems | Lattice integration | Integration effort remains high |
| Sustain operations | Manual support and maintenance | Operational support | Field uptime must prove out |
Workflow rows are intentionally operational because the company sells into mission environments, not consumer use cases.
[CE003, CE004, CE010]5.3 Differentiation and Controls
Differentiation comes from a mix of integration, IP, manufacturing, and support. The company can point to partner integrations and the General Dynamics relationship as evidence that it wants to own more of the operating layer, not just the point product. But the same breadth makes margin analysis harder and raises the bar on trust, safety, privacy, and compliance. In practice, the moat is not a single technical feature; it is the ability to keep shipping operational systems that customers can actually field and sustain over time. The strategic risk is that this operational moat only stays valuable if the product keeps getting easier to deploy across different missions without turning into a bespoke services business.[CE005, CE006, CE007, CE008, CE009, CE012]
| Layer | Role | Dependency | Risk |
|---|---|---|---|
| Sensor layer | Collects mission data | Hardware / feeds | Data quality |
| Autonomy layer | Decision and routing | Model performance | Safety / compliance |
| Command layer | Operator interface | Network integration | Security / uptime |
| Manufacturing layer | Builds the system | Supply chain | Lead times |
| Support layer | Keeps it fielded | Customer operations | Sustainability |
The architecture table intentionally separates software from manufacturing because the business combines both into one operating model.
[CE003, CE005, CE011, CE012]06Customers
6.1 Customer Segments
Anduril's customer base is concentrated in defense and homeland-security channels. The company sells to agencies that care about mission performance, security, and procurement reliability more than about consumer UX or self-service conversion. That means customer segmentation has to be read through the lens of buyer, user, and payer, not through a classic SaaS funnel. The visible footprint also suggests a company that grows by landing one program and then using that deployment to open the next adjacent program. That makes the market feel concentrated even when the public story shows many different agencies and partners. The same handful of program offices can therefore shape most of the company's visible growth path.[CU001, CU005, CU009]
| Segment | Buyer / user / payer | Scale / value | Gap |
|---|---|---|---|
| U.S. defense agencies | Buyer and payer | Largest visible budget pool | Exact account split unknown |
| Homeland-security agencies | Buyer and operator | Border / perimeter missions | Program-level detail limited |
| Allied ministries | Buyer and payer | Exportable growth channel | Policy and export constraints |
| Prime partners | Integrator / channel | Distribution lever | Indirect customer exposure |
The table is intentionally broad because public evidence reveals categories more clearly than named account lists.
[CU001, CU005, CU006]A simplified customer journey from first pilot to repeat program expansion.
[CU001, CU002, CU003, CU004, CU005, CU010]6.2 Adoption Trajectory
Adoption signals are strongest when a program moves from proof-of-concept language to production or scale language. Public materials around surge capacity and manufacturing indicate that Anduril has at least some customers willing to treat the company as a real delivery partner rather than a one-off prototype vendor. That matters because it suggests the company can create repeatable use cases, but it does not reveal how many accounts are actually active. The public story is therefore stronger on movement than on denominators.[CU002, CU008, CU010]
| Metric | Current evidence | Why it matters | What is missing |
|---|---|---|---|
| Program transition | Pilot to production language | Shows adoption depth | Exact count of live programs |
| Manufacturing pace | Surge-capacity and scale messaging | Signals repeat demand | Unit volumes by program |
| Hiring pace | Ongoing talent growth | Supports scale-up | True headcount / org chart |
| Partner expansion | Prime-adjacent relationships | Opens distribution | Contract-level revenue split |
The table uses adoption proxies because customer-level operating metrics are not public.
[CU002, CU008, CU010]6.3 Named Proof and Durability
The customer story is compelling but incomplete. Named partnerships, production language, and hiring all support a land-and-expand interpretation, yet the public record still leaves retention, renewal, and concentration data hidden. For an investor, that means the key question is durability: can a small number of large government relationships keep expanding, or will the company have to keep re-earning every program from scratch? The answer is likely somewhere in the middle, which is exactly why concentration and repeat-buy evidence matter so much. For diligence, that means a single strong proof point is not enough. Investors need to know whether the same account can keep expanding or whether every new win requires a fresh procurement cycle and a new round of persuasion.[CU003, CU004, CU006, CU007, CU011, CU012]
| Customer / partner | Type of proof | Production vs pilot | Limitation |
|---|---|---|---|
| Everfox partnership | Cross-domain partnership | Production-style relationship | No revenue disclosure |
| Surge capacity example | Manufacturing proof | Operational scale | Single-case evidence |
| General Dynamics partnership | Ground-force collaboration | Program-facing | Exact contract economics unknown |
Named proof is a mix of customer-facing and partner evidence because direct customer references are not always public.
[CU003, CU004, CU006, CU010]07Risks
7.1 Risk Ranking
Anduril's risk stack is what you would expect from a company sitting between defense tech and public policy. The company has to move quickly enough to win programs, but it also has to satisfy procurement, security, and compliance expectations that are much stricter than those faced by a typical software startup. That creates a risk profile where the same thing that makes the company attractive — autonomous systems deployed into sensitive missions — also makes it easy to attract scrutiny whenever something goes wrong or looks controversial. In that sense, risk is built into the business model, not an external add-on.[CR001, CR008, CR011]
| Risk | Jurisdiction / setting | Likelihood | Severity | Mitigation | Residual exposure |
|---|---|---|---|---|---|
| Export / procurement scrutiny | U.S. and allies | Medium | High | Compliance program and legal review | Medium |
| Public criticism / policy backlash | U.S. public sphere | Medium | Medium | Narrative discipline and customer focus | Medium |
| Audit or enforcement visibility | Unknown / private company | Low | High | No public disclosure available | High |
The register is ordered by severity and intentionally distinguishes public criticism from formal enforcement.
[CR002, CR006, CR008]A qualitative heatmap of likelihood versus impact for the main risk categories.
[CR001, CR002, CR003, CR004, CR005, CR006, CR012]7.2 Regulatory and Operational Risk
Regulatory and legal risk sit at the top because they can create sudden downside without warning. Public criticism around border security shows that the company's work can become a political issue, while the defense setting keeps privacy, export, and safety questions alive all the time. The operational layer is nearly as important: hardware programs can slip, supply chains can tighten, and support burdens can rise exactly when the company is trying to scale. Those are the kinds of failures that can turn a strong sales story into a delivery problem very quickly.[CR002, CR003, CR006, CR007, CR010]
| Failure mode | Likelihood | Severity | Mitigation maturity | Residual exposure |
|---|---|---|---|---|
| Manufacturing slippage | Medium | High | Medium | Medium |
| Support or uptime failure | Medium | High | Medium | Medium |
| Security / privacy incident | Low-to-medium | High | Medium | Medium |
| Supply chain disruption | Medium | Medium | Medium | Medium |
Operational risk is high because hardware programs and field support are part of the product itself.
[CR003, CR007, CR010]7.3 Partner, Financial, and Thesis Break Risk
Partner and capital risks are the subtler version of the same problem. Anduril relies on allies, primes, and program partners to broaden reach, which helps distribution but also creates dependency. The 2026 financing round buys time, but it does not remove the need for disciplined execution or a cleaner disclosure story. Investors should therefore watch for warnings in contract cadence, hiring, program deliveries, and public criticism rather than waiting for a single headline event. The thesis weakens when multiple small failures line up at once. Put differently, the company can survive any one of these risks, but investors should worry if several of them worsen together during the same budget cycle.[CR004, CR005, CR009, CR012]
| Dependency | Counterparty / setting | Failure scenario | Residual exposure |
|---|---|---|---|
| Prime channel | Prime contractors | Distribution squeeze or margin pressure | Medium |
| Allied programs | Allied ministries | Policy delay or export restriction | Medium |
| Capital provider | Private market | Funding pressure if growth slows | Medium |
| Customer concentration | A few large programs | Program cancellation or delay | High |
Partner and concentration risks are elevated because the company relies on a small number of large defense relationships.
[CR004, CR005, CR011]08Valuation
8.1 Current Price Context
Anduril's valuation now has a much higher anchor than it did in the last funding cycle. The 2026 Series H sets a new price point, but the real question for investors is whether the company can keep compounding fast enough to make the number feel conservative in hindsight. Because the business is still private, the market is pricing a story rather than a fully disclosed financial profile. That makes the valuation debate more dependent on the quality of the growth narrative than on a clean public model. The market is likely to keep rewarding proof, not promises. for now, at least.[CV001, CV002, CV011]
| Recommendation | Confidence | Risk rating | Valuation stance | Decision implication |
|---|---|---|---|---|
| Track | Medium | High | Stretched | Watch execution and disclosure |
| Do not chase | Medium | High | Stretched | Wait for more proof |
| Potential re-rate | Medium | High | Unknown | If margins and growth hold |
This is a judgment table, not a formal model output.
[CV004, CV005, CV010]A decision chain from scale and proof to the final valuation recommendation.
| Node / Connection | Node / from | To | Context |
|---|---|---|---|
| Node 1 | Scale is real | Series H and expansion prove access to capital | |
| Node 2 | Proof is incomplete | private disclosures remain thin | |
| Node 3 | Margins must improve | hardware mix still clouds returns | |
| Node 4 | Exit is possible | but not yet cleanly priced | |
| Node 5 | Recommendation: track | watch until disclosure catches up | |
| Node 6 | Break trigger | slower growth or weaker margins |
Proof is incomplete [CV003, CV011]
Margins must improve [CV005, CV008]
Exit is possible [CV010]
Recommendation: track [CV004]
Break trigger [CV012]
8.2 Recommendation and Stance
The recommendation stays cautious because the company has to clear multiple hurdles at once: more revenue, better margins, and better disclosure. In other words, the current price is not obviously wrong, but it is far too rich to ignore the evidence gaps. That is why the correct stance is to track the company rather than to assume the market has already solved the pricing problem. If the company can show operating leverage and repeatability, the valuation can be defended; if not, the multiple will feel stretched very quickly.[CV003, CV004, CV005, CV010, CV012]
| Argument | What would change the view |
|---|---|
| Thesis: growth and scale can justify the price | A slowdown or weaker margins would break it |
| Thesis: software attach can lift the multiple | No proof of attach or reuse would weaken it |
| Anti-thesis: public disclosure remains thin | An IPO-style filing would reduce the discount |
| Anti-thesis: capital intensity could stay high | A better cash-flow profile would ease concern |
The table pairs the investment story with the evidence that would most change the view.
[CV003, CV005, CV006, CV008, CV011]8.3 Scenarios and Exit Readiness
Scenario analysis helps because valuation here is less about one exact number and more about a range of outcomes. The bull case assumes fast program growth and software reuse; the base case assumes continued expansion but with a disclosure discount; the bear case assumes slower growth or a hardware-heavy mix. Comparable references are useful only as anchors, not as precise formulas, because the company is still private and still operating with more opacity than a public defense contractor. That is why exit readiness matters so much. The important point is that the market still has to decide whether Anduril is a rare defense platform or merely a very well-funded private contractor.[CV006, CV007, CV008, CV009]
| Scenario | Assumptions | Valuation / return logic | Key risk |
|---|---|---|---|
| Bull | Growth stays fast; margins improve | Multiple expands on stronger proof | Execution misses |
| Base | Growth continues; disclosure stays opaque | Current price roughly fair to slightly stretched | No clean re-rate |
| Bear | Growth slows; mix stays hardware-heavy | Multiple compresses | Funding or margin surprise |
| Exit | Public disclosure closes gap | IPO or similar liquidity event | Timing risk |
Scenarios are qualitative and intended to frame the diligence decision, not to provide a precise DCF.
[CV006, CV007, CV008, CV010, CV012]Disclaimer
This report is a public-evidence diligence snapshot, not investment advice. Important financial, legal, technical, and contractual facts remain non-public and should be verified directly with management and primary documents before any investment decision.
Evidence index
| ID | Statement | Confidence | Sources |
|---|---|---|---|
| CO001 | Anduril Industries is a late-stage private defense technology company founded in 2017 and headquartered in Costa Mesa, California. | High | SO001, SO007 |
| CO002 | The company was founded by Palmer Luckey, Brian Schimpf, Matt Grimm, Trae Stephens, and Joseph Chen. | High | SO002, SO005 |
| CO003 | Brian Schimpf serves as chief executive and Palmer Luckey remains a visible strategic founder. | Medium | SO002, SO005 |
| CO004 | Anduril closed a $1.5B Series F in 2024 at a $14B post-money valuation. | High | SO006, SO008 |
| CO005 | Public reporting in 2025 placed Anduril above a $30B valuation before the 2026 round. | Medium | SO005, SO006 |
| CO006 | Anduril announced a $5B Series H in 2026 and described it as a major capitalization event. | High | SO001, SO008 |
| CO007 | The company now presents itself as roughly a 7,000-person organization with a broad Southern California footprint. | Medium | SO003, SO004 |
| CO008 | Anduril is expanding its California campus footprint with a $1B investment and a new Long Beach/Lakewood site. | High | SO003, SO008 |
| CO009 | The company sells a bundled defense platform spanning Lattice software, autonomous vehicles, sensors, and related hardware. | High | SO007, SO005 |
| CO010 | Anduril's stated customer focus remains the U.S. military, border security, and allied governments. | High | SO007, SO001 |
| CO011 | The company remains private and does not disclose audited financial statements or a public cap table. | Medium | SO001, SO005 |
| CO012 | Anduril's milestone path shows a transition from startup formation to multi-program defense platform. | Medium | SO001, SO003, SO008 |
| CM001 | Anduril competes in the defense-autonomy market, not a consumer or enterprise SaaS market. | High | SM004, SM007 |
| CM002 | The main buyers are U.S. defense agencies, border-security agencies, and allied ministries. | High | SM004, SM006 |
| CM003 | Demand is being pulled by drone warfare, counter-drone needs, and faster sensor-to-shooter cycles. | Medium | SM003, SM005, SM006 |
| CM004 | Procurement cycles, security requirements, and export controls slow adoption even when the product is compelling. | Medium | SM003, SM004 |
| CM005 | The addressable spend is fragmented across autonomous systems, counter-UAS, sensors, and command software. | Medium | SM003, SM007 |
| CM006 | Legacy primes and in-house government builds remain meaningful substitutes for Anduril. | Medium | SM003, SM004 |
| CM007 | Anduril's hiring footprint suggests continued investment in autonomy, manufacturing, and field support. | Medium | SM001, SM002, SM008 |
| CM008 | The General Dynamics partnership expands the company's relevance to ground-force modernization programs. | Medium | SM006 |
| CM009 | Lattice SDK signals that Anduril wants a broader ecosystem rather than isolated point products. | Medium | SM007 |
| CM010 | The market is attractive because the budget pools are large, but timing is gated by policy and procurement. | Medium | SM003, SM004 |
| CM011 | Public reporting still leaves the exact TAM, SAM, and SOM highly uncertain. | Medium | SM003, SM004 |
| CM012 | The market can absorb more autonomy spending, but only if buyers trust reliability and mission performance. | Medium | SM004, SM006, SM007 |
| CP001 | Anduril competes against traditional primes, autonomy startups, and internal government builds rather than a single clean peer set. | Medium | SP001, SP004 |
| CP002 | General Atomics is one of the most important direct rivals in autonomous aircraft and CCA-style programs. | Medium | SP003, SP005 |
| CP003 | Shield AI and similar autonomy startups compete on software depth and pilotless aircraft narratives. | Medium | SP001, SP003 |
| CP004 | Palantir is an adjacent software competitor in command-and-control, even if it is not a hardware peer. | Medium | SP001, SP004 |
| CP005 | Legacy primes still win on scale, trust, certification, and procurement muscle. | Medium | SP003, SP004 |
| CP006 | Anduril's software stack and Lattice SDK are meant to create switching costs inside customer programs. | High | SP004, SP008 |
| CP007 | Multi-homing is possible because defense buyers can pair primes, software vendors, and specialty autonomy vendors. | Medium | SP001, SP003 |
| CP008 | Anduril's distribution improves when it can sell through or alongside prime contractor programs. | Medium | SP007, SP004 |
| CP009 | Public pricing is mostly opaque and program-specific rather than a standardized list price. | Medium | SP001, SP003 |
| CP010 | The company's latest partnership cycle suggests it is trying to broaden the competitive field beyond point products. | Medium | SP006, SP007 |
| CP011 | Competitive advantage depends on execution speed, manufacturing reliability, and customer trust rather than technology alone. | Medium | SP004, SP005, SP008 |
| CP012 | The clearest adverse evidence is that defense buyers can still choose status quo suppliers or build internally. | Medium | SP001, SP003 |
| CI001 | Anduril appears to make most of its money from government programs and bundled defense systems rather than consumer subscriptions. | Medium | SI005, SI006 |
| CI002 | The company bundles software, hardware, and support into program-specific pricing rather than a public list price. | Medium | SI005, SI007 |
| CI003 | Public evidence suggests revenue quality is high because counterparty risk sits with government buyers. | Medium | SI006, SI005 |
| CI004 | The 2026 Series H added $5B of capital and reset the company's current valuation context around $61B. | Medium | SI003 |
| CI005 | Cumulative public funding now exceeds $11B when prior rounds are added to the 2026 Series H. | Medium | SI001, SI003 |
| CI006 | Operating leverage remains unclear because the company does not publish GAAP statements or segment margins. | Medium | SI001, SI002 |
| CI007 | Labor, manufacturing, and field support are likely the largest cost drivers as the organization scales. | Medium | SI004, SI006 |
| CI008 | The capital base is large enough to support additional scale-up, but it does not eliminate execution risk. | Medium | SI003, SI004 |
| CI009 | Software attach and platform reuse could improve blended margins if program wins scale into repeatable deployments. | Medium | SI007, SI006 |
| CI010 | Debt and credit obligations are not disclosed publicly, so balance-sheet leverage is difficult to size. | Medium | SI001, SI002 |
| CI011 | The company's valuation remains rich relative to the disclosure it provides on revenue and margin quality. | Medium | SI001, SI003 |
| CI012 | A financial verdict still depends on whether growth can outpace capital intensity long enough to justify the current price. | Medium | SI001, SI003, SI007 |
| CI013 | Public reporting and contract-based inference place Anduril's current annual revenue run rate around $1.25B. | Medium | SI001, SI002 |
| CE001 | Anduril's product stack combines Lattice software with autonomous air, land, sea, and border systems. | High | SE003, SE006 |
| CE002 | The visible module set includes Ghost, Roadrunner, Dive-LD, Fury, Sentry, and Lattice SDK. | High | SE003, SE004, SE006 |
| CE003 | The architecture links sensors, autonomy, and mission software into one operational workflow. | Medium | SE003, SE004 |
| CE004 | Deployment depends on integration with customer networks, mission data, and field support. | Medium | SE004, SE005 |
| CE005 | Anduril differentiates itself through system integration and manufacturing know-how more than through a single point feature. | Medium | SE001, SE003 |
| CE006 | Trust, safety, privacy, and compliance are core product requirements because the company works in defense. | High | SE004, SE006 |
| CE007 | The roadmap appears to extend the product into partner integrations and broader mission workflows. | Medium | SE007, SE008 |
| CE008 | The General Dynamics partnership shows the company wants to own more of the ground-force integration layer. | Medium | SE008 |
| CE009 | The software and hardware bundle makes it harder to isolate a clean software-only margin story. | Medium | SE002, SE003 |
| CE010 | Operational support and reliability matter because these systems are meant to be fielded, not demoed. | Medium | SE005, SE006 |
| CE011 | Supply chain and manufacturing are part of the product stack rather than a separate back office function. | Medium | SE001, SE007 |
| CE012 | The product moat is operational and software-driven, not just a feature checklist. | Medium | SE003, SE004, SE006 |
| CU001 | Anduril's visible customer base centers on U.S. defense agencies, homeland-security agencies, and allied governments. | High | SU001, SU006 |
| CU002 | Adoption has moved past pure pilots in some programs and into production-style delivery. | Medium | SU004, SU008 |
| CU003 | Named customer proof includes government-facing programs plus partner evidence such as the Everfox relationship. | Medium | SU002, SU004 |
| CU004 | The customer relationship is likely to improve once a program lands because deployment, support, and integration create switching costs. | Medium | SU005, SU006 |
| CU005 | Customer concentration is still opaque, but the public evidence suggests a small number of large programs matter most. | Medium | SU001, SU005 |
| CU006 | Partner and channel dependence are material because some customer proof is indirect rather than direct. | Medium | SU002, SU008 |
| CU007 | Public evidence does not reveal retention, NRR, or customer-level renewal data. | Medium | SU001, SU005 |
| CU008 | The company's production and hiring signals indicate it is trying to convert early wins into repeat business. | Medium | SU003, SU008, SU007 |
| CU009 | The top-customer risk is likely meaningful because defense programs can be large but lumpy. | Medium | SU001, SU004 |
| CU010 | Land-and-expand dynamics matter because one successful deployment can open adjacent programs. | Medium | SU004, SU005 |
| CU011 | The customer story is stronger on public proof than on public metrics. | Medium | SU002, SU006 |
| CU012 | Anduril's current growth narrative depends on repeat buying from the same government ecosystem. | Medium | SU007, SU008 |
| CR001 | The highest-severity risks are regulation, operational execution, partner dependence, and capital intensity. | Medium | SR001, SR007 |
| CR002 | Autonomous defense systems face legal and regulatory scrutiny because the use case sits near sensitive policy boundaries. | Medium | SR001, SR006 |
| CR003 | Operational risk includes manufacturing scaling, support burden, and the possibility of delivery slippage. | Medium | SR003, SR005, SR007 |
| CR004 | Partner and dependency risk is meaningful because the company often works through primes or allied programs. | Medium | SR008, SR002 |
| CR005 | Capital intensity remains high even after the 2026 Series H because the business still needs manufacturing and talent spend. | Medium | SR007, SR003 |
| CR006 | Public criticism of border-security work shows that reputation and policy backlash are real business risks. | Medium | SR001, SR004 |
| CR007 | Security, privacy, and compliance controls need to stay strong because the company handles defense-adjacent data and systems. | High | SR006, SR004 |
| CR008 | No public audited financial package means many risk assumptions remain inferred rather than verified. | Medium | SR007, SR006 |
| CR009 | A large adverse event would likely show up first in delayed deliveries, partner friction, or weaker contract cadence. | Medium | SR003, SR005 |
| CR010 | The company mitigates some risk by pairing software with operational support and by emphasizing trust and veteran narratives. | Medium | SR004, SR006 |
| CR011 | Board-level or cap-table transparency is still limited, which complicates downside analysis. | Medium | SR007, SR002 |
| CR012 | The thesis breaks if capital needs, regulation, or delivery performance move in the wrong direction at the same time. | Medium | SR001, SR007, SR008 |
| CV001 | Anduril's current valuation context is around $61B after the 2026 Series H. | Medium | SV004 |
| CV002 | The 2025 Series G and the 2024 Series F set the key comparison points for the current price. | Medium | SV001, SV004, SV008 |
| CV003 | The latest valuation is rich enough that public investors will need stronger disclosure to stay confident. | Medium | SV002, SV003 |
| CV004 | The best current recommendation is to track rather than chase the stock at this valuation. | Medium | SV002, SV005 |
| CV005 | The valuation remains stretched because growth must stay fast while margins and disclosure both improve. | Medium | SV004, SV006 |
| CV006 | A bull case requires continued program wins, margin expansion, and more repeatable software attach. | Medium | SV004, SV007 |
| CV007 | A base case assumes growth continues but the company still deserves a discount for opacity. | Medium | SV002, SV005 |
| CV008 | A bear case would come from slower growth, hardware-heavy economics, or a funding surprise. | Medium | SV003, SV006 |
| CV009 | Comparable references include defense primes, Palantir-style software multiples, and prior private rounds. | Medium | SV001, SV002, SV005 |
| CV010 | Exit readiness is improving, but an IPO-style disclosure package is still necessary before the market will re-rate it cleanly. | Medium | SV004, SV007 |
| CV011 | Dilution and preference overhang remain hard to model because the cap table is not public. | Medium | SV002, SV003 |
| CV012 | The thesis breaks if growth slows or if the company cannot turn scale into better margins. | Medium | SV004, SV006, SV007 |