Production drivers, not plugin scaffolding. Each one is configured through maps in the admin interface, no code, no redeploy, no vendor engagement.
Discrete transitions, a coil flipping, a BGP session dropping, a binary HVAC point changing state, become events in the same stream as threshold breaches and statistical anomalies.
Rack servers, blade systems, storage, liquid cooling. Aligned to DMTF 2025.x, and re-exposed northbound as a compliant aggregated service root.
Out-of-band management for the fleet that predates Redfish, and it is always a larger share of the estate than the refresh plan assumes.
GPU cluster telemetry into the same alarm and health surface as the rest of the facility. No agent change on the node.
The scheduler is infrastructure. Cluster assets are first class, and job-to-node assignment is a platform relationship the driver owns.
A GPU node under a running training job is hot, loud and fully utilised by design. Workload state suppresses the anomaly penalty so health scores stay meaningful, while hardware faults continue to fire at full priority.
The streaming successor to SNMP for modern network gear, now production standard across every major platform.
Status flips on admin state, oper state and BGP sessions raise events the moment they happen, no polling overhead to detect them.
The lingua franca of the facility floor. UPS, PDUs, cooling, generators, power meters and industrial PLCs from any vendor.
DMTF Redfish 2025.2 formally added Modbus target and connection-method modelling to the standard. This platform was already built that way, Redfish BMC aggregation and Modbus facility integration behind one northbound API.
Smart PDUs, environmental sensors, energy meters and BMS gateways, anything already publishing to a broker.
Topics carrying pure discrete signals rather than physical units automatically emit status-change events on transition, so a contact closure is an event and not a number nobody reads.
The long tail. Everything in the estate that will never speak anything newer, still on the same alarm surface as everything else.
Past the server room door: chillers, air handling units, VAV boxes, cooling towers and the BMS gateways in front of them.
A pack bundles a driver, a JSON schema for its configuration and UI hints. Upload it, and the platform writes the source, imports it and registers it in the live protocol registry, no restart, no release train. The SNMP driver ships this way, which is how we know the path works in production.
Every published version is immutable, and operators choose which is active per asset type.
Roll back to a prior version from the admin interface when a map change misbehaves.
Pack upload is restricted to the platform-operator tier above all tenant accounts.