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 Skeptic
Has migrated a wiki whose "export" turned out to be one PDF per page, watched a self-hosted edition announced as retired with two years' notice, and read "your data is never used for training" above a subprocessor list naming two AI providers. Asks what a full export contains, which model reads the pages and where, whether readers are billed like editors — and what leaving would cost.
BlueSpice
XWiki
This judge's pick
Criterion by criterion
Editor, structure & search
BlueSpice
The Wikipedia visual editor plus a wikitext source editor, collaborative editing since version 4.5, search with filters that reaches into uploaded attachments and across every wiki of a Galaxy instance, and diagrams from Draw.io to BPMN are all documented. What I could not find: templates, page history with restore, comments and mentions, backlinks, and whether AI answers cite the pages they drew on — AI support appears as a bullet, with ChatGPT, Azure OpenAI, deepL and Ollama named as integration options rather than a documented answering feature.
XWiki
A real-time WYSIWYG editor with Markdown, templates, spaces and sub-wikis with page trees, comments with mentions, unlimited version history and Solr search across documents, attachments and objects with filters and tags are all documented. I found no public information on backlinks or a link graph, diagram support, searching from Slack or Teams, or AI answers that cite their source pages; the AI integration appears only as a Beta line on the pricing page.
Verification, ownership & freshness
BlueSpice
We found no public information on page owners or named experts, verification with review dates and reminders, approval or publishing workflows, read confirmations, or content analytics such as views, failed searches and stale-page reporting. The audit material we did read — a BSI C5 criteria-catalog audit report for BlueSpice Cloud, CyberEssentials certification, ISO 27001 planned — concerns the vendor's own operation, not content governance in the product.
XWiki
Unlimited version history, an out-of-the-box activity dashboard and a Pro analytics application for usage patterns and content relevance are described. I found no public information on page owners, verification with review dates and reminders, or a draft-and-approve publishing step; "Change Request" appears solely as the name of an extension supported at the Enterprise level, with no description of what it does.
Permissions, SSO & administration
BlueSpice
A Permission Manager with role-based rights, published screenshots of an editor role's individual permissions, and authentication via SAML, OpenID, LDAP and Kerberos against everything from Azure AD and Entra ID to Keycloak and Okta are documented, with administration of rights and access protection described as traceable. Guest access limits, enforced two-factor authentication, SCIM provisioning, and an audit log of access and permission changes are not described on the pages I read.
XWiki
Permissions at wiki, space, page and group level with view, edit, delete and administer rights, single sign-on via OIDC, SAML, CAS or Entra ID, LDAP/Active Directory, SCIM and IP allowlisting are each real and priced to a tier. The pricing matrix shows single sign-on absent from Starter and Basic and SCIM from everything below Enterprise, and I found no public information on an audit log of views and permission changes, guest access, admin-enforced two-factor authentication as a product feature, or permissions being honoured by search and AI answers.
Help-center publishing & integrations
BlueSpice
The integration half is broad and real: Slack, Teams, Jira, ServiceNow, Google and Microsoft documents, GitHub, enterprise search via iFinder and OpenSearch, and a documented Galaxy API for custom integrations, external data and automation. On the publishing half I found no public information on a branded help center, public sites, custom domains, SEO controls, an in-app widget, webhooks or a connector for AI assistants — and that is the half that reaches people outside the editor.
XWiki
An open-source MCP server for AI assistants, RESTful APIs, a bidirectional OpenProject integration, custom-domain support on the cloud tiers, and external knowledge base, public website and CMS among the stated use cases take this beyond basics. I found no public information on a help center with SEO controls and analytics, an in-product widget, help-desk ticket deflection, or webhooks; Slack, Teams, Google Drive and Microsoft 365 appear only behind general "hundreds of extensions and APIs" language.
Import, export & self-hosting
BlueSpice
Arriving is well covered: a Confluence migration service with a compatibility script and a live macro check, MediaWiki XML and CSV import via special pages or server-side scripts, and a documented on-premises path (Docker-only install for version 5, upgrade paths up to 5.1, four installation types) on an open-source Galaxy base. Leaving is where the pages go quiet: a full export's contents and whether history travels with it are not described, data return or deletion on termination is not described, and the FAQ shows the question of moving cloud data to on-premises without showing the answer — a buyer plans an exit on undocumented terms.
XWiki
Arriving is documented better than most: a Confluence Migration Toolkit moving pages, history, users, permissions, attachments and metadata, batch and incremental migrations, programmatic import via REST API, a post-migration report and terabyte-scale migrations without stopping Confluence. Leaving is addressed through export to PDF, ODT, RTF, XML or HTML, a downloadable self-hosted edition stated to offer the same feature set as the cloud, and Pro & Support at the same price on-premises or in the cloud — but I still want in writing whether a full export carries history and attachments in a format another tool imports, the name of the open-source licence, and contract-end data terms beyond personal-data deletion on request.
European sovereignty
BlueSpice
Much of the chain is provable: Hallo Welt! GmbH registered at Regensburg local court, cloud data stated to sit in Germany with a European server provider under EU-standard hosting, a published data processing agreement with technical-organisational measures and a subcontractor list, a published BSI C5 audit report, and a self-hosted open-source edition that keeps the wiki on the customer's own servers. What holds it back: the cloud infrastructure is not named, ISO 27001 is only planned, and the subprocessor locations with stated transfer bases come from the website privacy policy and include transfers to the USA under standard contractual clauses. Nothing states which AI provider reads customer pages for answers or whether content is used for training.
XWiki
The chain that is documented is French end to end: XWiki SAS as the entity, cloud instances hosted in France on OVHcloud, subprocessors listed as OVH and Scaleway both in France with no transfers, an ISO 27001 certificate with its scope actually published plus SOC 1/2/3, and a customer can instead self-host on its own servers and keep every page in its own chain. The gaps are the ones I always ask about: the AI integration (Enterprise, Beta) and the open-source MCP server name no model and no location, and I found no public information on whether customer content is used for training, on a data processing agreement, or on CDN, email, support and payment providers beyond the two infrastructure names.
Pricing transparency
BlueSpice
A thirty-day free trial of the pro edition with all features and a free open-source edition are the only cost facts I found; the on-premises subscription editions are named, but their prices are not. We found no public information on per-user prices, how readers or guests are counted, tier inclusions, storage limits, minimum seats or terms, or the self-hosted licence and support cost — a buyer cannot compute an annual cost from these pages alone.
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 by user count, sub-wiki counts, support contacts and reaction times, and a matrix showing which tier buys SSO, SCIM, AI, custom domains, IP allowlisting and migration tools. Still not computable from the captured pages: readers or guests are never priced as a separate role, VAT treatment is unstated, per-user cost between the 25-user and 500-user examples must be asked for, individual Pro App prices are not shown, and the captured pages give different figures for the starting price — €3.63/user/month on the migration page against €2.58/user/month on the pricing page. The "free" paths are a trial and a download behind a contact form asking for project details.
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.