requarks/wiki: Wiki.js 3.0 has just left beta, and everything you need to install it lives off the repository

Version 3 left beta in a week: 3.0.0-beta.705 to 3.0.2

The 3.0 line ran as a beta long enough to reach build 3.0.0-beta.705, published on 2026-10-26. Six days later, on 2026-11-01, 3.0.1 appeared as a regular release, and 3.0.2 followed on 2026-11-02, with the last push to the main branch the same day. For anyone asking whether Wiki.js is dead, the commit history answers it. For anyone planning a production deployment, the more useful observation is that two point releases landed within roughly a day of the first stable 3.0, so read the release notes for each before you upgrade.

Install steps live on docs.js.wiki, not in the repository

The README contains no install command. It links out to an official website at js.wiki, documentation at docs.js.wiki, a Requirements page at docs.js.wiki/setup/requirements and an Installation page at docs.js.wiki/setup/installation. The consequence is that the GitHub repository alone will not tell you which database or runtime versions 3.0 expects; you have to read the docs site, and you should check that its pages describe 3.0 rather than an earlier major version before following them. Release artifacts and their notes sit on the GitHub releases page, which the README labels as the changelog, so pair the docs site with the notes for the exact tag you deploy, such as 3.0.2, instead of assuming the docs were updated on the same day as the code.

Free to use under AGPL-3.0, funded by backers

Wiki.js is licensed under AGPL-3.0, a copyleft license, and costs nothing to use. The project is paid for by its community: a Gold Tier sponsor, GitHub Sponsors through the NGPixel account, Patreon under requarks, an OpenCollective at opencollective.com/wikijs, PayPal donations and a Threadless merchandise store. GitHub sponsors get their name and a link listed on the backers page of the Wiki.js website. If you plan to ship a modified build, read the AGPL-3.0 terms before distributing it.

Translations wait on volunteers

Localization runs through CrowdIn, and the README link to the translations guide at docs.js.wiki/dev/translations carries the note that the project needs help. If your users work in a language other than English, check the state of that language before rollout, and budget time to contribute strings yourself if coverage falls short.

Feature requests go to a feedback portal, not the issue tracker

New ideas are routed to feedback.js.wiki, a portal run on ProductBridge, rather than to GitHub. Chat happens on Discord, with further community channels on Bluesky, Telegram and the r/wikijs subreddit. The changelog is the GitHub releases page. If you want to influence what the 3.x line adds, file it on the portal, and keep GitHub releases as your source for what actually shipped.

The license badge still points at master while the default branch is main

The default branch is main, yet the license badge in the README links to blob/master/LICENSE. It is a small mismatch, but it matters if you write scripts, CI jobs or documentation that fetch files from the repository by branch name: use main, and do not copy branch paths from older badges or links without checking them.

A Vue codebase leaning on donated services

GitHub classifies the repository's primary language as Vue, so contributors working on the interface should expect Vue components rather than server templates. Several pieces of the project's own infrastructure are donated rather than paid for: Cloudflare supplies CDN, SSL and networking for the project, BrowserStack provides cross-browser testing access, Icons8 provides icon sets, CrowdIn provides the localization platform, Porkbun registers the domains and ProductBridge runs the feedback portal. None of this changes what you install on your own server, but it explains how a donation funded project keeps its public sites, translation workflow and testing running, and it means those services sit outside the repository: if you fork Wiki.js, you inherit the code, not the CrowdIn project, the feedback portal or the docs site, and you would need to replace each one yourself.

Editorial conclusion

Wiki.js suits teams that want a free, AGPL-3.0 wiki they host themselves and are comfortable following an external documentation site for setup. Teams that need a settled release history should note that 3.0 only left beta at the start of November 2026, with 3.0.1 and 3.0.2 a day apart. Before committing, read the requirements page on docs.js.wiki and the 3.0.x release notes on GitHub, and confirm the AGPL-3.0 terms fit how you plan to modify or serve it.

Frequently asked questions

Official sources

1. License: AGPL-3.0
2. Project website
3. README
4. Releases
5. requarks/wiki on GitHub