--- title: Enterprise โ€” what a company gets from instibrain description: What a company gets from instibrain, role by role: one brain it owns, control by space, its own AI, its files in its own systems, and the setup with its team. url: https://instibrain.ai/enterprise updated: 2026-11-08 site: https://instibrain.ai/llms.txt --- # 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 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. | What | Where it lives | How your AI reaches it | | What your company knows and has decided | Pages in the brain, in spaces with named readers | Over MCP, as its person, never above their role | | Files, records, tickets, and mail | The stores you already run | Through their own connectors, search, and retrieval, which we help you set up | | The map: which store holds what, and who may open it | A page in the brain | Read first, before the AI opens a file | | Passwords and keys | Each person's own vault | Signed 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 readers Each space shared whole with its people, groups, and agents, as reader, editor, or manager - A label on each page Public, internal, confidential, or restricted: how far its text may travel - Held writes Text from a confidential or restricted page waits for a manager before it lands anywhere wider - Sealed spaces Encrypted on your computers, path included; our server holds ciphertext it cannot open - Versions, with their writers In an open space: every version for 30 days, then one a day for a year, then one a week - Recovery by role A space's managers read its old versions; anyone else, through a grant from its owner 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. yours The 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 instibrain What 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 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. - Where AI fits. We look at your team's work with you and pick the jobs to give your AI first. - The first pages, written together. What your company knows and has decided, drawn from your people and your own material. - Your systems, connected. The tools your team already uses, so your people and your agents work from better data. - 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. - Training for your team. How each person works with the brain and their AI, day to day. 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 your reviewer Security Each claim, with where it holds and where it stops. the case Why instibrain The eight questions a company meets when it puts AI to work. team by team Use cases What each team writes down, and what its AI then answers. --- instibrain is made by WebWork AI, Inc. Everyone uses the same models ยท the difference is what yours knows.