# Limits and what is not built

Where Vraelis Contour stops today. This is the same status the rest of the site uses.

**Working in the experiment**

- Signed release and approval bindings
- Runtime policy enforcement: ONNX Runtime 1.23.2, CPUExecutionProvider only
- Real CPU inference on the approved bytes
- Desired against reported loaded observations, in baseline and reconcile modes
- A read-only evidence app over the recorded trace

**Being built**

- A Kubernetes collector (proposed in specification v1.3)
- Heartbeat freshness for runtime reports
- Live fault runs
- A latency study
- Adapters for customer runtimes

**Not claimed**

- Hardware attestation
- Customer deployments or adoption
- Certification or regulatory compliance
- Pricing or general availability

## Not built yet

| Item | Where it stands |
| --- | --- |
| Kubernetes collector | Proposed in specification v1.3. Not applied. |
| Heartbeat freshness | Not built. Nothing checks that a runtime is still reporting between observations. |
| Live fault runs | Not built. The captured run is one scripted sequence. |
| Latency study | Not built. There are no latency measurements. |
| Customer runtime adapters | Not built. The experiment supports ONNX Runtime 1.23.2 on CPU only. |
| Hardware attestation | Not built, and not claimed. |

## What the evidence does not establish

- How a model behaves, or that it has no backdoor. A signature endorses bytes; it does not describe behaviour.
- What a compromised host is running. The host and worker are trusted in the experiment, and the loaded identity is a self-report.
- Production readiness. The 133 passing tests (runtime rejection-diagnostics revision) measure automated behaviour inside the experiment.
- Customer demand. No customer has used Vraelis Contour.
- Anything about machines in the field. The model is synthetic, and the runtime is a CPU session in a lab environment named `non-actuating-lab`.

## What Vraelis does not claim

- Customers, adoption, or a partner endorsement of Vraelis Contour.
- Certification, regulatory approval or compliance with any standard.
- Pricing or general availability.
- Deployments in defense, critical infrastructure or government.
- Accuracy or detection numbers.

## Product access

Vraelis Contour is not for public use; it is built for release, platform and security engineers at suppliers and system integrators. There is no public API, command line tool, console or account. The internal automated testing tooling used for the experiment is not a customer developer platform.

To talk about Vraelis Contour, use Join us, which leads to the contact form. [Join us](https://vraelis.com/contact?topic=contour)

The development status page keeps the same lists in one place. [Development status](https://vraelis.com/contour/status)

---

Vraelis documentation, Products. https://docs.vraelis.com/limits