Kolibri only reads. It does not change firmware, configuration, or workloads, so it can run on production fleets without operational risk and without a maintenance window.
The engine
A read-only agent that earns its way onto production fleets.
Kolibri is the acquisition layer. It reads the device and the facility through standard interfaces, never writes, and transmits only model updates, so an operator can adopt it at fleet scale without surrendering raw telemetry or accepting operational risk.
Posture
Four constraints, designed in from the start.
The agent is built for the operator's constraints as much as the buyer's. Each property below removes a specific reason a data center would otherwise refuse to run it.
It runs without internet egress. In an air-gapped facility it performs local attestation and produces a signed evidence bundle that can be carried out, so isolation is not an obstacle to certification.
Raw telemetry never leaves the operator's premises. Only local model updates are transmitted to the aggregator, which resolves data-sovereignty concerns at the level of architecture rather than policy.
Lowering operator resistance is not a courtesy. It is what makes fleet-scale coverage achievable, and fleet-scale coverage is what builds the data that compounds into the moat.
What it reads
Standard interfaces, nothing proprietary required.
Kolibri reads what is already exposed by the device and the facility. The device interfaces give the measured condition facts; the facility power-chain connector is the only path to a real exposure signal, and it is what a GPU-telemetry-only competitor cannot produce.
Device interfaces · measured condition facts
Device telemetry
NVMLDCGM
ECC and Xid counts, retired and remapped pages, spare rows remaining, throttle, clock, and power-stability reads.
Platform management
BMCRedfish
Out-of-band platform state and thermal history, independent of the host operating system.
Vendor attestation
SPDMnvtrust / NRAS
Device-unique ECC-384 identity, VBIOS verification to detect re-flashing, and a RATS-compliant authenticity check, with an air-gapped local path.
Functional test
DCGM r4burn-in
A point-in-time functional pass and an in-fleet silent-corruption functional-integrity pass or fail.
Architecture
Gradients leave the building. Raw data does not.
The data-sovereignty boundary is the whole design. The agent computes a local model update on the operator's own hardware and transmits only that update to the aggregator, which combines updates into a federated global model. The global model improves without any operator's raw telemetry ever being centralized, and every certificate it produces is bound to the unit's permanent identity.
Operator premises Raw telemetry never leaves
DeviceNVML / DCGM PlatformBMC / Redfish AttestationSPDM, nvtrust FacilityPower-chain, SNMP / Modbus
Kolibri read-only agent EmitsLocal model update, gradient only gradients leave raw data stays
Voltry aggregator Federated global model Bound to identityPer-unit certificate Why this is the moat, not just a feature
An operator that will not share raw telemetry will still run a read-only agent that keeps its data in-house. That is what unlocks fleet-scale coverage, and fleet-scale coverage is what produces the two data assets no public dataset contains: paired facility-power-to-outcome records, and per-unit serial-level Hopper-and-newer lifetime records. Because history can only be built forward and cannot be backfilled, early coverage compounds into a record no later entrant can reproduce.