Sedimenta sits between a team workspace and a memory layer for AI agents. Here is how it differs from the tools people compare it with — and when those tools are the better choice.
The same shape — documents and databases for a team — but in Sedimenta agents are first-class writers: the server checks their writes against your rules, and every value keeps its source.
| Sedimenta | Notion | Confluence | Outline | Docmost | AFFiNE | |
|---|---|---|---|---|---|---|
| Run on your own server | Yes, including fully offline | No, cloud only | Data Center; Rovo agents cloud only | Yes | Yes | Yes, free up to 10 members |
| Databases | Typed, with relations, formulas and rollups | Yes | Pages only | Documents only | Bases, since 2026 | Basic, no relations or rollups |
| MCP for agents | Built in, token or OAuth | Yes, OAuth | Yes, OAuth; cloud | Built in | Paid edition | Built in; writes in preview builds |
| Agent writes | Checked by server rules; proposals for review | Confirmed by a person | Changing actions confirmed | API key scopes | — | — |
| Source of every value | Field-level, down to the quote | — | — | — | — | — |
| Pricing | Free for small teams; per workspace, not per seat | Per seat; agents Business+ | Per seat; Rovo credits | Per user | Free core; paid features | Per seat |
These are memory engines and APIs that a developer builds into an agent. Sedimenta is the memory of a company that any agent connects to — with a workspace where people read, correct and approve what agents wrote.
| Sedimenta | Mem0 | Zep | Cognee | Letta | Supermemory | |
|---|---|---|---|---|---|---|
| Built for | Teams and their agents | Agent developers | Agent developers | Agent developers | Building agents | Agent developers |
| Workspace for people | Pages, databases, permissions | — | — | — | — | — |
| Run on your own server | Yes | Yes; graph in cloud only | Cloud; BYOC on Enterprise | Yes | Yes | On Scale plan; server closed |
| Approval of agent writes | Any write can require it | — | — | Skill proposals only | Approval of tool calls | Derived memories, via API |
| Provenance | Field, document fragment, who approved | — | Link to episode | To file; hash chain behind a flag | Per commit | To whole document |
| Rules that refuse a write | Yes, enforced by the server | Extraction instructions | Strict ontology drops data | Strict ontology drops data | — | — |
Great tools for one person. Sedimenta is for a team: shared databases, permissions and agents that write for everyone — and it still runs on one laptop and exports to Markdown.
| Sedimenta | Obsidian | Capacities | Pieces | |
|---|---|---|---|---|
| Built for | Teams; also one person on a laptop | One person | One person | One developer |
| Team editing and permissions | Real-time editing, spaces, per-record access | — | — | — |
| Where data lives | Your server or laptop; Markdown export | Markdown files locally | Vendor cloud | Locally |
| Agents | MCP with rules and approval | Through plugins | — | MCP for coding tools |
Search finds answers across the systems a company already has. Sedimenta is where verified knowledge is stored and corrected. They work well together: what search finds and a person confirms can settle here, with its source.
| Sedimenta | Glean | |
|---|---|---|
| What it does | Stores and edits verified knowledge with provenance | Searches and answers across existing tools |
| Deployment | Your own server | Glean cloud or your cloud, managed by Glean |
| Agents write | With rules and approval | Through MCP, confirmed by a person |
We’re working with a small number of teams that already use AI agents in their daily work.
Request early access