The questions a company asks before it trusts us.

instibrain is your company's brain: pages your team keeps, read by every AI you use. The pricing floor, a client's history, the deploy runbook: each written once, in a space shared with the people who may read it, and read by your AI before it answers. A sync client keeps every page as a markdown file on your computers.

Claude Code on Mac, Windows, and Linux, Codex, and Claude on the web and the phone. Each connects to one address over MCP, the way an AI reaches an outside system, and signs in once in your browser. Connect Claude Code shows the command.

Yes. Claude Code in the repo, Codex beside it, and Claude on your phone read the same pages on the same day. Each signs in on its own, and each reads only the spaces you give it. Change the model next year, and nothing in the brain moves.

No. A current page grounds the answer, but a model can still misread it or not read it. Test answers on real work, and keep the review your work needs.

No. Every page of a space you sync is a plain markdown file in ~/instibrain/spaces/, one folder for each space, so your editor and Claude Code read files as they do today. The sync client adds one short header to each file: the page's id. Keys of your own in that header stay on your computer. Get started shows the first day.

What only one person knows today: the pricing floor and who approves an exception, why a deal was declined, the fix that worked last time, the reason a schema looks wrong. Decisions and their reasons, not your file store. Use cases goes team by team.

No. Your AI reads them through your own connections and writes what matters as pages, which your team reads and corrects. The files stay where they are; a page can say where each lives and how your AI opens it. A folder of markdown you already have becomes pages as it is.

Your people and their AIs. A correction is an edit to the page, and every AI reads the new text at its next read. An AI that may not change a page leaves a proposal, which an editor accepts or rejects.

Yes, in rooms. Each Claude Code window, each AI login, and each agent is a voice of its own, and you read every room you are in. A message is gone after 30 days; what matters becomes a page. Our server reads a room, so a secret never goes in one.

Up to 100,000 pages and 2 GiB, the versions it keeps counted in the bytes. Either limit can be set otherwise for an account. A write past one is refused with the figure, and nothing of it is written. An account pushes at most a hundred pages a second, with a hundred seconds' worth to burst. A profile picture holds 512 KiB, and a space's logo 256 KiB. Nothing caps an account's spaces or groups, or a person's computers or agents.

Yes. The account has team spaces, and each person has Personal, which their AIs read, and Sealed, which only their computers open. A space is shared whole with a person, a group, or an agent, as reader, editor, or manager, and the role covers every page in it. What only a few people should read gets a space of its own.

Yes. An AI you connect in the browser, such as Claude on the web or Codex, reads nothing until you give it spaces. Claude Code on a linked computer reads as you, every space that computer syncs. You give a connected AI each space on the cockpit's Devices page, to read or to write, never above your own role. No other person, and no AI, its own included, changes what it reads.

A member of the team that is not a person, such as a support bot. The account owns it, an owner or admin makes it, and a space is shared with it as with a person, at its own role. It reads no sealed space and no old version.

Every page of the space as it is now, and each change after. As a reader or an editor, nothing the space said before comes with it: no old version, removed page, or old path. As a manager, you see who changed which page, and every old version. Anyone else reads those through a recovery grant from the space's owner, for the whole space or one path.

An owner or admin invites a person by email from People, and the link works seven days. The invite names the team spaces the person will read, and the inviter reviews those pages first. One address gets three invites a day, and one account sends fifty a day. Someone who never joins is removed thirty days after the first invite at the latest.

The group every account has. It holds every person of the account, from the moment they join until they are removed. Share a space or a specialist with Everyone, and every later arrival reads it too.

What an AI leaves when it wants a change it may not make, such as an edit to the rules of a space. Every editor and manager of the space sees it in the cockpit, under Waiting for you. You reject it there, or tell your AI yes; the AI then makes the change and closes it.

Only at the version a manager approved. A script in a space's tools/ folder syncs to everyone the space is shared with, but the sync client runs a file only at its approved version, so an edit waits for a manager's review. A file someone runs by hand has no such check.

It depends on the space, and you choose it space by space. Our server reads a page of an open space; that is what lets Claude on the web and the phone reach it. A page of a sealed space is encrypted on your computer before it leaves, path included; we hold ciphertext and cannot read it.

It is the tick, when you make a space, that makes it sealed. Every page then opens only on the computers of the people the space is shared with, through the sync client. No web AI, phone, or browser opens it, the cockpit included. A teammate's first computer gets the key only after a person approves its fingerprint on a manager's computer. Each later one gets it after they approve it on a computer of theirs already in.

Yes, in an open space. The guard reads the new text of every write and refuses a password or key, a card or passport number, a server login outside its folder, and a line about a person's pay, assessment, or health where the space's owner has not allowed it. It matches patterns, with no model, so a secret of another shape passes. In a sealed space it runs on your computer before each save.

Yes, when it reads them. An AI that reads a file sees what the file says, the pages of a sealed space included. “Our server cannot read it” and “no system anywhere sees it” are different claims, and only the first is true of any product that involves a model.

A breached, seized, or rogue-admin host gets ciphertext for a sealed space, and an open space as markdown. Some metadata leaks either way: space names, counts, sizes, and timing, so a sealed space named layoffs tells us there is a space called layoffs. The security page lists every claim with its verdict.

ChaCha20-Poly1305 for content, X25519 with ML-KEM-768 to wrap a sealed space's key, HKDF-SHA256 to derive a key per page, Ed25519 to sign membership, and Argon2id for the recovery passphrase. Every primitive ships with Node 24.

A computer signs every request it sends with its own key. An AI writes with a credential of its own, which you sign out on Devices to end its access. Either way the brain records who made each write. Each admission to a sealed space is a signed entry in its membership chain.

Yes, each person in Settings: a code from an authenticator app, and ten recovery codes. Settings also lists every live session with its browser and address, and signs the others out.

On your computer, in a file inside each synced folder that only your user account opens. The keys sit there in the clear, so any program running as you on that computer can read them. Our server stores each sealed space's key only wrapped for each computer, and none of what it stores opens a page.

On servers in Europe that we rent; the provider holds the disks, and for a sealed space those disks hold ciphertext. The company is in the United States. Nightly database dumps stay on the same server, encrypted to a key that is not on it, newest fourteen. The privacy policy names every party that touches data.

The sync client seals all its keys under a passphrase into one backup file you keep off the machine. On a new computer, link with a code from Devices, restore that file, and sync; then revoke the lost computer, so its key leaves every sealed space. Lose every computer and the backup, and nobody can open a sealed space, us included.

An open space keeps every version of a page for 30 days, then one a day for a year, then one a week; the newest stays always. The space's owner can erase old versions at once. A sealed space keeps no history on our server. Version history shows who recovers what.

You keep the folders: every page of the spaces you sync is already a markdown file on your computers, and one setting keeps each folder's whole history in a git repository there too. What you keep has the detail.

Yes. Write to privacy@webwork.ai and we delete the account and its data. The nightly dumps keep fourteen nights, so a deletion takes up to about two weeks to age out of them.

No. We operate the one server. The wire contract it speaks is public in full on how it works, field by field.

Ask on Request access.