Three operational models. One enforcement engine.
The same kernel-level enforcement runs in all three. What changes is where it runs, who reviews an escalation, and what it can prove afterwards.
The Local Node.
A host-level daemon for engineers building and testing autonomous agents securely on local hardware.
- DeploymentLocal host — no account, no sign-in
- PlatformLinux, WSL2, macOS
- EnforcementeBPF + seccomp on Linux; proxy + shell interception on macOS
- Human reviewYellow Lane: Allow / Block / Pause, agent frozen while you decide
- EscalationOperator decision only
- TelemetryNone (zero data egress)
- Audit trailLocal Observatory and terminal log
- Policy managementLocal JSON/YAML, hot-reloaded
- LicenseAGPL-3.0
The Advanced Node.
A licensed build for engineers running agents against production. Adds multi-model consensus review, signed audit receipts, and SIEM export. Licensed per engineer — a team runs it today by buying one each.
- DeploymentLocal host — hub licence check at startup
- PlatformLinux, WSL2; macOS (Apple Silicon) via proxy + shell interception only
- EnforcementSame, plus a built-in policy floor a role cannot override
- Human reviewYellow Lane: Allow / Block / Pause, agent frozen while you decide
- EscalationJury of Rivals multi-model consensus
- TelemetryLicence check only — no event upload
- Audit trailEd25519-signed AARM receipts, export to 8 SIEM targets
- Policy managementLifecycle hooks, named sessions, --accumulate
- LicenseAGPL-3.0
The Steel Vault.
Fully sovereign deployment for regulated industries. Cryptographically verified policy enforcement mapped to the EU AI Act and ISO 42001, with one policy source of truth across the fleet.
- DeploymentVPC or air-gapped, against a private self-hosted hub registry
- PlatformLinux, WSL2; macOS (Apple Silicon) via proxy + shell interception only
- EnforcementSame floor, rolled out fleet-wide from one policy source
- Human reviewYellow Lane: Allow / Block / Pause, agent frozen while you decide
- EscalationJury of Rivals multi-model consensus
- Telemetry100% on-premise
- Audit trailCompliance documents compiled into policy; custom retention and export
- Policy managementSigned policy artifacts verified against a pinned public key, synced fleet-wide
- LicenseAGPL-3.0
Where the line falls. Below a handful of engineers, Pro is the answer: one licence each, every node enforcing its own policy locally. You have outgrown it the moment policy stops being a per-machine file — when the same rules have to be signed once and synced fleet-wide, pulled from a registry you host, or evidenced against a framework. That is Enterprise, and it is a conversation rather than a checkout because the deployment shape — VPC, air-gapped, on-premise hub — is the thing being priced. If you are somewhere in between, say so and we will tell you which side you are on.
Ask which side you are onStill deciding which model you are?
Lite is free and takes about a minute to install, so the cheapest way to answer that is to run it. If the deployment shape is the question — fleet-wide policy, a hub you host, evidence against a framework — that is a conversation rather than a checkout.