Read-only by design
CompanyOS lets AI Clients read relevant knowledge; it does not let them rewrite your source files.
A shared brain for your company or department
One shared brain your team's AI can read
Your team already uses AI — but it answers from whatever file someone uploaded last, not from everything your company knows. CompanyOS hands your shared knowledge to whichever AI client each Member already opens.
Read-only knowledge access. Workspace-scoped visibility. Answers grounded with linkable sources.
It reads everything your team knows and rewrites nothing — read-only by design, not by setting.
Free during early access. No sales call required to start.
The gap
Your AI knows everything. Except what your group knows.
Your Members already use AI, but the useful context sits in shared folders, personal notes, old decisions, and process documents.
CompanyOS gives your company or department one Workspace brain, so the same question gets the same answer from the same visible knowledge instead of from whoever uploaded the right file last.
Keep the AI tool. Add the Workspace context it was missing.
How it works
Three steps from scattered files to useful answers
-
01
Create a Workspace
An Owner creates the Workspace and invites Members. Use one Workspace for a company, one department inside a larger organization, a family, or another group.
Owner setup
-
02
Add knowledge
Company Files are visible Workspace knowledge; Personal Files stay scoped to the Member who added them.
Scoped by default
-
03
Connect your AI Client
Connect Claude, ChatGPT, or another AI Client over a read-only MCP Connection. Its shape follows OpenAI's documented search plus fetch pattern for ChatGPT deep research and company knowledge.
CompanyOS provides the MCP Connection; your AI Client plan controls whether you can attach custom connectors.
Answers with sources
Trust boundary
Built for shared context without loose access
Workspace-scoped visibility
Answers can use Workspace knowledge that a Member is allowed to see, with Company Files and Personal Files kept in their proper scopes.
Grounded answers
Responses are grounded in your files, with linkable sources so a Member can check the material behind an answer.
Owner gating
Owners control Workspace setup and Procedure publishing, so a Procedure's first publish never happens without Owner review; later Owner edits to a published Procedure go live logged under the Owner's name.
Procedures
Then turn good prompts into approved Procedures and Templates
Once the knowledge is in, depth follows. A Procedure is reusable AI guidance owned by the Workspace; a Procedure Template shapes the output it produces. Together they turn a one-off way of working into something every Member's AI client can run again, the same way each time.
Procedure draft
Write the weekly update from these source files. Call out decisions, open questions, and owner names.
Launch Plan
Pricing Notes
Support Checklist
- DraftAn Owner drafts the reusable instruction with their AI Client.
- Approval LinkReview this Procedure before it becomes available to the Workspace.
- Owner reviewsThe Owner confirms the draft in the web app before it becomes official.
- PublishMembers can use the approved Procedure from their AI tool with the same Workspace context and linkable sources.
Use cases
Built for the company or department you run
A whole company
For the founder or chief of staff who wants the team answering from the same policies, plans, files, and decisions — on whichever AI client each person already uses.
A department inside a larger org
For a team lead who needs a useful local brain now, without waiting for a company-wide knowledge project or a single approved tool.
Also for families and other groups
Families and other small groups, too: anyone who wants shared plans, documents, and recurring decisions in one calm place the right people can use — the same scoped, read-only brain, smaller in scale.
Per-Member visibility a shared folder can't do: every Member sees Company Files plus their own, and nothing else.
Honest comparison
If you're wondering about ChatGPT's built-in company knowledge…
Use it when it fits. ChatGPT's built-in company knowledge is a paid workspace feature, oriented around Business, Enterprise, and Education plans. If your whole team already lives in one of those workspaces, use what's built in.
CompanyOS is for the teams that don't: Members on different plans and different AI tools who want one Workspace brain, with read-only access, scoped visibility, Procedures, and linkable sources, and no move onto a single vendor's workspace tier.
Why not just a shared folder?
A shared folder stores files. It does not decide what a Member can see, expose a read-only MCP Connection to an AI Client, package repeatable work as an Owner-approved Procedure, or return grounded answers with linkable sources.
Every Member sees Company Files plus their own, and nothing else — a folder shares everything with everyone, or nothing with anyone.
Early access
Start free while CompanyOS is in early access
The free tier is the product, not a demo.
Free today
Create a Workspace, add knowledge, invite Members, and connect supported AI Clients when your AI Client plan allows custom connectors.
Free during early access. A Team tier is coming when billing is ready.
CompanyOS
Give your workspace a brain.
Start with the knowledge your team already has. Keep the AI tools your Members already use. Add the shared context, source links, and Owner-approved Procedures and Templates that make the answers trustworthy.