The XDA piece on ditching a paid wiki for DokuWiki in a Docker container made one point loudly: the self-hosted wiki space has quietly become as polished as the SaaS plans we have been renting. Notion, Confluence, and Coda all kept raising prices through 2025 and 2026, and the export tooling for each of them is just good enough to make a migration feel possible. We pulled together seven self-hosted wiki apps, deployed each on a small Linux box and tested again on a Mac running OrbStack, and ranked them on install pain, daily-use friction, and how cleanly we could leave again if we changed our mind.
What to look for in a self-hosted wiki
A few criteria separate the wikis that hold up after a year of growth from the ones that turn into archaeology projects:
- Editor model. WYSIWYG, Markdown, or a hybrid. The team’s writing habits decide which wins.
- Storage format. Flat files in git win for portability. A database wins for query speed and access control. Some apps split the difference.
- Search and linking. Full-text search and bidirectional links are the difference between a wiki and a folder of files.
- Access control. Per-page, per-shelf, or none. Match this to whether the wiki is private, team, or public.
- Hosting footprint. Docker compose with one image is the baseline. Multi-service stacks need a homelab that already runs Postgres or Redis.
- Backup story. Whether we can dump the entire wiki to a tarball and restore it elsewhere without losing edit history.
Quick comparison
| App | Best for | Storage | Editor | Setup difficulty |
|---|---|---|---|---|
| BookStack | Team wiki with clear structure | MySQL/MariaDB | WYSIWYG, Markdown, code | Low (one Docker image) |
| DokuWiki | Flat-file simplicity | Plain text files | Markup, with plugins | Very low |
| Wiki.js | Modern multi-editor wiki | Postgres/SQLite | Markdown, WYSIWYG, code | Medium |
| Outline | Notion-style team docs | Postgres + Redis + S3 | Block editor | High |
| TiddlyWiki | Single-file personal wiki | One HTML file | Inline | Trivial |
| SilverBullet | Local-first Markdown wiki | Flat Markdown files | Markdown + macros | Low |
| MediaWiki | The Wikipedia engine | MySQL/MariaDB | MediaWiki markup | Medium |
| Trilium Next | Hierarchical personal wiki | SQLite + flat | Block editor | Low (Docker or local) |
1. BookStack — Best for team wikis with clear structure
BookStack organises content as Books, Chapters, and Pages, which gives a team wiki visible shape without the freeform sprawl of pure note-taking apps. The editor is a friendly WYSIWYG by default, with optional Markdown and code-block modes.
Where it falls short: The Books/Chapters/Pages model is rigid. Power users miss bidirectional links and graph views.
Pricing: Free. Optional paid support from BookStack-aligned providers.
Platforms: Web app, runs on any Linux host that runs Docker. Native macOS via Docker Desktop or OrbStack. Windows via Docker Desktop or WSL2.
Download: bookstackapp.com
Bottom line: Pick BookStack for a team wiki that looks polished out of the box and stays easy to back up.
2. DokuWiki — Best flat-file pick
DokuWiki stores every page as a plain text file with version history kept as more plain text files. No database. The XDA piece walked through how that property alone makes restores, migrations, and incremental backups stop being scary.
Where it falls short: Markup is DokuWiki-flavoured, not Markdown. Plugins are needed for many modern features (Markdown editing, full-text speed, bidirectional links).
Pricing: Free.
Platforms: PHP app, runs on Linux, macOS (via Homebrew or Docker), and Windows (via XAMPP or Docker).
Download: dokuwiki.org
Bottom line: Pick DokuWiki for the simplest possible self-hosted wiki where the storage layer is “a folder of text files.”
3. Wiki.js — Best modern multi-editor
Wiki.js is the modern Node.js wiki with multiple editor modes (Markdown, WYSIWYG, code, tabular) and built-in support for git-based storage on top of a database. The 3.0 line cleaned up the editor and tightened the storage abstraction.
Where it falls short: Permissions and groups model is detailed enough to be slow to set up.
Pricing: Free. Wiki.js Cloud is the paid hosted offering.
Platforms: Linux, macOS, Windows. Docker image is the easy path.
Download: js.wiki
Bottom line: Pick Wiki.js if multi-editor flexibility matters and we want a database-backed wiki with optional git sync.
4. Outline — Best Notion-style team wiki
Outline is the closest self-hosted clone of Notion’s block editor and team-wiki feel. Collections, documents, and a clean public-share layer round it out. The 2026 releases added inline AI summarisation as an optional plug-in.
Where it falls short: Stack is heavier (Postgres + Redis + S3-compatible storage). Setup needs more homelab muscle than the single-image apps.
Pricing: Free for self-host. Outline Cloud is the paid hosted offering.
Platforms: Docker. Cleanest on a Linux server with managed Postgres and Redis.
Download: getoutline.com
Bottom line: Pick Outline if the team already loves Notion’s editor and we want to take it in-house.
5. TiddlyWiki — Best personal-pocket pick
TiddlyWiki is the single-file wiki that ships as one HTML document. Open it in a browser, write, save. The Node.js server build adds multi-user editing for small teams.
Where it falls short: Concept is unique enough to confuse first-time visitors. Sync needs a server, syncthing, or a git-backed setup.
Pricing: Free.
Platforms: Any browser. Optional Node.js server.
Download: tiddlywiki.com
Bottom line: Pick TiddlyWiki for a single-user wiki that lives in one file we can carry on a USB stick.
6. SilverBullet — Best local-first Markdown wiki
SilverBullet is the newer entrant that treats Markdown files as the source of truth, builds a wiki on top, and adds inline scripting for queries and live data views. The recent releases added Sync to multiple devices via a server or filesystem.
Where it falls short: Smaller community. Plugin ecosystem is still growing.
Pricing: Free.
Platforms: Web app, Docker, Linux, macOS, Windows.
Download: silverbullet.md
Bottom line: Pick SilverBullet if Markdown-on-disk is the storage we want and live queries appeal.
7. MediaWiki — Best for the Wikipedia engine
MediaWiki is the platform that runs Wikipedia, and it scales without complaint. The default install is heavier than the modern apps and the markup is its own dialect, but the page history, templates, and category systems are unmatched at scale.
Where it falls short: Markup steepens the learning curve. Default look is dated. Modern editor extensions help.
Pricing: Free.
Platforms: PHP, runs on Linux, macOS, Windows.
Download: mediawiki.org
Bottom line: Pick MediaWiki if we want the engine that powers the largest wikis on the internet, including their bulk-edit, template, and history tooling.
How to pick the right one
If we want the simplest possible install and we can live with markup: DokuWiki.
If we want a polished team wiki with shape out of the box: BookStack.
If we want Notion in-house and we have the homelab for it: Outline.
If we want one file we can carry anywhere: TiddlyWiki.
If we want Markdown-on-disk with modern features: SilverBullet.
If we want the Wikipedia engine: MediaWiki.
FAQ
What is the best free self-hosted wiki? DokuWiki for simplicity, BookStack for polish, Outline for a Notion clone, Wiki.js for multi-editor flexibility. All four are free.
What self-hosted wiki replaces Notion? Outline is the closest in editor model and team feel. BookStack covers most use cases with a different structural metaphor.
Is BookStack easy to set up? Yes. The official Docker image takes about five minutes to deploy on a Linux box with Docker installed. Backups are a single MySQL dump plus the uploads folder.
Does any of these run on Windows directly? Most run cleanest in Docker, and Docker Desktop on Windows supports all of them. DokuWiki and MediaWiki also run on native Windows via XAMPP or WAMP.
Can I migrate from Notion to a self-hosted wiki? Outline has the best Notion importer. BookStack and Wiki.js accept Markdown export bundles. Notion’s HTML and Markdown export is workable for everyone else.
