BookStack

Self-hosted wiki and documentation, honestly reviewed. No marketing fluff, just what you get when you run it yourself.

TL;DR

• What it is: Open-source (MIT) documentation and wiki platform built on PHP and Laravel — think Confluence or Notion, but the database is yours and the bill stays flat [2][5].
• Who it’s for: Small teams, internal ops, and solo founders who need structured documentation without paying $10/user/month to Atlassian. Also anyone who’s tried raw Markdown wikis and wants something their non-technical teammates will actually use [2][3].
• Cost savings: Confluence Standard runs $5.75/user/month (billed annually) — $115/month for 20 users. BookStack self-hosted runs on a £2.50 VPS by the project’s own claim [website]. Managed hosting via Stellar Hosted starts at €49/month for unlimited users [4].
• Key strength: Opinionated hierarchy (Shelves → Books → Chapters → Pages) that forces structure without configuration hell. WYSIWYG editor with built-in diagrams.net drawing. SSO (SAML2, OIDC, LDAP) included in the free community edition — not paywalled [website].
• Key weakness: The hierarchy is a double-edged sword — if your use case doesn’t fit the Books mental model, the structure fights you. The Markdown editor is functional but draws complaints. Not designed for extensibility; if you need plugins or custom content types, look elsewhere [3].

---

What is BookStack

BookStack is a self-hosted wiki platform built for structured, team-readable documentation. The project description is admirably plain: “a platform to create documentation/wiki content built with PHP & Laravel” [GitHub]. The homepage calls it “Simple & Free Wiki Software” — and for once, the self-description is accurate [website].

The core idea is a three-tier (technically four-tier) hierarchy: Shelves at the top level, containing Books, which contain Chapters, which contain Pages. Most users end up ignoring Shelves and working with Books as top-level categories [2]. This structure is the product’s main design bet. It doesn’t give you a blank canvas like Notion or a flat file tree like an Obsidian vault — it gives you a forced organizational system and trusts that the system is good enough for most documentation use cases.

The platform sits at 18,472 GitHub stars as of this review, which puts it in solid second tier behind Confluence and Notion but ahead of most other self-hosted wiki options. It’s built by a solo developer (Dan Brown) with community contributions, and the project has survived long enough to accumulate active commercial sponsors including diagrams.net and onyx.app [README].

What makes it practically different from the alternatives: SSO is included for free (Outline, for comparison, gates SAML behind a $59/month plan), the WYSIWYG editor has embedded diagrams.net support that reviewers specifically call out as a standout feature [3], and the whole stack runs on hardware that costs less than a Netflix subscription.

---

Why people choose it

The reviews we synthesized tell a consistent story: people land on BookStack because they want Confluence’s structure without Confluence’s pricing, and they stay because the UI is genuinely beginner-accessible.

The Confluence/Notion comparison. Confluence charges per user. At 20 users you’re past $100/month. Notion is cheaper but its freeform structure creates documentation that looks organized until someone new joins and can’t find anything. BookStack’s opinionated hierarchy — the thing reviewers sometimes complain about — is actually why teams end up keeping it. A user on AlternativeTo described it: “the preset structure of the software with shelves, books, chapters, pages makes it very comprehendible to organise, sort and navigate” [3].

The noted.lol reviewer, who has been using BookStack for several years, captures the practical reality clearly: “I have been using Bookstack for a few years and I absolutely love it.” Their actual use is minimal — just Books as categories and Pages inside them, ignoring Shelves and Chapters entirely — which is itself a telling signal. The platform works even when you only use a fraction of its organizational model [2].

The SSO angle. For small companies standardizing on Google Workspace or Azure AD, the fact that BookStack includes SAML2, OIDC, and LDAP in the free edition is a meaningful differentiator. Self-hosted tools that paywall SSO (Outline does this, GitBook does this) create a frustrating situation where you pay to manage users on top of running your own infrastructure. BookStack doesn’t do that [website][5].

The honest negative. At least one AlternativeTo commenter called BookStack “one of the worst documentation apps I had to use”, specifically criticizing the Markdown editor and the inability to use internal relative links as you would in any other wiki [3]. That’s a minority position — the overall sentiment across sources is positive — but the Markdown editor limitation is a real one. If your team writes in Markdown and expects wiki-style [[internal links]], BookStack will disappoint [3].

---

Features

Based on the official website, README, and review coverage:

Core content:

• WYSIWYG page editor (TinyMCE-based) with standard formatting, tables, code blocks, image embedding [website][5]
• Optional Markdown editor with live preview — switchable per-user in settings [website][2]
• Built-in diagrams.net (draw.io) integration — draw flowcharts and architecture diagrams inside any page [website][3]
• Page revision history — full versioned history of every page change [website]
• Cross-book sorting — move chapters and pages between books [website]

Organization:

• Four-tier hierarchy: Shelves → Books → Chapters → Pages [2][5]
• Global full-text search across all content [website]
• Deep-link to any paragraph [website]
• Tags for additional categorization [5]

Access control:

• Roles with configurable permissions (Administrators, Editors, Readers) [5]
• Per-book, per-chapter, per-page permission overrides [2][5]
• Public or private instance — toggle globally or per-page [2][website]
• SSO via OIDC, SAML2, and LDAP — included free [website]
• Social login options (Google, GitHub, etc.) as secondary auth [website]
• MFA (TOTP, backup codes) enforced at role level [website]

Export:

• Per-page export to PDF, HTML, Plain Text, or Markdown [2]
• Bulk export via CLI commands documented in the official docs [2]

API and integrations:

• REST API for external integrations [3][5]
• Multi-language UI — EN, FR, DE, ES, IT, JA, NL, PL, RU, and more via Crowdin [website]
• Light and dark mode, configurable per user [website][2]
• Custom branding (logo, colors, instance name) [2][website]

What it doesn’t do:

• No plugin system — the project README explicitly states it’s “not designed as an extensible platform” [README]
• No real-time collaborative editing (Confluence, Notion, Outline all have this)
• No AI writing assistant
• No built-in comments on pages (there are activity feeds but not threaded page discussion)

---

Pricing: SaaS vs self-hosted math

BookStack self-hosted (Community Edition):

• License cost: $0 (MIT) [README]
• Minimum VPS: £2.50–$6/month (project cites running happily on a £2.50 IONOS VPS) [website]
• All features included: SSO, MFA, API, full hierarchy, unlimited users, unlimited pages

Managed BookStack via Stellar Hosted:

• Standard: €49/month — unlimited users, unlimited docs, 10GB storage, email support [4]
• Premium: €99/month — 100GB storage, Slack support, SSO integrations, data migrations [4]
• Custom: from €149/month — unlimited storage at €25 per 100GB, SLA, HA [4]
• Enterprise: from €1,000/month — SOC 2 Type II, ISO 27001 compliance, dedicated account manager [4]

Confluence for comparison (Atlassian pricing, 2026):

• Free: up to 10 users
• Standard: ~$5.75/user/month (annual)
• 20 users: ~$115/month
• 50 users: ~$287/month
• 100 users: ~$575/month

Notion for comparison:

• Plus: $10/user/month
• Business: $15/user/month
• 20 users on Business: $300/month

Concrete math for a 25-person startup:

Confluence Standard at 25 users ≈ $144/month = $1,728/year. Notion Business at 25 users = $375/month = $4,500/year. BookStack self-hosted on a $12 Hetzner VPS ≈ $144/year. Stellar Hosted Standard ≈ €588/year ($650 equivalent) — still 62% cheaper than Confluence, with someone else handling updates.

The self-hosted savings are obvious. The managed-hosting math is also usually favorable once you account for engineering time to maintain a self-hosted instance and apply security patches. BookStack releases security updates actively — the homepage shows three security releases in the last 90 days [website].

---

Deployment reality check

The noted.lol review includes a working Docker Compose stack that gets a BookStack instance running with a MariaDB container. It’s a standard two-container setup with environment variables for the database connection [2]. The official image via lscr.io/linuxserver/bookstack is the most commonly used route.

What you actually need:

• A VPS with 1–2GB RAM (the project claims it runs on very low-end hardware [website])
• Docker and docker-compose, or a LAMP stack (PHP, MySQL/MariaDB, web server)
• A domain and reverse proxy for HTTPS (Caddy or nginx)
• An SMTP provider for email invitations and notifications

What can go sideways:

• The Markdown editor draws consistent criticism. One AlternativeTo reviewer rated it one star specifically because of it, calling it “horrible” with no support for internal relative links [3]. If your team is Markdown-native and expects wikilinks, this is a real blocker.
• The hierarchy is enforced. There’s no free-form page organization outside Books. If you want a flat, tag-based system (like Notion databases or Obsidian’s graph), BookStack’s structure will feel constraining.
• No real-time co-editing. Two people editing the same page will conflict. This is a meaningful gap versus Notion or Google Docs for teams that work on documents simultaneously.
• Security patching is your responsibility on self-hosted. The three recent security releases visible on the homepage [website] indicate an active maintainer, but also mean you need to stay current.

Time estimate: A technical user following the Docker Compose method can have a working instance in under 30 minutes. Adding a domain, SSL, and SMTP takes another hour. For a non-technical founder, budget a full afternoon or bring in someone to deploy it once.

---

Pros and cons

Pros

• MIT license, no paywalled features for core functionality. SSO (SAML2, OIDC, LDAP), MFA, the API, and the full hierarchy are all available in the free edition [website][5]. No “enterprise edition” for essential security features.
• Genuinely simple UX. The consistent reviewer takeaway is that non-technical people can use it without training. The WYSIWYG editor requires basic word-processing skills — that’s it [README][5].
• Built-in diagrams.net. Draw flowcharts, architecture diagrams, and process maps inside pages without switching tools. Reviewers specifically cite this as a standout feature [3][website].
• Flat per-instance cost. No per-user pricing. Add 5 users or 500, the VPS bill doesn’t change [2][website].
• Active maintenance. Three security releases in the past 90 days shows the project is watched and patched [website]. 18,472 GitHub stars and commercial sponsors indicate project health.
• Export flexibility. PDF, HTML, Markdown, and plain text per page, plus bulk export — no vendor lock-in on your content [2].
• Long-term stability. The project has a relaxed, explicitly stated philosophy of slow, continuous evolution with a stable upgrade path [README]. Not chasing hype features.

Cons

• The Markdown editor is weak. No internal wikilinks ([[Page Name]]), and reviewers specifically call it out as a pain point [3]. If your team writes Markdown and expects wiki-style cross-linking, this is a hard limitation.
• No real-time collaboration. Confluence, Notion, and Outline all have simultaneous co-editing. BookStack has page revision history but no live cursor presence [5].
• Hierarchy isn’t optional. Everything must live in a Book. If you want flat search-driven organization, there’s no way to turn off the hierarchy [2][5].
• Not extensible by design. The README explicitly says BookStack is “not designed as an extensible platform” for other use cases [README]. No plugins, no custom content types, no API-driven embed widgets.
• Solo maintainer. The project is primarily maintained by one developer (Dan Brown). This is both a strength (clear vision, no design-by-committee) and a risk (bus factor of one). Commercial sponsors help but don’t change the bus factor.
• No AI features. No writing assistance, no semantic search, no content suggestions. If you’re evaluating documentation tools in 2026, this is a visible gap versus Notion AI or Confluence AI.

---

Who should use this / who shouldn’t

Use BookStack if:

• You’re running a team of 5–100 people paying Confluence per-user pricing and want the bill to go away.
• Your team’s documentation workflow is structured — SOPs, runbooks, onboarding guides, internal wikis — not freeform notes.
• You need SSO and MFA without paying for an enterprise tier.
• You’re comfortable deploying Docker once (or willing to pay Stellar Hosted €49/month to skip that).
• You want a tool your non-technical teammates will actually write in, not just read.

Skip it (try Outline instead) if:

• You want real-time collaborative editing.
• Your team works heavily in Markdown and expects wikilinks.
• You want a cleaner modern UI with a less opinionated structure (though Outline gates SSO behind $59/month).

Skip it (stay on Notion) if:

• You need database views, relational content, or a blank-canvas approach.
• You’re a solo founder with simple needs — Notion’s free tier covers you.
• Your team already has Notion workflows built.

Skip it (try Wiki.js) if:

• You want flat-file storage, Git integration, or a heavily customizable wiki engine.
• Your team has developers who want to manage documentation like code.

Skip it (use Confluence) if:

• You’re deeply integrated with the Atlassian suite (Jira, Trello, Bitbucket) and the integrations justify the cost.
• Your compliance requirements need Atlassian’s enterprise certifications.

---

Alternatives worth considering

• Outline — Modern UI, better Markdown support, real-time collaboration. SSO costs $59/month; self-hosted is free. Closer to Notion in feel, less opinionated structure than BookStack [3].
• Wiki.js — More powerful, supports Git storage and many databases, highly configurable. Steeper setup. Better for engineering-led documentation.
• Notion — The freeform option. No self-hosted version. Per-user pricing at scale. Good if you value flexibility over structure.
• Confluence — The incumbent. Deep Atlassian integration, per-user pricing, no self-hosted free option.
• Docusaurus / MkDocs — Developer-centric, Markdown-first, Git-backed. No admin UI for non-technical contributors.
• XWiki — Enterprise wiki, more extensible than BookStack, more complex to run.

For a non-technical team leaving Confluence, the realistic shortlist is BookStack vs Outline. BookStack wins on price (SSO is free), simplicity, and the diagrams.net integration. Outline wins on collaboration and Markdown quality.

---

Bottom line

BookStack is what it says it is: a simple, self-hosted documentation platform that trades flexibility for approachability. The hierarchy is real and enforced, the Markdown editor has genuine limits, and there’s no plugin system or AI layer. But for a 10–50 person team running SOPs, internal guides, and onboarding docs — and paying Atlassian $100–$500/month for the privilege — the trade-offs are obviously worth it. MIT license, SSO included free, diagrams.net built in, runs on cheap hardware. The savings math is straightforward: a $6 VPS replaces a per-user bill that compounds every time you hire.

The one real risk is the single-maintainer dependency. The project is healthy and sponsored, but it’s not a VC-backed team with an SLA. If that’s the concern, Stellar Hosted’s managed tier [4] gets you maintained infrastructure at €49/month — still cheaper than Confluence at 20 users.

If the deployment step is the blocker, that’s a one-afternoon problem — exactly what upready.dev deploys for clients.

---

Sources

1. SourceForge — BookStack Reviews. https://sourceforge.net/software/product/BookStack/
2. noted.lol — “Bookstack - More than a Self Hosted Wiki”. https://noted.lol/bookstack/
3. AlternativeTo — “BookStack: An open source knowledge management application” (community reviews and feature listing). https://alternativeto.net/software/bookstack/about/
4. Stellar Hosted — “BookStack hosting - Managed, fast and secure” (pricing and managed hosting details). https://www.stellarhosted.com/bookstack/
5. ReviewsApp.org — “BookStack – Simple Team Documentation Management”. https://reviewsapp.org/bookstack-simple-team-documentation-management

Primary sources:

• GitHub repository: https://github.com/bookstackapp/bookstack (18,472 stars, MIT license)
• Official website: https://www.bookstackapp.com
• Live demo: https://demo.bookstackapp.com
• Installation docs: https://www.bookstackapp.com/docs/admin/installation