Establish what is supportable.
Connect the growth ambition, utility plan, protected retail allocation and cooling scope. Calculate usable capacity rather than relying on a pod label.
For data-center owners · A narrated decision experience
From a 5 MW retail base to an AI-ready campus. Explore what you can responsibly commit, which capacity can be accepted, and what the next pod can reuse.
IT capacity · earned through each release
A campus ambition is not an accepted capacity commitment.
Protect the baseKeep existing retail commitments and operating margins explicit.
Qualify each blockSeparate physical capacity, commercial support and acceptance.
Earn the next investmentCarry verified evidence into the next pod’s decision.
The owner’s growth question
Follow the evidence from a tenant request to a release decision. Then change the assumptions and compare the choices.
From 5 MW to 30 MW
Original narrated experience, with the decision lab, release checklist, assumptions and chapter navigation.
The decision path
The walkthrough keeps the same owner question in view as the evidence, choices and investment horizon change.
Connect the growth ambition, utility plan, protected retail allocation and cooling scope. Calculate usable capacity rather than relying on a pod label.
Trace the exposure and prior planning state. Compare waiting, staged release and acceleration, then inspect the evidence and authority needed for acceptance.
Test the effect on live capacity, retain the decision evidence and evaluate what later pods can reuse before committing to the 30 MW ambition.
This case assumes a 5 MW retail IT base and five proposed 5 MW GPU pods. It is separate from the Atlas Release R1 case on the data-center page. Figures are illustrative; IT capacity and facility power are different measures. Engineering evidence, operator acceptance, tenant agreement and capital authority remain required.