Knowledge Base, Wiki, and Intranet Publishing

Knowledge base and wiki platforms provide collaborative authoring, version control, and structured information architecture for organisational documentation. These systems serve as repositories for policies, procedures, technical documentation, and institutional knowledge, enabling staff to create, discover, and maintain information without specialised technical skills.

This page covers platforms where the primary function is collaborative content creation and management with wiki-style editing. Adjacent categories with different primary functions are addressed separately: document management systems (file-centric storage with metadata), content management systems (public website publishing), and learning management systems (structured course delivery). Intranet functionality overlaps with several tools here; this assessment focuses on content authoring and knowledge capture rather than broader digital workplace features.

Requirements taxonomy

This taxonomy defines evaluation criteria for knowledge base and wiki platforms. Requirements are organised by functional area and weighted by typical priority for mission-driven organisations. Adjust weights based on specific operational context.

Functional requirements

Core capabilities that define what the platform must do.

Content authoring and editing

Version control and history

Information architecture

Search and discovery

Media and file management

Permissions and access control

Technical requirements

Infrastructure, architecture, and deployment considerations.

Deployment and hosting

Scalability and performance

Integration architecture

Security requirements

Security controls and data protection capabilities.

Authentication and access

Data protection

Compliance and certifications

Operational requirements

Day-to-day administration and management.

Administration

Monitoring and maintenance

Support and documentation

Data management requirements

Data handling, portability, and lifecycle.

Import and migration

Export and portability

Accessibility requirements

Support for users with disabilities.

Functional capability comparison

Content authoring and editing

Assessment notes:

• MediaWiki F1.1: VisualEditor extension provides WYSIWYG; requires installation and configuration. Core installation uses wikitext.
• DokuWiki F1.7: Plugins required for most embed types; core supports limited embedding.
• BookStack F1.3: Edit locking prevents conflicts but no real-time synchronisation.
• SharePoint F1.2: Modern pages have limited source access; classic pages support more customisation.

Version control and history

Assessment notes:

• SharePoint F2.2: Version comparison available but less detailed than wiki-native platforms.
• BookStack/Confluence/SharePoint F2.5: Batch rollback capabilities limited compared to dedicated wiki platforms.

Information architecture

Assessment notes:

• MediaWiki F3.1: Flat page structure; hierarchy through categories and naming conventions rather than true parent-child.
• BookStack F3.5: Navigation follows fixed Shelf > Book > Chapter > Page structure.
• SharePoint F3.3: Cross-site linking more complex than within-site.

Search and discovery

Assessment notes:

• MediaWiki F4.4: CirrusSearch extension with Elasticsearch required for attachment search.
• DokuWiki F4.4/F4.5: Plugins available for enhanced search features.
• BookStack F4.2/F4.6: Basic search operators; limited faceted filtering.

Permissions comparison

Assessment notes:

• MediaWiki F6.1/F6.3: Page-level permissions require extensions; core uses namespace-level only.

Technical capability comparison

Deployment and hosting

Deployment details:

Assessment notes:

• MediaWiki T1.2: Third-party hosting available; no official Wikimedia-hosted service for private wikis.
• DokuWiki T1.4: Single-instance architecture; HA requires external load balancing with shared storage.
• SharePoint T1.1: SharePoint Server Subscription Edition available but requires Windows Server; Online is primary offering.

Integration architecture

API details:

Assessment notes:

• MediaWiki T3.3: Webhooks require extensions; not in core.
• DokuWiki T3.1: XML-RPC and JSON-RPC APIs; not REST-native.

Security capability comparison

Authentication and access

MFA methods supported:

Data protection

Assessment notes:

• MediaWiki/XWiki/BookStack S2.1: Encryption at rest depends on database and filesystem configuration; not application-managed.
• DokuWiki S2.1: Flat file storage; encryption requires filesystem-level implementation.
• SH notation: Self-hosted deployment provides full data residency control.

Security certifications

Assessment notes:

• MediaWiki/DokuWiki/BookStack: Open source self-hosted; certifications are deployment-specific, not vendor-provided.
• XWiki: XWiki SAS cloud offering does not currently hold SOC 2 or ISO 27001.

Operational capability comparison

Administration and support

Localisation

Data management comparison

Import and export

Migration paths:

Accessibility comparison

Commercial comparison

Pricing models

Cost notes:

• Self-hosted infrastructure costs vary by scale: small deployments £20-100/month, medium deployments £200-1,000/month
• Confluence pricing based on Cloud Standard/Premium tiers as of January 2026
• SharePoint included in Microsoft 365 Business/Enterprise plans; standalone pricing varies
• Nonprofit programmes require eligibility verification

Vendor details

Jurisdictional considerations:

• Confluence Cloud (US/Australia HQ): Subject to CLOUD Act; data regions available including EU
• SharePoint Online (US HQ): Subject to CLOUD Act; EU Data Boundary available
• XWiki Cloud (France HQ): EU jurisdiction; GDPR as primary framework
• Self-hosted FOSS options: Full jurisdictional control based on deployment location

Detailed tool assessments

MediaWiki

Type

Open source

Licence

GPL-2.0-or-later

Current version

1.45.1 (January 2026); LTS: 1.43 (supported until December 2027)

Deployment options

Self-hosted (Linux, Windows), Docker, Kubernetes

Source repository

https://gerrit.wikimedia.org/

Documentation

https://www.mediawiki.org/

Overview

MediaWiki powers Wikipedia and thousands of other wikis, making it the most deployed wiki platform globally. The software prioritises encyclopaedic content with features designed for large-scale collaborative knowledge projects: extensive revision control, sophisticated anti-vandalism tools, and a rich ecosystem of extensions. Architecture centres on wikitext markup with optional visual editing through the VisualEditor extension.

The platform excels at handling massive page counts and high concurrent editing loads. Wikipedia’s scale (60+ million articles, billions of pageviews monthly) demonstrates MediaWiki’s upper performance bounds. For smaller deployments, this robustness provides headroom but adds configuration complexity.

Capability assessment for knowledge bases and intranets

MediaWiki’s strengths align with documentation-heavy environments requiring precise version control and attribution. The wikitext markup language, while having a learning curve, enables complex templating and content reuse impossible in WYSIWYG-only systems. Transclusion (embedding content from other pages) supports single-source documentation patterns.

Permission granularity is MediaWiki’s primary limitation for enterprise knowledge bases. Core installation provides namespace-level access control; page-level permissions require extensions that add administrative overhead. Organisations expecting fine-grained content access will need extension configuration or alternative platforms.

Key strengths:

• Unmatched revision control with per-character attribution and visual diffs
• Extensive extension ecosystem (1,000+ available) for customisation
• Proven scalability from small teams to Wikipedia-scale deployments
• Strong content reuse through templates and transclusion
• Active development with regular releases and long-term support versions

Key limitations:

• Page-level permissions require extensions; core uses namespace-level only
• Visual editor is an extension, not core functionality
• Administrative interface distributed across special pages rather than unified console
• Steeper learning curve for wikitext markup compared to WYSIWYG-native platforms
• No built-in real-time collaborative editing

Deployment and operations

Self-hosted requirements:

Operating system: Linux (Ubuntu 22.04+, Debian 12+, RHEL 8+) or Windows Server
Runtime: PHP 8.1+ with required extensions
Database: MySQL 8.0+, MariaDB 10.6+, PostgreSQL 13+, or SQLite
Minimum resources: 2 CPU, 2GB RAM, 10GB storage
Recommended for production: 4 CPU, 8GB RAM, 50GB+ storage with caching layer

Deployment complexity: Medium. Core installation straightforward; production deployment benefits from caching (Memcached/Redis), job queue configuration, and extension management.

Operational overhead: Medium. Extension updates, database maintenance, and performance tuning require attention. MediaWiki-announce mailing list provides security notifications.

Upgrade path: Releases every 6 months with 1-year support. LTS releases every 2 years with 3-year support. Upgrade documentation comprehensive; database migrations handled by maintenance scripts.

Integration capabilities

API coverage: Comprehensive. Action API (api.php) provides full feature access; REST API (rest.php) offers streamlined access for common operations.

Key integrations:

Cost analysis

Direct costs:

• Licence: Free
• Support: Community (free) or third-party commercial
• Enterprise features: Available through extensions (mostly free)

Infrastructure costs (self-hosted):

Total cost of ownership: Low direct costs but factor in administration time. Organisations without PHP/Linux expertise will incur setup and maintenance effort.

Organisational fit

Best suited for:

• Technical documentation requiring precise version control
• Organisations with Linux/PHP administration capability
• Projects requiring extensive customisation through extensions
• Environments where wikitext markup proficiency exists or can be developed

Less suitable for:

• Organisations requiring fine-grained page permissions without extension investment
• Teams preferring pure WYSIWYG editing without markup
• Environments needing real-time collaborative editing

XWiki

Type

Open source with enterprise tier

Licence

LGPL-2.1

Current version

17.10.2 LTS (December 2025)

Deployment options

Self-hosted (Linux, Windows), Docker, Kubernetes, XWiki Cloud

Source repository

https://github.com/xwiki/xwiki-platform

Documentation

https://www.xwiki.org/xwiki/bin/view/Documentation/

Overview

XWiki combines wiki functionality with application development capabilities, positioning itself as a “second-generation wiki” that can serve as a platform for building structured applications. The Java-based architecture supports both traditional wiki content and custom applications built using XWiki’s scripting and extension framework.

Real-time collaborative editing, comprehensive access control, and enterprise features distinguish XWiki from simpler wiki platforms. The platform supports multiple wikis within a single installation, enabling multi-tenant deployments.

Capability assessment for knowledge bases and intranets

XWiki provides the most complete enterprise feature set among open source wiki platforms. Native support for page-level permissions, real-time collaboration, and structured data makes it suitable for complex knowledge management requirements. The extension marketplace includes both free community extensions and commercial “Pro” applications.

Resource requirements exceed lighter platforms. Java runtime and database dependencies create a larger operational footprint. Organisations should evaluate whether XWiki’s capabilities justify the infrastructure investment compared to simpler alternatives.

Key strengths:

• Real-time collaborative editing with presence awareness
• Fine-grained permissions at page and object level
• Application development platform beyond wiki content
• Multi-wiki support for tenant isolation
• Commercial support available from XWiki SAS

Key limitations:

• Higher resource requirements than PHP-based alternatives
• Complexity for simple wiki use cases
• Smaller community than MediaWiki
• Enterprise/Pro features require commercial licence

Deployment and operations

Self-hosted requirements:

Operating system: Linux (Ubuntu 22.04+, Debian 12+) or Windows Server
Runtime: Java 11+ (OpenJDK recommended)
Database: MySQL 8.0+, MariaDB 10.6+, PostgreSQL 13+
Minimum resources: 4 CPU, 4GB RAM, 20GB storage
Recommended for production: 8 CPU, 16GB RAM, 100GB+ storage

Deployment complexity: Medium-High. Java application server configuration, database setup, and Solr for search require familiarity with Java deployment patterns.

Operational overhead: Medium. Regular updates available; upgrade process documented but requires testing. XWiki SAS provides commercial support options.

Integration capabilities

API coverage: Comprehensive REST API covering pages, spaces, attachments, users, and extensions.

Key integrations:

Cost analysis

Direct costs:

• Licence: Free (LGPL)
• XWiki Cloud: From €9/user/month
• Pro extensions: Varies by extension
• Commercial support: Contact XWiki SAS

Infrastructure costs (self-hosted):

Organisational fit

Best suited for:

• Organisations requiring real-time collaboration
• Deployments needing fine-grained access control
• Teams building custom applications on wiki platform
• Environments with Java administration expertise

Less suitable for:

• Simple documentation needs where lighter platforms suffice
• Resource-constrained environments
• Organisations without Java operational experience

DokuWiki

Type

Open source

Licence

GPL-2.0

Current version

2025-05-14b “Librarian” (May 2025)

Deployment options

Self-hosted (Linux, Windows), Docker

Source repository

https://github.com/dokuwiki/dokuwiki

Documentation

https://www.dokuwiki.org/

Overview

DokuWiki stores content in plain text files rather than a database, radically simplifying deployment and backup. This file-based architecture makes DokuWiki the most portable and lightweight wiki option, deployable on minimal hosting with no database configuration.

The platform targets documentation and small-team wikis where simplicity outweighs feature richness. A mature plugin ecosystem extends core functionality, though DokuWiki deliberately maintains a smaller feature set than database-backed alternatives.

Capability assessment for knowledge bases and intranets

DokuWiki excels in scenarios where deployment simplicity and content portability are priorities. Plain text storage means content remains accessible even without the wiki software, and backups require only filesystem copies. The learning curve is minimal compared to feature-rich alternatives.

Limitations emerge with scale. Flat-file storage performs adequately for hundreds of pages but degrades with thousands. Search relies on file scanning rather than database indexing. Real-time collaboration and some enterprise features are unavailable.

Key strengths:

• No database required; plain text file storage
• Extremely lightweight resource requirements
• Simple backup and migration (copy files)
• Active plugin ecosystem
• Low learning curve for basic use

Key limitations:

• Performance degrades with large page counts (1000+)
• No real-time collaborative editing
• Search less sophisticated than database-backed platforms
• Some features require plugins rather than core functionality
• Visual editor via plugins only

Deployment and operations

Self-hosted requirements:

Operating system: Linux, Windows, macOS
Runtime: PHP 8.0+ with basic extensions
Database: None required (flat file storage)
Minimum resources: 1 CPU, 512MB RAM, 1GB storage
Recommended for production: 2 CPU, 1GB RAM, 10GB storage

Deployment complexity: Low. Upload files, configure web server, access through browser. No database setup required.

Operational overhead: Low. Updates via Extension Manager or manual file replacement. Plain text storage simplifies backup and troubleshooting.

Cost analysis

Direct costs:

• Licence: Free
• Support: Community only (third-party commercial available)
• All features: Free via core and plugins

Infrastructure costs:

Organisational fit

Best suited for:

• Small teams with straightforward documentation needs
• Resource-constrained environments
• Deployments where database administration is unavailable
• Content requiring plain-text portability
• Technical documentation with code snippets

Less suitable for:

• Large-scale deployments (1000+ pages)
• Environments requiring real-time collaboration
• Complex permission requirements
• Organisations expecting feature parity with commercial platforms

BookStack

Type

Open source

Licence

MIT

Current version

v25.12.1 (December 2025)

Deployment options

Self-hosted (Linux), Docker

Source repository

https://codeberg.org/bookstack/bookstack (primary), https://github.com/BookStackApp/BookStack (mirror)

Documentation

https://www.bookstackapp.com/docs/

Overview

BookStack organises content in a book metaphor: Shelves contain Books, Books contain Chapters, and Chapters contain Pages. This fixed hierarchy provides intuitive organisation for documentation but constrains content structure compared to freeform wikis.

The platform emphasises ease of use over configurability. A polished WYSIWYG editor, clear interface, and straightforward permissions model make BookStack accessible to non-technical users. Monthly releases deliver consistent improvements without disruptive changes.

Capability assessment for knowledge bases and intranets

BookStack suits organisations wanting structured documentation with minimal configuration. The book/chapter/page model works well for manuals, procedures, and organised knowledge bases. Role-based permissions cover typical access control requirements without complexity.

The fixed hierarchy limits flexibility. Content that doesn’t fit the book metaphor requires workarounds. Advanced wiki features (transclusion, complex templates, custom metadata) are absent or limited. Organisations outgrowing BookStack may face migration complexity.

Key strengths:

• Intuitive interface with minimal learning curve
• Polished WYSIWYG editor with Markdown option
• Clear permission model without complexity
• Active single-developer maintenance with monthly releases
• MIT licence permits unrestricted use

Key limitations:

• Fixed hierarchy (Shelf > Book > Chapter > Page) limits organisation flexibility
• No real-time collaborative editing
• Limited templating and content reuse compared to full wiki platforms
• Smaller extension ecosystem than established wikis
• Migration from BookStack more complex than text-based wikis

Deployment and operations

Self-hosted requirements:

Operating system: Linux (Ubuntu 22.04+, Debian 12+)
Runtime: PHP 8.2+, Composer
Database: MySQL 8.0+ or MariaDB 10.6+
Minimum resources: 2 CPU, 1GB RAM, 5GB storage
Recommended for production: 2 CPU, 2GB RAM, 20GB storage

Deployment complexity: Low-Medium. Standard LAMP/LEMP deployment; documented installation scripts available.

Operational overhead: Low. Straightforward updates via Git pull; database migrations handled automatically.

Cost analysis

Direct costs:

• Licence: Free (MIT)
• Support: Community (paid support from developer available)
• All features: Free

Infrastructure costs:

Organisational fit

Best suited for:

• Documentation that fits book/chapter structure
• Teams prioritising ease of use over flexibility
• Organisations without dedicated wiki administrators
• Small to medium deployments

Less suitable for:

• Content requiring freeform wiki organisation
• Large-scale deployments with complex permission needs
• Environments requiring extensive customisation
• Organisations likely to outgrow the platform

Confluence

Type

Commercial

Licence

Proprietary

Current version

Cloud: continuous deployment; Data Center: 10.2 LTS (December 2025)

Deployment options

Cloud (SaaS), Data Center (self-hosted)

Documentation

https://confluence.atlassian.com/doc/ (Data Center), https://support.atlassian.com/confluence-cloud/ (Cloud)

Overview

Confluence dominates the commercial wiki market, particularly in organisations using Atlassian’s Jira for project management. Cloud and Data Center editions serve different deployment models: Cloud provides SaaS convenience with Atlassian-managed infrastructure; Data Center enables self-hosted deployment for data sovereignty or compliance requirements.

Feature development prioritises Cloud; Data Center receives stability updates and eventually features from Cloud. Server edition reached end-of-life in February 2024, and Data Center support extends until March 2029.

Capability assessment for knowledge bases and intranets

Confluence provides comprehensive wiki functionality with enterprise features: real-time collaboration, sophisticated permissions, extensive integrations, and the Atlassian marketplace ecosystem. The platform handles large-scale deployments with documented performance characteristics.

Costs escalate with user count. Per-user pricing makes Confluence expensive for broad deployment across organisations. Vendor lock-in concerns arise from proprietary data formats, though export capabilities exist. Organisations should evaluate whether Confluence’s features justify costs compared to FOSS alternatives.

Key strengths:

• Polished user experience with real-time collaboration
• Deep Atlassian ecosystem integration (Jira, Trello, Bitbucket)
• Extensive marketplace with third-party apps
• Enterprise features (compliance, analytics, admin controls)
• Commercial support with SLA options

Key limitations:

• Per-user pricing expensive at scale
• Data Center requires significant infrastructure
• Cloud data resides in Atlassian infrastructure (jurisdictional considerations)
• Feature velocity favours Cloud over Data Center
• Migration from Confluence can be complex

Deployment and operations

Data Center requirements:

Operating system: Linux (Ubuntu, RHEL, Debian) or Windows Server
Runtime: Java 11+ (bundled)
Database: PostgreSQL 13+, MySQL 8.0+, Oracle 19c+
Minimum resources: 4 CPU, 8GB RAM, 50GB storage
Recommended for production: 8 CPU, 16GB RAM, 200GB+ storage

Deployment complexity (Data Center): High. Requires database, application server, shared filesystem for attachments, load balancer for clustering.

Operational overhead: Medium (Cloud), High (Data Center). Cloud eliminates infrastructure management; Data Center requires standard enterprise application operations.

Cost analysis

Confluence Cloud pricing (January 2026):

Nonprofit programme: 75% discount for eligible organisations via Atlassian Community License.

Data Center: Perpetual licence model based on user tiers; contact Atlassian for pricing.

Organisational fit

Best suited for:

• Organisations invested in Atlassian ecosystem
• Teams requiring real-time collaboration features
• Environments where commercial support is required
• Deployments with budget for per-user licensing

Less suitable for:

• Cost-sensitive organisations with large user counts
• Environments requiring full data sovereignty (consider Data Center)
• Organisations wanting to avoid vendor lock-in
• Simple wiki needs where FOSS alternatives suffice

SharePoint

Type

Commercial (Microsoft 365 component)

Licence

Proprietary (included in Microsoft 365)

Current version

SharePoint Online: continuous deployment; Server Subscription Edition: Version 25H2

Deployment options

SharePoint Online (Microsoft 365), SharePoint Server Subscription Edition (on-premises)

Documentation

https://learn.microsoft.com/sharepoint/

Overview

SharePoint serves as Microsoft’s collaboration and content management platform, integrated across Microsoft 365. While broader than a wiki, SharePoint’s site pages and communication sites provide wiki-like functionality alongside document management, team sites, and intranet capabilities.

SharePoint Online is the primary offering, delivered as SaaS within Microsoft 365. SharePoint Server Subscription Edition continues on-premises availability with semi-annual feature updates, though feature parity with Online varies.

Capability assessment for knowledge bases and intranets

SharePoint excels as an intranet platform with wiki capabilities rather than a pure wiki. Integration with Microsoft 365 applications (Teams, OneDrive, Office) creates a unified environment for organisations already using Microsoft’s ecosystem. Modern site pages provide content authoring, though the wiki model differs from traditional wiki platforms.

SharePoint’s complexity and Microsoft 365 dependency make it less suitable as a standalone wiki. Organisations not using Microsoft 365 face significant adoption costs. The platform’s breadth means wiki functionality competes with other use cases for administrative attention.

Key strengths:

• Deep Microsoft 365 integration (Teams, Office, OneDrive)
• Enterprise features (compliance, retention, eDiscovery)
• Extensive customisation via SharePoint Framework (SPFx)
• Microsoft Entra ID integration for authentication
• Familiar interface for Microsoft users

Key limitations:

• Requires Microsoft 365 subscription
• Complex administration compared to dedicated wikis
• Modern pages less flexible than traditional wiki markup
• SharePoint Server lags Online in feature availability
• Over-engineered for simple wiki requirements

Deployment and operations

SharePoint Online: SaaS, no infrastructure management required.

SharePoint Server requirements:

Operating system: Windows Server 2019/2022
Database: SQL Server 2019/2022
Minimum resources: 16GB RAM, 100GB storage

Deployment complexity: Low (Online), High (Server). Online eliminates infrastructure concerns; Server requires Windows Server, SQL Server, and SharePoint-specific expertise.

Operational overhead: Low (Online), High (Server). Microsoft manages Online infrastructure; Server requires significant administration.

Cost analysis

SharePoint Online is included in Microsoft 365 plans:

Nonprofit programme: Donated and discounted Microsoft 365 licences available for eligible nonprofits.

SharePoint Server: Perpetual licensing; contact Microsoft for current pricing.

Organisational fit

Best suited for:

• Organisations already using Microsoft 365
• Intranet requirements beyond pure wiki
• Environments requiring Microsoft compliance features
• Teams wanting unified Microsoft experience

Less suitable for:

• Organisations not using Microsoft 365
• Pure wiki requirements where dedicated platforms are simpler
• Cost-sensitive deployments where included Microsoft 365 licensing is unused
• Environments requiring non-Microsoft hosting

Selection guidance

Decision framework

Use this framework to narrow options based on primary constraints:

                                START
                                  |
                                  v
                +----------------------------------+
                | Is Microsoft 365 already in use |
                | across the organisation?        |
                +----------------+-----------------+
                                 |
                +----------------+----------------+
                |                                 |
                v                                 v
              YES                                NO
                |                                 |
                v                                 v
   +--------------------+           +------------------------+
   | Consider SharePoint|           | Is real-time           |
   | alongside wiki     |           | collaborative editing  |
   | alternatives       |           | essential?             |
   +--------------------+           +-----------+------------+
                                                |
                                    +-----------+-----------+
                                    |                       |
                                    v                       v
                                   YES                     NO
                                    |                       |
                                    v                       v
                         +------------------+    +---------------------+
                         | XWiki (FOSS)     |    | What level of       |
                         | or Confluence    |    | deployment          |
                         | (commercial)     |    | complexity is       |
                         +------------------+    | acceptable?         |
                                                 +----------+----------+
                                                            |
                                            +---------------+---------------+
                                            |               |               |
                                            v               v               v
                                         MINIMAL       MODERATE         HIGH
                                            |               |               |
                                            v               v               v
                                    +----------+    +----------+    +----------+
                                    | DokuWiki |    | BookStack|    | MediaWiki|
                                    | or       |    |          |    | or XWiki |
                                    | BookStack|    |          |    |          |
                                    +----------+    +----------+    +----------+

Recommendations by organisational context

For organisations with minimal IT capacity

Primary recommendation: BookStack

BookStack provides the best balance of capability and simplicity for organisations without dedicated IT staff. The intuitive interface requires minimal training, the book/chapter/page structure makes content organisation obvious, and deployment requires only basic Linux hosting. Monthly updates maintain security without disruptive changes.

Alternative: DokuWiki for even simpler deployments where database administration is unavailable. The flat-file architecture eliminates database complexity entirely.

Avoid: SharePoint (requires Microsoft 365 commitment), XWiki (higher infrastructure requirements), MediaWiki (extension complexity for basic permissions).

For organisations with established IT capacity

Primary recommendation: XWiki for real-time collaboration needs, MediaWiki for maximum flexibility

XWiki provides the most complete enterprise feature set among FOSS options: real-time editing, comprehensive permissions, and application development capabilities justify its higher resource requirements where IT capacity exists.

MediaWiki suits organisations valuing maximum customisation and proven scalability. The extension ecosystem addresses nearly any requirement, though configuration investment is substantial.

Alternative: Confluence where budget permits and Atlassian ecosystem alignment exists. Commercial support and polished experience may justify cost for some organisations.

For organisations with specific constraints

Strict data sovereignty requirements:

• Recommendation: Any self-hosted FOSS option (MediaWiki, XWiki, DokuWiki, BookStack)
• Configuration: Deploy on organisation-controlled infrastructure within required jurisdiction
• Avoid: SaaS offerings unless data residency guarantees meet requirements

Microsoft 365 environment:

• Recommendation: SharePoint for intranet needs integrated with Microsoft 365
• Alternative: BookStack or MediaWiki if wiki-specific features outweigh Microsoft integration
• Note: Evaluate whether dedicated wiki adds value beyond SharePoint capabilities

Minimal budget:

• Recommendation: DokuWiki (lowest infrastructure cost) or BookStack (best capability/simplicity balance)
• Configuration: Small VM or shared hosting sufficient for typical deployments
• Avoid: Commercial options and resource-intensive FOSS (XWiki)

Existing Confluence deployment:

• Recommendation: Continue with Confluence if meeting needs
• Migration consideration: XWiki provides native Confluence import; evaluate migration complexity vs. continuation costs

External resources

Official documentation

Open source projects

Commercial products

Relevant standards

See also

• Knowledge Management -Strategic approach to organisational knowledge
• Document Management -File-centric content management
• Collaboration Platform Strategy -Selecting collaboration tools
• Identity and Access Management -Authentication integration considerations
• Application Portfolio Management -Managing application landscape