Start with the current notice
DISA posted the final Core solicitation on September 3, 2026. The proposed base ordering period runs from December 8, 2027, through December 7, 2032, with an option extending ordering to December 7, 2037. A $21.6 billion ceiling describes maximum contract capacity, not an appropriation, award value already earned, or guarantee of demand. Government solicitation text
There is an important schedule correction for anyone preparing a response: the September 22 notice removes the October 6 proposal deadline and says an amendment will provide a revised date. The narrative update takes precedence over a stale date repeated in an opportunity summary. Current SAM notice
Core is an indefinite-delivery/indefinite-quantity acquisition using task orders. Its scope covers unclassified services at Impact Levels 2, 4, and 5, Secret at Impact Level 6, and Top Secret services including SCI and SAP requirements, together with tactical-edge delivery. The solicitation provides for firm-fixed-price consumption line items and time-and-materials ordering where appropriate. Buyers need to examine the complete terms and amendments, including the applicable performance work statement, before deciding how a workload will be supported.
This is an evolution of an established buying approach. The original JWCC was already designed around multiple providers, task orders, several classification levels, and tactical-edge requirements. The 2022 defense briefing described a $9 billion ceiling and emphasized that a ceiling was not guaranteed spending. It would be a mistake to treat the new solicitation as an immediate cancellation of existing JWCC contracts or as the first time defense cloud services could be acquired through task orders. Original JWCC briefing
Where Premier fits
The Premier catalog RFI describes a three-part marketplace concept:
- Hyperscalers: large-scale infrastructure and platform providers.
- Everything-as-a-Service: software, platforms, and infrastructure beyond the hyperscaler group.
- Commercial innovators and small businesses: additional offerings meeting provisional-authorization standards.
The government asked industry how to provide a catalog of authorized offerings and turn high-level mission requirements into orderable solutions. The RFI closed September 1. Its description signals a desire for broader participation, but it does not award contracts, guarantee direct access for every supplier, or establish a final Premier solicitation date. Premier RFI
For a specialized AI or edge-computing company, this distinction changes the preparation task. The current Core solicitation is expressly for hyperscale requirements. A company should determine whether it fits that requirement, supports an eligible offeror, or should prepare for a later opportunity. The original JWCC was never the only route into defense cloud work, and a new marketplace does not eliminate the need to understand other applicable contracts and program-specific buying decisions.
The handoff between infrastructure and applications
A mission application may need both commodity infrastructure and specialized software or services. Separating those purchases can encourage competition and make costs easier to see. It can also leave gaps in responsibility unless the buyer plans the whole service.
Consider an authorized analytics workload. Its infrastructure may satisfy one set of requirements while the application still needs configuration, data integration, user access controls, monitoring, and an accountable support team. If an application update changes a dependency, someone must own the review, deployment, and recovery process. Those obligations do not disappear because two services appear in the same marketplace.
For AI and joint command-and-control programs, degraded connectivity adds another set of questions. Which approved functions remain available when a connection is lost? How is information freshness communicated? How are changes reconciled when service returns? These are engineering and acceptance questions. Tactical-edge coverage in a solicitation does not establish that every service works in every disconnected, disrupted, intermittent, or limited-bandwidth environment.
A useful task order should make these boundaries explicit instead of relying on a general promise of seamless operation.
A buyer's checklist before ordering
- Define the service outcome. Identify the users, information, authorized purpose, and operating conditions the purchase must support.
- Check the exact offering. Confirm the relevant authorization, classification level, region or environment, and available features. Do not assume a provider's entire catalog shares one approval.
- Price the complete workload. Include compute, storage, transfer, licenses, migration, integration, support, and exit costs using comparable assumptions.
- Assign shared responsibilities. Name the owners of identity, data protection, monitoring, incident handling, and service restoration.
- Set acceptance evidence. Establish what demonstrations, records, and performance measures show that the delivered service meets the requirement.
- Plan change and exit. Specify usable data exports, interfaces, support transitions, and the consequences of changing providers or service versions.
Zero trust belongs in this assessment. NIST's framework focuses on protecting resources and making explicit access decisions rather than trusting a system because of its network location. A procurement route can support that approach, but the application and operating environment still need their own implementation decisions. NIST SP 800-207
What suppliers should prepare now
Providers should build a precise account of what they can deliver, at which authorization level, with which dependencies and support commitments. For smaller firms, a clear boundary is often more persuasive than a broad claim to cover the whole mission. Identify what is already available, what depends on another provider, and what still requires government action.
Market-entry planning should also distinguish provisional authorization from selection for a contract and from approval for a particular mission deployment. These are related decisions, not interchangeable credentials. Pricing and technical documentation should remain consistent across the catalog, proposal, and eventual task-order response.
Finally, follow amendments directly. A marketplace can change while industry is preparing to enter it. Keeping a versioned record of requirements and assumptions is a practical way to avoid designing a response around an obsolete deadline or an anticipated feature that never enters the final solicitation.
Judge the marketplace by its use
The central test will come after awards: whether program offices can compare real alternatives, buy a complete service, and change suppliers when necessary. Task-order transparency and disciplined catalog management deserve attention because they determine whether nominal competition becomes usable choice.
Measures such as delivery time, total workload cost, support performance, and successful data portability will be more informative than the ceiling alone. A marketplace earns its value when those measures improve for the people relying on the service.
Sources
- Current DISA Core notice and amendments
- Government Core solicitation text, reproduced PDF
- Premier catalog RFI
- Archived government Premier description
- Defense Department JWCC briefing
- NIST Zero Trust Architecture
Spartan X's engineering and cybersecurity practices connect these purchasing decisions to delivery: a defined service, clear responsibilities, and acceptance evidence that program leaders can use throughout the life of the capability.
