BookStack: A Self-Hosted Confluence Alternative for Small Teams
Confluence's per-user pricing looks cheap until your team crosses 10 people and loses the free tier. I moved our internal docs to BookStack on a $6/month VPS instead - here's what it actually costs and where it falls short.
Confluence's free tier is genuinely generous — up to 10 users, no cost. The problem is what happens the moment you cross that line. At 11 users you're off the free tier entirely and paying per seat, and the per-seat price only goes up as the team grows. I moved our documentation to BookStack, a self-hosted wiki, once that math stopped making sense.
The actual pricing
| Team size | Confluence Free | Confluence Standard |
|---|---|---|
| Up to 10 users | $0 | — |
| 12 users | Not available | $6.70/user/month = $80.40/month |
| 25 users | Not available | $6.70/user/month = $167.50/month |
If your team is 10 people or fewer, stop reading and stay on Confluence Free — there's no cost argument for self-hosting here, and I'll say so plainly rather than pretend otherwise. This post is for teams that have grown past that line, where Confluence's cost scales with headcount and BookStack's doesn't.
What BookStack costs instead
BookStack runs comfortably on the same small VPS tier I use for everything else in this stack — a $6/month Vultr instance (1GB RAM) handles it fine for a small team; I've seen it stay under 300MB RAM including its MySQL database at that scale. That number doesn't move whether your team is 12 people or 50.
| Team size | Confluence Standard | Self-hosted BookStack |
|---|---|---|
| 12 users | $80.40/month | $6.00/month |
| 25 users | $167.50/month | $6.00/month (maybe $12 for a bit more headroom) |
At 12 users that's a 92.5% reduction. The gap only widens as headcount grows, because BookStack's cost is the box it runs on, not a per-seat multiplier.
What you give up
BookStack is a straightforward hierarchical wiki — Shelves, Books, Chapters, Pages — and it covers the core job of an internal knowledge base well. But it's not a line-for-line Confluence replacement:
- No Jira integration. If your team lives in the Atlassian ecosystem and leans on Confluence-Jira linking, that workflow doesn't exist here.
- Smaller plugin/app ecosystem. Confluence's marketplace has years of third-party integrations. BookStack's feature set is what ships in core — page templates, permissions, a decent WYSIWYG/Markdown editor, revision history, and search. That's enough for most internal docs, but not everything Confluence does.
- You own the backups. Confluence Cloud's data durability is Atlassian's problem. With BookStack, backing up the MySQL database and file storage is yours — not hard, but not automatic either.
For a small team that mainly wants searchable internal docs — onboarding guides, runbooks, decision records — BookStack covers that job well. If you're deep in Jira workflows and rely on that integration daily, the migration cost probably isn't worth it yet.
Setup, in short
BookStack is a PHP/Laravel app with a MySQL backend, and it ships an official Docker image, which is the fastest way to get it running: a docker-compose file with the app container and a MySQL container, point a domain at it, and set up TLS same as any other self-hosted service in this stack. It's a lighter lift than Ghost — no Node build step, no separate mail relay required unless you want email notifications for page changes.
I run mine on the same kind of small Vultr instance I use for the rest of this stack — see the full cost roll-up for how the pieces fit together.
Disclosure: this post contains an affiliate link to Vultr. If you sign up through it, I may earn a commission at no extra cost to you. I only link to providers I actually use.