You've seen the economics. This is the architecture behind them — and why every choice here exists to protect that return.
Compute, power, cooling — each delivered as a factory-integrated module. On site you only connect power, cooling, and network. No on-site system commissioning.
The compute engine — pick a liquid-cooled path by workload, or run both on one shared 28–35 °C loop.
A grid-tied power asset — not just backup. 120 min ride-through standard, plus peak-shaving and demand response.
Free cooling whenever the climate allows, mechanical trim only when it doesn't — across all climates.
AI racks draw 80–150 kW and climb; GPU generations turn over every 1–2 years. The 12–24-month build model can't keep up. The real constraint is no longer how fast you can build — it's how fast you can energize, and how well you work with the grid.
Where you can build is decided by power. MDCX is engineered to be a grid-cooperative load — so it clears interconnection faster, and earns on power others can't use.
Powered by BESS, not diesel —
Myth: diesel isn't faster — UPS bridges the gap in both cases. So BESS wins on cost, logistics, and approvals.
An AI factory runs ~10× the scale of an enterprise data center. Full 2N / Tier III doubles your infrastructure CapEx on a massive base — straight against the IRR you just modeled.
And AI training isn't a financial-transaction workload. It checkpoints, restarts, and fails over at the node level — it carries no per-second SLA penalty. Buying enterprise-grade redundancy for it is capital spent to protect against a risk that doesn't cost you.
So redundancy is matched to each component's replaceability and blast radius:
| System | Strategy | Logic |
|---|---|---|
| Busbar / copper rails | Single-path, high-integrity | Not field-replaceable — redundant paths only add connection points and failure modes. |
| Cooling pumps / CDU | 2N | Supports online maintenance — swap without stopping compute. |
| Fans / compressors | N+1 | Degrade-and-continue on failure, not an immediate stop. |
| Compute nodes | Node-level failover | Local fault containment — failures don't propagate across the cluster. |
| Control plane | Redundant | No single point of control can take down the whole system. |
MDCX is a manufactured product, not a construction project: fully integrated and tested at the factory, online on arrival. The first cluster ships in ~4–6 months — and because the design is proven and the supply chain is warm, every batch after lands in 75–90 days.
CIOS ships with every block: see every sensor, turn every alarm into a ticket, meter every kilowatt-hour and GPU-hour.
Path-addressed telemetry: sgp01.pod002.cdu000.fws.supply.flow
Alarms → tickets → SLA, policy-gated setpoints.
Usage metering, capacity headroom, ops reports.
Fast deployment and lean redundancy don't mean cutting corners. Every block is built from tier-one industrial hardware and certified to recognized standards.
No compromise components. Every block is assembled from proven, tier-one industrial hardware.
All components meet UL / CE / CSA and the applicable regional standards.
End-to-end system-level certification targeted for completion in 2027.
Two container profiles — chosen by the GPU you want to run and the business you're building. Frontier training on Blackwell, or a lean inference business at scale.
Maximum-density training & high-performance inference. Premium, frontier-grade compute — high CapEx, highest return per container.
Pure inference at scale. Lower entry cost, simple operations, durable continuous revenue.
Running any of the above → CIOS · included →