How it works
An AI action can only run if FinalBoss has already signed a receipt allowing it. Not a log written afterward. A key issued before.
01 · Where it sits
Underneath the AI. Not beside it.
FinalBoss runs at the operating system, on your hardware. The AI never holds the key, so it cannot talk its way past the gate.
02 · The receipt
What's on a receipt.
1 Who asked. The agent's identity, not its word for it.
2 What exactly. The action and its target, down to the account.
3 The authority. The permission on file that allows it, or none.
4 The decision. Yes or no, written before anything moves.
5 A link to the last receipt. Delete one and the chain breaks.
6 Two signatures. Classic plus post-quantum. Anyone can check them offline.
03 · One action, start to finish
Ask
The AI asks to act.
Check
Authority checked for this exact action.
Receipt signed. Nothing has moved yet.
Run
Only now does the action happen.
Seal
Permission removed. Final receipt signed.
04 · Fail-closed
When in doubt, nothing runs.
05 · Where it runs
Your kernel
Bring your own kernel. On-prem, air-gapped, or your own cloud.
Your keys
You hold the signing keys and the receipts.
Verified chips
AMD SEV-SNP and NVIDIA H100 confidential computing.
Post-quantum
Ed25519 plus ML-DSA on every receipt.
Before you go live
BEAST finds what would have gotten through.
BEAST runs your agents against thousands of off-limits actions before production and shows what was blocked, and what was only logged.