Analytics cookies only (Google Analytics, PostHog). No ad networks, no cross-site tracking. See our privacy policy.
upstream: github.com/requarks/wiki (opens in new tab) · github.com/BookStackApp/BookStack (opens in new tab)
Pick Wiki.js
For a Markdown-first documentation wiki with an official image, a documented PostgreSQL compose file, and a broad module system (Markdown/visual/HTML editors; local, social, LDAP/SAML/CAS/OIDC login with 2FA, all free under AGPL-3.0) — accepting a 1 GB floor, a required sub-domain, and an export/import migration from 2.x to the 3.x line that went stable in November 2026.
Pick BookStack
For a non-technical team: shelves, books and pages in a plain MIT-licensed PHP app on 512 MB, with LDAP/SAML2/OIDC and social login also free, no major-version move on the horizon, but no official container image either.
Wiki.js and BookStack are the two "just give me a documentation wiki" picks in this hub, and both sit at the same difficulty 2/5. They part ways on almost everything underneath: BookStack is a PHP/Laravel application on MariaDB with a deliberately opinionated shelves → books → pages structure and a 512 MB floor; Wiki.js is a Node.js application that wants a PostgreSQL container beside it, documents a 1 GB floor, and puts its energy into editors and login modules. Neither is a real-time collaborative editor — if that is what you are after, look at Docmost or Outline instead.
BookStack organizes knowledge the way a bookshelf does: shelves hold books, books hold chapters and pages. That structure is the product. It nudges a non-technical team into filing things somewhere sensible, the WYSIWYG editor stays out of the way, and the whole thing runs as a tidy PHP app that has been quietly reliable for years. It is MIT-licensed, which is about as uncomplicated as software licensing gets.
Wiki.js is a developer's wiki. It ships Markdown, visual (WYSIWYG) and raw HTML editors side by side, an extensive admin area, and a module system for authentication, rendering, search and storage that you switch on and off per feature. It is AGPL-3.0 — fully open, with the copyleft strings that license carries for anyone who modifies and hosts it.
Both rate 2/5, and neither makes you do anything exotic, but the shapes differ:
ghcr.io/requarks/wiki, tagged by
major version) and the docs hand you a complete compose file with
PostgreSQL. What it does not ship is a database engine: you provision
Postgres yourself. The 2.x line also accepts MySQL, MariaDB, MS SQL Server
and SQLite, but Wiki.js 3.x supports PostgreSQL only.wiki.example.com is the deployment, not
example.com/wiki.Neither wiki charges for enterprise login, so this row is a draw rather than a differentiator. Wiki.js's free build includes local accounts with self-registration and password recovery, social login (Google, GitHub, Microsoft, Discord, Slack and more), enterprise providers (LDAP, SAML, CAS, Auth0, Okta, Azure AD) plus generic OAuth2 and OpenID Connect, and two-factor authentication on supported modules. Wikis can be public, fully private, or a mix.
BookStack's free MIT build answers with an AUTH_METHOD of standard,
LDAP, SAML2 or OIDC, plus social login through Google, GitHub, GitLab,
Azure, Okta, Slack, Discord and Twitch — all configured in its .env. Where
Wiki.js goes further is breadth of modules (CAS, Auth0, generic OAuth2 as
separate switchable providers); where BookStack is simpler is that the whole
matrix is a handful of environment variables.
BookStack lists 512 MB; Wiki.js documents 1 GB on Linux, while noting the process itself idles far lower and bursts during page rendering and indexing. On any current entry-tier VPS both fit, but if you are squeezing a wiki onto a box that already runs other things, BookStack is the lighter guest.
BookStack's pitch is stability, and its release cadence reflects that. Wiki.js has just made its big move: 3.0, a rewrite, shipped as a stable release on 1 November 2026. Its upgrade docs say "an in-place upgrade is not possible" from 2.x; you export a backup from the final 2.x release (2.5.317) and import it into a fresh 3.x instance, then re-enter module and security settings by hand. 3.x requires PostgreSQL (17 or 18) and nothing else. Our install snippet and measurements are still on the 2.x image, so a Wiki.js 2.x install today comes with that migration attached, where a BookStack install does not.
Wiki.js wins this comparison for most self-hosters because the things it adds — Markdown editing alongside a visual editor, the project's own container image with a documented compose file, and a broad module system — are the things a developer-heavy team runs into first, and its 1 GB floor is the smallest VPS tier anyway. Enterprise login is not the tiebreaker: both ship LDAP, SAML and OIDC for free. BookStack is the better pick when the audience is non-technical and the goal is a wiki that gets filled in rather than admired: lighter, simpler, MIT, and with no 3.0 migration to plan for. Both are good; the question is who will be writing in it.
BookStack lists a lower minimum: 512 MB vs 1024 MB for Wiki.js.
No. Wiki.js is AGPL-3.0, BookStack is MIT.
Pick Wiki.js if your team writes in Markdown and wants the project's own container image with a documented PostgreSQL compose file. Pick BookStack if the people writing are not developers — its shelves/books/pages structure and WYSIWYG editor do more for adoption, and it runs on 512 MB under an MIT license. Enterprise login is not the deciding factor: both ship LDAP, SAML and OIDC in their free builds.
Both do. BookStack runs on MariaDB. Wiki.js bundles no database engine at all — 2.x also accepts MySQL, MariaDB, MS SQL Server and SQLite, but Wiki.js 3.x (stable since 1 November 2026) supports PostgreSQL only, so start on Postgres.
Yes. Wiki.js 3.0 shipped as a stable release on 1 November 2026. Upstream's upgrade docs say an in-place upgrade from 2.x is not possible: you update to the final 2.x release (2.5.317), export a backup with the built-in Export for Wiki.js 3.x tool, and import it into a new 3.x instance. 3.x requires PostgreSQL. Our install snippet and measurements are still on 2.x, so treat the move as a migration rather than an image-tag bump.
Paid link — we earn a commission if you shop through it.
The flat-file team wiki with page ACLs vs. the engine behind Wikipedia.
Simple and truly open vs. slick and real-time.
A real-time Notion-style wiki with a paid ring vs. the simplest fully free docs wiki.