Wiki.js is a modern, lightweight wiki application built on NodeJS and distributed as open source under the AGPL-3.0 licence, aimed at teams and organisations that want to publish and maintain their own documentation and knowledge base rather than renting a hosted one.
What it is
Wiki.js is an open-source wiki application written in Vue and built on NodeJS. It lives in the JavaScript and Node.js ecosystem, is tagged cross-platform, nodejs, markdown, git, documentation and wiki, and presents itself as a next-generation wiki for documentation and knowledge base work. The project is developed in the open on GitHub at Requarks/wiki under the AGPL-3.0 licence, with a Vue front end, a NodeJS back end, and a documented installation path for self-hosting.
The concrete problem it solves is ownership of written knowledge. Teams that need a collaborative documentation space usually face a choice between a hosted wiki service they do not control and a pile of Markdown files with no structure. Wiki.js replaces the hosted wiki product with something the operator runs themselves, while the topic list points to Git and Markdown as first-class concerns so that authored content stays in plain, portable formats. It also carries translation work through its own documentation site, so the interface is not English-only.
Key capabilities
- NodeJS application with a Vue front end, distributed as a self-hosted wiki rather than a hosted service.
- Markdown as a content format, alongside the project's documentation and knowledge base focus.
- Git integration indicated by the repository topic list.
- Cross-platform operation, per the repository topics.
- Official Docker image
requarks/wiki published on Docker Hub, with the pull count tracked in the README badges.
- Continuous build and publish handled by the GitHub Actions workflow
build.yml.
- Source code written to the Standard JavaScript style guide, with badges for release version, AGPLv3 licence, build status, downloads and Docker pulls.
- Community channels listed in the README: Discord chat, Reddit at r/wikijs, Bluesky at @js.wiki and Telegram at @wiki_js.
Who uses it and how
- Teams that need an internal documentation or knowledge base site and are willing to operate the application themselves.
- Organisations that require their written content to remain in Markdown and under their own control, which the Markdown and Git topics support.
- Operators who prefer container deployment, using the published
requarks/wiki Docker image rather than a from-source NodeJS build.
- Contributors and translators: the README carries a translations link and an explicit call for help, so localisation is an active community workflow.
- Administrators evaluating the software without committing: an online demo is listed at docs.requarks.io/demo.
Getting started
The primary documented path is self-hosting: installation instructions live at docs.requarks.io/install, with prerequisites at docs.requarks.io/install/requirements, and an official Docker image is published as requarks/wiki. A hosted demo is available at docs.requarks.io/demo for evaluation before deployment.
How it compares
No list of paid products that this project replaces is provided in these facts, and no comparable self-hosted wiki tools are named either, so Wiki.js stands alone in this registry. Judged only on what the facts state, the relevant axes are licence and hosting: it is AGPL-3.0 and self-hosted, which places questions of data ownership and cost entirely with the operator rather than with a vendor.
When to use it — and when not to
Pick Wiki.js when a self-hosted, NodeJS-based wiki in Markdown is the goal and the team can run and maintain it, including the database and other dependencies that its own installation requirements page describes. The README excerpt available here is largely badges and navigation links, so a prospective adopter must read docs.requarks.io for the operational detail rather than judging from the repository front page. The AGPL-3.0 licence is also a real constraint for organisations with strict licensing policies, and the open issue count of 182 signals a backlog worth reviewing before committing.
