Verify, test, and certify used GPU clusters before you buy or deploy.
The problem
The serial number is not yet a condition record.
A datacenter GPU already exposes identity, configuration, error, repair, thermal, power, utilization, and event data. Those facts rarely cross organizational boundaries in a standardized, policy-bound, independently verifiable form.
439
Signed field bundles
C0/A0 evidence bundles banked by Voltry's field program as of the VCM-1 v0.3 maturity statement.
40+
Registry identities
Software-reported A0 identities across the field program; physical-silicon continuity is not independently established at A0.
27
Sensor characterizations
Banked across four device models, measuring reported-value cadence and internal energy-signal consistency.
Evidence classes
Four evidence classes, kept separate.
A value is not meaningful until its evidence class is known. Voltry keeps hardware reads, replayable calculations, statistical estimates, and party assertions separate. Modeled evidence remains decision-inert in VCM-1 v0.3.
A fact read from hardware or an authoritative device interface.
- Model, UUID, serial, and PCI topology
- Driver, VBIOS, and InfoROM state
- ECC, row-remap, and retirement state
- Thermal, power, energy, clock, and utilization reads
- PCIe, interconnect, configuration, and vendor events
The record includes the source and capture context.
A deterministic function that another party can replay.
- Duty odometer and incident rates
- Coverage and threshold distance
- Seven non-compensatory axes
Inputs, formula version, and output travel together.
A statistical estimate with its uncertainty and calibration stamp.
- Always presented as a band
- Never used to determine a VCM-1 grade
- Explicitly marked when calibration is pending
Modeled evidence is labeled and remains outside VCM-1 grades.
A party-signed assertion, attributed to the party making it.
- Ownership and custody
- Facility assignment
- Reservation and configuration intent
A declaration is verified as signed, not promoted to a measurement.
Certificate properties
Five properties of every record.
Every claim names what it is
Measured, derived, modeled, and declared evidence stay visibly distinct. A reader can see the source and the trust boundary before interpreting a result.
Evidence states its assurance level
A0 through A3 state how strongly evidence is bound to the physical device, from host-signed self-report through platform binding and independent witness.
A scan is not a history
C0, C1, and C2 say whether the record is a point-in-time scan, functional observation, or continuous history. Coverage is never inferred from a good-looking result.
Absence is never a pass
Missing evidence produces Not Assessed, not a favorable guess. Once VGR-1 publishes, a missing required axis produces UNGRADED rather than dropping out of the minimum.
The result can be independently rebuilt
A retained verification package lets a third party check integrity, provenance, and the derivations VCM-1 and its versioned artifacts specify.
From monitoring to portable evidence
A record counterparties can retain and verify.
Operator-plane monitoring produces useful signal for the operator. Voltry's category is different: selected evidence made portable, policy-bound, and independently verifiable by an external counterparty, with the residual trust boundary stated on the record.
- 01
Trust
AttestationSchedules, periodic reports, and party assertions remain useful inputs, but they do not bind a claim to the device or make it independently replayable.
- 02
Telemetry
Raw signalVendor and operator tooling can monitor fleet health. It is designed for the operator plane, not as a portable counterparty record.
- 03
A portable record
Certified recordClassified evidence, explicit assurance and coverage, canonical signatures, and ledger proofs that a relying party can retain and verify.
- Identity strength stated on the face
- Missing evidence remains visible
- Specified derivations are replayable
- Tamper-evident history
Summary
Voltry is an evidence pipeline: read-only capture, canonical signed records, an append-only registry with a transparency ledger, deterministic evaluation, and audience-scoped views.