# Suppliers and integrators

Release, platform and security engineers at suppliers and system integrators.

> **Intended, not deployed.** Intended application areas. Vraelis has no customer deployments in them.

## You ship it. Someone else runs it.

### The release lands in their system

Your signature does not grant permission to change it.

### An unexpected release creates risk

For both sides, even when nobody intended harm. A baseline kept on purpose is not an incident.

### Both sides need the same record

Not a deployment log only one of you sees.

> **Hypothesis.** These teams meet this problem first. We are testing it.

## The workflow, in this area

1. Identify the release.
2. Bind approval to the release and destination. Release authorization may need two approvals: the supplier's and the operator's.
3. Integrate with a supported runtime.
4. Compare approved and reported.
5. Preserve discrepancies, missing evidence and recovery. Both sides start from the same deployment evidence.

![Release cpu-2 in Vraelis Contour with its identity digests and approval.](https://vraelis.com/v8/contour/app-release-cpu2.webp)

*Read-only evidence app, inside the controlled ONNX reference experiment.*

## Not claimed

- No customers or deployments, and no partner endorsement of Vraelis Contour.
- No pricing or general availability. Not for public use.
- No certification.
- No hardware attestation. Runtime identity is a worker self-report.

- [Suppliers and integrators on vraelis.com](https://vraelis.com/applications/integrators): The page this summary comes from.
- [Model integrity](https://docs.vraelis.com/model-integrity): Related research.
- [Security evidence](https://docs.vraelis.com/security-evidence): Related research.
- [Machine trust](https://docs.vraelis.com/machine-trust): Related research.

---

Vraelis documentation, Vraelis. https://docs.vraelis.com/integrators