Real-time, conflict-free
Every page is a CRDT document, not a string in a database. Simultaneous edits merge deterministically — no locks, no “someone else is editing”, no lost paragraphs.
Native MCP server
→
The knowledge base
The knowledge base
your agents can read.
Reams is a self-hosted, real-time collaborative wiki built on CRDTs — with a Model Context Protocol server in front of it. Your team writes the docs. Your agents search, read and write them — under the same permissions and through the same editing layer as your team.
AGPL-3.0 · Self-hosted · No enterprise tier
reams.internal / product / specs
Engineering/Specs/Search rewrite
Search rewrite
We replace the Postgres tsvector path with a dedicated index. This document is the source of truth for the migration — the agent drafts release notes from it.
◇
Decision — ship behind
SEARCH_V2, default off until QA signs off.Rollout is staged per space. Owners are notified on…
Emma
Built on open foundations
- Yjs CRDT
- PostgreSQL
- Model Context Protocol
- TipTap
- Redis
- AGPL-3.0
Product
A wiki that holds up under real teams.
Most internal docs rot because writing them is friction and reading them is a search problem. Reams attacks both ends: editing that feels like a document, structure that machines can traverse.
Freshness as a first-class signal Planned
A wiki is only trustworthy if you know which pages still are. Per-page verification and drift detection are not built yet. The groundwork is: every body edit already emits a page.content_updated webhook.
Spaces & nested pages
Organise by team, then by hierarchy. Permissions follow the space, so the tree stays clean.
Templates that fit the work
Save any page as a template for specs, decisions, postmortems. Structure is what makes a page retrievable later — by a person or a model.
Search that reaches page content
Full-text across page titles and content, in every space you can see. The MCP search tool queries the same index.
For agents
Your docs, exposed as tools.
Reams speaks the Model Context Protocol. Point an MCP client at it and your assistant works against the wiki directly — reading the current spec instead of a six-month-old paste. Local clients connect over stdio today; the HTTP transport for hosted connectors is still in testing.
list_spacesEnumerate what the agent is allowed to see
read_pageFetch a page with its structure intact
searchQuery across spaces, scoped by permission
create_pageWrite a new page into a space, from Markdown
update_pageEdit through the CRDT layer, never around it
Your assistantClaude, IDE, or any MCP client
MCP
Reams MCP serverTools, auth, scoping
HTTP · API key or OAuth
ReamsPages · Spaces · Permissions
PostgreSQLYjs collab
Permissions are not optional
The agent acts as the person who issued its credential and sees exactly what they can see — no more. Access checks run in the same guard layer the UI uses. Keys cannot yet be narrowed below their owner's access.
Writes go through the editor, not around it
Agent edits merge through the same CRDT as a human keystroke, so an agent can write to a page someone has open without overwriting their work.
Webhooks on every change
Page create, update, delete and body edits emit events to your endpoint — so drafting, freshness checks and review workflows can run on your side of the wire.
Collaboration
Written by humans, in the same room.
The editor is TipTap over Yjs, with a dedicated collaboration process. Presence, cursors and concurrent edits are handled by the CRDT, not by a last-write-wins race.
- Live cursors and selections, per user
- Inline comments and threads
- Page history, with restore
- Import from Markdown, HTML and Notion; export to Markdown and HTML
Rollout plan
Stage one covers the Engineering space only. QA signs off before the flag flips.
Kevin
Stage two extends to Product and Releases…
E
EmmaCan we gate this per-space instead?
Open source
All of it. Not the demo half.
The Reams wiki is AGPL-3.0 end to end. There is no enterprise directory, no licence server, no feature that unlocks when you pay. The MCP server is a separate program, and its licence has not been decided yet.
- No enterprise code in the wiki
- Runs on your infrastructure, your Postgres, your data
- Source offer reachable from every deployment (AGPL §13)
The repository is private. Access is granted to the people who use a Reams deployment, on request.
Request source access →$ git clone git@github.com:davidnguyen2205/reams.git
$ pnpm install
$ pnpm run migration:latest
$ pnpm dev # client + API
$ pnpm run collab:dev # collab — once the API is up
▸ API http://localhost:3000
▸ Collab ws://localhost:3001
▸ Ready.
Plans
Self-host free. Let us run it if you'd rather not.
The software is the same either way. You are paying for operations, not for features.
Self-hosted
Freeforever
The wiki under AGPL-3.0, on your own infrastructure.
- Unlimited users, spaces and pages
- Real-time collaborative editing
- API keys and webhooks
- Community support
Planned
Cloud
Managedpricing to be announced
We host, patch, back up and monitor it. Same codebase, none of the on-call.
- Everything in Self-hosted
- Backups and upgrade management
- Hosted MCP endpoint
- Priority support
Planned
Enterprise
Talk to uscustom
For teams with a procurement process and a compliance reviewer.
- SSO and directory sync
- Audit log export
- Deployment assistance
- SLA-backed support
Reams is early. Cloud and Enterprise are on the roadmap, not on the shelf — the self-hosted build is what runs today.
FAQ
Questions worth asking first.
How is this different from Notion or Confluence?
Two ways. The wiki runs on your infrastructure under AGPL-3.0, so there is no data-residency conversation and no feature gate. And it is designed for machine consumption as a first-class case — the MCP surface is part of the product, not a third-party integration scraping an export.
What is MCP, and why should a wiki care?
The Model Context Protocol is an open standard for connecting AI assistants to tools and data. A wiki is exactly the kind of context an assistant needs and usually cannot reach. Exposing pages as MCP tools means the model reads the current document, under your permissions, instead of whatever was pasted into a chat months ago.
Can an agent overwrite our documentation?
It can edit whatever the person who issued its credential can edit — there is no separate review step for agent writes yet, so issue credentials accordingly. Edits route through the same collaboration layer as human ones rather than writing to the database directly, and the MCP server reads each page update back to confirm it actually landed.
What does AGPL-3.0 mean for us?
You can run, modify and self-host Reams freely. The network clause means that if you run a modified version and others use it over a network, you must offer those users the corresponding source of your modification. Running it unmodified for your own team creates no publication obligation. This is a summary, not legal advice.
Is Reams production-ready?
The self-hosted build runs, and real-time collaborative editing is verified. All five MCP tools are verified against a running instance over stdio; the HTTP transport has only been handshake-tested, and the OAuth sign-in it uses has not had a security review. The managed Cloud offering does not exist yet. If you are evaluating for a critical workload today, talk to us before you commit — we would rather tell you it is early than have you find out.
Give your team a wiki.
Give your agents a source of truth.
Deploy it this afternoon, or tell us what you need and we will tell you honestly whether Reams is there yet.