Plan, build and operate. One estate model across all of it.

Every block reads and writes the same record of your datacenters.

DCHelix platform

Plan & build sellable capacity → commissioned hall

The core one estate model

Operate impact and cost on every fault

Govern & data
Governed end to endChange request on every write · Approval-gated actions · Audit trail · Every count derived
Deploy where your data must liveOne platform, your choice of footprint, inside your identity stack.
On-premisesYour cloudAir-gappedEmbedded in your portal

One estate model. The graph every block reads and writes: building, plant, racks, devices, ports, cables, GPUs, services, customers and contracts. Every count is derived from it, never typed in.

  • 51 entity types, 107 relationships
  • Stable identities, so adding data never reshuffles the rest
  • Import template in load order for onboarding
Explore

The modules

Every screen, from the first plan to the live estate.

Plan, build, operate and govern: each stage has its own screens, and every one of them reads the same estate model.

Architecture

One collector per site. One model for the estate.

Read-only southbound, outbound-only from the site, and the same REST contract the screens use for your own tools.

Inside your datacenterread-only · no inbound ports
  • BMS · UPS · PDUs · metersBACnet · Modbus · SNMP
  • CRAH · CDUs · sensorsBACnet · Modbus
  • Routers · switches · opticsSNMPv3 · gNMI · syslog
  • Servers · BMCsRedfish · IPMI
  • GPUs · scheduler · fabricDCGM · Slurm · UFM
  • Doors · cages · CCTVPACS · VMS
On-site collectoractive + standby
  1. Read each source with a read-only role
  2. Normalise alarms; keep source and time
  3. Buffer when the uplink drops
  4. Send outbound only, one channel
Never controls plant · never polls tenant gear
DCHelixone estate model · one alarm model · one money model
IngestOTLP · remote write · events
Storestime series · events · records
Estate modelsites → racks → devices → ports, customers, contracts
Read models
ImpactRevenueRoot causeGPUPhysicalCapacityPower economicsSecurityCompliance
Opstral AIanswers · causes · actions, approval-gated
Screens · API · eventsthe same REST contract the screens use · CloudEvents
Your systemsthe module that owns a record stays its system of record
  • ITSM · incidents, changes, tickets
  • CRM · customers, contracts, notices
  • IPAM · DNS · DHCP
  • SIEM · OCSF events
  • Your tools · REST API v1 · webhooks · Kafka
Runs where your data must liveOn-premisesYour cloudAir-gappedYour identity · OIDCEmbedded in your portal

Design principles

Rules the whole product keeps.

Six decisions that hold on every screen, so a figure, an alarm or a record means the same thing wherever it appears.

  1. 01Counts are derived, never typed inEvery number comes from the entities behind it, so the same figure reads the same on every screen.
  2. 02An alarm counts only where it belongsSite, edge, dependency or downstream. Downstream symptoms appear under the incident that caused them.
  3. 03One issue per impacted serviceEach service is charged to its most severe cause, so money reconciles across issues, customers and sites.
  4. 04Health shown calmlyLEDs, beacons, halos and chips. Red and amber are used only for faults.
  5. 05Every record change has a change requestStandard pre-approved work, an open CR at the site, or a new one raised for approval.
  6. 06The platform module owns the recordCRM, ITSM, inventory and projects stay where they are. DCHelix builds what is datacenter-specific.

Questions answered

How is DCHelix different from DCIM?

A DCIM keeps asset records and plans space and power. DCHelix keeps those records too, under change control, and adds live operations on top: alarms scoped to the site, incidents with affected customers and revenue, power economics, security and compliance evidence, all on one estate model. It can import your existing DCIM.

How does DCHelix work with the systems we already run?

The system that owns a record keeps it. CRM, ITSM, inventory and projects stay where they are, and DCHelix reads and writes them through their APIs. DCHelix builds only what is datacenter-specific, such as the facility, GPU, money, planner and DCIM models, so no record is kept twice.

See your own estate in it.

Bring the fault your team keeps dealing with. We walk it end to end on a demo estate shaped like yours, then agree what a one-site pilot should prove.