BookStack
Free, self-hosted wiki with a Books/Chapters/Pages hierarchy, built-in diagrams, SAML/OIDC auth, and role-based permissions. Runs on PHP and MySQL
Quick Start
docker run -d --name bookstack -p 8080:80 lscr.io/linuxserver/bookstack Overview
BookStack is a free, MIT-licensed wiki platform built around a deliberate structure: Shelves hold Books, Books hold Chapters, Chapters hold Pages. That hierarchy sounds limiting on paper, but in practice it is exactly what keeps documentation tidy when multiple people are writing. If your team produces SOPs, onboarding guides, runbooks, or policy manuals, the enforced structure means content stays findable instead of drifting into a flat pile of pages.
Setup is straightforward. BookStack runs on PHP and MySQL, deploys comfortably in two Docker containers, and works on a $5 or $6 VPS. There are no external dependencies like Redis or S3 required, and it ships with built-in email and password authentication so you can get started without configuring an external identity provider first. SAML2, OIDC, LDAP, and social login are available when you need them.
The editor gives you a choice: a clean WYSIWYG mode for non-technical writers, or Markdown with live preview for those who prefer it. Diagrams.net is integrated directly into the page editor, so flowcharts and architecture diagrams can be created and stored without leaving the platform. Full-text search covers all content with paragraph-level precision. Role-based permissions work at every level of the hierarchy, and MFA is built in.
Where BookStack is honest about its limits: there is no real-time collaboration. Two people editing the same page at the same time is not supported. The interface is functional and reliable but does not feel like a modern Notion-style tool. If your team wants collaborative editing and a flatter document structure, Outline is the closer comparison, though it requires considerably more infrastructure and carries a non-open-source license. For teams who simply want a clean, private place to store knowledge without operational complexity, BookStack is the clearest choice available.
BookStack: Pros & Cons
| Pros (The Wins) | Cons (The Friction) |
|---|---|
| Simplicity: Runs on PHP and MySQL; no Redis, S3, or external auth required. | No real-time collaboration: Two people cannot edit the same page simultaneously. |
| Structure: Enforced hierarchy keeps docs tidy; paragraph-level search built in. | Rigid hierarchy: Shelves/Books/Chapters/Pages doesn’t suit non-linear content well. |
| Auth & Permissions: SAML2, OIDC, LDAP, MFA, and role-based access all included. | UI: Functional but traditional; lacks the polish of newer Notion-style tools. |
| Diagrams: Diagrams.net built into the editor; no third-party embed needed. | No mobile app: Browser-only; no native iOS or Android client. |
Use Cases
Specific ways to use BookStack for your workflow.
Deployment Strategy
Recommended ways to host BookStack in your own environment.