Palantir Technologies has opened a new front in its long-running campaign against custom software development inside the federal government, filing a pre-award bid protest at the Government Accountability Office on July 20, 2026 against the Defense Intelligence Agency's ASTRA solicitation. The company argues that DIA is buying a bespoke technical-research platform when commercial products already meet the mission, and that federal acquisition law requires the agency either to buy a commercial solution or to rewrite its requirements so one can compete. GAO is expected to rule by October 28, 2026.
Background
ASTRA — short for Advanced Systems for Technical Research and Analysis — is structured as a task order for custom software development, issued under the SITE III contract vehicle. DIA wants a platform to support technical research and analysis across its intelligence mission. Rather than compete a commercial product and configure it, according to Palantir's protest, the agency scoped the work as ground-up development.
That framing is the crux of the dispute. Palantir has spent years arguing that the government defaults to custom builds when mature commercial software could do the job faster and at lower cost. It has pressed the same "commercial item" statutory theory before: Washington Technology notes that Palantir previously challenged DIA's Prometheus project on similar grounds. The publication framed the ASTRA challenge as Palantir "invok[ing] its favorite law again," underscoring that this is a reprise of a strategy the company has run rather than a one-off objection to a single solicitation.
The timing matters. Palantir filed before any award was made, which puts the structure of the solicitation itself — not the selection of a competitor — at the center of the case. Pre-award protests of this kind ask GAO to intervene while an agency still has room to change course without unwinding a signed contract.
Key Details
The legal backbone of the protest is the Federal Acquisition Streamlining Act of 1994, or FASA. The statute directs agencies to buy commercial items when they meet the government's needs, and to state requirements in a way that lets commercial products compete unless doing so is genuinely not workable. Palantir contends DIA skipped that analysis and wrote ASTRA in a way that presumes custom development from the outset.
Palantir layers additional authority on top of FASA. It cites a 2009 National Defense Authorization Act provision that favors commercial software, along with implementing language in the Defense Federal Acquisition Regulation Supplement and the Federal Acquisition Regulation. Taken together, the company argues, those rules obligate DIA to prefer a commercial solution or to justify — on the record — why one will not work for the ASTRA mission.
A bid protest, in GAO's own terms, is a challenge to the terms of a solicitation or the award of a federal contract — and here Palantir is contesting the terms, not an award. Because the protest was filed before award, it triggers the automatic stay under the Competition in Contracting Act. The practical effect of a pre-award CICA stay is that the agency generally cannot proceed with the procurement while GAO reviews the challenge — the freeze applies to the whole acquisition, not just to a single evaluation. That is what gives a pre-award protest its leverage: the clock stops on the entire procurement rather than on one contested decision.
GAO's bid-protest process runs on a fixed clock. The agency files its report roughly 30 days after the protest, the protester submits comments about ten days later, and a decision follows by the statutory 100-day mark — which here falls on October 28, 2026. No public docket number has been reported. The protest does not allege that a specific competitor was favored in an award; it attacks the way the solicitation is written, which is why Palantir moved before any contract changed hands.
What It Means for Contractors
The ASTRA protest is a template as much as a dispute. Palantir has now invoked the commercial-item mandate often enough that contractors on both sides of the build-versus-buy line should read solicitation structure, not just evaluation criteria, for protest exposure. The way a requirement is scoped, well before any proposals are evaluated, is now itself a point of legal attack.
For commercial software vendors, the lesson is that FASA and the 2009 NDAA provision are live tools, not dormant statutes. A vendor that believes an agency has scoped a requirement to exclude a viable commercial product can challenge the solicitation before award — and the CICA stay gives that challenge immediate weight by freezing the procurement. That leverage is strongest pre-award, when the agency can still rewrite requirements without tearing up a signed contract or triggering a corrective-action scramble.
For systems integrators and custom-development shops, the same dynamic is a risk. A task order scoped as ground-up development on a vehicle like SITE III can be paused for months by a single pre-award protest, regardless of the integrator's qualifications or price. Program offices that want to avoid that outcome will need a documented market-research record showing why commercial products cannot meet the requirement — the exact analysis Palantir says DIA never performed.
The broader signal is about how intelligence-community buyers write requirements. ASTRA is a technical-research and analysis platform, a category where commercial data-integration and analytics tools have matured considerably. When an agency in that space opts for custom development, it now invites a predictable legal test. A GAO decision sustaining Palantir's protest would push more IC solicitations toward commercial-first language and force agencies to show their market research up front; a denial would hand program offices firmer ground to justify custom builds when they can document the need.
Contractors watching the October 28 deadline should treat it as a read on the durability of the commercial-item mandate itself. The ruling will shape how aggressively agencies can scope custom work — and how often excluded or losing commercial vendors reach for FASA to reset a procurement before an award is ever signed. For companies that sell configurable commercial platforms into the defense and intelligence market, that is a precedent worth tracking well beyond DIA.
