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 Support Knowledge Manager
Owns the knowledge base of a Dutch SaaS company with customers in six languages and a support team of twenty-five. Writes once for agents and customers, publishes the public part as a help center on the company's own domain, and watches which searches find nothing. Wants review dates that nag the right expert, translations kept in step with the source, a widget inside the product, and articles that show up in the help desk next to the ticket.
BlueSpice
XWiki
This judge's pick
Criterion by criterion
Editor, structure & search
BlueSpice
The Wikipedia-based visual editor, a wikitext source editor, collaborative editing and a central search with filters that also finds text inside uploaded attachments cover how my team would write and find again, with diagrams through Draw.io and dashboards on top. We found no public information on backlinks, Markdown support, AI answers that cite their source pages, or running search from Slack or Teams.
XWiki
The writing-and-finding backbone is there for my team: a WYSIWYG editor combining Markdown and rich text with slash commands, templates, page trees and sub-wikis, real-time co-editing with comment threads and @ mentions, unlimited version history, and Solr-powered search across documents, attachments and objects with filters and tags. We found no public information on backlinks or a link graph, diagrams, search from Slack or Teams, or AI answers that cite their source pages — the AI side appears as an open-source MCP server and an Enterprise beta — so it lands above a solid mid-level editor-and-search setup without the grounded-answer layer.
Verification, ownership & freshness
BlueSpice
For content that must stay true, the captured pages describe little: we found no public information on page owners, review dates with reminders, approval workflows, read confirmations or an audit trail of changes. The nearest facts are dashboards showing key metrics and a published internal audit against the BSI C5 catalog, which speaks to the vendor's own cloud operations rather than the freshness of our articles.
XWiki
What is documented is unlimited version history, an out-of-the-box activity dashboard, and an Analytics Application (Pro) framed around usage patterns and keeping knowledge relevant. I found no public information on page owners, review dates with reminders, draft-and-approve workflows, read confirmations, failed-search analytics, duplicate detection or an audit trail of approvals — the exact freshness machinery I need for twenty-five agents writing in six languages — so this stays at the history-and-dates level.
Permissions, SSO & administration
BlueSpice
Authentication standards SAML, OpenID, LDAP and Kerberos and a long list of identity providers from Entra ID to Keycloak and Okta, together with a Permission Manager where the individual rights of a role such as editor can be inspected, read like an enterprise deployment. We found no public information on SCIM provisioning, enforced two-factor authentication, an access audit log or IP restrictions, which keeps it below the top level.
XWiki
Permissions are documented at wiki, space, page and group level with view, edit, delete and administer rights, alongside users and groups management, LDAP, Active Directory and Entra ID, SSO through SAML, OIDC and CAS from the Business plan, SCIM at Enterprise, and IP allowlisting from Business up. We found no public information on an audit log of views, edits and permission changes, on guest and external access rules, or on permissions being honoured by search and AI answers, which holds it below the top band.
Help-center publishing & integrations
BlueSpice
The integration story is broad and real: a documented Galaxy API, Slack, Teams, Jira, ServiceNow, Google and Microsoft document embeds, and AI services from Azure OpenAI to Ollama — the connective tissue my help desk would need. We found no public information on help-center publishing with a custom domain, an in-product widget, webhooks or a connector for AI assistants, so the customer-facing half of this picture stays open.
XWiki
External knowledge base, public website and CMS are named use cases, custom domain support is included from the Basic plan up, themes and navigation are customisable, RESTful APIs are documented, and there is a bidirectional OpenProject integration plus an open-source MCP server for AI assistants. We found no public information on SEO controls, multilingual publishing, an in-product widget or contextual help, help-desk integration with ticket deflection, or webhooks — the exact channels my help center would live in — so it reads as a published-site-and-API story rather than a full help-center delivery stack.
Import, export & self-hosting
BlueSpice
Self-hosting is the strong card: on-premises editions on a subscription, installation and update documentation with Docker instructions, a documented migration path from MediaWiki, and open-source Galaxy code. Confluence migration is offered as a service with a script, a live macro check and a planning questionnaire, though the pages describe segmentation and WikiText conversion with minor manual post-processing rather than guaranteeing hierarchy and permissions intact. We found no public information on a full export with history in an open format or on data return and deletion at the end of a contract.
XWiki
Arriving is the strongest story: a Confluence Migration Toolkit moving data, page history, users, permissions, attachments and metadata, with batch and incremental migration, exports without stopping Confluence, pre-migration validation, a post-migration report, bridge macros for 150+ Confluence macros, terabyte-scale experience, and SharePoint and MediaWiki paths at Enterprise. Self-hosting is a first-class route with the same feature set as the cloud and installations across Linux, Tomcat, Docker, Debian and Kubernetes, and export covers PDF, ODT, RTF, XML and HTML. We found no public information on export that includes page history, the open-source licence by name, or data return and deletion terms on termination.
European sovereignty
BlueSpice
Hallo Welt! GmbH is a Regensburg company with a full imprint, the cloud keeps data in Germany with a European server provider, and customers can download a GDPR data processing agreement, technical measures and a subcontractor list from the legal pages. Transfers to the US ride on standard contractual clauses or binding corporate rules, and an internal BSI C5 audit report for the cloud is published, though ISO 27001 is only planned. The infrastructure provider goes unnamed, and we found no public information on the AI model chain that would read our pages or on training with customer content.
XWiki
The cloud runs in France on OVHcloud, the subprocessor list names OVH for hosting and Scaleway for encrypted backup redundancy, both in France with no third-country transfer, ISO 27001 is certified with a stated scope covering cloud hosting and support, SOC 1, 2 and 3 apply to the hosting infrastructure, and the legal notice and CNIL declaration sit with XWiki SAS and its French publication director. A self-hosted path that keeps hosting, access management, integrations and data residency entirely on our own servers is documented too. We found no public information on a published data processing agreement, an AI model provider in the subprocessor chain, or a statement that customer content is not used for training.
Pricing transparency
BlueSpice
A free open-source edition and a thirty-day trial of the pro edition with all features are public, and the on-premises editions are named, but the captured pricing pages show no per-user or per-tier figures. Without prices for readers, guests, support or the self-hosted licence, my annual cost for twenty-five editors is not computable from public pages alone.
XWiki
Every plan is priced publicly — 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), Enterprise €33,990 / year for 500 users (€5.67 / user / month) — with user limits, storage bands by team size, support reaction times, a 20% saving on three-year terms, an online ordering discount, and the statement that cloud and on-premise Pro & Support share the same pricing. The feature matrix shows what costs extra: SSO from Business, SCIM, the AI beta and unlimited users at Enterprise, custom domain support outside Starter. We found no public information on reader or guest pricing, VAT treatment, or the standalone price of Pro apps and the migration toolkit below the Business plan.
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.