XWiki

What Is XWiki?

When Ludovic Dubost launched XWiki in 2004, Notion did not exist. Confluence was a year old. Google Docs was still two years away. The wiki format — pioneered by Ward Cunningham in 1995 — was the dominant model for collaborative knowledge management. Most wiki projects from that era are dead. XWiki is not.

Twenty-two years later, XWiki remains actively developed, open-source under LGPL 2.1, and backed by XWiki SAS, a profitable French company in Paris. The platform has evolved far beyond simple wiki pages. It now supports real-time collaborative editing, structured data, a visual application builder, and a marketplace of over 700 extensions. European institutions, universities, and enterprises use it as their knowledge backbone.

XWiki occupies an unusual niche. It is more customisable than Confluence, more self-hostable than Notion, and more extensible than nearly any competitor. The price for that power is complexity. This is not a tool you deploy in an afternoon. But for organisations that need a knowledge platform they truly own — code, data, and all — XWiki is one of very few options with two decades of production-hardened reliability.

Key Features

Real-Time Collaborative Editing

XWiki supports both WYSIWYG and wiki syntax editing, with real-time collaboration that shows co-editors' cursors and changes live. The WYSIWYG editor has improved substantially over recent versions, though it still lacks the fluid feel of Notion's block editor. For structured documentation — technical specs, policies, runbooks — the editing experience is more than adequate. The wiki syntax option gives power users precise control over formatting and embedded macros.

Application Builder (App Within Minutes)

This is XWiki's most distinctive capability. The App Within Minutes wizard lets you create custom structured applications directly within the wiki — no coding required. Define fields (text, date, list, user), set up views, and generate a working database application embedded in your wiki pages. Teams use it for asset inventories, project trackers, HR directories, and approval workflows. It does not replace a full low-code platform, but for lightweight structured data needs, it eliminates the spreadsheet sprawl that plagues most wikis.

Extensions Marketplace

The 700+ extension marketplace covers integrations, macros, themes, and application templates. Diagram.net integration embeds visual diagrams. The Confluence migrator imports spaces and pages from Atlassian. Office importer handles Word and Excel files. LDAP and OpenID Connect extensions manage authentication. Quality varies — some extensions are maintained by XWiki SAS, others by community contributors with inconsistent update cycles. Always check the last-updated date before installing.

Granular Access Control

Permissions in XWiki operate at wiki, space, page, and object levels. You can create separate wikis for different departments, restrict specific spaces to certain groups, and control edit versus view access per page. For organisations handling sensitive internal documentation — legal, HR, finance — this granularity is essential. The permission model is more flexible than Confluence's space-level approach, though the configuration interface requires patience to master.

Scripting and Customisation

XWiki exposes a powerful scripting API supporting Groovy, Velocity, and Python. Developers can create custom macros, automated workflows, and dynamic page content. This extensibility is what separates XWiki from simpler wiki tools — but it also means that deeply customised installations become harder to upgrade. Organisations should balance customisation depth against long-term maintenance costs.

Pricing

XWiki's pricing model is refreshingly simple for an enterprise tool. The Community Edition is entirely free — no user limits, no feature restrictions, no time-limited trial that expires into a paywall. You download it, deploy it on your own server, and use it indefinitely. The only cost is your infrastructure and administration time.

XWiki Cloud starts at €3.60/user/month (minimum 10 users) for the Standard plan. The Pro plan at €5.40/user/month adds priority support, custom domains, and advanced analytics. Enterprise pricing is custom and includes dedicated infrastructure, SLA guarantees, and professional services.

For a team of 50, XWiki Cloud Standard costs €180/month. Confluence Standard for the same team runs approximately $575/month. That is a significant difference, particularly for organisations that do not need Atlassian's broader ecosystem. Self-hosted XWiki costs nothing beyond server resources — a compelling argument for teams with in-house sysadmin capacity.

EU Compliance & Privacy

XWiki SAS is a French company headquartered in Paris, placing it squarely under EU jurisdiction. The cloud hosting runs on European infrastructure. But the real compliance advantage is self-hosting: organisations that deploy XWiki on their own servers achieve complete data sovereignty. No data leaves their environment. No third-party processor is involved.

The open-source licence (LGPL 2.1) means the entire codebase is auditable. Security teams can inspect every line of code, run their own vulnerability assessments, and apply patches on their own schedule. For public sector organisations, defence contractors, and regulated industries, this transparency is a hard requirement that proprietary tools cannot satisfy.

XWiki also supports data export in standard formats, ensuring that organisations are never locked into the platform. If you decide to migrate, your data comes with you.

Who It's Best For

EU public sector and regulated industries that require complete data sovereignty and open-source auditability. Self-hosted XWiki meets the strictest data residency requirements.

Technical teams — developers, DevOps, engineering — who want a knowledge base they can extend with scripts, custom applications, and deep integrations.

Organisations migrating from Confluence that want to reduce Atlassian licensing costs without losing wiki functionality. The Confluence migrator smooths the transition.

Universities and research institutions that need a free, extensible platform for collaborative documentation across departments with varying access requirements.

The Verdict

XWiki is not for everyone. The learning curve is real. The UI will not win design awards. Setting up a self-hosted instance demands genuine technical investment. But for organisations that value ownership over convenience, XWiki delivers something rare: a mature, open-source knowledge platform with no vendor lock-in, no per-user tax on the self-hosted edition, and two decades of continuous development proving it will still be here in another twenty years. In a market increasingly dominated by proprietary SaaS, that independence has real value.

Frequently Asked Questions

Is XWiki GDPR compliant?

Yes. XWiki SAS is a French company operating under EU law. The cloud version hosts data in European data centres. Self-hosted deployments give you complete control — no data leaves your infrastructure, and no third-party data processor is involved.

Can I migrate from Confluence to XWiki?

Yes. XWiki provides a Confluence migrator extension that imports spaces, pages, attachments, and permissions. The migration handles most standard content well. Complex Confluence macros and marketplace app data may require manual cleanup after import.

Is the Community Edition really free forever?

Yes. The LGPL 2.1 licence guarantees this. There are no user limits, no feature gates, and no expiration. XWiki SAS monetises through cloud hosting and enterprise support, not by restricting the open-source edition.

What technical skills do I need to self-host XWiki?

You need familiarity with Java application servers (Tomcat or Jetty), a relational database (PostgreSQL, MySQL, or MariaDB), and Linux server administration. XWiki provides Docker images that simplify deployment significantly. Ongoing maintenance includes updates, backups, and monitoring.

How does XWiki compare to Notion?

XWiki is open-source and self-hostable; Notion is proprietary and cloud-only. XWiki offers deeper customisation through scripting and extensions. Notion has a vastly superior user interface and onboarding experience. XWiki suits technical teams that need control; Notion suits teams that prioritise ease of use.