JEDI Cloud Contract

The JEDI Cloud Contract was a U.S. Department of Defense enterprise cloud computing procurement program intended to award a single-vendor, multi-year contract to provide commercial cloud services across unclassified, secret, and top-secret workloads.

Expanded Explanation

1. Technical Function and Core Characteristics

The Joint Enterprise Defense Infrastructure, or JEDI Cloud Contract, defined a framework for the Department of Defense to acquire Infrastructure-as-a-Service (IaaS) and Platform-as-a-Service (PaaS) capabilities from a commercial hyperscale provider. It sought standardized compute, storage, networking, and security services across classification levels, including global availability and edge support.

The contract required compliance with strict security and accreditation baselines for federal and defense systems, including Federal Risk and Authorization Management Program (FedRAMP) High and Defense Department Security Requirements Guide controls. It also called for capabilities such as data encryption, identity and access management, continuous monitoring, and support for tactical and disconnected operations.

2. Enterprise Usage and Architectural Context

In architectural terms, JEDI aimed to function as a foundational enterprise cloud environment for the Department of Defense, supporting applications ranging from business systems to mission and warfighting workloads. It intended to consolidate disparate hosting environments into a common cloud backbone with uniform security and management policies.

The program described a multi-domain architecture spanning on-premises (on-prem), tactical edge, and commercial data centers, with cross-domain solutions for different classification levels. It targeted migration of legacy applications, development of new cloud-native workloads, and standardized DevSecOps toolchains and services.

3. Related or Adjacent Technologies

The JEDI Cloud Contract related directly to other U.S. Government Cloud (G-Cloud) acquisition vehicles such as the General Services Administration cloud schedules and follow-on Defense Department contracts. It later intersected with the Joint Warfighting Cloud Capability program, which adopted a multicloud, multi-vendor approach.

From a technology stack perspective, JEDI aligned with commercial hyperscale cloud services, including virtual machines, containers, managed databases, object storage, and security services. It also interfaced with Department of Defense networks, identity systems, and existing defense enterprise services.

4. Business and Operational Significance

For industry, the JEDI Cloud Contract represented a large, long-term federal cloud opportunity with extensive compliance, security, and global infrastructure requirements. It illustrated how defense and national security customers structure single-award enterprise cloud procurements under federal acquisition regulations.

Operationally, JEDI documented requirements for delivering cloud services to classified and tactical environments, including latency, survivability, and sovereign data handling. Although the Department of Defense canceled JEDI and moved to a multicloud strategy, its documentation continues to inform enterprise-scale public sector cloud contracting and architecture.