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 Operations Lead
Head of operations at a 180-person machine builder in Baden-Württemberg, where onboarding, travel rules and the service hotline's answers live in a shared drive, three OneNote books and two colleagues' heads. Wants one place the whole company actually uses: an editor office staff manage without training, a search that finds the answer rather than the file, pages that name who keeps them current, and a price that does not double when the workshop gets read access.
BlueSpice
XWiki
This judge's pick
Criterion by criterion
Editor, structure & search
BlueSpice
The captured pages show the Wikipedia visual editor plus a wikitext source editor, collaborative editing since version 4.5, a central search with filters across all wikis that also finds content inside uploaded files, and diagram tools such as Draw.io and BPMN. Templates, page history with restore, comments and mentions are not described in the captures, and we found no public information on AI answers citing their source pages, backlinks or search from Slack or Teams.
XWiki
The real-time editor combines rich text and Markdown with a slash command for images, videos and macros, pages sit in spaces, sub-wikis and page trees, and there are templates, forms, comment threads with @ mentions and unlimited version history — our office staff could run this without training. Search is Solr-powered across documents, attachments and objects with filters and tags, which is what the service hotline needs. We found no public information on backlinks, a link graph, diagrams, or AI answers that cite the pages they drew on.
Verification, ownership & freshness
BlueSpice
We found no public information on page owners, review dates and reminders, approval workflows, read confirmations or content analytics. The captured compliance items — a published internal BSI C5 audit report for the cloud, orientation towards BSI IT-Grundschutz and CyberEssentials certification — describe the vendor's own operations, not page-level governance in the wiki, and the documentation pages I read contain nothing on verification or freshness of content.
XWiki
What the pages show is unlimited version history, an out-of-the-box activity dashboard, and an Analytics application described as revealing usage patterns and keeping knowledge relevant. I found no public information on a named owner or verifier per page, review dates with reminders, a draft-and-publish step, or read confirmations for mandatory pages — and pages that name who keeps them current is exactly what our onboarding and travel rules need. A Change Request extension is listed as supported at the Enterprise tier, but the captured pages do not describe what it does.
Permissions, SSO & administration
BlueSpice
Authentication via SAML, OpenID, Kerberos and LDAP is stated, together with a long list of identity providers customers use — Azure AD and Entra ID, Okta, Keycloak, ADFS and more — which answers the single sign-on questions our IT will ask. The Permission Manager in the pro edition lets admins view the individual permissions of a role such as editor, and rights management is described as central for enterprise customers; we found no public information on SCIM provisioning, enforced two-factor authentication or an audit log of access and permission changes.
XWiki
Permissions go down to wiki, space, page and group with view, edit, delete and administer rights — finer than most — and SSO via SAML, OIDC, CAS or Entra ID plus LDAP and Active Directory are published, though several of these appear only from the Business tier upward. SCIM is listed for the Enterprise tier and IP allowlisting from Business. We found no public information on guest access with limits, an audit log of views and permission changes, or whether search and AI answers respect page rights.
Help-center publishing & integrations
BlueSpice
The integration catalogue is broad — Slack, Microsoft Teams and Rocket.Chat for chat, Google and Microsoft documents placed on pages, Jira, OpenProject and YouTrack for tasks, plus ServiceNow, GitHub and Gitlab — and the Galaxy API is described for custom integrations and automation, with AI services including Azure OpenAI, ChatGPT, deepL and a self-hosted Ollama option. We found no public information on help-center publishing, custom domains, an in-app widget or ticket deflection, which is what our service hotline would need for customers.
XWiki
A custom domain is included from the Basic cloud tier, the look and feel is brandable, and the platform is positioned for public websites and external knowledge bases. RESTful APIs, more than nine hundred extensions, an open-source MCP server for AI assistants and a bidirectional OpenProject integration are published. We found no public information on named Slack, Teams, Google Drive or Microsoft 365 connectors, help-center SEO controls, an in-app widget, or ticket deflection in a help desk.
Import, export & self-hosting
BlueSpice
Arriving is well documented: a Confluence migration path with a whitepaper, a migration questionnaire and planning meeting, script-based transfer of segmented data with images and documents linked, and MediaWiki XML or CSV imports through special pages or a server script; staying on our own servers is possible too, with the on-premises editions Sky, Sapphire and Indigo, Docker installation instructions and documented patch and upgrade paths. The captured pages state that migration requires conversion to WikiText and minor manual post-processing, and we found no public information on a full export with page history in an open format or on data return when a contract ends.
XWiki
The Confluence Migration Toolkit is described as moving data, page history, users, permissions, attachments and metadata, with batch migration, terabyte-scale imports, a post-migration report and preserved structure — the strongest leaving-and-arriving story I have scored. Export runs to PDF, ODT, RTF, XML and HTML, there are RESTful APIs, and the self-hosted download is stated to offer the same feature set as the cloud, deployable on Linux, Docker or Kubernetes. Everything published here says a move out would be on our terms.
European sovereignty
BlueSpice
The vendor is a German company in Regensburg with full register details, cloud data is stated to be located in Germany with a European server provider, and a GDPR data processing agreement with technical-organizational measures and a subcontractor list is published, with transfers to providers such as Cloudflare covered by EU standard contractual clauses. CyberEssentials certification is stated and an internal BSI C5 audit report for the cloud is published while ISO 27001 is described as planned, and a documented self-hosted open-source route exists; we found no public information naming the hosting infrastructure, the AI model provider's role and location, or whether customer content is used for training.
XWiki
The vendor presents itself as built in Europe, cloud instances run in France on OVHcloud, and the subprocessor list names OVH in France for hosting and Scaleway in France for encrypted backups, both marked with no transfer outside the EU. ISO 27001 is stated with its scope — cloud hosting and support services by XWiki SAS — alongside SOC 1, 2 and 3, and an on-premise edition is documented that keeps every page on our own servers, which for a Baden-Württemberg machine shop settles the hosting question. We found no public information on a published data processing agreement, on an AI model provider in the chain, or on a statement that customer content is never used for training.
Pricing transparency
BlueSpice
The captured pages confirm a 30-day free trial of the pro edition with all features and free trial data transfer to a licensed version, a free personal consultation, and named on-premises subscription editions Sky, Sapphire and Indigo under a subscription contract. We found no per-user or per-tier prices, reader or guest charges, storage limits, minimum terms or the on-premises licence cost in the captured facts, so I cannot compute the annual cost for 180 people, let alone for read-only workshop access.
XWiki
Four tiers carry exact euro figures — "Starter €773 / year for 25 users (€2.58 / user / month)" through "Enterprise €33,990 / year for 500 users (€5.67 / user / month)" — with per-tier storage ladders, sub-wiki counts, support reaction times and a feature matrix that says plainly which tier gets SSO, SCIM, IP allowlisting, custom domain or the Beta AI, and cloud and on-premise are stated to cost the same. The captured pages give different figures for the entry price: the migration page states "Starting at €3.63/user/month" while the pricing page shows "Starter €773 / year for 25 users (€2.58 / user / month)". What I cannot compute is the workshop's read-only access — we found no public information on reader or guest seats, VAT treatment, or the price of an individually purchased Pro app.
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.