Talk to sales → TCO Analysis →
Software · Operations OS · CIOS

Every point
has a path.

CIOS is the Compute Infrastructure Operating System that ships with every MDCX modular data center. Query a CDU flow. Open a ticket from an alarm. Meter kWh without invoicing.

Sgp01.Pod002.Cdu000.Fws.Supply.Flow
Path addressing Alarms → Tickets Usage metering Open-core
● Available · Apache-2.0
Source on GitHub ↗ Talk to sales →
1 box
To start
≥7 days
Offline autonomy
Modbus + SNMP
Shipped drivers
Open-core
Apache-2.0
01
What CIOS is

The ops portal that ships with the box

CIOS is built for modular plants — pods, CDUs, immersion tanks, loops — not a generic building BMS. One box runs the site plane. The core is open-core Apache-2.0 at github.com/MDCX-ORG/CIOS.

CIOS ops portal home: site pods, firing alarms, and operations modules
Ops portal — the site home operators actually use. Not a marketing render.

Related: Factory-tested vs field-built modular AI data centers — Controls that ship with a factory-tested envelope (site plane today).

02
Address it

A stable identity for every sensor and setpoint

Points are path-shaped. Drivers ingest Modbus TCP and SNMP v2c into a gateway stream and time-series store. You query and set by path — not a flat tag dump.

$cios query Sgp01.Pod002.Cdu000.Fws.Supply.Flow
$cios set Sgp01.Pod002.Cdu000.Fws.Supply.Setpoint
03
Operate it · MDCX Care+

Alarms become tickets on the same path

The work queue is the plant: CDU filter checks, UPS on battery, coolant sampling. Lifecycle, SLA scan, webhooks and email. Maintenance windows suppress alarms when work is planned.

CIOS tickets queue with path-addressed assets such as Sgp01.Pod000.Cdu000
Tickets — each row is a path. Open → acknowledged → resolved → closed.
04
Meter it

Usage facts. No invoice.

Measurement and usage records are open source: kWh and rack-hour style facts, list, export, rollup. Commercial billing, statements, and ERP stay parked — CIOS does not invoice.

Usage (OSS)

Records and rollups for reconciliation and the customer portal. Facts only — no money fields.

Capacity headroom

See remaining power and cooling before the next block lands. Forecast assistants are Roadmap.

Two portals

Ops portal for tickets, PM, and the site tree. Customer portal for status, SLA, and usage.

05
Architecture

Open-core layers. Edge-first box.

A single box runs the site plane offline for ≥7 days. Drivers, telemetry, and usage are Apache-2.0. Twin, capacity, and tenant surfaces are commercial. Multi-site fleet is Roadmap.

Layer What it is License
L1–L2 Drivers, gateway, time-series, path dictionary Apache-2.0
Usage Measurement, records, rollups — no money Apache-2.0
L3 Site twin and capacity engine Commercial
L5 Tenant / org substrate. Billing is parked. Commercial
L6 AI Ops — predictive and assistants Roadmap
Site plane · shipped

One site, complete loop

  • Drivers → gateway → stream → time-series
  • Path addressing & CLI query/set
  • Alarms, tickets, PM, windows
  • Usage records & local portals
Fleet plane · Roadmap

Multi-site Roadmap

  • Cross-site rollup / NOC view
  • Central policy distribution
  • Fleet capacity planning
06
Roadmap

We publish what ships. These don't, yet.

Honest strip — not a promise calendar.

Roadmap

GPU-level telemetry

DCGM and per-GPU metrics beyond facility path addressing.

Roadmap

Multi-site fleet plane

NOC-style aggregation across sites.

Roadmap

AI Ops

Predictive maintenance and capacity forecast assistants.

07
Runs on

Included with every MDCX block

Hardware without an operating system is just metal. Pick a block; CIOS ships with it.

L1240C45
L1240C45SUR150 · Liquid Cooling · 1,240 kW IT
I400C45 / I400C40
I400C45SUT50 / I400C40ST50 · Immersion Cooling · 400 kW
Why MDCX
Cluster principles · Computing Unit + BESS + Hybrid Chiller
Every MDCX block ships with CIOS.

Read the source, talk to sales, or pick a Liquid Cooling or Immersion Cooling block.

Source on GitHub ↗ Open TCO Analysis → View products