As of 1 Nov 2026, the panel rates BlueSpice 3/5 and XWiki 3/5 in Knowledge Base & Wiki. Weighted by what each judge cares about, 0 of the 6 judges pick BlueSpice and 6 pick XWiki. XWiki scores higher on 6 of 6 criteria (Help-center publishing & integrations, Import, export & self-hosting, Verification, ownership & freshness, plus 3 more). Provenance — BlueSpice: EU-Made; XWiki: EU-Made. Ratings are the AI panel’s opinion, formed from public evidence: how scores are made.
Per the computed table, XWiki holds the higher mean on the seven criteria and the higher weighted total in six of six judge rows. The leans differ by criterion: knowledge governance, portability and hosting, and pricing transparency run 6 judges for XWiki, 0 for BlueSpice; access control and publishing and integrations sit 5 for XWiki with 1 tie each; sovereignty sits 4 for XWiki with 2 ties; and authoring and search splits 3 for XWiki, 3 ties, 0 for BlueSpice. BlueSpice is strongest on sovereignty (7.0) and portability and hosting (6.3): its verdict records cloud data stated to sit in Germany, a published GDPR data processing agreement, and on-premises editions; the verdicts note it publishes no prices. XWiki's verdict cites OVHcloud hosting in France and published pricing from €773 / year for 25 users to €33,990 / year for 500 users. Both sovereignty attribute lists read unknown.
Choose BlueSpice if
You need cloud data stated to sit in Germany with a European server provider, plus a published GDPR data processing agreement, technical-organizational measures and a subcontractor list — BlueSpice's verdict records these under sovereignty, its strongest criterion (mean 7.0).
Your compliance review asks for a BSI C5 audit report covering the cloud — BlueSpice's verdict records an internal one.
Your sign-in stack runs on SAML, OpenID, LDAP or Kerberos with named identity providers — BlueSpice's access control (mean 6.2) rests on these, with a Permission Manager in the pro edition.
You are moving off Confluence and want an on-premises edition under a subscription contract — BlueSpice documents a Confluence migration path, and portability and hosting (mean 6.3) is among its strongest criteria.
Choose XWiki if
You need published prices before contacting the vendor — XWiki lists Starter at €773 / year for 25 users and Enterprise at €33,990 / year for 500 users, and pricing transparency leans 6 judges to 0 (means 7.0 vs 2.8); the captured pages give different figures for the starting per-user price.
You must move Confluence page history, users, permissions and attachments, and export to PDF, ODT, RTF, XML or HTML — portability and hosting leans 6 judges to 0 for XWiki (7.8 vs 6.3).
Your team self-hosts but wants the same feature set as the vendor's cloud — XWiki's verdict records a self-hosted edition with the same feature set as the cloud.
You need the higher knowledge governance score of the two, even though both score low there — the bench gives XWiki knowledge governance 6 judges to 0 (3.8 vs 1.7), with two judges recording no BlueSpice rating.
You need hosting in France — XWiki's verdict records OVHcloud hosting with subprocessors OVH and Scaleway, both in France with no third-country transfer; sovereignty leans 4 judges to 2 for XWiki (7.7 vs 7.0).
Read this comparison as one judge. Each weighs the same scores by what they care about.
The Quality Manager
Quality manager at a medical device supplier certified to ISO 9001 and ISO 13485, where every work instruction must be approved, versioned and read by the people it applies to. Today that means Word files, a sign-off sheet and an audit every spring. Wants approval workflows with named reviewers, read confirmations, review dates that expire pages, an audit trail they can export for the certifier, and permissions that keep drafts out of sight.
BlueSpice
XWiki
This judge's pick
Criterion by criterion
Editor, structure & search
BlueSpice
The captured pages show the Wikipedia visual editor alongside a wikitext source editor, collaborative editing since version 4.5, and a central search across all wikis with filters that also finds text inside uploaded attachments; diagrams and embeds of office documents and media arrive through the listed integrations. I found no public information on templates, comments and mentions, page history with restore, backlinks, or AI answers that name the pages they were drawn from.
XWiki
A real-time WYSIWYG editor with Markdown and rich text, a slash command for images, videos and macros, templates and forms, spaces, sub-wikis and page trees, comments and mentions, unlimited version history, and Solr search across pages, attachments and structured objects with filters and tags — that covers how my procedures get written and found. We found no public information on backlinks or a link graph, diagram support, or AI answers that cite the pages they draw on; the AI integration itself is described only as a Beta on the Enterprise plan.
Verification, ownership & freshness
BlueSpice
This is the part my certifier would ask about first, and the captured pages offer almost nothing: a maintenance script named batchStabilize and dashboards showing key figures are all that touch the content lifecycle. I found no public information on named page owners, review dates with reminders, approval or draft-review workflows, read confirmations for mandatory pages, stale-content analytics, or an exportable audit trail of who changed and approved what.
XWiki
For my ISO 13485 world this is the weak spot: unlimited version history, an out-of-the-box activity dashboard and a Pro analytics application for usage patterns are described, and an extension named Change Request is listed as supported on the Enterprise plan, but we found no public information on named page owners or verifiers, review dates with reminders, approval workflows with named reviewers, read confirmations for mandatory pages, duplicate or stale-content detection, or an exportable audit trail of changes and approvals.
Permissions, SSO & administration
BlueSpice
The Permission Manager in the pro edition lets an administrator inspect the individual permissions of a role such as editor, authentication runs via SAML, LDAP, OpenID and Kerberos against named providers including Azure AD, Entra ID, Active Directory, Okta and Keycloak, and access is protected by individual credentials and SSL. I found no public information on enforced two-factor authentication, SCIM provisioning, guest or external access, or an audit log of views, edits and permission changes, which is what I would need before drafts could live here.
XWiki
Permissions by wiki, space, page and group with view, edit, delete and administer rights, LDAP and Active Directory, single sign-on through SAML, OIDC, CAS and Entra ID from the Business plan, SCIM on Enterprise and IP allowlisting on Business and Enterprise would let me keep drafts out of sight before sign-off. We found no public information on guest or external access limits, an audit log of views and permission changes, or two-factor authentication enforced for the wiki's own users; the security page describes multi-factor authentication for XWiki's sensitive access rather than as a product feature I could configure.
Help-center publishing & integrations
BlueSpice
The pages document a Galaxy API for custom integrations, custom extensions, external data retrieval and automation, alongside integrations for Slack, Teams, Rocket.Chat, Jira and other task systems, Google and Microsoft documents, ServiceNow and specialist search engines. I found no public information on a branded help center or public site with a custom domain, webhooks, ticket deflection or a connector for AI assistants, so nothing here speaks to serving people outside the wiki.
XWiki
Custom-domain publishing on XWiki Cloud with public website, CMS and external knowledge base use cases, a documented RESTful API, an open-source MCP server for AI assistants, a bidirectional OpenProject integration and an ecosystem of 900+ extensions give me real routes out of the editor. We found no public information on help-center analytics, ticket deflection in a help desk, webhooks, or Slack and Teams connectors on the captured pages, which keeps this off the top band.
Import, export & self-hosting
BlueSpice
Arriving and staying are well covered: a documented on-premises edition the customer hosts, with Docker installation instructions, upgrade paths and four installation types, an open-source Galaxy edition, bulk import through MediaWiki XML and CSV via special pages in the interface, and a vendor-run Confluence migration service with a compatibility script, live macro check, questionnaire and planning meeting. I found no public information on a full export including page history in an open format, or on data return and deletion when a contract ends, so the exit cost is only partly computable.
XWiki
The Confluence migration story is the strongest I have reviewed: a toolkit that migrates data, page history, users, permissions, attachments and metadata, batch and incremental migrations, a post-migration report of issues, terabyte-scale imports, and a track record of 230+ migrations and SharePoint and MediaWiki paths on Enterprise. A self-hosted edition documented with the same feature set as the cloud, the same pricing on premises, and export to PDF, ODT, RTF, XML and HTML; we found no public information on the open-source licence by its name or on the deletion of every content copy at termination.
European sovereignty
BlueSpice
The legal notice names Hallo Welt! GmbH in Regensburg with a German commercial register number and VAT ID, the cloud pages state that customer data sits in Germany with a European server provider, and a GDPR data processing agreement with technical-organisational measures and a subcontractor list is published on the legal pages, with a BSI C5 audit report released and CyberEssentials certified while ISO 27001 remains planned. The server provider itself is not named, website services such as Cloudflare run under standard contractual clauses, and I found no public information on which AI model provider would read pages or whether content is used for training; a documented self-hosted edition lets a regulated customer keep every page on own servers.
XWiki
XWiki Cloud runs in France on OVHcloud, with OVH and Scaleway both listed as subprocessors located in France with no third-country transfer, behind XWiki SAS with a CNIL declaration, an ISO 27001 certification whose scope is stated as cloud hosting and support services, and SOC 1, 2 and 3 for the hosting infrastructure; a documented on-premise edition additionally keeps every page on our own servers with our own data residency. We found no public information on a published data processing agreement, on the AI model provider and its location, or on a statement that customer content is not used for training.
Pricing transparency
BlueSpice
A 30-day free trial with all pro features, a free open-source edition and on-premises editions supplied under a subscription contract are what the captured pages state publicly. No per-user or per-tier figures appear on any page I read, so the annual cost for a given number of editors, or what single sign-on, AI or data residency would add, cannot be computed; a free personal consultation is offered instead.
XWiki
The pricing page is unusually complete: Starter €773/year for 25 users (€2.58/user/month), Basic €1,486/year for 25 users (€4.95/user/month), Business €2,318/year for 25 users (€7.73/user/month) and Enterprise €33,990/year for 500 users (€5.67/user/month), each with user limits, storage bands, and an inclusion matrix running from SSO and SCIM to custom domain, AI, antivirus and support reaction times, plus a 20% three-year discount and the same price in the cloud or on premises. What I still could not compute: reader or guest seats, the individual price of Pro Apps sold separately, VAT treatment, and migration or setup fees below the Business plan where the Confluence Migration Toolkit is included for free.
Sovereignty, side by side
Dimension
BlueSpice
XWiki
Legal entity
Not determined
Not determined
Hosting location
Not determined
Not determined
Hosting options
Not determined
Not determined
Open source
Not determined
Not determined
Data processing agreement
Not determined
Not determined
Transfer impact assessment
Not determined
Not determined
Facts, side by side
Only facts both products carry under the same definition — anything else would not be a fair row.
As of 1 Nov 2026, the panel rates both 3/5. Weighted by what each judge cares about, 0 of the 6 judges pick BlueSpice and 6 pick XWiki. Which one fits depends on the criteria that matter to you; the table on this page shows both side by side, and each judge’s reading has its own page. Both were scored by the same AI bench under the same rubric, from public evidence only, as the methodology describes.
Is BlueSpice or XWiki European?
BlueSpice is European (EU-Made). XWiki is European (EU-Made). Provenance is read from each company’s own legal pages: who builds it and who owns it.
Where do BlueSpice and XWiki store customer data?
Per the vendors’ own pages as captured — BlueSpice: Default not stated; pages mention Germany. XWiki: its pages as captured do not say.