32 self-hosted Confluence alternatives

Last reviewed Aug 26, 2026 · 451 words

Before comparing wikis, answer one question: does your team write documentation in a browser, or in a Git repo? Browser writers should be choosing between BookStack, Outline, and Docmost. Teams whose docs live next to code are usually happier skipping the wiki entirely for MkDocs or Docusaurus, where pages are Markdown files that ship through the same pull-request review as everything else. Most Confluence refugees are the first kind, so that's where this guide spends its time.

What you gain and what you give up

The gains are speed and cost. Every app here searches and loads noticeably faster than Confluence Cloud, there's no per-seat bill creeping up with headcount, and your internal engineering docs stop living on someone else's infrastructure. Permissions, SSO, and LDAP are covered — BookStack, Outline, Docmost, and Wiki.js all speak SSO.

The losses are the Atlassian gravity well. No Jira issue embeds, no marketplace of macros, no vendor to page when it breaks — you are now the person who upgrades the wiki and backs up its Postgres database. And nothing self-hosted matches Confluence's whiteboards and databases features yet.

Which replacement fits which user

BookStack (19,001 stars, MIT, PHP) is the easy default for teams up to a few dozen: its books-chapters-pages structure keeps non-writers organized, and it runs happily in 512 MB. Outline (40,325 stars) is the choice when real-time collaborative editing and slick search matter more than a fully open license — it's BSL-licensed and wants Postgres plus Redis. Docmost (21,464 stars, AGPL) is the closest visual match to modern Confluence, with spaces, nested pages, and live editing; it only shipped in 2024, so expect rough edges. Wiki.js fits teams that want many editors and auth providers in one engine, with the caveat that its version 3 rewrite has been in progress for a while.

What survives the export

Confluence exports spaces as XML, HTML, or PDF. Nothing here ingests the XML. The workable path is HTML export plus a converter script into Markdown — page text, headings, and images survive; macros, page-tree ordering, comments, and permissions do not. BookStack can ingest HTML pages through its API, and Outline imports Markdown in bulk. Plan on a scripted bulk pass, then a human week of re-organizing the top 50 pages people actually read. Historical page versions stay behind in Atlassian's export.

The default pick

BookStack for most teams: easiest to run, easiest to teach, MIT-licensed, and boring in the way documentation infrastructure should be. Pick Docmost instead if your team will genuinely miss editing the same page at the same time.