Cerebro builds the layer between an AI agent and anything that matters. A policy gate before the action. A rollback path after it. A record a reviewer can check. A person who approves. We run our own company on it every day.
A deterministic gate checks each consequential action before it runs. The rules are code, not a prompt.
Every change keeps a way back. Records are superseded, never overwritten.
Each decision lands on a hash-chained, append-only ledger. A reviewer can check it without trusting us.
Unusual actions wait for a person. Risky ones are blocked before anything moves.
An independent checker gates every material step. No work counts as done on the worker's own word.
Agents run where you can see them and switch them off.
Your AI. Your machine. Your rules.
Drive a captured run. Ten payment requests: some allowed with a receipt, some held for a person, some blocked before a dollar moves. Every decision reconciles across policy, ledger hash and payment receipt.
Open the demo → White paper v2.3SHA-256 sums, a verification guide and a public slice of our evidence ledger.
Read and verify → Open source · Apache 2.0The spend gate itself: a policy gate, a hash-chained ledger and human approval.
View on GitHub →Agent systems for document, capture and operations work, built on the four guarantees above. Includes specialist models fine-tuned on owned hardware and tested on held-out exams the model never saw in training.
Local inference on your hardware, with a profile that runs disconnected.
We run our own company on the same platform, every day, before anyone else does.
Delivered alongside: cybersecurity and compliance (NIST SP 800-171, CMMC, Zero Trust), cloud architecture and security on AWS, and incident response.
A Brain that remembers your work, session rituals that open and close each day, and skills you can read. It runs in Claude Code, in local files you own. Version 0.3.0 alpha, no servers.
Your AI. Your machine. Your rules.
Short explainers: what we build, why it is different, and how to start. No sign-up.
What operator-owned AI means, and why owning your memory and your rules beats renting a hosted assistant.
Read → 02How memory, skills and routing layer on top of Claude Code, and what Libro adds over bare Claude Code.
Read → 03Most AI forgets you when you close the tab. See how Libro keeps your context in local files you own.
Read →Short notes on what we build, what breaks and how we fix it. New subscribers get the Libro starter install guide.
No spam. Unsubscribe anytime.
Building along with us? The AI Build Room is on Skool.
Questions about a governed AI deployment, teaming, or Libro? Send a note. We reply within one business day.
Tell us what you are working on.