biclave

No agent acts on one key.

An AI from a different company checks every action. Your people countersign. Then it runs.

Claude · AnthropicGPT · OpenAIGemini · GoogleGrok · xAIGitHubAzurePaymentsMicrosoft 365key oneClaudekey twoGeminimergedeploypayemailillustration · two keys, never from the same company, then yours
independent by design

Two keys. Two makers. Always.

An AI checking work from its own company can share the same blind spots. So Biclave always asks a different company's AI to check.

  • Key one is the AI that does the work. Key two is an AI from a different company that checks it.
  • Biclave never lets a company check its own AI's work. It is a rule in your charter, not a setting.
  • Every pairing is recorded, so an auditor can see which AI built a change and which one checked it.
key one · does the work
ClaudeAnthropic
key two · checks it
…choosing a checker
Claude finishes a change

illustration

how the keys work

Two independent keys. Then yours.

The agent that builds is never the one that checks. Follow one change through Biclave.

change #128 · commit f63e5ee95dd9opened
key one

The builder

An AI coding agent plans and builds inside a sandbox. Your checks run against exactly what will be committed.

key two

The independent verifier

A model from another vendor reviews the exact commit. Its verdict is bound to the bytes it read.

you

Your countersign

Nothing is accepted on one key. You approve the exact change, and a veto window stays open.

agents that act on their own

Your agents work all night. Nothing consequential should happen on one key.

AI agents are starting to pay suppliers, email customers, share files and change production. The same rule applies to every one of those actions: an AI from a different company checks it, and the right person approves it.

ask first

Agents ask before they act

A consequential action waits for the two keys before it happens, not a review after the fact.

one approval

One approval, one action

An approval covers one exact action. It cannot be stretched to cover anything else.

keys apart

Never the same company

The AI that checks an action never comes from the company whose agent wants to take it.

Talk to us about the agents you run →

illustration

trust and evidence

Every step leaves evidence you can check.

Show an auditor who built a change, who checked it, who approved it, and the exact bytes each one saw.

D-0001 · acceptanceexample

Codex returned PASS FOR THIS GATE and the acceptance rule holds. Accept the package?

key one head f63e5ee95dd9 · built in a sandboxkey two verdict PASS · bound to packet f63e5ee95dd9charter approved by hash 4d342141019b
Type exactly: I decide accept for D-0001
sealed · events.jsonl
sha-256

A charter approved by hash

Change a rule, a template or a line of code, and Biclave stops acting alone until you approve again.

two makers

Builder and checker kept apart

Key one and key two always come from different companies, and the pairing is recorded.

bound

Approvals bound to the change

An answer applies only to the exact decision it answered. Change the question and the approval lapses.

append-only

A sealed audit trail

Every decision, verdict and transition is recorded and chained before anything acts on it.

sandbox

Sandboxed agents

Agent steps run in the operating system's sandbox behind a command guard. Secrets never reach the logs.

stop

It stops itself

Stop rules, daily budgets and a bounded shutdown. When something is off, it asks instead of guessing.

Governance built into one vendor's agent checks that vendor's work, by that vendor's rules. Biclave keeps the keys apart.

early access

Put a second key on your agents.

Biclave is in early access with a small number of teams. Tell us which agents you run and the controls you need, and we will show you Biclave on your own work.

Request early access