Release verification
Every Vidai release is signed. Verify before you run.
A public signing key lets you confirm that a download or a container image came from us and has not been altered. The mechanism today is cosign; the principle does not depend on the tool. This page is the canonical entry point.
Our public signing key
The canonical URL, in plain text.
https://vidai.uk/.well-known/cosign.pub If anything tells you the Vidai signing key lives somewhere else (a tweet, a GitHub gist, an email from us), that thing is wrong. The only canonical location is the URL above on this domain.
Key fingerprint, SHA-256
A second trust anchor.
0eba bf29 90d8 0953 8326 9054 a9dc ed58 a604 3608 9974 1abd 9b16 a88a 87b4 631c Computed over the DER form of the public key, the same form openssl and cosign print. Reproduce with:
openssl pkey -pubin -in cosign.pub -outform DER | openssl dgst -sha256 How to verify
The principle is the same; the command lives with the artefact.
The exact commands live with each product's install guide in the docs, because a download and a container image are each verified slightly differently: Control room and VidaiMock. Those commands are the authoritative ones, not a command on this page.
The principle is constant. In every case:
- 01Fetch the public key from the canonical URL above.
- 02Confirm its fingerprint matches the value on this page.
- 03Point your verification tool at the key and the artefact you downloaded.
- 04Run the command from that release's install guide in the docs.
- 05Accept the artefact only if verification succeeds.
Coverage and rotation
What this key signs, and how it changes.
Coverage today
What this key signs
As of Control room 1.0.0-rc.1 (November 2026), this key signs the Control room Community release download and the container images it runs, and VidaiMock's Docker image, tarball and binary. Each install guide lists exactly which files are signed and how, so you can always confirm whether the artefact in your hand is in scope.
Key rotation
The URL is stable; the key behind it can change
If we rotate the signing key, the URL above stays the same, the bytes behind it change, and the new fingerprint is published on this page. Downstream tooling should fetch the key fresh per verification rather than cache it indefinitely. If caching is unavoidable, expire on a short TTL.
Rotation events also appear in the security.txt file alongside the contact details.
When in doubt
Email us.
If a key, fingerprint, signature or artefact looks wrong, or if you can't find the verification step for an artefact you have, email [email protected]. Coordinated disclosure terms and the latest contact details are at /.well-known/security.txt.
How we start together
Start with one team, on your own AI traffic.
- 01
Pick one app or team
Point it at the Control room. One configuration change; nothing else changes.
- 02
Watch for two weeks
Every call priced, checked and recorded. Rules start in observe mode.
- 03
See the evidence
What it cost, what it caught and what it would have stopped, from your own traffic.