Wiki platform
XWiki runtime, configuration, extensions and controlled version changes are operated reproducibly.
WZ-IT designs, migrates and operates XWiki as a central knowledge platform - including database, search, SSO, extensions, backups and defined service levels.
The following are trademarks of their respective owners: XWiki (XWiki SAS and the XWiki project). WZ-IT is an independent service provider and has no business, partnership, or contractual relationship with these companies. We offer independent migration, installation, hosting, and operations services.
XWiki combines wiki pages, attachments, revision history, search and granular permissions. Beyond free-form documentation, templates, forms and structured data turn content into a maintainable knowledge base.
WZ-IT considers the complete platform: application, relational database, permanent file storage, Solr search, identity, reverse proxy, extensions, monitoring and recovery. This turns an installation into an operationally controlled system.
We assess spaces, pages, attachments, macros, permissions, links and integrations, then plan test migration, validation and cutover. What can be transferred automatically depends on the source system, version and extensions in use.
XWiki Standard is open source. Optional XWiki Pro extensions, vendor support and commercial migration tools are itemised separately from WZ-IT operations.
Organisational knowledge remains useful only when application, search, permissions and recovery keep working. We combine XWiki, its database, permanent storage, identity and operational processes into a documented platform.
XWiki runtime, configuration, extensions and controlled version changes are operated reproducibly.
Page structures, templates, attachments and permissions are aligned with teams and information classifications.
Directories, SSO, the REST API and connected systems are integrated through defined data and access paths.
Monitoring, updates, backups and restore tests cover the database, configuration and permanent file storage together.
We separate technical platform operations, knowledge-base design and business ownership of content.
| Area | Responsibility | Scope and boundaries |
|---|---|---|
| Architecture and provisioning | WZ-IT | Target design, reverse proxy, TLS, database, persistent storage, search and reproducible deployment. |
| XWiki runtime and updates | WZ-IT | Maintenance of the agreed instance including release assessment, backup and a controlled upgrade path. |
| Monitoring and backups | WZ-IT | Monitoring and consistent protection of the database, XWiki configuration and permanent data directory. |
| Identity and permissions | Shared | WZ-IT implements the technical connection; the customer defines groups, roles, spaces and required business access. |
| Information architecture and templates | Shared | WZ-IT supports structures, templates and data models; business teams confirm terminology, processes and owners. |
| Content and approvals | Customer | Accuracy, maintenance, retention and business approval remain with the responsible organisational units. |
| Migration and custom extensions | Optional WZ-IT service | Confluence migration, custom applications, macros, integrations and workflows are planned as a separate project scope. |
Create, comment on and maintain content using WYSIWYG or wiki editors. Revision history, changes and rollback remain traceable.
Use templates, forms, metadata and custom data structures to build handbooks, policies, registers and internal applications.
Find content and attachments through integrated search, organise areas clearly and extend the platform through the Extension Manager.
Control access for users, groups, spaces and individual pages. Separate wikis can represent organisational units where the governance model supports it.
Connect existing identities through LDAP or suitable OIDC, SAML and other authentication components while documenting local emergency access.
Connect pages, attachments and structured data to portals, automation and other business systems through the REST API.
Assess existing data and configuration, migrate them in a test run and move to managed operations through a controlled cutover.
Secure SSO, roles, administrative paths and external access for the application and existing infrastructure.
Back up all stateful components consistently and document the recovery path for the agreed scope.
Monitor and update the application and its technical dependencies and operate them under the agreed service level.
A clearly defined operating scope instead of an opaque hosting flat fee.
We set up a test instance for you, usually on the next business day. No payment details required. After seven days it is deleted unless you continue.
We combine the right compute size with ongoing operations, backups, monitoring and a service level appropriate for the criticality of XWiki. High availability and recovery targets are designed separately where needed.
We also design custom hosting architectures, integrations and migrations around XWiki. Contact us for a technical assessment.
One managed standard XWiki application is included in the Starter workload. Business and higher levels add a flexible operations allowance for planned work during regular service hours. Select compute, additional applications, storage and the appropriate service level.
A workload is one compute instance with the applications agreed for it.
One standard app per workload is already included. Additional dedicated servers count as separate workloads.
€79.90 per started TB and month, including daily encrypted offsite backup with 7-day retention.
Enquiry
Briefly describe the current state and objective for XWiki. We assess infrastructure, integration, and ongoing operations.
User count alone is insufficient. Pages, attachments, search index, concurrent editing, imports, extensions and recovery objectives affect compute, database and storage.
| Usage scenario | Technical starting point | Key factors |
|---|---|---|
| Small internal knowledge base with moderate attachments | M, relational database | Actual demand also depends on index size, extensions and concurrent use. |
| Several teams using templates and regular search | M or L, separate database and file backups | Search index, storage growth and access peaks are assessed before provisioning. |
| Confluence migration with many attachments and macros | L plus migration environment | Assessment, test imports, acceptance criteria and fallback require a separate project plan. |
| Business-critical platform or multiple wikis | Custom architecture | Isolation, database, storage, search and recovery targets determine the design. |
The calculator covers a standard XWiki workload without vendor licences or a migration project. XWiki Pro, commercial extensions, data migration and custom development are itemised separately.
The standard price describes one managed workload. Migrations, large data sets, paid vendor extensions and special availability targets are added transparently.
Dedicated workload with aligned compute, backup, monitoring and service level.
Operation in the customer's account when network, identity or data requirements favour that model.
Integration with existing virtualisation, database, storage, network and backup processes.
XWiki connects to directories and internal source systems through controlled private links.
XWiki distributes relevant data across its database, configuration and permanent data directory. Access, storage, search and recovery are therefore designed as one architecture.
Browsers, editors, administrators, automated imports and connected portals or applications.
Reverse proxy, TLS, network rules, rate limits and optional private access through NetBird or VPN.
Local roles plus LDAP, OIDC or other authentication components with aligned groups, depending on the target design.
Pages, attachments, revisions, comments, templates, structured data, extensions and search.
Wiki documents, metadata, user references, permissions and other relational platform data.
Configuration, file storage, extension data and other content not held exclusively in the database.
Solr index, REST API, email, directories and optional connected business systems.
A complete backup includes more than the database. Before production, we document backup scope, sequence and recovery of the entire platform.
Answers about Confluence migration, licensing, SSO, backups and operations.
Yes. XWiki Standard is an open-source wiki platform for structured documentation and knowledge management. Features, user experience and extensions differ from Confluence and should be assessed against the specific requirements.
Yes. We assess spaces, pages, attachments, macros, permissions and links, then run a test migration with defined acceptance criteria. Not every macro or plugin can be mapped automatically; deviations are documented before cutover.
The configured operational scope can include compute, installation, monitoring, backups, updates and the selected service level. Migration, custom data models, special integrations and vendor licences are offered separately.
XWiki Standard is open source. XWiki SAS also offers paid Pro extensions and vendor support. If required, those licence and support costs are shown separately from WZ-IT operations.
Yes. Depending on the identity platform, LDAP or suitable authentication extensions such as OpenID Connect can be used. Compatibility, licensing and group mapping are verified before implementation.
At minimum, the relational database, relevant XWiki and servlet configuration, and the permanent data directory. Additional file stores and extensions are included as needed. We design consistent backups and test recovery.
Yes. We can install XWiki on suitable customer-owned infrastructure and optionally operate it afterwards. Database, persistent storage, reverse proxy, network, backup and monitoring are integrated into the existing environment.
As an alternative to managed hosting in the data centre, WZ-IT provides the hardware, configures XWiki, and handles hardening, monitoring, updates, backup and technical support. Access can be limited to the internal network or enabled through VPN and existing identities.
from EUR 349 excl. VAT / month · plus one-time provisioning and initial setup

08.10.2025
1. Introduction: Why Knowledge Management Needs to be Rethought Knowledge management is a key success factor in modern companies. From internal IT runbooks to project...
28.10.2025
Introduction Many companies are currently still using Atlassian Confluence as a knowledge management and documentation platform. With the end of support for the on-premises version...
These solutions are often used together with XWiki
These solutions offer similar functionalities and can be evaluated together
These solutions are direct alternatives with similar use cases
No risk: worst case, you leave with a clearer understanding of your project than before.


“WZ-IT's advice on our Azure migration was technically sound and completely non-binding right from the intro call - we took away a great deal.”
Whether a specific IT challenge or just an idea - we look forward to the exchange. In a brief conversation, we'll evaluate together if and how your project fits with WZ-IT.