BookStack is a free, open-source, self-hosted wiki platform that organizes content the way a library does: shelves contain books, books contain chapters, and chapters contain pages. It is MIT licensed, written in PHP on top of Laravel, and runs comfortably on a small Docker container or a cheap VPS. For engineering teams that want a tidy internal knowledge base without paying per seat or sending their data to a SaaS vendor, BookStack is one of the cleanest options on the open source knowledge base shortlist.
This review covers what BookStack actually is, how it stacks up against the other free knowledge base software people compare it to, and where it fits in your stack. If you are looking for a hosted, branded, public-facing docs site instead, the trade-offs at the end are the section to read.
What is BookStack?
BookStack is wiki software first released in July 2015 by UK developer Dan Brown. The first commit went up under the name "Oxbow" and was renamed eleven days later. It exited beta with version 21.04 in April 2021 and has been on a calendar versioning schedule since. The current stable line as of this review is the v26.x series, with security releases shipping monthly.
The pitch is simplicity. Most wikis ask you to think in pages and tags. BookStack asks you to think in shelves, books, chapters, and pages, which maps to how people already organize physical reference material. That model is opinionated, and it is the main reason teams either love BookStack or bounce off it.
It is fully free to download, install, and self-host. There is no paid tier, no enterprise SKU, no usage cap. The trade is that you run it yourself.
Who maintains BookStack?
BookStack is maintained by Dan Brown and a community of contributors. As of the project's tenth anniversary in July 2025, the repo had 16,926 GitHub stars and 186 direct contributors, making it the most popular PHP wiki on GitHub. In early 2026, the canonical source moved from GitHub to Codeberg, though a mirror remains on GitHub for the existing audience.
Funding comes from sponsorships listed on the project page (Diagrams.net is a longtime gold sponsor) and from individual GitHub Sponsors. There is no commercial entity behind BookStack pushing a paid version, which is part of why the project has stayed focused.
Key BookStack features
BookStack ships a focused feature set rather than a kitchen sink. The headline capabilities:
- Books, chapters, pages, shelves. Four content levels, no more. Pages live in books, chapters group pages inside a book, shelves group books. A book can sit on multiple shelves.
- WYSIWYG and Markdown editors. Both are built in. The Markdown editor has a live preview pane. Switching between editors per page is supported.
- Full-text search. You can search at book level or globally across every book, chapter, and page. Direct links to specific paragraphs are also supported.
- Role and permission system. Granular roles control who can view, edit, create, or delete content. Permissions can be set per-user or per-role and inherited down the hierarchy.
- Page revisions. Every edit creates a revision. You can diff revisions and roll back to any previous version.
- Diagrams.net (draw.io) integration. Built into the page editor for inline diagram creation. No external tool needed.
- PDF, HTML, plain text, Markdown export. Pages and books export to all four formats out of the box.
- OIDC, SAML2, LDAP, plus social login. Email and password is the default, but the SSO options cover most enterprise environments. Social logins include GitHub, Google, Slack, Microsoft, and others.
- Multi-factor authentication. TOTP and backup codes are built in and can be enforced per-role.
- REST API. Covers CRUD operations on the core content types, useful for migrations and automation.
- 43 languages. UI translations contributed by the community, configurable per-user.
- Light and dark themes. Configurable per-user.
- Visual and logical theme systems. Customize views, icons, and translation strings without forking the core.
That feature list is intentionally narrower than Confluence or Wiki.js. There is no native plugin system in the traditional sense, no real-time collaborative editing, and no built-in commenting workflow that competes with Notion's. If you need any of those, BookStack is not your tool.
How do you install BookStack?
There are three real install paths. None of them are zero-config, but the Docker route gets close.
Docker
The community-maintained image at linuxserver/bookstack is the path most teams take. You run a docker-compose.yml with the BookStack container plus a MariaDB or MySQL container, set a few environment variables for the database connection and app URL, and you are up. Backups are a matter of dumping the database and snapshotting the uploads volume.
LAMP stack
If you already run a Linux server with Apache or Nginx, PHP 8.2+, and MySQL or MariaDB, the official installation guide walks you through cloning the repo, running Composer, configuring a .env, and serving the public/ directory. This is more work than Docker but gives you the most control over the runtime.
Manual / hosted by a third party
A handful of providers (Cloudron, Stellar Hosted, NETWAYS, OctaByte, and others) offer one-click BookStack hosting for a monthly fee. This is the closest BookStack gets to a SaaS experience, but you are still running BookStack on top of someone else's infrastructure. Pricing varies from about $5/month to $30/month depending on the provider.
The minimum hardware target is genuinely small: BookStack runs on the project's reference VPS at around £2.50/month. Most teams over-provision and stop noticing it.
How does BookStack compare to other wikis?
The honest comparison is split: BookStack against other self-hosted wikis, and BookStack against hosted SaaS knowledge bases. They are different categories doing different jobs.
Self-hosted alternatives
| Tool | Stack | Editor | Best for |
|---|---|---|---|
| BookStack | PHP / Laravel | WYSIWYG + Markdown | Small to mid teams that want structure |
| Wiki.js | Node.js | Markdown + visual | Teams that want flexibility and integrations |
| DokuWiki | PHP, no DB | Markup (DokuWiki syntax) | Tiny teams that want zero database setup |
| MediaWiki | PHP | Markup (wikitext) | Public encyclopedic wikis |
| Outline (self-hosted) | Node.js | Block-based | Teams that like a Notion-style editor |
Wiki.js is the closest direct competitor. It has a more modern UI, real-time collaboration, and richer authentication options, but it asks more of your server and the setup is more involved. If your team prioritizes structure over flexibility, BookStack wins. If you want a sleeker editor and tag-based organization, Wiki.js usually wins.
DokuWiki is the simplest to install (no database, just files) but feels dated and is harder to scale past a few hundred pages. MediaWiki is what Wikipedia runs on and is overkill for most internal wikis.
Hosted SaaS alternatives
| Tool | Hosting | Pricing (entry) | Best for |
|---|---|---|---|
| BookStack (self-hosted) | You run it | Free + server cost | Internal wikis, control-conscious teams |
| Confluence | Atlassian cloud | $6.05/user/month | Large orgs already on Jira |
| Notion | Notion cloud | $10/user/month | Cross-functional teams |
| Outline (hosted) | Outline cloud | $10/user/month | Notion alternative with cleaner docs focus |
| GitBook | GitBook cloud | $8/user/month | Public-facing developer docs |
The trade is straightforward. Confluence, Notion, Outline, and GitBook bill per seat. BookStack costs the same whether you have 5 users or 500. The flip side is that none of those SaaS tools require you to run Docker, manage backups, or apply security patches. For a team of 50 paying $300/month for Confluence, BookStack pays for itself in a month. For a team of 5, the math is closer to neutral once you account for sysadmin time.
For deeper SaaS comparisons, the Confluence alternative breakdown covers the trade-offs in full.
What is BookStack actually good at?
After running BookStack for a real team, the strengths show up quickly:
- Onboarding new team members. The book metaphor makes it obvious where things live. New hires find the "Engineering Onboarding" book and read it like a manual.
- Internal SOPs and runbooks. Hierarchical structure suits step-by-step content. Chapters group related procedures, pages hold the actual steps.
- Policy and compliance docs. Page revisions and granular permissions mean you can lock down sensitive content and audit who changed what.
- Long-lived reference material. Books that get updated monthly rather than minutely. The structure rewards content that doesn't move much.
- Teams that want their data on their own infrastructure. No vendor, no data egress concerns, no surprise pricing.
The internal documentation playbook covers the workflow side of running a wiki like this in detail.
Where does BookStack fall short?
Every honest review has to cover the limits. BookStack has a few real ones.
No native cloud-hosted version. There is no bookstack.com you sign up for. You either run it yourself or pay a third-party host. For teams without a sysadmin, that is a hard barrier.
The structure is rigid. Books, chapters, and pages is the only way to organize content. There is no nested-folder model, no Notion-style infinite-depth pages, no graph view. Teams that want fluid information architecture often outgrow it.
Public-facing docs are not the use case. BookStack can be made publicly viewable, but it does not give you a branded marketing-grade docs site. The theming is basic. There is no custom domain plus SSL workflow that compares to a hosted docs platform. If you want public product documentation, look at a SaaS knowledge base or a hosted docs tool instead.
No real-time collaboration. Two people editing the same page step on each other's changes. The page-revision system catches it, but the live-Google-Docs experience is not there.
Plugin ecosystem is limited. The "Visual Theme System" and "Logical Theme System" let you customize behaviour, but there is no marketplace of community plugins. You write the customizations yourself.
Setup is not zero-config. Docker makes it tractable, but you still need to wire up MariaDB, configure the .env, set up an SMTP server for password resets, and arrange backups. A non-technical user cannot install BookStack alone.
Where Docsio fits compared to BookStack
BookStack and Docsio solve different problems for different audiences.
BookStack is the right choice when you need an internal wiki for a small or mid-sized engineering team, you have someone who can run a Docker container, and you want to keep your data on infrastructure you control. It is the cleanest option in that category.
Docsio is the right choice when you are a SaaS founder or small product team that needs a branded, public-facing documentation site live this week, with no PHP setup, no hosting decisions, and an AI agent that drafts the actual content from your existing website. The AI generates structured docs from your URL in under five minutes, hosted with SSL, custom domain support included on every plan. Two different jobs.
If you want internal wiki plus public docs, you can run both. BookStack handles the internal SOPs, Docsio handles the customer-facing site.
Who should pick BookStack?
The clear "yes" cases:
- Small to mid engineering teams (5 to 50 people) who want structured internal docs without per-seat billing
- Self-hosting fans who want their data and infrastructure under their control
- Compliance-conscious orgs that need on-prem deployment and audit trails
- Budget-constrained teams moving off Confluence at $6+/user/month
- Replacements for Notion or Confluence where the team specifically wants the book metaphor
The "probably not" cases:
- Public-facing product documentation (use a hosted docs platform)
- Teams that need real-time collaboration (use Notion or Outline)
- Teams without a technical owner (use a SaaS option)
- Highly fluid information architecture (use Notion or Wiki.js)
A useful gut check: if your team would happily read a 30-page onboarding manual organized as a book, BookStack will feel right. If your docs are more like a constantly-updating Slack thread, BookStack will feel constraining.
How does BookStack compare to Confluence?
This is the single most-asked comparison, so it gets its own section. The headline differences:
- Cost. Confluence Standard starts at $6.05/user/month. BookStack costs whatever your server costs.
- Hosting. Confluence is Atlassian Cloud (or self-hosted Data Center starting at $27,000/year). BookStack is self-hosted on whatever you run.
- Editor. Confluence's editor is more polished. BookStack's is simpler and ships both WYSIWYG and Markdown.
- Features. Confluence has more: macros, integrations with Jira, advanced workflows, page templates, in-line comments. BookStack covers the wiki essentials and stops.
- Lock-in. Confluence's export is workable but messy. BookStack exports clean Markdown, HTML, PDF, or plain text per page or per book.
For teams already paying for the Atlassian suite (Jira, Bitbucket, etc.), Confluence is the path of least resistance. For everyone else, BookStack is dramatically cheaper and good enough at the wiki job.
Frequently asked questions
What is BookStack used for?
BookStack is used to build internal wikis, knowledge bases, runbooks, SOPs, onboarding manuals, and reference documentation. Teams typically run it as a private internal tool for their engineering, operations, or support staff. It works for any structured documentation that fits the books-and-chapters model.
How much does BookStack cost?
BookStack is fully free and open source under the MIT license. You pay only for the server you run it on, which can be as low as a few dollars per month for a small VPS. There is no paid tier, no per-seat pricing, and no enterprise SKU. Third-party hosts charge a small monthly fee if you do not want to self-host.
How does BookStack compare to Confluence?
BookStack is free and self-hosted with a simpler, more focused feature set. Confluence is paid SaaS starting at $6 per user per month with deeper integrations into the Atlassian suite. For pure wiki use, BookStack is significantly cheaper. For teams already on Jira and Bitbucket, Confluence is the path of least resistance.
Is BookStack good for public documentation?
BookStack can be configured to be publicly viewable, but it is not designed for branded customer-facing product docs. The theming is basic and there is no native custom-domain plus SSL workflow that competes with hosted docs platforms. For public product documentation, a tool focused on that use case is a better fit.
Who uses BookStack?
BookStack is used by small to mid-sized engineering teams, IT departments, educational institutions, and self-hosting hobbyists. Public examples on TheirStack include Dallas Theological Seminary, Canadian Bank Note Company, and various IT services firms across the US, France, Germany, and Canada.
Final verdict
BookStack is the cleanest open-source self-hosted wiki for teams that want structure, control, and zero per-seat billing. Ten years in, it is stable, well-maintained, and unburdened by feature creep. The book metaphor is opinionated and that opinion is the entire point.
If you need an internal wiki and you can run a Docker container, install it tonight. If you need a public-facing branded docs site, that is a different tool and a different review. For everything in between, the best move is honest about the trade-off: BookStack saves you money on seats, costs you sysadmin time, and gives you a tidy place to write things down.
For a quick pick across the broader category, the best knowledge base software roundup compares hosted and self-hosted options side by side. If your job is public-facing docs from your existing website, Docsio generates a branded docs site in under five minutes and hosts it for you, free.