All essays
§012 · Architecture

NASA's hardware obligations signal return to vertical integration

This week's appropriations data shows NASA obligating funds across five prime contractors for in-house hardware development, manufacturing, and assembly—a pattern that marks a deliberate retreat from the commercial-services model that defined the agency's 2010s procurement strategy.

3 min · Published 2026-06-22 · By Bridger

The obligated contracts span upper-stage manufacturing (Boeing), spacecraft delivery (Lockheed Martin), weather instrument development (L3Harris), extravehicular operations (Hamilton Sundstrand), and continued Russian collaboration on human spaceflight. Taken individually, none of these actions is remarkable. Taken together, they represent a structural choice: NASA is buying things again, not services.

The distinction matters because it determines who can compete. Commercial services contracts—the model that produced Commercial Crew and Cargo Resupply—are milestone-based, fixed-price, and open to firms without legacy production facilities. Hardware development contracts are cost-plus, require demonstrated manufacturing capacity, and reward incumbents who can absorb technical risk across multi-year timelines. The former model opened NASA procurement to non-traditional entrants. The latter closes it.

Why vertical integration returns

Three factors explain the shift. First, geopolitical friction has made supply-chain legibility a priority. The inclusion of a Russian Space Agency obligation—for joint human spaceflight activities—is notable not because it exists but because it appears alongside domestic hardware contracts that duplicate capabilities previously sourced internationally. Second, the failure of commercial lunar landers to meet Artemis timelines has revived internal skepticism about fixed-price contracts for unproven systems. Third, congressional appropriators have consistently funded traditional prime contractors for flagship programs while scrutinizing newer entrants.

NASA is buying things again, not services—and that distinction determines who can compete.

The practical effect is that allied firms entering the US federal market now face a higher barrier at NASA than they did five years ago. A commercial services contract requires a credible technical proposal and financial bonding. A hardware development contract requires domestic production capacity, cost accounting systems compliant with FAR Part 31, and a track record managing multi-year development programs under government oversight. Most allied tech firms meet the first set of requirements. Few meet the second.

The pre-RFP window narrows

Vertical integration also compresses the timeline for positioning. Commercial services contracts typically allow 12-18 months between program announcement and contract award, during which new entrants can establish US subsidiaries, secure facilities, and build relationships with NASA program offices. Hardware development contracts emerge from multi-year budget cycles, with vendor selection often implicit in the budget justification documents submitted 18-24 months before obligation. By the time an RFP appears, the competitive set is already defined.

Allied firms that treat NASA as a commercial-services buyer will miss this. The agency's public messaging still emphasizes partnerships and innovation, but the appropriations data reveals a different operational reality. The contracts obligated this week were not competed in any meaningful sense—they represent the continuation of relationships established years earlier, often through Other Transaction Authority agreements or prototype projects that predated formal procurement.

For platform intelligence, the implication is straightforward: tracking NASA's budget justifications and pre-solicitation engagement is now more valuable than monitoring RFP releases. The window for positioning has moved upstream, into the two-year period when program offices translate strategic guidance into budget requests. Firms that enter NASA's procurement landscape at the RFP stage are not early—they are late.

The broader pattern holds across agencies returning to vertical integration as a risk-mitigation strategy. Energy's continued obligations to national laboratory operators (Argonne, Jefferson Lab) follow the same logic: when geopolitical uncertainty rises, agencies preference known counterparties with demonstrated capacity over competitive processes that might surface cheaper but unproven alternatives. Allied firms can compete in this environment, but only if they recognize that the competition begins before the formal procurement process does—and that hardware credibility now outweighs commercial agility.

Built on this thesis

See how it shows up in the product.

Request access