instibrain
Sign in

One brain.
Every AI you hire.

Connect any AI to one brain that knows your company — and that you own. The whole product, in five steps.

Walk the five steps → How it works

Five steps, one screen each.

three parts, one rule

Four things to know before the walk.

Two of them we build, one is yours already, and the last is the only decision the server ever makes.

The brain

The store your company owns. Every page sits in the area you choose: the one we read, or the one we hold as ciphertext.

The sync client

Runs on each device. It adopts, materializes, syncs and captures conflicts — and it holds the keys to a secure area.

The agent

The AI you already pay for — Claude Code, Codex, Cursor, ChatGPT, any MCP client. You bring it; the brain makes it yours.

One rule

The server refuses to guess. Concurrent writes get a 409, and your device merges.

the walk

Five steps, start to finish.

One page, from a file on your laptop to an answer from your AI. Each step is one screen, and each one is the real shape of the thing.

  1. 1

    The file on your laptop.

    A page is a markdown file in a folder you already have. The sync client adds a short header — an id, a scope, a key id — and nothing changes about how you write it.

  2. 2

    The sync.

    Save, and the sync client pushes the node. When two devices edited the same page, the server answers 409 and writes its copy beside yours; you merge, then push with instibrain resolve. The server holds ciphertext, so it never guesses.

  3. 3

    What our server stores.

    A secure-area page reaches us as ciphertext, path included; we hold the bytes and cannot read a word. An open-area page is stored as markdown, so a surface holding no key can still read it.

  4. 4

    Your AI reads it.

    Three lines in .mcp.json, and any MCP client — Claude Code, or whatever you use — reads your brain before it answers. Approve writing, and it edits too.

  5. 5

    Who else can read it.

    Every page carries one setting: its area. In the open area, every connection you approve reads every page. In the secure area, a scope decides which devices hold the key, and nothing else opens it.

what it is made of

The protocol, the crypto, and the words.

Every term on this band has one meaning on this site. Hover to hold the band still.

409 on conflict version vectors MCP over Streamable HTTP HTTP sync at /v0 per-node accept two areas, two transports three lines, no SDK
secure area encrypted on your device secure-area paths are ciphertext sizes are bucketed ChaCha20-Poly1305 X25519 + ML-KEM-768 a signed reader chain post-quantum key wraps no third-party crypto
brain — the store you own sync client — runs on your machine agent — the AI you bring node — one unit of memory area — who can read the page scope — who it is shared with materialize — nodes into files

Connect any AI to one brain that knows your company — and that you own.

Read the mechanism, or the security model with its limits stated.

See how it works → Read the security model