TCO Analysis →
Software · Operations OS · CIOS

The operating system
of the AI Factory.

CIOS is the Compute Infrastructure Operating System for every MDCX data center. Traditional DCIM watches UPS, cooling, and racks. CIOS watches what pays: utilization, PUE, cost, and revenue.

Telemetry Alarms → Tickets Ops Workflows Usage Metering
● Available
1 box
To start
≥7 days
Offline autonomy
Modbus + SNMP
Shipped drivers
Open-core
Apache-2.0
01
What CIOS is

See it → Control it → Monetize it

Every MDCX data center ships with its operating system. Hardware blocks deliver capacity; CIOS turns that capacity into operated, metered, revenue-ready infrastructure.

CIOS is built for modular data center concepts — Tank, CDU, immersion, pod — not generic building BMS. Assets are path-addressed so every sensor and setpoint has a stable identity:

sgp01.pod002.cdu000.fws.supply.flow

The product ladder is deliberate: first make the site legible, then make it operable under policy, then make usage and capacity exportable for commercial decisions. Autonomous / unattended operation is Roadmap — not claimed as shipped.

Licensing is open-core: Apache-2.0 core with commercial surfaces. One line for the site; details off-site.

02
See it

Telemetry that matches how the plant is built

Plugin drivers ingest field protocols into a gateway stream and time-series store. The asset model speaks modular data center language, not generic racks.

Drivers

Modbus TCP and SNMP v2c shipped. Path-addressed points map into the site asset tree.

Asset model

Pods, CDUs, immersion tanks, and loops as first-class objects — not a flat tag dump.

Digital twin line

3D scene mapping of your pods is a capability of the lab pipeline — no Omniverse claim.

03
Control it · MDCX Care+

Alarms become tickets. Setpoints stay policy-gated.

Operations workflows turn plant state into work that can be tracked, SLAd, and closed — without free-for-all remote control.

Alarms → tickets

Alarm engine opens tickets with lifecycle, SLA scan, and notify (webhooks / email).

PM & maintenance

Schedules, inspections, spares, and maintenance windows that suppress alarms when work is planned.

Policy-gated control

CLI cios query / cios set with risk classes — not open write access.

04
Monetize it

Usage records, capacity headroom, ops reports

CIOS meters what the plant consumes and produces so commercial teams can act. It does not invoice.

Usage metering

Records, rollups, and export for kWh and GPU-hour style usage — for reconciliation and customer portals.

Capacity headroom

See where the site still has room before the next block lands.

Portals

Ops portal for operators; customer portal for status, SLA, and usage. No billing or ERP claims.

05
Architecture

Site plane shipped. Fleet plane labeled Roadmap.

Edge-first: a single box can run the site plane offline for ≥7 days. Multi-site aggregation is explicit Roadmap.

Site plane · shipped

One site, complete loop

  • Drivers → gateway → stream → time-series
  • Asset model & path addressing
  • Alarms, tickets, PM, windows
  • Usage records & local portals
  • Policy-gated CLI
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.

Every MDCX data center ships with CIOS.

Model the economics in TCO, or explore the hardware blocks.