Capacity
Accreditation-Ready Infrastructure for Government and Secure Workloads
Island Roadhouse is developing a Missouri campus for government, defense and regulated workloads that need accredited space and dependable power.
The initial campus plan includes one 12 MW GPU/HPC data hall as a Secure Mission Hall: an ICD 705 accreditation-ready shell, on a campus planned so that campus generation carries the compute load.
Accreditation-Ready Space, on a Campus Designed Around Its Own Power
Secure programs need accredited space, and the routes to it are all slow. A bespoke SCIF build carries its own supply chain, commissioning path and operating model. A retrofit inside existing colocation works within a boundary designed for something else. Both then meet the constraint that gates every AI program: deliverable power.
Island Roadhouse Data Centers is planning one of the campus’s 12 MW colocation GPU/HPC halls as the Secure Mission Hall: an ICD 705 accreditation-ready shell, planned as a security overlay on the campus standard high-density block rather than as a separate platform. That is a deliberate engineering position. Single-purpose secure builds are where cost, schedule and operational risk concentrate, and a hall that shares the campus supply chain, commissioning path and operating model does not carry that premium. Building to the technical specification with complete construction documentation is planned so that the SAPF path is preserved.
The facility scope Island Roadhouse plans to provide includes:
- The accreditation-ready shell and envelope
- Boundary-capable construction, with controlled and inspectable MEP interfaces
- Planned security support space adjacent to the hall
- Segregated telecom pathways, with a separable secure demarcation
- Construction Security Plan execution, with the Site Security Manager function shared with the sponsoring customer
- As-built, penetration and construction-security records
- Facility operation under a secure operating model
Two regimes govern this category, and they are distinct. Facility accreditation under ICD 705 and the IC Tech Spec governs the physical facility, its perimeter, penetrations, access and alarms, and is granted by a customer-sponsored Accrediting Official.
Information-system authorization, including DoD Impact Level 5 and Impact Level 6 and FedRAMP High, governs the information system and its operator, and attaches to the platform rather than to the building. Island Roadhouse plans the facility path. The facility design is intended to serve as an inherited-controls base for a customer authorization package.
Power Behind the Meter
The completed campus is planned around co-located advanced atomic generation, and the campus is designed so that campus generation carries the compute load, with utility service supporting ancillary non-compute site loads.
Built to Your Basis
Perimeter, countermeasures and compartmentation stay open until a sponsoring customer defines them. The fit-out is then built to that basis rather than retrofitted to it.
- GPU and HPC capacity in repeatable 12 MW halls
- 2N electrical distribution to the rack, with N+1 cooling equipment at block level
- Direct-to-chip warm-water liquid cooling
- Carrier-neutral connectivity, with dual meet-me rooms planned
- The customer sponsors the Cognizant Security Authority and Accrediting Official
- The customer sets the threat assessment and concept of operations
- The customer determines storage posture, compartmentation and TEMPEST countermeasures
- Island Roadhouse would build under the approved Construction Security Plan and would keep the evidence trail
Sustainability Meets Security
Island Roadhouse pairs mission assurance with a low-water, behind-the-meter design.
- Low-Water Design. Reduced reliance on evaporative cooling and on large process-water demand.
- Heat Reuse. The campus is designed to recover heat for beneficial use where a customer needs it, and to reject all required heat without depending on one.
- Behind the Meter. Power generated on-site instead of straining the public grid.
The Accreditation Path, and Who Owns Each Step
For a secure program, the constraint most likely to cause delay is deliverable power. The campus is designed so that the compute load does not depend on a utility interconnection. Accreditation itself is a customer-sponsored act: it follows an engagement and cannot precede one. A sponsor engaging while the design is pre-FEED has the shell shaped to its own concept of operations, rather than inheriting assumptions that were set for another tenant.
Accreditation is granted by a customer-sponsored Accrediting Official, against the threat assessment and concept of operations that the customer sets. The steps, and who owns each of them are:
- Sponsorship and Requirements: The customer establishes sponsorship, identifies the Cognizant Security Authority and Accrediting Official, and sets the threat assessment, storage posture and operating requirements.
- Design Review and Approval: The government reviews and approves the design concept, and approves the final design before secure construction begins. The Construction Security Plan is approved and a Site Security Manager is in place.
- Construction and Evidence: Island Roadhouse builds under the approved Construction Security Plan, with inspections and a documented evidence trail, and would carry that documentation discipline from shell construction onward, before any sponsor exists.
- Accreditation and Authorization: The customer prepares the Fixed Facility Checklist and accreditation package, the government makes the accreditation decision, and the customer authorizes its information system inside the accredited facility.
Under the secure operating model, Island Roadhouse operates the facility and the customer remains the steward of its own classified material, with Island Roadhouse not holding, handling or taking custody of classified data or classified material. The final division of responsibility is set with the sponsoring customer and its Cognizant Security Authority. Final authorization, accreditation and compliance approvals remain specific to each tenant, workload, cloud platform, agency and operating model.
Next step
Start a Capacity Discussion
Organizations evaluating long-term AI, hyperscale, or enterprise compute capacity can begin with a capacity discussion to align deployment needs, timing, and the appropriate capacity profile.