Architecture and migration
Sizing, target environment, data transfer, cutover and recovery are resolved before production operations.

WZ-IT plans, installs and operates Wiki.js as managed hosting, in your cloud or on premises. Depending on the target design, we also provide migration, secure network and identity integration, monitoring, backups, updates, integrations and further development.
The following are trademarks of their respective owners: Wiki.js (Requarks (Nicolas Giard)). 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.

Wiki.js is extensible open-source wiki software with visual and Markdown editing, search and granular permissions. The project is released under the AGPL-v3 licence.
Wiki.js is based on Node.js and supports different databases as well as external search and storage targets. The architecture is selected for user volume, content size, integrations and availability requirements.
We install, host and operate Wiki.js for your company - either on our secure, privacy-focused infrastructure in Germany or other locations, as well as on-premise in your own environment.
We provide 24/7 monitoring, backups and maintenance for your Wiki.js instance. Human response times and support coverage follow the selected service level.
Works on virtually any platform and is compatible with PostgreSQL, MySQL, MariaDB, MS SQL Server or SQLite.
Manage all aspects of your wiki using the extensive and intuitive admin area.
Wiki.js is based on Node.js. Actual performance depends on the database, search, storage, caching and selected infrastructure.
Fully customize the appearance of your wiki, including light and dark mode.
Make your wiki public, completely private or a mix of both with granular permissions.
Wiki.js intelligently makes use of available resources - from Raspberry Pi to high-performance VM in the cloud.
Installation guides are available for supported platforms. Production effort also depends on database, identity, networking, backups and migration scope.
Built-in authentication with self-registration and password recovery capabilities.
Use 3rd-party authentication services like Google, Facebook, Microsoft, GitHub, Discord, Slack and more.
Integrate with LDAP, SAML, CAS, Auth0, Okta, Azure AD and more. Generic OAuth2 and OpenID Connect modules included.
Add an extra layer of security using two-factor authentication for supported authentication modules.
Connect your wiki with an ever-expanding list of external integrations for authentication, logging, rendering and more.
Professional installation on your infrastructure - on-premise, cloud or hybrid
In your data center
AWS, Azure, Hetzner & more
Advanced architecture after technical and licence assessment
Secure access and access control for your installation
WireGuard, NetBird or Tailscale
Directly or through an upstream identity layer
Depends on application, edition and identity provider
Fail2Ban, Rate Limiting, IP Whitelisting
We set up secure VPN access to your installation - ideal for remote work and external employees.
Full-service installation with no hidden costs
Wiki.js stands out with its modern architecture (Node/GraphQL). We extend this base to seamlessly integrate documentation into technical workflows.
Wiki.js is API-first. We use the GraphQL API to not only display content but programmatically create it - e.g., automatic documentation from code comments.
Docs-as-Code. We configure Git sync so changes in the repo immediately land in the wiki - and vice versa. Including review workflows via pull requests.
Standard Markdown not enough? We develop rendering modules for specific data types: CAD files, interactive schematics, or Swagger UI embeddings.
How we implement Wiki.js development in practice.
Login must occur via an internal legacy IDP that does not speak standard OIDC/SAML.
Development of a custom Passport.js strategy for Wiki.js that performs authentication against your proprietary system.
API documentation in the wiki is always outdated because developers have to maintain it manually.
CI/CD pipeline that generates OpenAPI/Swagger files during build and pushes them to the wiki via GraphQL. Always in sync with code.
Complex relationships between articles (e.g., IT infrastructure) are hard to understand in text form.
Embedding a graph visualization module (Mermaid/D3.js) that automatically represents links between pages as an interactive network map.
We do more than provide an application. WZ-IT designs the technical architecture, integrates network and identity, operates the agreed scope and develops integrations when the standard product is not enough.
Sizing, target environment, data transfer, cutover and recovery are resolved before production operations.
SSO, secure access, internal systems and existing security components are integrated appropriately.
Updates, backups, technical monitoring and response paths follow a transparent operational scope.
APIs, automation and custom extensions can be delivered beyond basic deployment.
The exact scope depends on the application, edition, infrastructure and criticality. Vendor licences and non-standard components are quoted separately.
Collaboration platforms connect communication, files, identities and integrations. We treat them as a complete system rather than a single container.
Browser, desktop and mobile clients access shared workspaces through agreed roles.
TLS, firewall rules, reverse proxies or private network paths are designed around the platform's exposure.
Local accounts, SSO, directories, service accounts and emergency access are connected through clear roles.
Workspaces, communication, sharing and roles are configured and operated in a controlled way.
Messages, content, uploads, search, retention and backups.
Notifications, calls, TURN or further services depending on the feature set.
SSO, provisioning, bots, webhooks and connected business systems.
The diagram is a resilient target model. Its implementation depends on edition, data flows, load, availability objectives and existing infrastructure.
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.
Compute, applications, storage and response are shown separately. You can see what ongoing operations include and which requirements need a technical assessment.
We also design custom Wiki.js architectures, integrations and migrations. Contact us for a technical assessment.
One managed standard Wiki.js application is included in the Starter workload. Every service level also includes flexible expert time 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.
Briefly describe the current state and objective for Wiki.js. We assess infrastructure, integration, and ongoing operations.
Whether you run Wiki.js in-house or need to host confidentiality-professional data §203-ready - we build, operate and maintain Wiki.js on an encrypted on-site server. Data never leaves the building in cleartext.
See Wiki.js on-premise
Everything you need to know about Wiki.js
Wiki.js is a modern, open-source wiki engine based on Node.js. It allows you to create content in Markdown or via a visual editor and organizes knowledge bases, documentation, or internal wikis in a structured and clear manner.
Wiki.js combines several advantages: fast, performant execution thanks to Node.js, flexible storage options (including Markdown + Git backend instead of database lock-in), modern interface, visual and Markdown editing, version control, search function, and granular access rights - ideal for teams, companies, or government agencies.
Wiki.js is platform-independent - you can run it on VM, bare-metal server, Docker, or cloud VM. Supported databases include PostgreSQL, MySQL, MariaDB, SQLite, MS SQL, etc.
Yes - Wiki.js can be deployed in the cloud, on VMs, or as an on-premise installation. With our managed service, we install and configure Wiki.js on your infrastructure - locally in your data center, privacy-focused, and with control over data location and access.
You can edit content using Markdown or use the visual editor - ideal for both developers and non-technical users. Multimedia (images, videos, documents) can be easily embedded.
Wiki.js stores content as Markdown files, and through Git integration, changes can be versioned, tracked, and reverted if needed. This provides security and transparency - ideal for enterprise wikis and documentation.
Yes - Wiki.js has a fine-grained role and rights management: you can precisely control who can view, edit, or administer content. This makes the system suitable for internal company wikis with confidential information.
Yes - Wiki.js supports multilingualism and can be configured as a multilingual wiki. This makes it suitable for international teams or globally operating companies.
Wiki.js is ready to use in just a few clicks. The platform is designed to be intuitive and requires no technical expertise for daily use.
Yes - Wiki.js is performant and scalable. Thanks to the Node.js engine, efficient caching, and support for lightweight or powerful infrastructure, the wiki can keep up with growing demands.
We offer complete installation and configuration, hosting on your infrastructure or in certified data centers, backup & versioning, security hardening, monitoring, and optional managed service for operation, updates, and support.
For companies of all sizes - from small teams to enterprise - who want central knowledge management, documentation, internal manuals, or collaborative document work. Especially suitable when data protection, control, version history, or rights management are important.
Yes - Wiki.js supports various authentication options (e.g., LDAP, OAuth), can be integrated into existing infrastructures, and is suitable for complex environments with multiple applications and services.
Through Git backend, version control, and regular backups, data and documents can be securely restored. With managed hosting or professional maintenance, we ensure your wiki runs reliably and stably.
Unlike cloud wikis, with Wiki.js you retain full control over data, hosting, and infrastructure - ideal for data protection, compliance, GDPR. Additionally, expensive ongoing license or usage fees are eliminated.
There are several self-hosted wiki platforms: Docmost is a modern collaboration platform with real-time features. BookStack uses a simple hierarchical structure (Books/Chapters/Pages) and is particularly user-friendly. Both are open source and self-hostable. We're happy to advise you on which solution best fits your requirements.
These solutions are often used together with Wikijs
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.