Skip to content
OpenSourceSoftware.ai

GitHub stars

29,107
—Awaiting first sync

Awaiting first sync

No measured star history yet

What is Wiki.js?

Wiki.js is a self-hosted wiki for teams that want their documentation in one searchable place. Writers can choose Markdown or a visual editor, and every change is tracked. It connects to company sign-in systems and can mirror its content to a Git repository.

Wiki.js is a self-hosted wiki built on Node.js. Pages can be written in Markdown, a visual editor or raw HTML, with version history, group permissions and more than 40 languages. Content can sync to Git or back up to cloud storage, and sign-in supports local accounts, LDAP, SAML, OpenID Connect and social logins.

Core capabilities

  • Markdown, visual and HTML editors with page history and revert.
  • Git sync to GitHub, GitLab, Bitbucket and Azure DevOps.
  • Sign-in through LDAP, SAML, CAS, Okta, Azure AD and OpenID Connect.

Editing and page history

Wiki.js offers a Markdown editor with live preview, a visual editor and a raw HTML editor. Every page keeps its version history, so changes can be compared and reverted. An assets manager handles uploaded files and images. The interface is translated into more than 40 languages, with right-to-left support and multilingual page content.

  • Wiki
  • Markdown
  • Version history
  • Localisation

Storage, search and access control

Content can sync to Git hosts such as GitHub, GitLab, Bitbucket and Azure DevOps, and back up to AWS S3, Azure Blob Storage, Google Cloud Storage, DigitalOcean Spaces or a local or SSH location. Search can use the built-in database engine, Algolia, Azure Search or Elasticsearch. Users belong to groups with granular permissions and page rules. Sign-in options include local accounts, social logins, LDAP, SAML, CAS, Auth0, Okta, Azure AD, OAuth2 and OpenID Connect.

  • Git sync
  • Backups
  • Search
  • SSO

Run it yourself under AGPL-3.0

The official docs point production users to the stable 2.x release, published as the Docker image ghcr.io/requarks/wiki:2 and configured with DB_TYPE, DB_HOST, DB_USER, DB_PASS and DB_NAME. PostgreSQL is highly recommended, while 2.x also supports MySQL, MariaDB, MS SQL Server and SQLite. Without Docker it needs Node.js 22 or 24, and the wiki must run on its own domain or subdomain. Version 3.0 is in beta and marked as not for production, and it will support PostgreSQL only. Wiki.js is released under the AGPL-3.0 licence.

  • Self-hosted
  • Docker
  • PostgreSQL
  • AGPL-3.0

Where it fits

Use cases

  1. 01

    Keep wiki content in a Git repository

    Set up Git sync and connect a repository on GitHub, GitLab, Bitbucket or Azure DevOps. Pages are then kept in the repository as well as the wiki. For extra safety, add a backup target such as AWS S3, Azure Blob Storage, Google Cloud Storage or a network location over SSH.

  2. 02

    Give each team its own section of the wiki

    Create groups for each team and grant them permissions. Page rules can match an exact path, a path prefix or suffix, or a regular expression, so each group only sees or edits its own pages. The wiki as a whole can be public, private or a mix of both.

  3. 03

    Connect the wiki to your company login

    Enable an authentication module such as LDAP, SAML, CAS, Okta, Azure AD or generic OpenID Connect, alongside or instead of local accounts. Put users into groups to apply the right permissions. Two-factor authentication is available for supported modules.