BookStack

What Is BookStack?

In 2015, a UK developer named Dan Brown built a small documentation tool because the existing options frustrated him. Confluence was expensive and bloated. DokuWiki felt dated. MediaWiki required a PhD in wikitext. He wanted something that organised knowledge simply — Books contain Chapters, Chapters contain Pages — with a clean interface and zero cost.

A decade later, that side project has become one of the most widely deployed open-source documentation platforms in the world. BookStack remains a single-developer project. It remains 100% free. There are no paid tiers, no open-core dual licensing, no "enterprise edition" upsells. The MIT licence means anyone can use, modify, and redistribute the software without cost or significant limitation. Five feature updates and 18 patch releases shipped in 2025 alone.

BookStack runs on PHP 8.x with the Laravel framework and MySQL. It requires minimal infrastructure — a USD 5 VPS handles small to medium teams comfortably. Enterprise authentication is built in: LDAP, SAML 2.0, OIDC, multi-factor authentication, and role-based permissions. A REST API, outgoing webhooks, and diagrams.net integration round out the feature set. For organisations that want structured documentation without vendor lock-in or recurring costs, BookStack is the answer that keeps on giving.

Key Features

Books, Chapters, and Pages

BookStack's content model is its defining feature. Knowledge is organised into Books (top-level containers), which hold Chapters (sections), which contain Pages (individual documents). This three-level hierarchy maps naturally to how teams already think about documentation: a "DevOps Handbook" Book contains a "CI/CD" Chapter, which contains a "GitHub Actions Pipeline" Page.

The hierarchy is immediately understandable without training. Contrast this with Confluence's spaces-and-pages model, which works but requires learning Confluence's navigation patterns, or Notion's infinitely nestable pages, which offer flexibility at the cost of discoverability. BookStack's structured approach prevents the "where did I put that?" problem that plagues free-form tools.

Enterprise Authentication

For a free tool, BookStack's authentication capabilities are remarkably complete. LDAP integration connects to Active Directory or OpenLDAP directories. SAML 2.0 support enables single sign-on through Okta, Azure AD, or any SAML-compliant identity provider. OIDC connects to Keycloak, Authentik, Auth0, and Google Workspace. Social login options include GitHub, Google, Slack, and more.

Multi-factor authentication adds a second layer of security. Role-based permissions control who can view, edit, create, and delete content at the Book, Chapter, and Page level. These are not premium features locked behind a paywall — they ship with every installation.

Built-In Diagrams and Editing

BookStack offers both a WYSIWYG visual editor and a Markdown editor with live preview. The Markdown editor preserves original content formatting, while the visual editor handles users who prefer word-processor-style editing.

The diagrams.net integration is built directly into the page editor. Click a button, draw a flowchart or network diagram in the full diagrams.net editor, and save it as an embedded PNG that remains fully editable. No plugins to install, no external service to configure. For technical documentation — architecture diagrams, process flows, network topologies — this integration is worth more than it first appears.

REST API and Webhooks

BookStack exposes a comprehensive REST API covering Books, Chapters, Pages, Shelves, Users, and Attachments with full CRUD operations. Outgoing webhooks fire on configurable events — page created, page updated, book deleted — enabling integration with Slack, custom automation workflows, or backup systems.

The API enables programmatic content management: import documentation from external sources, sync content with Git repositories, or build custom front-ends on top of BookStack's content store.

Export and Portability

Pages export to PDF (via browser print), Markdown, and HTML formats. Books can be exported as compiled documents. The Markdown export preserves original content if pages were written in the Markdown editor. This means data is never trapped — migrating away from BookStack is straightforward, which is a deliberate design choice reflecting the project's open-source philosophy.

Pricing

BookStack costs nothing. Zero. There is no paid tier, no premium feature, no commercial edition, no support contract. The entire platform — every feature, every authentication method, every API endpoint — is available under the MIT licence at no cost.

The cost of running BookStack is the infrastructure: a Linux VPS, PHP, MySQL, and basic system administration. At current VPS pricing, that starts around EUR 4-5/month for a small instance. A team of 50 users runs comfortably on a EUR 10-20/month server.

Compare this to Confluence Cloud at USD 6.05/user/month (Standard) — a 50-person team pays USD 302.50/month. Notion charges USD 10/user/month for Business plans, or USD 500/month for the same team. BookStack's total cost for 50 users: the price of a VPS.

The hidden cost is system administration. Someone needs to install, update, and maintain the server. For teams without operations capacity, this is a genuine barrier. Several third-party providers offer managed BookStack hosting, though none are affiliated with the project.

EU Compliance & Privacy

BookStack is self-hosted by design. Data stays on your server. Nothing is transmitted to BookStack, to Dan Brown, or to any third party. There is no telemetry, no analytics, no phone-home behaviour.

This architecture makes GDPR compliance straightforward: deploy BookStack on a server in an EU data centre, and data residency is guaranteed by infrastructure rather than by vendor promises. The organisation controls the data processing agreement because it controls the infrastructure. No sub-processors, no cross-border transfers, no adequacy decisions.

The project itself is UK-based ("european" tier, post-Brexit), but since BookStack is self-hosted software, the developer's location is irrelevant to data processing. The data goes where you put the server.

Who It's Best For

Small to medium teams that need structured documentation without budget for Confluence or Notion. BookStack delivers 80% of the functionality at 0% of the licence cost.

Self-hosting enthusiasts and DevOps teams who already manage their own infrastructure and want documentation that lives alongside their other tools. BookStack integrates with existing LDAP/SAML identity providers.

Organisations with strict data sovereignty requirements that cannot use cloud-hosted documentation platforms. Self-hosting on EU infrastructure guarantees compliance without vendor dependency.

Technical documentation teams that need diagrams.net integration, Markdown editing, and API access for automated content management. BookStack's developer-friendly architecture fits engineering workflows.

The Verdict

BookStack proves that free software does not mean inferior software. Its Books/Chapters/Pages model is more intuitive than Confluence's navigation. Its authentication stack rivals commercial platforms. Its diagrams.net integration is genuinely useful. The absence of real-time collaboration is a legitimate gap, and the single-developer bus factor is a risk organisations should acknowledge. But for teams that can self-host, BookStack delivers structured documentation with enterprise authentication at a cost that rounds to zero. That value proposition, a decade into the project, remains unmatched.

Frequently Asked Questions

Is BookStack really completely free?

Yes. There are no paid features, no dual licensing, no open-core model, and no enterprise edition. Every feature ships under the MIT licence. The project is funded by voluntary donations and sponsorships.

Can BookStack replace Confluence?

For structured documentation with role-based permissions and enterprise authentication, BookStack covers the core use case. It lacks Confluence's real-time collaboration, marketplace add-ons, Jira integration, and managed cloud hosting.

Does BookStack support GDPR compliance?

BookStack is self-hosted, so data stays entirely within your infrastructure. Deploy on an EU server and data residency is guaranteed. No data is transmitted to the project or any third party.

What technical requirements does BookStack have?

PHP 8.x, Laravel, and MySQL 5.7+ or MariaDB 10.2+. A Linux VPS with 1 GB RAM is sufficient for small teams. Docker images are available for containerised deployment.

Is there a hosted version of BookStack?

No official hosted version exists. BookStack is self-hosted only. Third-party managed hosting providers offer BookStack instances, but these are independent of the project.