Army Names Anduril Lead for NGC2 Common Data Layer; Lattice Platform to Scale AI Integration Across Force
Anduril's selection reflects a shift in how the Army is bundling AI integration with platform architecture — rather than bolting AI onto existing C2 systems, NGC2 makes the data layer AI-native from the start.
This creates a moat: if Lattice becomes the de facto standard for data ingestion and fusion, competitors (Palantir, Microsoft, Google) face a choice between reverse-engineering Anduril's interfaces or building parallel stacks. The decision also signals the Army is betting on a single vendor for data-layer governance — a concentration risk that will surface in the next IG audit if interoperability problems emerge.
This contracts Anduril into the Army's core data architecture at a critical scaling moment — the decision locks Lattice as the integration substrate for AI and multi-domain operations across a force of 485,000 active-duty personnel.
If Lattice becomes the standard, Anduril gains control over data interoperability standards that will constrain or enable every other sensor, fire-control, and AI application the Army procures for the next 5-7 years. The baseline contract is the leverage point: whoever owns the data layer owns the veto over downstream integrations.
Watch whether TRADOC publishes NGC2 interface specifications by Q1 2027 — if they don't, Anduril de facto controls the standard.
What is the contract value for the NGC2 common data layer baseline, and does it include LRIP funding or is it limited to architecture/engineering work? Does the Army require Lattice APIs to be open-source or proprietary?
Fault Lines
Strategic intelligence, synthesized daily — with a public track record. Every call graded against what actually happened.