Analytics cookies only (Google Analytics, PostHog). No ad networks, no cross-site tracking. See our privacy policy.
upstream: github.com/docmost/docmost (opens in new tab) · github.com/BookStackApp/BookStack (opens in new tab)
Pick BookStack
For a documentation wiki with no paid edition at all: MIT-licensed, books/chapters/pages, LDAP/SAML2/OIDC and social login plus role-enforceable MFA in the free build, on an estimated 512 MB PHP + MariaDB stack, though with no official container image.
Pick Docmost
If real-time collaborative editing is the point: an AGPL-3.0 core with spaces, comments, page history and built-in Draw.io, Excalidraw and Mermaid diagrams on Node.js + PostgreSQL + Redis, knowing that SSO, MFA, Bases, page-level permissions and AI are licensed Business features, audit logs, SIEM and SCIM are Enterprise, and releases are still pre-1.0.
Docmost and BookStack are both self-hosted answers to Confluence and Notion, and both rate difficulty 2/5 here. They answer from different decades. Docmost is a TypeScript/Node.js wiki on PostgreSQL + Redis with real-time collaborative editing and an AGPL-3.0 core with a paid tier built into the same codebase. BookStack is a PHP/Laravel application on MariaDB, organized into books, chapters and pages, MIT-licensed with nothing held back. You don't choose between them on editor features. You choose on whether live co-editing is worth a heavier stack and a paywall on login.
This is the difference you will notice first.
If your team drafts documents together, Docmost is the only one of the two that fits. If pages are mostly written by one person and read by many, BookStack's model is fine and has less machinery underneath.
BookStack is MIT, "fully free and open" in the project's own words. There is no paid edition and no gated feature list.
Docmost's core is AGPL-3.0, a genuinely open license, but the repository also carries enterprise-licensed directories, and Docmost's own edition table draws a clear line. The free Community edition includes real-time collaboration, spaces and space permissions, groups, comments, page history, diagrams, public sharing, full-text search and Notion import. Bases (databases), SSO (SAML 2.0 / OIDC / LDAP), multi-factor authentication, page-level granular permissions, AI and MCP are Business features, and audit logs, SIEM and SCIM are Enterprise-only. All of them need a license key, even when you self-host.
This row is where BookStack's pull is strongest.
BookStack's free build handles login in full. There is standard email and
password, plus LDAP, SAML2 or OIDC, plus social login, all set in its
.env. MFA is built in (TOTP apps and backup codes) and can be enforced
per role, and a role-and-permission system lets you lock down content and
actions.
Docmost gives you a built-in login on day one, so you don't need to run an identity provider (unlike Outline). But SSO and MFA are both on the Business side of the line, and so are page-level permissions. The free build restricts access by space and group.
A team that needs SSO or MFA for compliance pays for it with Docmost and gets it free with BookStack.
Both rate 2/5, for different reasons:
curl it,
set APP_URL, an APP_SECRET of at least 32 characters and the database
password (which appears twice), and bring up three containers: app,
PostgreSQL, Redis. Our 1 GB floor is an estimate for that trio. The
project publishes no RAM minimum.On a box that already runs other things, BookStack is the lighter guest.
Docmost is pre-1.0. Its releases are still 0.x, and it adds features quickly. The flip side is that breaking changes between versions are possible, so read the release notes before pulling a new image. BookStack has been quietly reliable for years and ships dated releases. Its update docs still ask you to back up the database and uploads before every update and to read the version-specific notes, because releases have raised the PHP and database minimums.
BookStack wins this comparison for most self-hosters. Everything a team needs to run a wiki properly comes in its free MIT build: enterprise login, MFA enforced per role, and a permission system. It runs on half the RAM and has years of stable releases behind it. Docmost is the better product only on its one big feature, real-time collaborative editing, which BookStack does not have. If that is the point for your team, Docmost is worth choosing, but know that login hardening sits behind its license key. If you want live co-editing and free SSO, neither app gives you both. Compare Docmost with Outline and BookStack with Outline. If the pull toward BookStack is really about Markdown and login modules, see Wiki.js vs BookStack.
BookStack lists a lower minimum: 512 MB vs 1024 MB for Docmost.
No. Docmost is AGPL-3.0, BookStack is MIT.
Pick BookStack unless real-time co-editing is essential. It is MIT-licensed with no paid edition, and its free build includes LDAP, SAML2 and OIDC login, social login and MFA you can enforce per role, on an estimated 512 MB. Pick Docmost if your team drafts pages together live. Its AGPL-3.0 core does real-time collaboration, but SSO, MFA and Bases need a Business license.
No. BookStack uses a single-editor model with draft autosave and a warning when someone else is editing the same page. Docmost supports real-time collaboration in its free Community edition.
BookStack. Its MIT build supports LDAP, SAML2 and OIDC plus social login and built-in MFA. In Docmost, SSO (SAML 2.0, OIDC, LDAP) and MFA are Business-edition features that need a license key, even when self-hosted.
Paid link — we earn a commission if you shop through it.
The flat-file team wiki with page ACLs vs. the engine behind Wikipedia.
Simple and truly open vs. slick and real-time.
Two Notion-style real-time wikis on the same stack — an AGPL core with a paid ring vs. a source-available whole.