Supply integrity

Verify what you were sold.

Any supplier can be compromised, and no vendor's assurances survive contact with a determined problem. The only durable answer is that the customer can check. So this page is not a promise that nothing is wrong — it is the list of checks that tell you whether something is.

Three things you can verify yourself

The hardware you received

Serial number against the manifest we shipped, firmware hash against the image we published, and boot attestation where the board supports it. If the unit was intercepted, reflashed or substituted, the hash will not match.

ngari verify hardware --serial <S> --firmware-sha256 <H>

The weights you run

Every model we ship carries the licence it was released under and the checksum of the exact checkpoint. An Apache-2.0 model cannot be revoked from you, which is precisely why we prefer them. A model we cannot verify the licence for is a model we will not promise.

ngari verify weights --model <name> --sha256 <H> --licence <L>

What the software did

The receipt chain records every consequential action with a hash linked to the one before it. You can recompute the chain and detect a gap. A log you can recompute is evidence; a log you have to trust is a story.

ngari verify receipts --chain <file>

How we handle a vendor under question. We separate shipping from promising. A component whose supplier is under an unresolved integrity question still ships if it passed inspection — but we will not forecast supply or capability on it, and we will not repeat an allegation we cannot source. A shipment is an operation. A promise is a forecast. Only the forecast is gated by an unverified question.

What we will not do

We will not name an individual or a company in connection with an unverified allegation, including in a sales conversation. We will not imply that a competitor's product is compromised to win a deal. And we will not claim our own chain is clean because we have not looked — the checks above exist because looking is the job.

If you find something

Write to security@ngari.ai. A mismatch is a defect, not a support ticket, and it gets a dated record and an owner. If the finding is in our supply chain rather than our code, we will tell affected customers what we know, what we do not, and when we will know more.

This page is a verification procedure, not a legal opinion and not a statement about any third party. What the AI itself can and cannot be relied on for: limits & liability. Where the data goes, lane by lane: privacy.