XWiki

XWiki is a collaboration platform for building a shared knowledge base, from editable wiki pages to structured records and forms. It is best suited to organizations that want to shape how knowledge is organized and choose where it is hosted. Teams looking for a straightforward, low-maintenance wiki may find its flexibility comes with more choices than they need.

Overview

Founded in 2004 and headquartered in Paris, XWiki brings collaborative editing together with tools for organizing structured information. Its open-source XWiki Standard is free for on-premises use, while XWiki also offers cloud and on-premises options for organizations seeking managed hosting or professional support.

The deployment choice matters. XWiki Cloud includes setup, hosting, upgrades, maintenance, backups, security updates, and 24/7 monitoring. It runs in France on OVHcloud infrastructure, whose hosting infrastructure XWiki says has ISO 27001, SOC 1, and SOC 2 certifications. Organizations deploying on their own infrastructure retain control over hosting, access management, integrations, and data residency, but take on the operational responsibility themselves.

Key features

Editing combines a WYSIWYG editor with in-place changes, attachments and previews, comments, annotations, notifications, and full change history. That makes XWiki a fit for teams that need to revise and discuss knowledge in place, not simply publish finished pages. Version history provides a record of changes, while comments and annotations support review.

AppWithinMinutes helps users create structured pages and forms; filterable livetables make the resulting data easier to browse. This is a meaningful advantage for organizations managing repeatable information, such as records or internal processes, rather than a collection of free-form articles alone.

XWiki says it offers more than 700 ready-to-use extensions and hundreds of APIs in its scripting language. That breadth gives teams room to adapt the platform, but also makes it a better match for organizations prepared to select and manage the extensions they need than for those seeking a narrowly defined, ready-made tool.

Enterprise integration features include Active Directory and LDAP connections, single sign-on, office-document import and preview, PDF viewing and export, and data imports. XWiki Pro lists Google Apps, Office 365, and OnlyOffice connectors, along with Active Directory and Azure Active Directory SSO apps. AI search or answers and Slack integration are also available; semantic search is not.

Pricing

XWiki uses a freemium model, with a free plan and paid plans whose prices are custom pricing. A 30-day trial is offered, extendable on request, with no credit card required. The homepage describes it as up to 30 days of full trial.

Paid plans are billed yearly or for three years, with a 20% saving on the three-year term. Starter suits smaller teams willing to use cloud hosting, but its 25-user cap and single sub-wiki leave little room for a growing or multi-wiki setup. Basic raises the cap and allows on-premises deployment; Business and Enterprise extend the user and sub-wiki limits for larger organizations. Community avoids a subscription price, but is on-premises only and has no guaranteed community support. Organizations that need support experts can consider XWiki Pro, which offers different support levels with coverage, response times, and channels varying by plan.

Platforms

XWiki supports web, Linux, Windows, API, and self-hosted environments. This range accommodates both browser-based use and organizations that want to run the software on their own infrastructure.

Who it's for

XWiki is a strong candidate for organizations that need structured knowledge, extensibility, and a choice between managed cloud hosting and self-hosting. It is particularly well suited to teams with repeatable information to manage, or with requirements around data residency and access control. A small team that wants a simple hosted wiki without deployment decisions or custom configuration should look elsewhere.

Pros and cons

• Pro: Structured pages, forms, and filterable livetables let teams organize information beyond conventional wiki articles.
• Pro: Cloud and on-premises deployment serve different priorities, from managed operations to control over hosting and data residency.
• Pro: A large extension and API ecosystem creates room to tailor the platform to organizational needs.
• Con: The free Community plan is on-premises only and provides no guaranteed support.
• Con: Paid plans have user and sub-wiki caps, and their prices are custom pricing, making plan fit and cost harder to judge before a quote.
• Con: Starter is cloud-only, so teams that need self-hosting must consider a higher plan.

Alternatives

For a fully free, self-hosted wiki, Wiki.js is an alternative with an AGPL-licensed free-forever plan. BookStack is another free, MIT-licensed self-hosted option for readers who want software they can download and install themselves.

CompassDocs may suit teams prioritizing unlimited users and documents on its free self-hosted Community plan; its Cloud plan is listed at 8.00 US. KBPublisher is worth considering when an on-premises free edition with unlimited staff users, end users, articles, and files is the priority.

Happy HR is a freemium alternative focused on recruitment software. Jostle is a paid alternative with a free plan and plans that include news, an activity feed, employee recognition, discussions, email digest, and mobile apps.

HRDocket Employee Self-Service may fit a reader seeking employee self-service, with a free tier limited to one employee profile and one company. Vivantio is a paid alternative for readers considering ITSM software; its published range is $49–$99 per agent per month, billed annually, and end users are free.

Readers comparing categories can also browse HR Knowledge Base Software and Internal Knowledge Base Software.

Verdict

Choose XWiki if your organization needs a knowledge platform that can handle structured content, extensive customization, and either cloud or on-premises deployment. Its strongest reason to choose it is the combination of structured pages and deployment control; its main drawback is the planning required around plan caps, custom pricing, and support. If you want a small, simple wiki with a clear low-cost hosted plan, a more focused alternative is likely a better fit.