Skip to content
Suppliers and integrators

For teams who ship models into systems they do not own.

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

An engineer inspecting equipment in a workshop.

Intended application areas. Vraelis has no customer deployments in them.

Why it matters

You ship it. Someone else runs it.

The release lands in their system

Your signature does not grant permission to change it.

A wrong release is a security event

For both sides, even when nobody intended harm.

Both sides need the same record

Not a deployment log only one of you sees.

HypothesisThese teams meet this problem first. We are testing it.

How Vraelis Contour would apply

Five steps, release to record.

How Vraelis Contour works
  1. Identify the release

    Working in the experiment: model and configuration digestsProposed: preprocessing identity
  2. Bind approval to the release and destination

    Release authorization may need two approvals: the supplier's and the operator's.

    Working in the experiment: signed bindings
  3. Integrate with a supported runtime

    Working in the experiment: ONNX Runtime 1.23.2, CPUProposed: customer runtime adapters
  4. Compare approved and reported

    Working in the experiment: evidence app
  5. Preserve discrepancies, missing evidence and recovery

    Both sides start from the same deployment evidence.

    Working in the experiment: recorded observationsProposed: investigation workflow
Release cpu-2 in Vraelis Contour with its identity digests and approval.
Read-only evidence app, inside the controlled ONNX reference experiment.
Limits

What we do not claim.

  • 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.

Build stronger evidence for model releases.

Join us in building Vraelis Contour.