The Locked Cockpit: Why the Pentagon Is Paying Small Vendors to Pry Open Its Own AI

An analyst can see the AI's answer but not pull the data behind it — and that small frustration is now a defense-wide fight over who owns military information.

An analyst stares at a screen that already knows the answer. The AI has flagged the vehicles, ranked the threats, drawn the box. But when she tries to pull the raw track underneath it — to feed her own model, to check the work, to hand it to a teammate on a different system — the door is shut. The data is right there. She just can't take it with her. That small, daily frustration is now the seed of a defense-wide fight over who actually owns military information.

The moment people feel before they see the policy

Talk to anyone who works inside a modern military command center and you'll hear a version of the same complaint: the tools are impressive, and the tools are walls. Each platform shows you what it wants to show you, in the format it chose, behind the login it controls. The information is the government's. The plumbing is the vendor's. And when the plumbing is proprietary, "your" data can feel like someone else's hostage.

That is the human stakes behind a dry-sounding development: the Navy and the wider Department of Defense have been openly courting small companies to build tools that make data inside the Maven Smart System easier to reach, move, and reuse. It sounds like a procurement footnote. It's actually a confession — and a course correction.

The record: what Maven is and how it got here

Project Maven began in 2017 as the Pentagon's first serious push to put machine learning on the firehose of drone and surveillance video — the "Algorithmic Warfare Cross-Functional Team." Its early, infamous chapter was Google's involvement, which collapsed in 2018 after thousands of Google employees protested and the company declined to renew. The work didn't stop; it changed hands.

Over the following years the program matured into the Maven Smart System (MSS), a software layer that fuses sensor feeds and intelligence into a single targeting-and-decision picture. Palantir became the central vendor. In May 2024 Palantir was awarded a Maven Smart System contract reported at roughly $480 million, and in 2025 the Army moved to expand that ceiling substantially — public reporting put the enlarged ceiling near $1.3 billion. Oversight now runs through the Pentagon's Chief Digital and Artificial Intelligence Office (CDAO). These are large, real, checkable numbers, and they point at one fact: MSS is no longer an experiment. It is operational infrastructure that real commands depend on.

Here's the tension that creates. When one company's system becomes the place where the picture lives, the question of how easily other tools can read and write that picture stops being academic. It becomes a question about flexibility, cost, and — in a shooting war — speed.

Why "make the data accessible" is the whole ballgame

A closed data ecosystem is seductive for a buyer. One vendor, one throat to choke, one integrated experience that mostly just works. The hidden bill comes later, and it comes in three forms.

Lock-in. Once your workflows, your training, and your data formats live inside one system, leaving is expensive enough that you mostly don't. The vendor's pricing power grows precisely because switching is painful.

Innovation throttle. If a clever 12-person startup builds a better detection model, it doesn't matter unless that model can get the data in and push results back out. A walled garden means the only innovation that ships is the kind the wall-owner approves.

Resilience. In a real conflict, "one system, one vendor, one network path" is also "one place for everything to fail." Redundancy requires that more than one tool can read the same truth.

The Pentagon has said the quiet part out loud with a framework called Open DAGIR — Open Data and Applications Government-owned Interoperable Repository — announced by CDAO in 2024. The premise is blunt: the government keeps ownership of the data and the integration layer, and multiple vendors plug into it on common standards. Inviting small vendors to build accessibility tools on top of Maven is that philosophy turning into purchase orders.

The opportunity — and the catch

For small companies, this is a rare open door. Defense work usually rewards incumbents with armies of compliance staff. A solicitation that says, in effect, help us get our own data out of a system we already bought is a niche where a sharp, fast team can win on merit. The on-ramps exist — SBIR awards, CDAO pathways, prototype contracts — and the ask is concrete rather than visionary.

But notice the strangeness of the situation. The government is paying a second set of vendors to undo a constraint created by buying from the first. That is the real signal here, and it's worth saying plainly: interoperability is not free, and it is not automatic. If you don't demand open data on the way in, you pay other people to pry it open on the way out. "Records over spin" cuts both ways — the spin is that any single AI platform is a finished answer; the record is that the Pentagon is now spending money to reopen one it already owns.

There's tension for the incumbent too. Genuine openness erodes the moat. A vendor can wave the interoperability flag in a press release while keeping the most valuable hooks — the export formats, the APIs, the bulk pulls — slow, partial, or gated. Whether "accessible" means truly portable or merely viewable through an approved window is the detail that decides who actually holds the power. Watch the API docs, not the slogans.

The takeaway

The locked cockpit is a choice, not a law of physics. Closed systems buy you speed and simplicity today and hand you a bill in lock-in, stalled innovation, and brittleness tomorrow. The Navy and DoD courting small vendors to open up Maven's data is the Pentagon paying that bill in installments — and quietly admitting that "government-owned, vendor-operated" only protects you if owned includes the right to walk your data out the door.

For builders, the opening is real. For buyers everywhere — not just in defense — the lesson is cheaper if you learn it before you sign: insist that the data be yours in fact, not just on paper. The analyst staring at an answer she can't extract is the future of every organization that treats interoperability as someone else's problem.