- Potential benefitIncreases DoD flexibility to acquire commercial AI software and data (including subscription models), which supporters…
- Potential benefitExpands market opportunities for commercial software and data providers and could shift or increase contractor and priv…
- Potential benefitEnables DoD to fund modification, testing, and further development of AI software internally or via contractors, potent…
FAST Act
Referred to the House Committee on Armed Services.
The bill, titled the Flexible Acquisition of Software Technology Act (FAST Act), authorizes the Secretary of Defense to procure software and data in multiple delivery models (software as a service, software as a product, data as a service, data as a supply), to modify software, and to research, develop, test, and evaluate software to support artificial intelligence systems for Department of Defense operational needs. It allows the Secretary to use amounts appropriated or otherwise made available for any purpose to carry out these authorities.
Degree of concern over civil-liberty and bias safeguards: progressives emphasize need for explicit statutory protections; conservative focuses more on national-security vetting.
Relative to its intended legislative type, this bill clearly establishes an administrative authority allowing the Secretary of Defense to procure and modify software and data to support AI systems and requires issuance of regulations, but it remains skeletal: it supplies definitions and permissive funding language while omitting detailed mechanisms, timelines, fiscal analysis, explicit connections to specific procurement statutes, safeguards, and concrete accountability provisions.
The bill, titled the Flexible Acquisition of Software Technology Act (FAST Act), authorizes the Secretary of Defense to procure software and data in multiple delivery models (software as a service, software as a product, data as a service, data as a supply), to modify software, and to research, develop, test, and evaluate software to support artificial intelligence systems for Department of Defense operational needs.
It allows the Secretary to use amounts appropriated or otherwise made available for any purpose to carry out these authorities.
The Secretary is required to issue or modify regulations governing these procurements, modifications, and their oversight.
On content alone, the bill is modest, technical, and aimed at improving DoD flexibility around AI-related software and data — characteristics that favor enactment when folded into larger defense bills. However, its permissive funding language, sparse guardrails, and potential clashes with existing procurement rules invite scrutiny and amendment. Without being attached to a larger must-pass vehicle or strengthened with oversight and procurement safeguards, its standalone passage is uncertain.
Relative to its intended legislative type, this bill clearly establishes an administrative authority allowing the Secretary of Defense to procure and modify software and data to support AI systems and requires issuance of regulations, but it remains skeletal: it supplies definitions and permissive funding language while omitting detailed mechanisms, timelines, fiscal analysis, explicit connections to specific procurement statutes, safeguards, and concrete accountability provisions.
Degree of concern over civil-liberty and bias safeguards: progressives emphasize need for explicit statutory protections; conservative focuses more on national-security vetting.
Who stands to gain, and who may push back.
These are examples from the analysis, not a ranked list of the most-affected groups.
- Potential burdenIncreased reliance on cloud‑hosted software and remotely accessed data services could raise cybersecurity, data‑soverei…
- Potential burdenSubscription‑based procurement (software‑as‑a‑service, data‑as‑a‑service) can create ongoing, recurring costs and vendo…
- Potential burdenThe broad authorization to use amounts 'appropriated or otherwise made available' for any purpose could reduce transpar…
Why the argument around this bill splits.
Degree of concern over civil-liberty and bias safeguards: progressives emphasize need for explicit statutory protections; conservative focuses more on national-security vetting.
A mainstream liberal/left-leaning observer would view the bill as a targeted modernization of acquisition authorities that could help the Defense Department develop AI capabilities, but would be concerned about insufficient guardrails on civil liberties, bias, and accountability.
They would note the bill’s broad funding language and general regulatory directive but see a lack of explicit requirements for ethical safeguards, transparency, or human-rights protections.
Overall they would be cautiously open to its goal of enabling AI development for defense while wanting stronger limits and oversight written into law.
A centrist/moderate would generally welcome the bill’s goal of giving the Defense Department clearer authority and flexibility to acquire modern software and data to support AI, while wanting concrete assurances about oversight, cost control, and compatibility with existing procurement law.
They would see the regulatory requirement as a necessary step but note the bill lacks detail on timelines, reporting, and specific guardrails.
Overall they would lean supportive if the implementing regulations include transparency, fiscal controls, and safeguards to prevent sole-source overreach.
A mainstream conservative would likely view the bill favorably as a practical step to modernize and speed up Defense Department acquisition of software and data to maintain technological and national-security advantages.
They would appreciate the flexibility to use available funds and the emphasis on enabling commercial delivery models like SaaS, which can keep the military current.
At the same time, they would be attentive to ensuring these authorities do not cede sensitive systems or IP to foreign or insecure vendors and would want strong national-security and procurement-competitiveness safeguards.
The path through Congress.
Reached or meaningfully advanced
Reached or meaningfully advanced
Still ahead
Still ahead
Still ahead
On content alone, the bill is modest, technical, and aimed at improving DoD flexibility around AI-related software and data — characteristics that favor enactment when folded into larger defense bills. However, its permissive funding language, sparse guardrails, and potential clashes with existing procurement rules invite scrutiny and amendment. Without being attached to a larger must-pass vehicle or strengthened with oversight and procurement safeguards, its standalone passage is uncertain.
- Whether the bill would be incorporated into larger, regularly enacted defense legislation (where enactment likelihood rises) or remain as a standalone measure.
- Lack of an accompanying cost estimate or scoring in the text; the fiscal impact hinges on how the authorization to use "amounts appropriated or otherwise made available" is interpreted and constrained in practice.
Recent votes on the bill.
No vote history yet
The bill has not accumulated any surfaced votes yet.
Go deeper than the headline read.
Degree of concern over civil-liberty and bias safeguards: progressives emphasize need for explicit statutory protections; conservative focu…
On content alone, the bill is modest, technical, and aimed at improving DoD flexibility around AI-related software and data — characteristi…
Relative to its intended legislative type, this bill clearly establishes an administrative authority allowing the Secretary of Defense to procure and modify software and data to support AI systems and requires issuance…
Go beyond the headline summary with full stakeholder mapping, legislative design analysis, passage barriers, and lens-by-lens tradeoff breakdowns.