The Attestation Subject
A signed statement has to say what it is vouching for. The attestation subject is that identity anchor: the name the proof is bound to, so you can confirm the evidence belongs to the workload you meant to run. Each backend has its own way of naming the workload it sealed. Nito normalizes everything else, and surfaces this difference in the result rather than hiding it.Where Backends Differ
None of this changes what the proof means. It changes how you read the fields.
What Stays the Same
Whichever backend served the call, the evidence flows through the same attestation pipeline, the same seven-gate baseline, and the same result shape. The verify-yourself path applies unchanged. In the result, a proof-format label tells you which backend produced the evidence, and a subject field, where present, carries the name the proof was bound to. Read the fields on the result you actually received rather than assuming a fixed shape. Which backend serves a given model is discovered at runtime and reported per model, so read it from the model’s own attestation metadata rather than a static list. Each model is served by exactly one backend, so there is never ambiguity about which format applies.Related Resources
Attestation Pipeline
The flow every backend feeds into.
The Seven-Gate Baseline
The checks that run regardless of backend.
Verify It Yourself
Completing the hardware verification.