v0.9.0 adds revision history, link refactoring, optimistic locking, and permalinks โ four features that solve real problems in shared documentation.
A self-hosted wiki for long-lived documentation.
Built for engineers, self-hosters, and small teams.
LeafWiki keeps documentation structured, portable, and easy to operate: single Go binary, SQLite-based runtime storage, and Markdown stored on disk.



"Exactly what I'm looking for for years."
"I'm very impressed with LeafWiki's usability."
"I like this app and hope development continues."
LeafWiki is built for documentation that should remain usable over time: explicit structure, portable Markdown, authenticated editing, and a small operational footprint.
Built-in editing, live preview, search, roles, and content workflows inside the app instead of a plain Markdown file browser.
A clear hierarchy you control instead of a flat note feed. Especially useful for runbooks, archives, and internal documentation sets.
Full-text search, keyboard shortcuts, and a built-in editor help keep operational documentation quick to update and easy to revisit.
Your content remains easy to back up, move, and version. LeafWiki stays app-first while keeping the underlying content portable.
Single Go binary or Docker, SQLite at runtime, no external database setup, and multi-platform builds for Linux, macOS, Windows, and ARM64.
Admin, editor, and viewer roles, optional public read-only mode, optimistic locking, and feature-flagged revision history and link refactoring.
Quick start
docker run -p 8080:8080 \
-v ~/leafwiki-data:/app/data \
ghcr.io/perber/leafwiki:latest \
--jwt-secret=secret \
--admin-password=admin \
--allow-insecure=truesudo /bin/bash -c \
"$(curl -fsSL https://raw.githubusercontent.com/perber/leafwiki/main/install.sh)"Don't want to manage a server?
A hosted LeafWiki option is in the works โ same product, no setup, backups and TLS handled for you.
Why I built LeafWiki
I wanted a wiki that stays small enough to operate comfortably and structured enough to trust over time.
LeafWiki started from a practical need: documentation that remains understandable years later. Runbooks, internal docs, operational notes, and personal knowledge bases all benefit from structure, but many existing tools feel either too heavy or too loose.
The goal was never to build an all-in-one workspace. The goal was to build a real wiki application around Markdown: structured navigation, editing, search, roles, and managed content workflows inside the app, without turning operations into a project of their own.
Today, LeafWiki fits best for personal wikis, engineering notebooks, internal team documentation, archives, SOPs, and Markdown collections that need a more structured home. It is intentionally not trying to be a Confluence or Notion clone.
Patrick Erber ยท LeafWiki is focused on simple documentation, not enterprise workflows. See use cases โ
What's next
UI translations for languages beyond English, shaped by contributor support and real-world usage.
Additional structure for teams that want more organization without turning the product into a workflow-heavy platform.
Support the project
LeafWiki is free and open-source. If it is useful to you or your team, GitHub Sponsors helps fund maintenance, bug fixes, documentation, and focused improvements on the roadmap.
Have a question, evaluating LeafWiki, or found a bug? Open a discussion on GitHub โ
From the blog
Product updates, release notes, and longer write-ups around LeafWiki.
Notion locks your content in. Confluence is too heavy. Wiki.js needs a real database. BookStack needs PHP. None of them hit the middle ground I was looking for.
A wiki is only useful if opening it costs no effort. Here is how LeafWiki handles the daily editing workflow: keyboard-first navigation, Ctrl+V image uploads, and a live Markdown preview.