MDCX is a solution design company for modular AI data centers. We define standards, deliver repeatable design methods, and build an ecosystem of hardware blocks × operations OS × compute marketplace — not a pure product catalog.
Public summary of positioning locked 2026-08-08. Full narrative:Why MDCX.
Who we are / are not
| We are | We are not |
|---|---|
| Solution design and system-integration narrative owners | A pure OEM catalog site |
| Maintainers of modular data center standards and reference architectures | A single-SKU brochure |
| Method providers for deploy, deliver, remote ops, and monetization | Ad-hoc civil EPC without a standard |
| Ecosystem orchestrators (blocks + CIOS + DCM + partners) | A closed non-interoperable stack |
Four capability axes
Every MDCX component — Liquid Cooling and Immersion Cooling containers, CIOS, DCM, Designers, TCO — is designed against the same four outcomes. Specs and product pages should map claims to these axes.
1. Rapid deploy
Rapid Deploy
After the pad is ready: power up, network, and load IT as fast as a factory-tested block allows. Carried mainly by modular containers and standard interfaces.
2. Rapid deliver
Rapid Deliver
Repeatable supply and configuration cycles — not one-off projects. Carried by standard SKUs, Designers that freeze configurations, Docs, and the USD output spec.
3. Remote operate
Remote Operate
Low headcount operations: telemetry paths, alarms → tickets, usage metering. Carried primarily by CIOS.
4. Token aggregation
Token aggregation ·
Meter, compose, and monetize compute rights
Compute, energy, and usage rights that can be measured, composed, and monetized. Carried by DCM (Roadmap) plus CIOS metering and TCO economics. Fixed English term — do not substitute “tokenize / mining / coin” in customer copy.
How components map
| Component | Deploy | Deliver | Remote | Token aggregation |
|---|---|---|---|---|
| Liquid / Immersion blocks | Factory prefab, standard pads | SKU BOM, replicable units | Sensors into CIOS | Meterable kW / GPU capacity |
| Design tools | Site assumptions | Config freeze ·?code= | Asset drafts | Inputs to TCO / DCM later |
| CIOS | Day-0 bring-up | Standard ops model | Primary | Usage metering |
| DCM | — | — | Marketplace ops (Roadmap) | Primary |
| TCO | — | Economic proof of a SKU | — | Revenue / cost narrative |
Public funnel (site)
- Why a modular data center standard is needed
- Four axes (this page)
- Solution lines — Liquid Cooling · Immersion Cooling · CIOS · DCM
- Validate with TCO → open Designer with
?code= - Docs for delivery and interchange (USD, matrix)
- Engage partners / contact
SKUs under the standard
Product codes are instances of the standard, not the whole story. Always show Alias first, SKU ID small under (product matrix). Draft SKUs appear as Coming soon only until Admin Publish.