Home / Software Alternatives

Self-Hosted Confluence Alternatives: The Operations Guide, Because the Install Is the Easy Part

Black server cabinets with red cabling standing in a row in a data center.

Photo: Brett Sayles / Pexels

Why this query exists, and the bar a replacement must clear

Atlassian is ending the self-hosted era of its own product: Confluence Server support ended in February 2024, new Data Center subscriptions stopped selling to new customers in March 2026, and Data Center itself reaches end of life on March 28, 2029, when instances go read-only. The readers of this guide are the teams that hosted Confluence for a reason, data residency, network isolation, or plain sovereignty, and now must host something else. The general Confluence guide frames the deadline; this guide owns the running of the replacement. A self-hosted Confluence alternative has to clear a specific bar before features matter: it deploys on your infrastructure including air-gapped networks, it keeps data residency under your control, and it authenticates through enterprise SSO (SAML, LDAP, or OIDC) without a paid add-on unlocking the login page. BookStack, Wiki.js, and XWiki clear the bar fully in their free editions; Docmost clears it with its importer and some enterprise features on a paid edition; Outline self-hosts under a source-available license, which the open-source companion audits in full. If your requirement is a vendor contract rather than your own operations, that is the on-premise guide's question, and answering it with this bench will disappoint both sides.

ToolInstall weightStackSSO in free editionUpdate style
BookStackLightestPHP and MySQLYes (LDAP, SAML, OIDC)Release upgrades, well documented
DokuWikiLightestPHP, files onlyVia plugins and auth back endsVery low maintenance
Wiki.jsMediumNode.js and a databaseYes, pluggable authVersion upgrades need care
DocmostMediumDocker, PostgreSQL, RedisCore yes; importer is paidContainer updates
XWikiHeaviestJava and a databaseYesPlatform upgrades, planned windows

The operations that decide whether this survives

Install screenshots are where incumbent guides stop; operations are where self-hosting is won. Update duty first: a wiki holding company knowledge is internet-adjacent infrastructure, and an unpatched one is a liability with your procedures inside it, so the discipline is monthly updates with a server snapshot taken before each run and the upgrade command written down where a second person can find it. Backups second: the database plus uploaded attachments plus configuration, copied off the machine, because a backup on the same disk is a hope, not a backup. Restore third, and this is the step everyone skips: restore the backup into a scratch instance once before go-live, and once a year after, because the first time you test a restore should not be during the incident. Ownership fourth: name the person who owns this server on a holiday weekend, in writing, with a deputy. The tools differ mainly in how much of this they demand. BookStack and DokuWiki can be run by a competent generalist in an afternoon a month. Wiki.js and Docmost ask for ordinary container and database care. XWiki asks for a platform owner, and repays it with enterprise depth. Price the whole thing honestly against staying hosted: the licenses here are $0, and Confluence Cloud's per-user cost varies by band (November 2026 reads place Standard between about $5.78 and $7.15 per user), so below roughly a few dozen users the hosted bill is often cheaper than your admin hours, and the reason to self-host is sovereignty, not savings. Say that out loud in the planning meeting and the decision gets better.

Interactive tool

Comparison Builder

Pick two or three products and see them side by side on the numbers that decide the purchase.

MeasureBookStackWiki.jsOutline
Starting paid priceFreeFreeFree
Free optionFree plan: fully free and open source; you provide the serverFree plan: fully free and open source; you provide the serverFree plan: the self-hosted Community edition is free to run on your own server
PlansSelf-Hosted: freeSelf-Hosted: freeSelf-Hosted Community: free ยท Cloud: not published
PlatformsWeb, LinuxWeb, Linux, Windows, macOSWeb
Best forinternal manuals and runbooks, small teams self-hosting a wiki, ops documentationtechnical teams that think in Markdown, Git-backed documentation, self-hosters who want a modern wikiteams wanting a modern wiki they can run themselves, Confluence refugees who value the editor, Slack-centric teams
StrengthsThe simplest serious wiki to install and run; Fixed hierarchy keeps documentation findable; Enterprise sign-in (LDAP, SAML, OIDC) included freeMarkdown pages can live in a Git repository; Modern editor with multiple editing modes; Flexible auth, search, and storage back endsThe most modern editing experience among self-hostable wikis; Real-time collaboration and strong search; Slack and API integrations
Watch out forThe book structure is deliberately rigid; No real-time collaborative editing; You own updates, backups, and securityAGPL-3.0 terms apply to modified network deployments; Heavier to run than BookStack; The 3.0 release line has been long in developmentBSL-1.1 is source-available, not an OSI open-source license; Hosting it as a competing document service is excluded by the license; Cloud pricing was not verified to this dataset standard

Lowest entry price: BookStack at Free per month flat. Real free plan: BookStack, Wiki.js, Outline. Entry price is the floor, not the decision: check the plan line above for the tier that actually includes the feature you need.

All figures from vendor pricing pages, checked November 18, 2026. Some vendors price by contacts, tasks, or operations instead of seats; those notes are in the plan data and the linked pricing guides.

Choosing your weight class, then migrating

Match the tool to the operator you actually have. A small team with one technical generalist should take BookStack: shelves, books, chapters, and pages, enterprise sign-in free, and the shallowest operations curve on the bench. A technical team that thinks in Markdown and Git should take Wiki.js, accepting its heavier runtime for pages that can live in a repository. A team replacing Confluence's collaborative feel should take Docmost, budgeting its paid Business edition ($6 per seat billed annually in our dataset) if the Confluence importer and enterprise features matter. An organization replacing Data Center at scale should take XWiki and staff it like the platform it is. Migration follows the standing method: export the full Confluence instance once and keep it read-only, inventory spaces by macro dependency because app-powered macros convert nowhere, migrate the living third of pages, and run the new wiki as truth for a full quarter before the old one goes dark. With the 2029 deadline, a migration begun in 2027 is a project; begun in 2028, it is an emergency with a sales team attached. The checklist below sequences the operational setup in the order that prevents regret.

Interactive tool

Self-Hosted Wiki Operations Checklist

Check off each step as you finish it. Your progress stays on this page.

0 of 6 complete

0% done

Related guides

This decision rarely stands alone. The guides below cover the closest questions on the chart, each with prices checked on the vendor pages.

Frequently asked questions

What is the best self-hosted alternative to Confluence?

BookStack for most teams: free and open source under MIT, the lightest install on the bench, enterprise sign-in (LDAP, SAML, OIDC) included, and a hierarchy that keeps documentation findable. Wiki.js for Markdown and Git-centered teams, Docmost for a modern collaborative editor, and XWiki when the deployment is large enough to deserve a platform owner.

How much does self-hosting a wiki actually cost?

$0 in license fees for BookStack, Wiki.js, XWiki, and DokuWiki, plus infrastructure (a small server is enough for BookStack) plus admin time: updates, backups, and restore tests, roughly an afternoon a month for the light tools and a named platform owner for XWiki. Against Confluence Cloud at roughly $5.78 to $7.15 per user for Standard depending on band, self-hosting wins on sovereignty long before it wins on price.

Can a self-hosted wiki really replace Confluence Data Center?

For pages, structure, permissions, and search, yes, with the right weight class. What does not carry over is the Marketplace: app-powered macros and Jira-embedded live data have no equivalent in the open bench. Inventory macro and app dependency first; a wiki whose value is prose migrates cleanly, and a wiki whose value is its apps is a rebuild project wearing a migration costume.

What authentication should a self-hosted wiki support?

At minimum SAML or OIDC for single sign-on, and LDAP where the directory is the source of truth. BookStack includes LDAP, SAML, and OIDC in its free edition; Wiki.js and XWiki offer pluggable authentication; Docmost covers core needs with enterprise features on its paid edition. A wiki that asks employees for a separate password in 2026 will be routed around within a month.

When should we start migrating off Confluence Data Center?

Now, on a plan that finishes well before March 28, 2029, when Data Center subscriptions expire and instances become read-only. Atlassian stopped selling Data Center to new customers in March 2026 and renewals end March 30, 2028. A self-hosted migration has an operational runway (install, SSO, restore test, parallel quarter) that compresses badly; begun early it is a project, begun in 2028 it is an emergency.

Photo credits: Brett Sayles (Pexels). Photos are served from this site; follow the credit to the library page for the original.