Overview
Self-hosted wiki platform for internal docs, knowledge bases, and public documentation.
Wiki.js is a self-hosted wiki platform for teams that want internal documentation, knowledge bases, or public docs without handing their content and access control to a SaaS wiki service.
Why people choose Wiki.js
The official site positions Wiki.js around a modern writing experience, broad deployment flexibility, and the ability to mix public and private content. It appeals to teams that want something friendlier than a bare Markdown repo but still flexible enough for developer documentation and internal knowledge management.
What is included in the stack
Official product and docs pages highlight Markdown and visual editing, authentication modules that range from local logins to LDAP, SAML, OAuth2, and OpenID Connect, built-in search, version tracking, asset management, themes, localization, and storage or backup integrations such as Git and cloud object storage.
What to know before you deploy
Wiki.js is easier to position than many heavier enterprise knowledge platforms, but it is still a real application stack. You need to choose a database, plan backups, and decide how much of the auth, search, and storage module surface you actually want to maintain.
Best fit
Choose Wiki.js when you want a polished self-hosted wiki for team docs, runbooks, or mixed public-private documentation. If you want a simpler book-style docs tool with fewer moving parts, lighter documentation apps may be easier to operate.
Interface previews
Screenshots of the Wiki.js interface.
Feature support
| Feature | Support |
|---|---|
| Markdown and visual page editingOfficial product pages show both Markdown and a visual builder so technical and non-technical users can work in the same system. | Supported |
| Broad database compatibilityThe official site says Wiki.js can run with PostgreSQL, MySQL, MariaDB, MS SQL Server, or SQLite. | Supported |
| Local and enterprise authenticationOfficial docs list local auth plus LDAP, SAML, Auth0, Okta, OAuth2, and OpenID Connect style integrations. | Supported |
| Version history and page comparisonThe feature list says all content modifications are tracked and can be compared or reverted. | Supported |
| Built-in search with external search optionsOfficial docs describe built-in search plus optional external engines such as Elasticsearch and cloud search services. | Supported |
| Asset management and media uploadsThe product site highlights an assets manager for organizing uploaded media and files. | Supported |
| Git and external storage backup targetsOfficial docs describe Git and cloud storage integrations for sync or backup, but the exact setup depends on which modules you enable. | Partial support |
| Localization and multilingual contentOfficial product pages say Wiki.js is translated into more than 40 languages and supports multilingual content. | Supported |
Community signals
- Stars
- 29k
- Forks
- 3.3k
- Open issues
- 5
- Last commit
- 18h ago
- Latest release
- 3.0.0-beta.651
- Repo created
- Aug 2016
Includes open pull requests
2d ago
Refreshed nightly from the GitHub API.
Questions
What is Wiki.js used for?
Wiki.js is used to build internal documentation, runbooks, team knowledge bases, and public docs sites on infrastructure you control.
Is Wiki.js a self-hosted Confluence alternative?
For many teams, yes. Wiki.js covers the core self-hosted wiki use case with editing, search, permissions, version history, and enterprise-friendly auth options.
Does Wiki.js support Markdown?
Yes. The official site lists Markdown as a first-class editor, and it also offers a visual editor for people who do not want to write markup directly.
Can Wiki.js use LDAP or SSO?
Yes. Official docs list enterprise authentication modules including LDAP, SAML, OAuth2-style options, and OpenID Connect integrations.
What database does Wiki.js need?
Official product pages say it can run on PostgreSQL, MySQL, MariaDB, MS SQL Server, or SQLite, which gives self-hosters flexibility during deployment.
Can Wiki.js back up content to Git?
Partly yes. Official docs describe Git and external storage modules for sync or backup workflows, but the exact behavior depends on which modules you enable and maintain.
What is the main Wiki.js tradeoff?
Wiki.js gives you more control than a hosted docs platform, but you still need to manage the database, upgrades, auth choices, and the module surface you turn on.
support // the lab
Found this write-up useful?
If it saved you time or a rebuild, you can support more practical homelab guides.