Self-hosted Confluence alternatives
Most teams reading this are not shopping. They are being moved. Confluence Data Center stops taking new customers on March 30, 2026, blocks licence expansion after March 30, 2028, and reaches end of life on March 28, 2029, at which point it goes read-only with no patches. If you self-host because of data residency, an air-gapped network or a procurement rule, Cloud is not the answer and neither is Notion, which has no on-premises option at all. This page compares the four wikis you can actually run yourself, on the two things that decide the project: the licence and the import path.
XWiki if import fidelity matters most: it is the only option with a mature Confluence importer that handles macros, and LGPL 2.1 passes procurement. BookStack if you want the simplest thing that works and can script the content move; MIT, one PHP app, one database. Docmost for a modern editor, but note the Confluence importer is Business-tier only. Outline is the nicest to use and the licence is source-available, not open source.
Licence reality check
What you are actually allowed to run
| Tool | Licence | Open source? | Confluence import | Stack to operate | Catch |
|---|---|---|---|---|---|
| Confluence Data Center | Commercial, per-user | ✗ | n/a | Java, Postgres, your own cluster | Read-only after 2029-03-28 |
| XWiki | LGPL 2.1 | ✓ | ✓ Mature: trees, attachments, many macros | Java servlet, Postgres or MySQL | Dated default UI; extension sprawl |
| BookStack | MIT | ✓ | ✗ Script an HTML or Markdown conversion | PHP, MySQL or MariaDB | Fixed shelf and book hierarchy |
| Docmost | AGPL 3.0 | ✓ | Business tier only | Node, Postgres, Redis | Young project; import is paywalled |
| Wiki.js | AGPL 3.0 | ✓ | ✗ Git sync, no Confluence path | Node, Postgres | v3 has been in progress a long time |
| Outline (self-hosted) | BSL 1.1 | ✗ Source-available | ✓ HTML export, macros dropped | Node, Postgres, Redis, S3-compatible storage | Cannot resell as a hosted service |
Sources: Atlassian Data Center end of life · XWiki · BookStack · Docmost · Wiki.js · Outline. Compiled July 2026.
The licence distinction that trips people up
"Self-hostable" and "open source" are not the same claim, and the difference only surfaces when legal reviews the choice. BookStack (MIT), XWiki (LGPL 2.1), Docmost and Wiki.js (both AGPL 3.0) are OSI-approved open source: fork them, patch them, run them anywhere, no vendor can change the terms on the code you already have. Outline ships under the Business Source License 1.1, which grants you the source and the right to run it internally but forbids offering it as a hosted service to third parties. For a company wiki that restriction is theoretical. For a procurement policy written as "open-source-only", it is a hard no, and finding that out after the pilot is a wasted quarter.
AGPL 3.0 has its own wrinkle worth naming: if you modify Docmost or Wiki.js and expose the modified version over a network, the licence obliges you to offer those modifications' source to users. Running unmodified upstream, which is what almost everyone does, triggers nothing. Some enterprise legal teams still refuse AGPL outright as policy, so check before you build the deployment.
Import is the real constraint, not features
Every one of these tools can hold your documentation. Almost none of them can take it from Confluence cleanly, and this is where listicles are least reliable. XWiki is the honest winner: its Confluence importer handles page hierarchies, attachments and a real share of macros, which is the difference between a migration and a rewrite. Docmost advertises a Confluence importer, but it sits behind the paid Business tier, so the combination people go looking for, free self-hosting plus Confluence import, does not exist there. BookStack and Wiki.js expect you to convert an HTML or Markdown export yourself; entirely doable with a script, and a week of someone's time for a large instance. Outline ingests Confluence HTML exports and preserves formatting while dropping macros.
Whatever you pick, macros do not survive. Excerpt-include, Jira issue tables, roadmap planners, Marketplace app content: these are Confluence-specific and become plain text or vanish. Inventory which macros you actually depend on before choosing, because that list, not the editor, decides how painful the move is.
When self-hosting is the wrong answer
The licence costs nothing and the operation costs something every month. A serious deployment needs a host, Postgres with backups you have actually restored from, object storage for attachments, TLS, an SSO integration and a named person who applies patches. For a 50-person wiki that is a few hundred dollars a year of infrastructure plus a recurring slice of an engineer's attention, against roughly $3,250 a year for Confluence Standard at the same headcount. Self-hosting usually wins on cash and loses on attention.
Below roughly 20 users the arithmetic stops making sense unless data residency or air-gapping is a genuine requirement rather than a preference. And if you are still on the Confluence free tier at 10 users or fewer, you are paying nothing today; do not trade that for a database you have to babysit. The managed middle ground is real: Outline Cloud, XWiki's own hosting or Docmost Cloud give you the same product with someone else on call, at a fraction of an enterprise wiki's cost.
Common questions
FAQ: self-hosting after Data Center
When does Confluence Data Center actually stop working?
Atlassian has published a three-step wind-down rather than a single date. New Data Center sales end on March 30, 2026. Existing customers can no longer expand their licence after March 30, 2028. End of life is March 28, 2029, after which the product goes read-only: no security patches and no support. Your instance will not switch itself off, but running an unpatched wiki with no vendor fixes is not a position most security teams will sign off on, so the practical deadline is earlier than 2029.
Which self-hosted wiki has a genuinely open licence?
BookStack is MIT, XWiki is LGPL 2.1, and Docmost and Wiki.js are AGPL 3.0. All four are OSI-approved open source. Outline is the exception: it ships under the Business Source License 1.1, which is source-available but not open source, and it forbids offering Outline as a hosted service to third parties. For internal company use BSL 1.1 is unproblematic in practice, but it does fail procurement checklists written as open-source-only, and that is worth knowing before you shortlist it.
Which self-hosted options can import from Confluence?
Fewer than the listicles claim. XWiki has the most mature Confluence importer, handling page trees, attachments and a meaningful share of macros. Docmost has a Confluence importer but it is gated to the paid Business tier, so free self-host plus Confluence import is not a real combination. BookStack and Wiki.js have no first-class Confluence importer and expect a scripted HTML or Markdown conversion. Outline imports Confluence HTML exports as pages with formatting preserved and macros dropped. If import fidelity is your main constraint, XWiki is the honest answer.
Is self-hosting actually cheaper than Confluence Cloud?
The licence is free; the operation is not. A small production deployment means a VM or container host, Postgres with real backups, object storage for attachments, TLS, an auth integration, and someone who patches it. Budget a few hundred dollars a year of infrastructure for a 50-person wiki plus a recurring slice of an engineer's time. Against Confluence Standard for 50 users, roughly $3,250 a year, self-hosting usually wins on cash and loses on attention. Below about 20 users the maths rarely justifies it unless data residency or air-gapping is a hard requirement.