Fail-closed broker
Destructive actions — delete, overwrite, deploy, spend — are blocked by default. If the broker is unsure, the answer is no. The AI never gets raw access to your shell.
Software · beta
ORA is a governed AI operator. Its security broker physically can't delete, spend, or send anything without your yes — and every action lands on a tamper-evident audit chain. We run 3D3D's own operation on it every day.
ORA is a local-first governed AI operator. A fail-closed security broker sits between the AI and your machine: destructive actions are blocked by default, anything risky becomes a plain-English proposal you approve or reject, and every action is written to a hash-chained, signed audit trail. Your hardware, your rules, your keys.
The broker sits between the AI and your machine and enforces the floor in deterministic code — not a prompt the model can be talked out of.
This is the actual approval queue from the workspace we run 3D3D on. Every risky action answers five plain questions and then waits for you — staged here with synthetic data, never a real client detail.

Destructive actions — delete, overwrite, deploy, spend — are blocked by default. If the broker is unsure, the answer is no. The AI never gets raw access to your shell.
Anything risky becomes a proposal: what it is, why now, what happens if you approve, what it touches, whether it can be undone. Nothing moves without your yes.
Every action lands on a SHA-256 hash chain with Ed25519-signed records. The log can only ever grow — a rewrite breaks the chain and is caught.
The exfiltration floor: the governed shell can work on your files without reaching the internet, so a hijacked command can't ship your data off the box.
Re-measured against the running system. No cloud hop, no per-token billing, no model in the security path — the floor is deterministic code.
The A0–A5 ladder sets how much ORA may do on its own before it must ask. Even at A5, nothing overrides the fail-closed floor — the leash gets longer, never removed.
Every panel is the ORA workspace we run 3D3D from, staged with synthetic data so no real client, lead, or inbox detail appears.

One dial (A0–A5) sets how much ORA may do alone; a hard daily cap stops it running up a cloud bill; local-only keeps every model on your machine. The fail-closed floor holds at every level.

The locked principles — like “nothing leaves this machine without intent” — can't be removed, even by you in a hurry. Below them, the internet lane stays locked so a hijacked command can't exfiltrate.

What needs you, what ORA did overnight, and honest system health — with the big red Stop-everything button one click away on every screen.

ORA researches prospects and drafts the outreach, then holds every send in the approval queue. It never emails a lead, quotes a price, or books work on its own.

Incoming mail is sorted and a reply is drafted in your voice. Nothing leaves the box until you approve it — and high-impact sends take a deliberate two-step confirm.

Jobs, invoices, and revenue in one place — the same workspace 3D3D runs its own business on, every day.

Sending to a real customer, spending real money, or touching many records triggers a second, deliberate confirm — so nothing consequential ever happens on one stray click.
A fail-closed layer any AI agent connects to. It blocks destructive commands, keeps your secrets off-limits, and logs every action to a tamper-evident trail, right on your own machine.
Apache-2.0 · works with Claude, Codex, Cursor, and Cline · no account, no telemetry.
Governed AI operator
See the full picture on ORA's own site, start free with Warden — the open-source fail-closed core — or have us wire the full governed operator into your operation.