Skip to content

Works alongside the monitoring you already run

DC Sim does not replace your monitoring or DCIM. It places their data on the rack, PDU or cooling unit it belongs to and lets you fail things. Zabbix and NetBox connect directly: paste a URL and a read-only token, press Test, preview, import. Every other tool reaches the twin today as an export through the template sheets.

Status, tool by tool

ToolStatusToday
Readings sheet (any tool's CSV export)Availabletime, item, metric, value: metric history from any monitoring tool, fitted to the twin.
ZabbixAvailableTested against a live Zabbix 6.0 demo instance (1,417 hosts) with a read-only token. Zabbix 6.0 and later.
NetBoxAvailableImport from NetBox: tested end to end against a live NetBox 4.7 demo instance (24 sites). Two-way sync and a NetBox plugin are on the roadmap.
Grafana and PrometheusRoadmapGrafana CSV exports today. Prometheus collector: built into the agent, not yet tested against live exporters. Grafana panel: roadmap.
SolarWindsRoadmapCSV today: export nodes and metrics from SolarWinds → map to the DC Sim sheets → import; read-only connector on the roadmap
ManageEngine OpManagerRoadmapCSV today: export inventory and monitor values from OpManager → map to the DC Sim sheets → import; read-only REST connector on the roadmap
Sunbird dcTrackRoadmapCSV today: export cabinets, items and circuits from dcTrack → map to the DC Sim sheets → import; read-only REST connector on the roadmap
PRTGRoadmapCSV today: export devices and sensor values from PRTG → map to the DC Sim sheets → import; read-only API connector on the roadmap
CloudSinoPartnerCloudSino distributes the Chinese-language edition of DC Sim; CloudSino DCIM exports are a CSV data source for the Sensaka edition today; live connector on the roadmap
Redfish BMCs, SNMP UPSes, Home Assistant, Proxmox, GPU telemetryRoadmapConnectors are built into the agent and are not yet tested against live systems. Readings sheet today.
BMS (Modbus, BACnet) and fire panelsRoadmapReadings sheet today.

How a connector works

  1. Connect: open ⋯ → Connect NetBox or Zabbix, paste the URL and a read-only API token, press Test. The test shows the version and what it can see (sites, racks, devices, cables; or hosts, items, problems).
  2. Preview: the result is rendered as the template sheets (Devices, Cables, Racks, Power, Networks, Readings) with the same import report and checks as an Excel upload.
  3. Import: confirm, and the twin is built or updated. Re-sync works like a re-upload: you see a change list first.

For a system inside your own network, the same connector runs in a small outbound-only agent; tokens never reach the browser.

For tool makers

If you make one of these tools: we read, we never write without opt-in, we name you on your integration page, and we want to be listed where your users look for integrations. See the partner program.

Questions people ask
Which integrations are live today?

Zabbix and NetBox: connect with a URL and a read-only token, preview, import. Both were tested against live demo instances. Every other tool reaches DC Sim as an export through the template sheets; their live connectors are on the roadmap.

Will the connectors need inbound access?

No. Live data will come through a small agent inside your network that only dials out over one WebSocket and never listens on a port.

Will DC Sim write anything into my tools?

No. Reading comes first. Exporting a design back as planned inventory is on the roadmap and will be opt-in per tool.

My tool is not listed. Can I still use it?

Yes, through the Readings sheet (time, item, metric, value) and the inventory sheets. Tell us which tool you run; connectors are built in order of demand.

One Excel file. Your room in 3D.

Fill in the Devices sheet and send it with your walkthrough request; we import it on the call. What each sheet does