instibrain
Sign in
instibrain  /  enterprise

One brain your company owns, set up with your team.

Each person's AI reads the pages of their role, and each space names who may read it. We set it up with your team; your files stay in your systems, and the AI stays the one you already pay for.

Request access → Take the tour
The cockpit's People page for a company of 56: two owners, five admins, 49 members, and six invited, each with their role, the day they joined, and their computers
by role

Each role gets its part of one brain.

One set of pages, shared space by space and read by every AI on the team. Here is what each role gets from it.

the company One brain it owns, as files

Every page is a markdown file on the computers you link. It outlives any model, and it stays when a person leaves.
each person An AI that knows their role

The spaces shared with them and the specialists of their job, from the first question.
each AI Its person's pages, not one more

An AI reads what its person gives it, never above that person's role.
each agent A member at its own role

A support bot or a writer reads the spaces shared with it, and no sealed space.
IT and security Who reads what, and what we cannot

Named readers, labels, held writes, sealed spaces, history, and recovery by role.
leadership Decisions, written once

What was decided and why, as pages every AI reads before it answers, and can name.
your data

Your files connect to your AI, never to us.

The brain holds what your company knows and has decided. Files, records, tickets, and mail stay in the stores you run, and the brain keeps a map of where each one lives.

WhatWhere it livesHow your AI reaches it
What your company knows and has decidedPages in the brain, in spaces with named readersOver MCP, as its person, never above their role
Files, records, tickets, and mailThe stores you already runThrough their own connectors, search, and retrieval, which we help you set up
The map: which store holds what, and who may open itA page in the brainRead first, before the AI opens a file
Passwords and keysEach person's own vaultSigned in as its person; never written in a page

instibrain stores and indexes none of your files. Pages know. Retrieval finds.

control

Each space names its readers, and our server cannot read a sealed one.

Your managers decide who reads each space, and every write names its writer. Your reviewer checks each claim on the security page.

  • Named readersEach space shared whole with its people, groups, and agents, as reader, editor, or manager
  • A label on each pagePublic, internal, confidential, or restricted: how far its text may travel
  • Held writesText from a confidential or restricted page waits for a manager before it lands anywhere wider
  • Sealed spacesEncrypted on your computers, path included; our server holds ciphertext it cannot open
  • Versions, with their writersIn an open space: every version for 30 days, then one a day for a year, then one a week
  • Recovery by roleA space's managers read its old versions; anyone else, through a grant from its owner
Sharing a team space: each person and the group Everyone with a role, reader, editor, or manager, a tab for agents, and Share with below

A label alone stops nothing; the hold is what our server enforces. Our server reads an open space on purpose, and a removal cannot recall what was already pulled. Every limit, beside its guarantee.

your AI

Bring the AI you already pay for.

Your AI reads the brain over MCP and does the work on your vendor's contract. We run no model, and your pages train none.

yoursThe AI, the model, and its bill.
  • Claude Code and Codex, in the terminal
  • Claude, on the web and the phone
  • Any MCP client, at the brain's one address
  • Next year's model, on the same pages
instibrainWhat your AI knows and may do.
  • The pages, in spaces with named readers
  • The map to your systems, and the tools a manager approved
  • Sealed spaces that open only on your computers
  • No AI run or called by the brain
What Claude Code on the laptop reaches: each space set to read and write, read, or not reached, and each specialist the same

Claude Code, Codex, and Claude on the web and the phone have run on our brain. How an AI connects.

the implementation

We set it up with your team, as part of the offer.

A company gets the implementation with the product, done beside its own people. WebWork, the founder's own company, is the first case of this work.

  1. Where AI fits. We look at your team's work with you and pick the jobs to give your AI first.
  2. The first pages, written together. What your company knows and has decided, drawn from your people and your own material.
  3. Your systems, connected. The tools your team already uses, so your people and your agents work from better data.
  4. Retrieval and tools, built for your data. Search over your own stores, RAG included, and the tools your work needs; your files stay where they are.
  5. Training for your team. How each person works with the brain and their AI, day to day.
A company space in the cockpit: its folders for clients, decisions, knowledge, meetings, people, rules, and tools, the inbox waiting for a person, and the space's index
how it starts

Start with one useful task on your own material.

Pick a job your team does every week. When it works on your own pages, the team follows, space by space.

One task

A job your team repeats, done on your own material.

first
The team

Each person links a computer, and their AI reads the spaces of their role.

next
The company

More spaces, more systems connected, and the implementation as deep as the work needs.

then

The price is by request: write to us with your team and the task you would start with.

Bring one task; we set up the rest with your team.

Request access for your company, or take the tour first.

Request access → Take the tour