XWiki

XWiki is an enterprise wiki for organizations that need shared content, structured information, and control over who can access it. It is best suited to teams prepared to choose between running their own instance and using XWiki Cloud. Its appeal is breadth and configurability; the practical trade-offs are deployment upkeep and cloud storage limits.

Overview

XWiki brings document management and structured data organization together with collaborative wiki editing. Contributors can use wiki syntax or a WYSIWYG editor, and version history lets them compare or restore earlier page versions. That makes it a stronger fit for evolving organizational knowledge than for teams seeking only a simple place to publish static pages.

Page rights can govern viewing, editing, and deletion, and apply to an individual page, its child pages, or an entire wiki. This granularity suits content shared across different audiences, but calls for deliberate access-rule design. XWiki SAS is an independent company founded in France in 2004 and headquartered in Paris.

Key features

Editing, permissions, and publishing

Version history provides a way to review and recover page changes, while custom domains and SSO support organizational publishing and access needs. Content analytics adds visibility into content use. Together, these capabilities serve teams managing a substantial wiki, though the access controls and publishing options matter most when the organization has varied audiences or administrative requirements.

Extensions and integrations

The extension catalog spans more than 900 applications, macros, skins, plugins, and themes. That range gives teams options to adapt XWiki to their workflows, but also means they must choose and maintain the extensions they rely on. Listed connectors include Active Directory, Office 365, Google Apps, and OnlyOffice; collaborative apps include meetings, forums, calendars, and task management. A RESTful remote API supports integration with other applications.

Hosting and security

XWiki can be self-hosted or used through XWiki Cloud. Supported installation environments include Linux, Tomcat, Jetty, Docker, and Debian. Self-hosting gives organizations deployment control, with responsibility for keeping the instance on a supported version and reviewing monthly security updates. XWiki Cloud is hosted in France on OVHcloud and includes automated backups, proactive monitoring, antivirus scanning, and regular security maintenance.

Cloud storage is a consequential constraint: when an instance exceeds its plan's included storage, wiki actions may be limited to viewing pages. Organizations considering the hosted option should account for that cap. The free XWiki Cloud demo lasts 10 days and can be extended twice.

Pricing

XWiki uses a freemium model, with a free plan and a 10-day trial. Published plan descriptions distinguish editions by hosting and user capacity, but plan prices are custom pricing.

Community avoids a paid hosted offering but requires self-hosting. The paid tiers scale by user count; support for paid Pro offerings includes professional technical help and support levels with SLA coverage. For XWiki Cloud, exceeding included storage can restrict actions to viewing, so user capacity alone is not enough to assess fit.

Platforms

XWiki supports web access, Linux, Windows, self-hosted deployment, and an API. Its installation options also include Tomcat, Jetty, Docker, and Debian. Teams wanting a managed route can choose XWiki Cloud; those selecting self-hosting should plan for version and security maintenance.

Who it's for

XWiki suits organizations building knowledge bases, collaborative intranets, public websites, or business applications, especially when page-level permissions, version control, and extensibility are central requirements. It is less suitable for teams that want a narrowly scoped, maintenance-free wiki without weighing hosting, extension choices, or cloud storage capacity.

Pros and cons

• Pros: Page rights can be scoped from a page to a whole wiki, useful for content serving distinct audiences.
• Pros: Version comparison and restoration help teams manage changing shared content.
• Pros: More than 900 extensions, named connectors, and a RESTful API offer multiple routes to tailor and connect the platform.
• Pros: XWiki Cloud includes backups, monitoring, antivirus scanning, and regular security maintenance.
• Cons: Self-hosting requires attention to supported versions and monthly security updates.
• Cons: Cloud storage overages may reduce wiki actions to viewing pages.
• Cons: Starter is capped at 25 users, while higher tiers are separated by substantial user-count limits.

Alternatives

For a broader starting point, browse the Knowledge base software directory.

• Nuclino is an option for teams whose stated needs fit its free tier of up to 50 items, three canvases, and 2 GB total storage.
• ProProfs Knowledge Base offers a free tier for one author and up to 25 pages, a narrower starting point for small knowledge bases.
• Confluence may suit a team that fits its free-forever offer for 10 users, 2 GB file storage, and three active whiteboards per user.
• Zoho Learn provides a free tier capped at five users, three spaces, five manuals, five courses, 1 GB storage, and two learning paths.
• BlueSpice is a self-hosted alternative with a free distribution that includes a visual editor, performance search, templates, and PDF export.
• GitBook is a web-based option whose free plan targets individuals and includes one free user, unlimited page views, and 10 GitBook Agent messages per week.
• Wiki.js is a free-forever, AGPL-licensed, self-hosted alternative.
• Docmost offers an open-source community edition with real-time collaboration, spaces, full-text search, page history and restore, and public sharing.

Verdict

Choose XWiki if your organization needs a configurable wiki with granular page permissions, recoverable version history, and room to extend or integrate it. Its principal advantage is that combination of content control and flexibility; look elsewhere if you want to avoid deployment maintenance or cannot accommodate the cloud storage-overage restriction.