Trip a contained agent on your own machine.
Design partners get one signed build for Linux. In about ten minutes, a demo agent goes past its quota, the breaker kills it, a relaunch is refused, and you check the signed evidence with an open-source verifier. It needs no API keys. We send builds on request, not as a public download.
Linux x86_64. Tested on Ubuntu 26.04, Ubuntu 24.04 under WSL2, and Debian 13.
Release signing key
Every build we send is signed with one Ed25519 key that we keep offline. Before you run it, check that this fingerprint matches the one in the public repository's README. This page and the README are two separate places, so a change to one would show up as a mismatch.
SHA256:yp+kIpuLgQ9ENakbk0Sm0y3uSf2WYW4NhtaqT+BRcT4
The full key, as the allowed_signers line that OpenSSH uses to check a signature:
release@cybercircuit.ai namespaces="cybercircuit-release" ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIBFu0A1fDzovoVloCtVVa424IDdQRDILbFqm8WosiOhT
If we ever replace the key, the new one will be announced here and in the README, and signed by this one.
How access works
Tell us what your agents do and what they can touch. If Cyber-Circuit fits, we send you the signed build, its checksum file and signature, and the quickstart. The quickstart starts by checking the signature against the key above, then runs the demo and verifies the evidence.
The verifier is open source in the public repository, so you can check evidence bundles without the build.
What's in the build
| File | Licence |
|---|---|
circuitbreaker: the gateway, sandbox launcher, and evidence tools. One static binary. | PolyForm Internal Use 1.0.0 |
cybercircuit-verify: the open-source evidence verifier, written from the published bundle format. | Apache-2.0 |
| Quickstart and guide, including how to run Claude Code, Codex CLI or Gemini CLI inside it. | Apache-2.0 |
PolyForm Internal Use lets your organisation use the gateway for its own internal operations, free and with no time limit. You can't redistribute it. It comes as is, with no warranty.
We installed the build on a freshly created machine, following only the quickstart: it took about six minutes from the first command to an independently verified evidence bundle.
Before you rely on it
- Linux on x86_64 only, and only the three systems above have been tested.
- Run it on a test machine or VM first. The agent can change anything in the workspace you give it.
- Receipts stay on the same machine unless you set up off-host delivery. The public transparency log shown on Lab results is not configured by the quickstart.
- The post-quantum signature library is a pinned pre-release that has not been independently audited.
- An evidence bundle shows what the gateway recorded and signed. It is not proof of compliance.
Running agents with real tool access?
We're looking for a few design partners running coding agents on Linux. Tell us what your agents can touch, and we'll tell you honestly whether Cyber-Circuit fits yet.