Free Beta · 10 spots · Starting September 2026

A wiki you can leave, hosted by someone else.

No Docker, no VPS, no maintenance window. And if you ever want to leave, your content leaves with you โ€” plain Markdown files, no proprietary format, no lock-in.

LeafWiki page view with tree navigation

Write

Markdown, not a block editor fighting you for every keystroke.

A block editor makes you decide: quote, callout, toggle, before you've written a sentence. LeafWiki is a text file. Open a page and start typing. Split view shows the rendered result live, so you're never guessing what it'll look like. Paste a screenshot with Ctrl+V and it's uploaded and linked automatically.

If you already write your README, your notes, or client documentation in Markdown, there's nothing new to learn here. Same format โ€” just with folders, search, and history on top.

LeafWiki split-screen editor with live preview
LeafWiki importer bringing in existing Markdown pages

Move in. Move out, if you ever want to.

Bring the docs you already have.

If you already have Markdown files โ€” exported from Notion, pulled out of Obsidian, or just sitting in a folder โ€” the importer brings them in, structure and links intact. No weekend lost copy-pasting into a new tool.

And nothing holds you here either. Your docs stay in plain .md files the whole time โ€” export everything as a ZIP whenever you want, no proprietary format to untangle first.

Share with a link, not a login request

Turn on public read-only mode, keep editing behind your own login.

Anyone with the link can read โ€” no account for them to create, nothing for you to explain over email. That covers a client runbook shared outside your org, a team page someone half-technical needs to find on their own, or a public how-to page for customers. One reader put the last case plainly in a GitHub discussion: a computer-repair shop needed a page their customers could read without creating an account. Same feature, several uses.

LeafWiki branding settings โ€” site name, logo, favicon

Make it look like yours

Your name on it, not ours.

Swap the site name, upload your logo and favicon. Whoever reads it sees your product's docs or your practice's wiki. LeafWiki is the engine running underneath โ€” it doesn't need to say so.

Good fit if

  • You're a solo founder, small team, or consultancy documenting your own product or client work
  • You're tired of a per-seat bill that grows every time you add someone
  • You want your docs as plain Markdown files โ€” searchable, greppable, yours to back up
  • You occasionally need a page the public or a client can read without creating an account

Probably not for you if

  • You need real-time collaborative editing
  • You need per-page or per-team permissions for a large org

That's a different product โ€” I'd rather say so now than after you've signed up.

Founding member pricing โ€” after the beta

Solo
$6/month
1 editor · 1 GB storage
Team
$19/month
Up to 10 editors · 5 GB storage

The Team plan covers up to 10 editors for one flat price โ€” not per seat. Grow from 2 people to 10 without the bill climbing with every hire.

The beta itself is free. This is what founding members pay once it ends โ€” locked in for as long as you stay subscribed, as a thank-you for testing early, not a discount that quietly disappears. All prices excl. tax.

Viewers don't count โ€” unlimited read-only sharing included.

Servers hosted in the EU.

Help shape LeafWiki Hosted

The beta starts in September 2026 โ€” free, for 10 people. I'm looking for a small group to actually use it, tell me what's missing, and help shape what launches before it costs anything.

Get a beta spot and I'll reach out personally โ€” no sales pitch, just questions about how you'd use it.

No payment now. No payment during the beta either. Just your email โ€” spots are limited to 10.

Patrick Erber

I use LeafWiki myself as my own notebook โ€” real dogfooding, not a demo. LeafWiki is a project I maintain myself, alongside my day-to-day consulting work.

No spam. I'll reach out personally about your use case.