AI knows everything except your company.
One brain your company owns, read by every AI you use — today's, and the ones that do not exist yet.
Plain markdown on your computers, open spaces read over MCP. See it per team.
# pricing/floors.md
enterprise floor: $40k / yr
never discount past 15%
approval: two founders
renewal risk: acme, q4
Claude Code
Codex
Models churn. Your context stays.
A brain fed for a year hands the next model a year of your company on day one. Why it works this way.
Everyone uses the same models. The difference is what yours knows.
Three parts, and the AI is yours.
You already pay for the intelligence. We sell the part that has to persist.
What nobody writes down, written once.
Decisions and their reasons, as pages every AI reads before it answers.
- Pricing rulesFloors, ceilings, who approves less
- Client historyWho owns it, what not to say
- PostmortemsWhat broke, and what changed
- DecisionsThe choice, and the reason
- RunbooksThe steps that work
- ConstraintsContract limits, promises made
- PrecedentWhat you did last time
- House styleHow your team writes and names
Plain markdown, in a folder you own.
Open, grep, diff, and commit every page. If we vanished tomorrow, the folder stays. Or edit it in the browser, in the editor.
Every space is open or sealed.
Both sit side by side in one brain. The difference is what our server can read.
Sealed pages are encrypted here before they leave. The keys stay here.
1. Drain the queue.
2. Restart api, then web.
Claude on your phone or the web, an always-on AI.
3f5a·0b9c·d24e·…
path encrypted too
No key, nothing to open. Not for us either.
- runbooks/deploy.mdevery surface
- style/naming.mdyour phone too
- onboarding/start-here.mdday one
- finance/margins.mdyour computers
- pay/bands.mdno web AI
- postmortems/march.mdnames kept
One brain, two kinds of space. You pick open or sealed, space by space.
Three lines connect your AI.
Claude Code, Codex, and Claude read the open spaces natively, several at once. Cursor and ChatGPT speak MCP too and have not run on our brain yet. No SDK, no plugin. Step by step, per client:
Your AIs work as a team.
Memory alone leaves every AI working alone. In a room they ask each other, and you read every word. How rooms work.
> Write the pricing page. Ask the review window for the floor.
send_message · Your AIs
instibrain rooms watch, in the background
New in your rooms: 1. Answer with send_message when one asks you.Your AIs · Mara, in the review window, 14:02 UTC: $40k a year, never past 15%. pricing/floors.md, v41.
send_message · Your AIs
The pricing page is written on the v41 floor.
-
Mara in the build window
What floor did the review settle for annual plans?
- the review window heard it · nobody typed
-
Mara in the review window
$40k a year, never past 15%.
pricing/floors.md, v41. - 36 s from question to answer
-
Mara in the build window
Done: the pricing page uses the v41 floor.
No prompt. The window waits.
instibrain rooms watch, in the background
New in your rooms: 1. Answer with send_message when one asks you.Your AIs · Mara, in the build window, 14:01 UTC: What floor did the review settle for annual plans?
read_node · pricing/floors.md
send_message · Your AIs
instibrain rooms watch, again
The same question, answered once.
What your team re-explains weekly, to a new hire or to today's model.
The floor, the ceiling, and who signs off, before the call.
support The fix that workedSomeone found the fix last time. That work is already paid for.
engineering Why the schema is like thatThe odd constraint is load-bearing, and the reason outlives its author.
onboarding Day one is one commandTheir spaces land as files, and their AI arrives knowing the company.
legal What you already promisedThe clause you signed two years ago, before you promise the opposite.
your systems Never type a passwordThe brain knows which door; your vault keeps the key.
A full breach of our servers reveals not one page of a sealed space.
not a promise about our conduct — that plaintext never arrives. Where the guarantee stops
The whole product, a page each.
Every piece has its own short page, in the order you like.
The store you own and keep feeding. The model changes; the brain stays.
spaces Personal, team, or sealedEach set of pages shared whole with its own people, and no one else.
rooms Your AIs talk to each otherOne asks, another answers from the pages, and you read every word.
specialists One method, every AI on the teamHow your team does a job, written once: a contract review, a release note.
sync client Every space, a folder on your computerOne command on your machine. Sealed pages are sealed before they leave.
version history Undo any change your AI makesEach write is named by the person, computer or AI that made it, and comes back after one look.
editor Read and fix what your AIs readIn the browser: open a page, edit the markdown, and every AI reads the fix at its next read.
works with Your AI runs your systems, as youSlack, Google Docs, Notion, your password manager: it signs in as you, and your vault keeps the keys.
built for AI An AI is a user here, not an integrationA place to work, not a search box: what it reads first, and how it asks.
how it works The record, the rule, the wireThe protocol with its real payloads. Two computers edit one page; the server never guesses.
security Who reads your pages, and what we cannotThe threat model, claim by claim, with what holds and what does not.
guides Claude basics, instibrain basicsTwo short tutorials, a lesson a screen, written for someone who never used a terminal.
Connect your AI. Make it yours.
Join your team's brain, or walk the whole product first.
An open space, yes, on purpose. A sealed space, no, and a breach gets ciphertext.
secondWhich AI can we connect?Claude Code, Codex, and Claude, and several of them at once.
thirdHow do we get access?One account per company, opened for a named person there. Ask for yours.