Most internal wikis fail not because the writing is bad but because finding anything becomes a chore after a few months. Flat lists of pages, endless search queries, and topics buried four clicks deep make people stop updating the wiki at all. BookStack is an open-source documentation platform that solves this by insisting on structure from the start. Content lives in a hierarchy of Shelves, Books, Chapters, and Pages, which means a reader can browse rather than just search. The project lives at github.com/BookStackApp/BookStack and has 18,948 stars.
| Fact | Value |
|---|---|
| What it is | Self-hosted team documentation platform |
| Built by | Dan Brown and community (open-source) |
| License | MIT -- free to use and modify |
| Platforms | Linux, Docker |
| Requires | PHP, MySQL/MariaDB, and a web server; or Docker |
| Install method | Docker Compose or Linux shell installer |
| Verdict | Install for structured internal documentation; evaluate if your team just needs a quick wiki |
What BookStack actually is
BookStack is a web application for writing and organizing team documentation. The defining feature is its hierarchy: at the top level you have Shelves, which are optional groupings that work like library sections. Below Shelves are Books, which are the main organizing unit. Each Book contains Chapters, and each Chapter contains Pages. Pages are where the actual content lives.
This structure is deliberately opinionated. When content is tagged "Server Onboarding > Chapter 3 > Setting Up VPN Access," a new hire can navigate there without knowing the exact phrase to search for. They browse the table of contents like a physical binder, not a search engine.
The application is built in PHP (a server-side programming language that powers a large share of the web, including WordPress). PHP runs on virtually any shared Linux hosting environment. The database is MySQL or MariaDB (MariaDB is a community-maintained fork of MySQL that is fully compatible; either works identically with BookStack). Both technologies are mature and widely supported, which matters for self-hosted software you plan to run for years.
BookStack is not a project management tool, not a CMS (Content Management System, a platform for managing a public website), and not a note-taking app. It is a focused documentation platform. That focus keeps the interface clean and the learning curve short for both writers and readers.
What you get after installing it
The editor is the first thing writers notice. BookStack ships with a WYSIWYG editor (What You See Is What You Get, meaning content looks formatted as you type rather than showing raw code) as the default. Bold text looks bold, tables look like tables, and images can be dragged in. For writers who prefer plain text, a Markdown editor (a lightweight formatting syntax popular with developers and technical writers) is also available per page. A built-in diagram tool for flowcharts and org charts means you do not need a separate tool like Lucidchart for simple visuals.
Search is full-text and covers all content across all Books. Page revision history tracks every edit with a diff view (a side-by-side comparison that highlights what was added or removed) so you can see what changed and who changed it. Attachments (PDFs, spreadsheets, images) can be uploaded and linked from any page.
Permissions work at the role level: Admin, Editor, Viewer, or custom roles you define, assigned per Book. Engineering docs can be read-only for the rest of the company; HR policy Books can be invisible to contractors. Granular enough for most configurations, without becoming a complex per-user permission matrix.
For corporate environments, BookStack supports SSO (Single Sign-On, meaning employees log in with their existing company credentials rather than creating a separate BookStack password) via SAML and LDAP. SAML (Security Assertion Markup Language) is the standard protocol used by enterprise identity providers like Okta and Azure Active Directory to handle that login handoff. LDAP (Lightweight Directory Access Protocol) is the older directory protocol used by on-premise Active Directory installations. If your company already manages user accounts centrally, BookStack can plug into that system. GitHub and Google OAuth (a login standard that lets users authenticate with an existing account rather than a new password) are also supported for smaller teams.
The REST API (Application Programming Interface, a way for software to talk to BookStack programmatically over HTTP) is well-documented and covers reading and writing all content types. This is the hook for AI agent workflows, covered more in the comparisons section.
The install experience
Two paths: Docker Compose or the shell installer for bare Linux.
The Docker path is the simpler one for most operators. Docker runs software in isolated containers, so all the PHP, database, and web server dependencies are bundled together. A docker-compose.yml file is in the official docs at bookstackapp.com. You fill in a few environment variables (configuration values like APP_URL, database credentials, and an encryption key that Docker reads at startup), run docker compose up -d, and BookStack is running. First setup takes ten to fifteen minutes.
The bare Linux path uses a community shell script that installs PHP, MySQL, Nginx (a web server that handles incoming requests), and BookStack itself on Ubuntu LTS (Long Term Support, a release that gets security updates for five years). Both paths produce the same result. After install, you open the URL in a browser and you are inside the editor.
One thing to plan for before installing: BookStack does not come with an automatic SSL certificate setup the way Coolify or similar tools do. You need to configure HTTPS separately, either by putting BookStack behind a reverse proxy (a web server like Nginx or Caddy that handles SSL and routes traffic to BookStack) or by running Certbot (a free command-line tool) to generate a Let's Encrypt certificate (a free SSL certificate from a nonprofit certificate authority that powers HTTPS on millions of sites). This is a one-time setup but requires a bit more familiarity with web server configuration than the install itself.
Where it fits and what to compare it to
The natural comparison is Confluence, Atlassian's documentation platform. Confluence uses a similar hierarchy (Spaces, Pages, child pages) and is the most common team wiki in enterprise settings. The difference is price and weight: Confluence on Atlassian Cloud starts at $5.75 per user per month, adds billing complexity as teams grow, and carries integration overhead from the rest of the Atlassian suite. BookStack is free to run on your own server, has no per-seat fee, and is simpler to administer. For teams that want Confluence-style structure without the Confluence price or the vendor dependency, BookStack is the practical answer.
Notion is the other common reference point. It uses a flat page structure (any page can be a subpage of any other page) and supports databases (tables where each row is a page). Notion is cloud-only and has no enforced hierarchy. Teams that want structure out of the box find BookStack easier to maintain at scale; teams that want total flexibility in how pages relate to each other lean toward Notion.
Wiki.js is the closest open-source alternative: also self-hosted, with a similar editor and full-text search. It supports more storage backends (Git, PostgreSQL, SQLite, S3) and is more flexible in how content is organized. That flexibility is also a tradeoff -- it puts the organizational decisions on your team instead of imposing sensible defaults. If you want structure decided for you, BookStack is easier to start with.
Outline is another open-source wiki worth evaluating (reviewed separately at agenthread.co/blog/outline-knowledge-base-review). Outline is more Notion-like in its editor and layout and targets teams that want a faster, more flexible writing experience. BookStack is more structured and better suited to documentation that needs to be navigable by people who did not write it.
The AI agent angle: BookStack's REST API makes it a useful output target for agents. A Claude Code or Cowork workflow that researches a topic, generates a report, or processes data can write the output directly to a BookStack page via API. The page lands in the right Chapter and Book, is immediately searchable, and carries a revision history. For teams using AI agents for research or documentation generation, this is a meaningful practical benefit over tools that require manual copy-paste.
Verdict
Install BookStack if your team produces documentation that people need to navigate, not just search. The hierarchy solves a real problem: information that is easy to write is often hard to find six months later, and BookStack's structure creates a browsable table of contents by default. The MIT license means no seat fees, no vendor lock-in, and no negotiating over pricing as the team grows.
Hold off if your team has fewer than ten to fifteen people and primarily needs a place to write quick notes. A flat wiki or even a shared folder of Markdown files might have less overhead. BookStack is worth its setup time when the documentation library is large enough that navigation matters.
SSO support via SAML and LDAP makes it serviceable in corporate environments where a basic wiki would not fit. The built-in diagram editor, revision history, and attachment support round out a feature set that compares well to paid alternatives at considerably lower total cost.