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 IT Administrator
Runs IT for a public utility with 900 staff whose Confluence Server held twelve years of pages until Atlassian ended its support. Was offered the cloud, read the subprocessor list and went looking instead. Needs a migration that keeps page trees, permissions and attachments, single sign-on against Entra ID with groups synced, an audit log the auditor accepts, and an edition they can run in the utility's own data centre if the works council or the regulator asks.
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, a central search across all wikis with filters, and search inside uploaded attachments are all documented. We found no public information on templates, comments and mentions, page history with restore, or whether the AI support cites the pages behind its answers, so this stays mid-band for us.
XWiki
The captured features pages document a WYSIWYG editor combining Markdown and rich text, spaces and sub-wikis with page trees, templates, real-time co-editing with comment threads and @ mentions, unlimited version history, and Solr search across documents, attachments and objects with filters and tags — that is the page-tree world our Confluence Server held. We found no public information on backlinks, a link graph, or AI answers that cite their source pages; the AI integration appears only as a Beta on the Enterprise plan. That lands it just above the solid middle of the scale for me.
Verification, ownership & freshness
BlueSpice
After twelve years of Confluence pages I need owners and review cycles, and here the captured pages show only dashboards with key figures and a list of maintenance scripts, including a batch stabilisation script. We found no public information on page owners, verification intervals, approval workflows or read confirmations; the published BSI C5 audit report covers the cloud operation rather than content governance.
XWiki
Unlimited version history is documented, a Pro Analytics Application is offered to keep knowledge relevant, and the Enterprise plan names Change Request among its supported extensions. We found no public information on per-page owners, review dates with reminders, read confirmations for mandatory pages, or an exportable audit trail of who changed and approved what — and that audit trail is exactly what our auditor asks for, so this stays low.
Permissions, SSO & administration
BlueSpice
Single sign-on is documented via SAML, OpenID, Kerberos and LDAP with identity providers including Microsoft Entra ID, Azure AD, Okta and Keycloak, and the Permission Manager exposes each role's individual permissions — that covers our Entra ID sign-in. We found no public information on directory group synchronisation, SCIM provisioning, enforced two-factor authentication, or an exportable audit log of access and permission changes, which is exactly what our auditor will ask for.
XWiki
Fine-grained rights by wiki, space, page and group, LDAP through Active Directory and Microsoft Entra ID, SSO via OIDC, SAML or CAS from the Business plan, SCIM provisioning at Enterprise, IP allowlisting, and MFA with periodic access reviews on the security page — that is the Entra ID story I need. We found no public information on directory group sync as such, guest or external access limits, or an audit log of access and permission changes, which caps it below the enterprise level.
Help-center publishing & integrations
BlueSpice
The integration catalogue is broad and named: Slack, Teams and Rocket.Chat; Jira, OpenProject and YouTrack; Google and Microsoft documents; Draw.io, LucidChart and Grafana; ServiceNow; plus the Galaxy API for custom integrations and AI services ranging from Azure OpenAI and ChatGPT to a local Ollama. We found no public information on a branded help center with custom domain, an in-product widget, webhooks or an MCP connector for AI assistants.
XWiki
Public website, CMS and external knowledge-base use cases with custom domain support from the Business plan, RESTful APIs, a bidirectional OpenProject integration and an open-source MCP server for AI assistants give us a real publishing and integration story. We found no public information on Slack or Teams integrations, webhooks, SEO controls or a help-desk ticket-deflection link, so I cannot place it higher.
Import, export & self-hosting
BlueSpice
This meets my core need: a Confluence migration path with a live macro compatibility check, a migration script that moves macros and content automatically, a questionnaire and planning meeting, segmentation into wiki articles with images and documents linked, and an honest note that minor manual post-processing may be needed. On-premises editions under a subscription contract come with installation, Docker and update documentation on a free open-source base. We found no public information confirming that page hierarchy and permissions survive the move, on full export formats, or on data return at termination.
XWiki
The Confluence Migration Toolkit is documented to move data, page history, users, permissions, attachments and metadata, with batch and incremental migration, Confluence macro bridge equivalents, a post-migration report and terabyte-scale precedent — precisely our twelve-year page tree. A self-hosted edition on Linux, Tomcat, Jetty, Docker or Debian, with Kubernetes, Windows and clusters at Enterprise, offers the same feature set as the cloud at the same pricing, which satisfies the works-council scenario. We found no public information on export that includes history in an open format, on data return at termination, or on the open-source licence by name, so it stops short of the top.
European sovereignty
BlueSpice
Hallo Welt! GmbH is registered at the local court in Regensburg, Germany, the cloud is documented as hosted in Germany with a European server provider under EU standards, and a data processing agreement with technical-organisational measures and a subcontractor list is published on the legal page. A BSI C5 criteria-catalog audit report for the cloud is published, CyberEssentials certification is stated with ISO 27001 planned; and if the works council asks, the on-premises edition runs the wiki on our own servers. We found no public information on where the AI providers process wiki content or whether content is used for model training.
XWiki
XWiki SAS is a French company with a French publication director and CNIL declaration, cloud instances run on OVHcloud in France, and the subprocessor list names OVH and Scaleway, both in France with no third-country transfer; ISO 27001 is stated with its scope spelled out, alongside SOC 1, 2 and 3. For the regulator, the documented self-hosted path on our own infrastructure with control over hosting, access management and data residency settles the residency question outright. We found no public information on a published data processing agreement or on any AI model provider in the chain, which keeps it one step from sovereign end to end.
Pricing transparency
BlueSpice
A 30-day free trial of the pro edition with all features and a free open-source edition are documented, but we found no public price per user, tier prices for the cloud, or licence and support costs for the on-premises subscription editions. I cannot compute an annual cost for 900 staff from the captured pages, so this sits at the low band despite the clear edition structure.
XWiki
Four tiers are priced publicly with exact euro figures, per-user prices, user limits, storage by tier and user count, and a feature matrix showing exactly where SSO, SCIM, LDAP, IP allowlisting, custom domain and the AI integration sit; cloud and on-premise carry the same pricing and ordering online gives a 5% discount. What the pricing page does not let me do is compute the annual cost for our 900 staff between the published 25-user and 500-user figures, and we found no public information on individual Pro App prices or VAT treatment.
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.