In December 2022, the Department of Defense awarded the Joint Warfighting Cloud Capability contract — JWCC — to four technology companies: Microsoft, Amazon Web Services, Google Cloud, and Oracle. The contract ceiling was $9 billion, spread across a multi-vendor framework designed to provide cloud computing services at every classification level the military operates, from unclassified Impact Level 2 through the most sensitive compartmented programs at Impact Level 6 and above. The contract replaced the Joint Enterprise Defense Infrastructure — JEDI — a $10 billion single-vendor award that Microsoft won in 2019 before it was canceled in July 2021 amid Amazon’s legal challenge and shifting Pentagon cloud strategy. JWCC was presented as a more competitive, resilient approach: multiple vendors, multiple clouds, redundancy at every layer. But the structure of the contract, and the way it has been implemented, reveals something more consequential than a procurement reform. JWCC is the framework through which quantum computing will enter the classified heart of the American military establishment.
To understand how, start with what has already been deployed. Microsoft Azure Stack Hub is an on-premises extension of Azure that allows organizations to run cloud services inside their own data centers, disconnected from the public internet. For the Department of Defense, Azure Stack Hub operates inside air-gapped networks — environments with no physical or electronic connection to outside systems. These include Sensitive Compartmented Information Facilities (SCIFs), submarine command centers, forward-deployed tactical operations centers, and underground installations that house the military’s most sensitive command-and-control systems. Azure Stack Hub at Impact Level 5 handles controlled unclassified information and mission-critical data. At Impact Level 6 and above, it processes classified national security information, including signals intelligence, operational plans, and nuclear command-and-control data. Microsoft’s Active Directory — the identity and access management system that authenticates every user and device on a network — has become the backbone of identity management across both NIPRNet, the unclassified military network, and SIPRNet, the classified Secret-level network. Every login, every file access, every application launch on these networks passes through Microsoft’s authentication layer.
Amazon Web Services occupies a parallel position. AWS GovCloud, launched in 2011, was the first major commercial cloud platform purpose-built for government workloads. AWS holds FedRAMP High and DoD Impact Level 5 authorizations, and its Secret Region — AWS Secret Cloud — operates at Impact Level 6, supporting classified workloads for the intelligence community and the Department of Defense. Amazon’s relationship with the intelligence community predates JWCC by nearly a decade: in 2013, the CIA awarded a $600 million cloud computing contract to AWS, a deal that transformed the intelligence community’s approach to data storage and analysis. AWS now provides the cloud infrastructure for multiple intelligence agencies, and its Secret Region is physically located within facilities controlled by the intelligence community. Under JWCC, AWS extends this capability across the broader DoD, providing classified cloud services to combatant commands, service branches, and defense agencies.
Google Cloud and Oracle round out the JWCC consortium, each bringing distinct capabilities. Google holds FedRAMP High authorization and has been expanding its Assured Workloads platform for government customers, though it has been more measured than Microsoft and Amazon in pursuing the highest classification levels. Oracle Cloud Infrastructure entered the defense market aggressively, leveraging its database dominance in government agencies and its acquisition of Cerner, which gave it control of the electronic health records for the Military Health System. Oracle’s distributed cloud architecture — which allows Oracle Cloud to run in customer-controlled locations, including inside military facilities — makes it a natural fit for classified environments that require on-premises computing with cloud management capabilities. Together, these four vendors form the cloud layer of the modern American military. Every branch, every combatant command, every intelligence agency can procure cloud services from any or all of them under JWCC.
Now introduce quantum computing into this architecture. Each of the four JWCC vendors is simultaneously developing or partnering with quantum computing technology. Microsoft is building topological qubits through its Majorana program and integrates third-party quantum hardware through Azure Quantum. Amazon operates its own quantum computing service, Amazon Braket, which provides cloud access to quantum processors from IonQ, Rigetti, Oxford Quantum Circuits, and QuEra Computing, while also running the AWS Center for Quantum Computing in Pasadena, California, where it is developing its own superconducting quantum processor. Google operates the Quantum AI lab in Santa Barbara and is building processors in-house, from the 53-qubit Sycamore through the 105-qubit Willow. Oracle, while not building quantum hardware, has positioned its cloud infrastructure as quantum-ready, designing its distributed cloud architecture to integrate quantum coprocessors as they become available. The JWCC contract framework does not restrict these vendors from integrating new computing modalities into the services they provide to the military. Quantum computing is not a separate contract — it is an evolution of the cloud services already being delivered.
Beyond the four JWCC primes, a constellation of quantum computing startups feeds into the defense ecosystem through partnerships, subcontracts, and direct government funding. IonQ, a publicly traded trapped-ion quantum computing company based in College Park, Maryland, has been particularly aggressive in pursuing government contracts. IonQ’s trapped-ion systems, which use ytterbium and barium atoms suspended in electromagnetic traps and manipulated with laser pulses, offer high gate fidelities and all-to-all qubit connectivity. The company has announced partnerships with the U.S. Air Force Research Laboratory, received funding from the Intelligence Advanced Research Projects Activity (IARPA), and is accessible through both Amazon Braket and Azure Quantum. Rigetti Computing, based in Berkeley, California, builds superconducting quantum processors and operates its own cloud platform, Rigetti Quantum Cloud Services. Rigetti has received contracts from the Defense Advanced Research Projects Agency (DARPA) for quantum computing research and is accessible through Amazon Braket. Quantinuum, formed from the merger of Honeywell Quantum Solutions and Cambridge Quantum Computing, operates trapped-ion systems with the highest published quantum volume of any commercial quantum computer and has deep relationships with defense and intelligence customers inherited from Honeywell’s decades of defense contracting.
IBM, while not a JWCC prime, operates the IBM Quantum Network, which includes partnerships with national laboratories, universities, and government agencies. IBM’s quantum computing roadmap — from the 127-qubit Eagle through the 133-qubit Heron to the planned 100,000-qubit Starling system — is among the most detailed in the industry. IBM has partnered with the Department of Energy’s national laboratories, including Oak Ridge, Argonne, and Lawrence Livermore, to explore quantum applications in nuclear simulation, materials science, and cryptanalysis. The company’s quantum-safe cryptography program, which develops algorithms resistant to quantum attacks, has been adopted by multiple federal agencies. IBM’s exclusion from JWCC does not mean exclusion from the defense quantum ecosystem — it means IBM’s quantum technology enters through a different door, via national laboratory partnerships and direct agency contracts rather than the centralized cloud framework.
The financial architecture of military computing deserves scrutiny that it rarely receives. The Department of Defense has failed every comprehensive audit it has ever undergone since the requirement was mandated by Congress in 1990. The first full audit was not even attempted until 2018, and the Pentagon has failed every year since. The scale of the accounting discrepancies is not a rounding error. In fiscal year 2015, the Office of the Inspector General reported that the Army alone had $6.5 trillion in unsupported journal voucher adjustments — accounting entries for which no supporting documentation could be found. The entire federal budget that year was approximately $3.8 trillion. The Army’s unsupported adjustments exceeded the entire U.S. budget by nearly a factor of two. These are not contested figures; they are drawn from official inspector general reports. The Defense Finance and Accounting Service acknowledged the adjustments but stated they were largely the result of the DoD’s antiquated financial systems. What programs, installations, and infrastructure were funded through these unauditable channels remains an open question — one that intersects directly with the documented existence of deep underground military bases whose construction and operating costs do not appear in any publicly available budget line item.
The convergence of quantum computing capability, classified cloud infrastructure, unauditable military spending, and underground installations is not speculative. Each element is documented independently in government reports, corporate filings, contract announcements, and inspector general audits. JWCC provides the contractual framework. Azure Stack Hub, AWS Secret Region, and Oracle Distributed Cloud provide the deployment mechanism into classified environments. Quantum processors from Microsoft, Google, IonQ, Rigetti, and others provide the computing capability. And the Pentagon’s persistent audit failures provide the financial opacity that allows infrastructure of extraordinary scale to be built, operated, and expanded without public accounting. The 932-node network of deep underground military bases documented in this investigation did not build itself, and it does not run on paper ledgers. It runs on computing infrastructure — cloud computing infrastructure supplied by the same companies that hold JWCC contracts, now adding quantum processing to their classified service offerings.
The quantum cloud war is not a metaphor. It is a literal competition among the most powerful technology companies on Earth to control the computing infrastructure of the American military, from the surface to the deepest underground facility. The stakes are not measured only in contract dollars, though $9 billion is substantial. They are measured in capability — the capability to break encryption, optimize logistics for operations that do not appear in any public record, simulate materials for weapons that have not been disclosed, and process intelligence at speeds that redefine what surveillance can accomplish. Every quantum qubit that comes online inside a classified cloud network expands that capability. The investigation on this site follows these threads from the contract awards through the technology deployments to the installations they serve. The quantum cloud war is here. The question is not whether it will reshape military computing — it is whether any institution outside the defense establishment will know the full scope of what has been built until long after it is operational.