BookStack

Self-hosted documentation wiki with a fixed shelf, book, chapter and page structure

As of 30 August 2026, BookStack is free to use. An MIT-licensed PHP documentation platform you run yourself. Softwr lists it under Documentation. BookStack is made by BookStack (independent open source project), available on Web, Self-hosted, Docker.

Visit siteVisit BookStack

Overview

What BookStack does

BookStack is an open source documentation and knowledge base application built on Laravel with a MySQL or MariaDB database. Content is organised into shelves, books, chapters and pages, edited in either a WYSIWYG editor or Markdown, with page revisions, drafts, per-item permissions, full text search, a REST API and export to PDF, HTML, plain text and Markdown. It is released under the MIT licence with no paid edition and no feature held back. The fixed hierarchy is the design decision that decides whether it suits you. Most wikis let pages nest arbitrarily and end up as a tree nobody can navigate after two years. BookStack refuses that: everything is a page, in an optional chapter, in a book, on an optional shelf, and no deeper. Teams documenting products, procedures and runbooks find that the structure does the organising for them. Teams migrating a deep Confluence space find it a wall, because content five levels down has to be flattened by hand. The second decision is that the project ships no hosted service. There is no vendor to buy an SLA from, and third-party hosts have no support relationship with the project, so the operational burden is real and permanent. Buyers are internal IT, engineering and operations teams who want documentation on their own infrastructure without a licence fee, frequently in organisations where data cannot leave a specific network or jurisdiction. The trade-off is a small maintainer base and a database-centred content model. Pages live in MySQL rather than in Git, so review by pull request is not possible and bulk migration out means scripting against the API.

What people use it for

Running an internal knowledge base on infrastructure inside a network that cannot reach external SaaS
Documenting procedures and runbooks where a fixed structure prevents the tree sprawl a free-form wiki produces
Replacing a Confluence licence for a team that needs pages, permissions and search but none of the surrounding suite
Publishing customer-facing manuals from the same instance as internal documentation using per-book permissions

Where it falls short

Concrete and checkable, so you can decide whether any of them matter to you. This is the half of a review a vendor will not write about BookStack.

There is no vendor-hosted option at all, so you own the server, TLS certificates, database backups and upgrades, or you pay a third-party host that has no support relationship with the project and no ability to fix a bug.
The shelf, book, chapter, page hierarchy is fixed at four levels and cannot be reshaped, so migrating a deeply nested Confluence or MediaWiki space means flattening content by hand and losing the original structure.
It requires PHP and MySQL or MariaDB, which is a stack many engineering teams no longer run, so adopting it usually means introducing a database and runtime nobody else in the organisation maintains.
Development is concentrated on a single maintainer, which makes the bus factor a legitimate procurement question for anything the organisation intends to depend on for a decade.
Content lives in the database rather than in files under version control, so there is no docs-as-code workflow, no review by pull request and no branch per release.
Export is per page, chapter or book, so moving a large instance to another platform means writing a script against the REST API rather than copying a directory of Markdown.

Cross-shopped

What people choose instead of BookStack

Each pairing was judged by two reviewers asking whether a buyer would genuinely weigh the two against each other. The ones that failed were deleted rather than published.

BookStackvs
Nuclino
Nuclino: If you want a hosted knowledge base with no servers to run and can accept per-user pricing
BookStackvs
MkDocs
MkDocs: If documentation should live in Git as Markdown and be published as a static site
BookStackvs
GitBook
GitBook: If a hosted product with an editing experience for non-technical writers matters more than self-hosting

Pricing

What BookStack costs

Taken from the vendor's own pricing page. Prices move, so check before you buy.

BookStack

Free

MIT licence with no paid edition
All features included, no seat limits
Self-hosted on your own infrastructure
Community support through the project forum
No vendor SLA available at any price

Capabilities

Features

Shelves, books, chapters, pages
A fixed four-level structure that constrains how documentation can be organised
Dual editors
WYSIWYG or Markdown chosen per page, so writers and engineers can work in the same book
Granular permissions
Role-based access applied down to individual books, chapters or pages
Full text search
Search with filters for tags, creator, updated date and content type
Page revisions
Version history with diffs and restore, plus autosaved drafts
REST API
Programmatic create, read, update and delete over content for migration and automation
External authentication
LDAP, SAML2 and OpenID Connect with role mapping from the identity provider
Export
PDF, HTML, plain text and Markdown export at page, chapter or book level
Audit log
Records who changed or viewed what, for internal review requirements

Answered, with sources

Questions people ask

Each answer names the page it came from, so you can check it rather than take our word for it.

Is there a paid or hosted version?

No. BookStack is MIT-licensed with no commercial edition and no official hosted service. Third-party hosts exist but are unaffiliated with the project.

Can I nest pages more deeply?

No. Four levels is the design, not a limitation waiting to be fixed, and content that needs deeper nesting has to be restructured.

Does it support single sign-on?

Yes, through LDAP, SAML2 or OpenID Connect, with group to role mapping, and none of it is gated behind a paid tier because there is no paid tier.

How hard is it to migrate content in?

Straightforward for flat content through the REST API, awkward for deeply nested wikis, because the structure has to be collapsed to fit.