Self-hosted Confluence alternative: own your team's docs with BookStack

Your team's documentation is one of the most valuable things you own -- runbooks, onboarding guides, architecture decisions, the answers to the questions people keep asking. It's also exactly the kind of thing SaaS wikis quietly turn into a recurring bill. Confluence charges per user, every month, and keeps every page on Atlassian's cloud. Add a few contractors and the invoice climbs; the knowledge itself never quite belongs to you. BookStack is the alternative you host and own -- a genuine documentation platform, not a stripped-down notepad.

What BookStack is

BookStack is a free, open-source documentation and wiki platform built around a simple metaphor: your knowledge lives in pages, pages are grouped into chapters, chapters into books, and books sit on shelves. Anyone who has used a library already understands the structure, which is the whole point -- it's approachable in a way most wikis aren't. You don't have to use every level, either: a book can hold pages directly, so the same structure scales from a handful of notes to thousands of pages without getting in the way.

Under that friendly surface is a mature, full-featured application. It's been developed in the open since 2015, built on PHP and Laravel, and companies, schools, and open-source projects use it to run their entire knowledge base. Confluence puts single sign-on behind a paid add-on and meters every user past a small free tier. BookStack ships SSO for everyone, with no seat count to police.

The features that actually matter

• Shelves, books, chapters, and pages -- a four-level hierarchy that keeps a large documentation set navigable instead of a flat pile of pages. Books generate their own contents and page navigation automatically.
• A friendly WYSIWYG editor -- or Markdown -- write in a clean visual editor that behaves the way you expect, or switch to a live-preview Markdown editor; both save to the same page. Confluence's editor is perfectly good -- this one just doesn't bill per seat.
• Full-text search that actually finds things -- search across every shelf, book, and page at once, with search operators and tag filters to narrow results. It's the feature you reach for most, and it holds up.
• Granular permissions -- role-based access control with per-item overrides, right down to a single shelf, book, chapter, or page. Everyone gets it; there's no permissions tier to unlock.
• Built-in diagrams -- the drawing tool from draw.io (diagrams.net) is integrated directly into the editor, so architecture diagrams and flowcharts live inside the page, not stranded in some other app.
• Page revisions and history -- every edit is saved. Compare versions, see who changed what, and roll back with a click.
• Tags, comments, and exports -- tag content for cross-cutting organization, discuss changes in page comments, and export any page or book to PDF, HTML, or Markdown whenever you want your data out.
• A REST API and webhooks -- create and update pages programmatically, script bulk imports, or fire events into your other tools when content changes, so BookStack fits into whatever you already run.

Why self-host it instead of the hosted version

• Your knowledge stays yours. Documentation is often the most sensitive thing a company writes down -- incident postmortems, security procedures, internal architecture. Self-hosting keeps all of it on infrastructure you control, not stored and indexed on a third party's cloud under terms they can change.
• The cost doesn't scale per head. Confluence bills per user, every month, forever. A wiki that costs the same whether five people read it or five hundred changes how you think about access -- you stop rationing seats and just let everyone in. Self-hosted BookStack has no per-seat meter at all.
• It's yours to brand and bend. Set your own logo and primary color, wire up your own SSO, run it at your own domain. It reads like an internal tool your company owns, because it is one -- not a rented tab with someone else's name in the corner.

Who it's for

BookStack fits anyone who has outgrown scattered docs but doesn't want an enterprise contract:

• Small and growing teams who need a real knowledge base -- onboarding, runbooks, policies -- without watching a per-seat invoice grow with every hire.
• IT departments and MSPs documenting systems, procedures, and client environments, who need granular permissions to keep the right pages in front of the right people.
• Schools, communities, and open-source projects building a shared reference that should be free to read for everyone involved, where a per-user license makes no sense at all.

The honest setup notes

We'll be straight with you: BookStack is a proper web application, and running it yourself is a real commitment. It's a PHP/Laravel app that needs a MySQL or MariaDB database alongside it -- so you're maintaining two moving parts, and the database is where every page you write actually lives. That means backups you actually test, not just assume are running.

You'll also want SMTP configured for the things email is essential to -- user invitations, password resets, and notifications all depend on it. And like any self-hosted app exposed to the world, it needs regular updates for security fixes, plus TLS, a domain, and enough memory to stay responsive.

None of this is exotic. It's just steady, ongoing work that has nothing to do with writing documentation -- which is the part you actually care about. So you can do all of it yourself, or you can let us run it.

Deploy it in one click

Rolling your own BookStack means provisioning a server, installing PHP and its extensions, standing up a MariaDB database, configuring the web server and TLS, wiring in SMTP, and then owning every update and backup from then on. It's very doable, and it's an afternoon that turns into a standing chore.

On Caliber Node, you deploy BookStack in one click. We handle the database, the TLS certificate, the reverse proxy, and the runtime, on infrastructure we keep patched. You get a working instance at your own subdomain in a few minutes -- and it's still genuinely yours: real logs, SFTP access to your files, and your data exportable whenever you want it. Managed convenience, without the black box.

First run

Once your instance is live, here's the fastest path to a documentation base you'll actually use:

1. Sign in as the default admin, change the password, then set your instance name, logo, and primary color under Settings.
2. Create your first shelf -- think of it as a top-level category, like "Engineering" or "Company Handbook."
3. Add a book to that shelf and give it a clear title; this is where a real topic lives.
4. Write your first page in the WYSIWYG editor -- paste in an existing doc, drop in an image, or sketch a quick diagram to see the editor work.
5. Invite your team and set permissions on the shelf so everyone lands exactly where they should.

That's a working, searchable knowledge base -- built in about the time it took to read this.

The bigger picture

Documentation is institutional memory -- the accumulated knowledge that keeps a team functioning as people come and go. It's strange how readily we hand that to a vendor who bills us monthly for the privilege of reading our own words, and who holds the export button. Owning the tool you keep it in isn't really about saving a few dollars; it's about making sure the thing your team knows can't be locked behind a renewal notice or a pricing change. Your knowledge base should outlive any subscription.

Deploy BookStack in a few minutes →

Or browse the full app catalog to see what else you can own.

One-click self-hosted apps, managed for you -- real logs, SFTP, and your data always exportable. Never a black box.