Skip to content
Vraelis homeDocs
Join us

Critical infrastructure

View as Markdown
Join usMeet Vraelis Contour

In energy, water and communications, vendors ship models into systems operators own.

Intended, not deployed

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

The vendor ships it. The operator runs it.

Releases cross operators

Both sides need to know which release is running.

An unexpected release is a security and operational risk

A change to an operational system, to be reviewed as one.

The change record needs the model

What was approved, for where, and what the runtime reported.

The workflow, in this area

  1. Identify the release.
  2. Bind approval to the release and destination. Destination-bound approval: one site's approval does not cover another.
  3. Integrate with a supported runtime.
  4. Compare approved and reported.
  5. Preserve discrepancies, missing evidence and recovery. Deployment evidence kept for the operator's change process.
No loaded report is available for this observation.
Read-only evidence app, inside the controlled ONNX reference experiment.

Not claimed

  • No deployments with utilities or other operators, and no customers.
  • No integration with control systems or operational technology networks.
  • No replacement for an operator's change management or protective controls.
  • No certification or regulatory compliance.
  • No hardware attestation. Runtime identity is a worker self-report.
Critical infrastructure on vraelis.comThe page this summary comes from.ReadSecurity evidenceRelated research.ReadMachine trustRelated research.ReadModel integrityRelated research.Read

Last updated: October 12, 2026