Is documentation the goal or a side effect?
Answering that removes half this category immediately.
Documentation is the goal: XWiki for structured, permissioned knowledge you self-host; Nuclino for a fast team wiki people actually write in; BlueSpice for controlled documents in a regulated organisation.
Documentation comes with the work: OpenProject includes a wiki alongside Gantt charts, agile boards and time tracking; Zenkit's Hypernotes handles knowledge inside a wider productivity suite; Stackfield keeps documents alongside chat, tasks and projects.
Documentation is one part of replacing Google Workspace entirely: Nextcloud, which brings files, calendar, contacts, Talk for chat and video, and Nextcloud Office, with an app marketplace on top.
Why do most knowledge bases fail?
Because nobody writes in them, and every other consideration is downstream of that.
Nuclino is built on that observation. It is genuinely fast — instant search, instant page loads, no configuration to complete before you start writing — and the effect is behavioural rather than aesthetic: when writing something down takes seconds, more gets written down. A tool that takes four seconds to load a page trains people not to open it.
Its graph view shows how pages connect, which surfaces the structure that emerges from internal linking rather than requiring someone to design a hierarchy up front — the task that stalls most wiki rollouts before any content exists.
Real-time collaborative editing, Markdown support, version history and board views round it out. Nuclino GmbH is in Munich with EU hosting, free tier and paid plans from about €6 per user per month. What it deliberately lacks: self-hosting, and permissions granular enough for a large organisation.
What does a regulated organisation need that a wiki does not have?
Proof that the right version was approved and that the right people read it — and BlueSpice is the only tool here that provides it.
For a manufacturer with ISO certification, a work instruction is not a page. It needs an approval workflow before publication, document versioning and control so the current revision is unambiguous, and read confirmations recording that named staff acknowledged the procedure. An auditor asks for exactly those records.
BlueSpice adds that machinery on top of MediaWiki, the software behind Wikipedia — a foundation proven at a scale nothing else in this category approaches — with granular permissions, full-text search and PDF export. It runs self-hosted or on German hosting, with a free GPLv3 edition and Pro and Farm editions on subscription.
The honest costs: the MediaWiki interface and syntax are dated and that affects adoption, self-hosting needs operational capability, and the quality-management features are in the paid editions rather than the free one.
How do you leave Confluence?
Through XWiki, which is the only tool here with a documented migration path rather than an export button and good luck.
That path matters because Confluence migrations fail on the details — page hierarchies, attachments, macros, permissions and internal links that all break silently. Having a documented route is the difference between a project and an abandoned project.
What you land in is more capable than a wiki in one specific way: XWiki stores structured data inside pages, so a page can hold fields, and collections of pages become queryable. Its application builder turns that into small applications — a supplier register, an equipment inventory, a decision log — built inside the wiki rather than requesting them from IT.
XWiki SAS has been in Paris since 2004, under LGPLv2.1, fully self-hostable or on XWiki Cloud EU from about €3 per user per month, with granular permissions, versioning, LDAP and SSO, and an extensions marketplace. The trade-offs: the interface is dated enough to affect adoption, self-hosting a Java application needs capability, and the application builder has a learning curve.
When is a full platform the better answer?
When the knowledge base keeps being where the work is not, which is the usual reason documentation goes stale.
Nextcloud replaces the whole Google Workspace footprint on infrastructure you control: file sync and sharing, calendar, contacts, Nextcloud Talk for chat and video, Nextcloud Office for documents and spreadsheets, plus an app ecosystem covering everything from project boards to password management. AGPL-licensed, free self-hosted, with enterprise plans and managed providers available.
OpenProject covers project work with a wiki attached — Gantt charts, agile boards, time tracking, budgets and team collaboration, self-hosted or on German cloud hosting from €5.95 per user per month, and used by Siemens, Audi and government agencies. Zenkit offers flexible views over the same data — Kanban, list, table, calendar, mind map — with Hypernotes for knowledge management and Zenchat for team communication, from €9 per user per month with German hosting.
Stackfield takes a different angle entirely: chat, tasks, projects, file sharing, video calls, Kanban and Gantt with end-to-end encryption throughout, from Munich at €4.99 per user per month — so the provider cannot read the content, which is a stronger position than German hosting alone.
