Wiki.js
Self-hosted wiki on Node.js with Git sync, flexible page structure, and deep authentication support. Multiple editors, 50+ integrations, and no forced content hierarchy
Quick Start
docker compose up -d Overview
Wiki.js is a self-hosted wiki built on Node.js that covers more ground than most alternatives in the category. Where BookStack enforces a strict hierarchy and DokuWiki stores everything as flat files, Wiki.js uses a path-based page structure you define yourself, with storage that can point to a database, a Git repository, or both at once.
The editor choice is genuinely useful. Markdown with live preview covers technical writers, and the WYSIWYG visual builder handles contributors who should not need to know what a backtick is. Both write to the same page history, which tracks every edit with the ability to compare versions or revert.
The integration depth sets it apart from simpler alternatives. Authentication supports OAuth, SAML, LDAP, Auth0, Okta, Azure AD, and more out of the box. Storage can route to S3, Azure Blob, Google Cloud, or local disk. Git sync means your entire wiki can live as a repository, readable outside the application entirely. Search uses the built-in engine or Algolia.
The tradeoffs are real. Wiki.js runs on Node.js rather than PHP, so it is more resource-hungry and the setup is more involved than BookStack or DokuWiki. There is no real-time collaborative editing. Custom theming is not straightforward. Version 3.0 has been in development for an extended period without a public release, which has created uncertainty about the project’s direction.
For a team that needs flexible structure, strong authentication options, and Git-backed storage, Wiki.js is the most capable open option. For a smaller team that just wants structured documentation and a minimal setup, BookStack takes less work to run.
Wiki.js: Pros & Cons
| Pros (The Wins) | Cons (The Friction) |
|---|---|
| Git sync: Pages back up to a Git repo; readable outside the app. | Node.js overhead: Higher resource footprint than PHP alternatives; more involved setup. |
| Auth depth: OAuth, SAML, LDAP, Auth0, Okta, Azure AD all built in. | No real-time collab: Two people cannot edit the same page simultaneously. |
| Flexible structure: Path-based pages with no forced hierarchy; fits most content shapes. | Limited theming: Custom themes are not straightforward to build or apply. |
| Multiple editors: Markdown and WYSIWYG in the same install for mixed teams. | v3.0 uncertainty: Long-running rewrite with no public release has stalled momentum. |
Use Cases
Specific ways to use Wiki.js for your workflow.
Deployment Strategy
Recommended ways to host Wiki.js in your own environment.