Skip to content
Join us
Autonomous systems

AI security for autonomous systems.

Robots and vehicles get model updates in the field, often from a supplier.

Join usVraelis Contour
An industrial robot arm inside a manufacturing cell.

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

Why it matters

Models ship to machines in the field.

Updates land in someone else's fleet

In a facility or fleet the supplier does not operate.

The wrong release is a security event

A different release, or the wrong machine, changes what it does.

The first question is which model

When a machine surprises you, the answer should come from a record.

HypothesisRobotics is one segment we study. Release and platform engineers at robotics suppliers and integrators meet this problem early.

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

    Destination-bound approval: one machine's approval does not cover another.

    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

    A version mismatch shows as reload pending, not assumed.

    Working in the experiment: evidence app

  5. Preserve discrepancies, missing evidence and recovery

    Working in the experiment: recorded observationsProposed: investigation workflow
Approved cpu-2 beside reported loaded cpu-1, with the differing fields marked.
Read-only evidence app, inside the controlled ONNX reference experiment.
Limits

What we do not claim.

  • No deployments on robots or vehicles, and no customers.
  • No robot or vehicle integration. The experiment is a synthetic ONNX CPU workload.
  • No protection against adversarial inputs or perception attacks.
  • No certification, and no evidence freshness for machines in the field: heartbeats are not built.
  • No hardware attestation. Runtime identity is a worker self-report.
Development status

Related research

Electronic components on a circuit board.Model integrityAn engineer inspecting or repairing a circuit board.Adversarial threatsEquipment and workstations in an engineering laboratory.Security evidence

Build stronger evidence for model releases.

Join us in building Vraelis Contour.

Join usDevelopment status