Docmost
| License | FOSS problems | Maintenance | SSO | Users | Tested |
|---|---|---|---|---|---|
| AGPLv3Copyleft license. If you modify it and run it as a service, you must publish your changes. Surrounding linked code must also be open. | Open Washing | Active | ❌ | Unlimited | ✅ |
Description
Docmost is a collaborative wiki and knowledge base — Notion-style nested pages, workspaces, comments, databases, and kanban boards. Positioned as a modern alternative to Confluence or Notion, self-hostable via Docker.
Features
- Nested pages and workspaces — Notion-style organization, not a fixed hierarchy.
- Comments — included in the free tier.
- Databases and kanban boards — paywalled, not part of the free tier despite the AGPLv3 label (see License and governance).
- Basic page editor — what the free tier actually gives you.
Usage patterns
- Small private wiki, no integration requirements — the free tier covers this: a clean interface, reasonable feature set for basic documentation, easy to self-host via Coolify.
- Not a fit for anything needing SSO or API access — both paywalled, along with MCP integration, disabling public sharing, and advanced search — infrastructure-level features, not premium ones.
License and governance
The AGPLv3 label is misleading. Paywalled features fall into two categories: actual product features that make it useful as a knowledge base (databases, kanban boards, templates, comment resolving — most of what would make it worth adopting), and technical infrastructure you'd expect to be free regardless of tier (SSO, API access, MCP integration, disabling public sharing, advanced search). SSO alone is a dealbreaker for any serious multi-user setup — a security and usability baseline, not a premium. Self-hosting a tool restricted this way carries the operational cost while the vendor retains control over the feature set.
Conclusion
Why you would — a clean interface and reasonable feature set for basic, no-integration documentation, easy to self-host via Coolify, if the free tier genuinely covers the need.
Why you wouldn't — most of what would make it worth adopting over a genuinely free alternative is paywalled, including baseline infrastructure like SSO — not a premium feature anywhere else in this catalog. Fully FOSS alternatives exist that don't pull this. See Setup for the actual deploy steps.