If your team writes in Markdown — or wishes it could — finding a hosted wiki that actually respects that is harder than it should be.
Most hosted options fall into one of two camps. Some are powerful but expensive per user, which gets painful fast for a small team. Others are convenient but proprietary: the editor looks like Markdown, the import works, but the content lives in a block format that isn’t quite the same as a plain .md file.
For teams where that distinction matters, the options narrow down quickly.
What Markdown-first teams usually want
The pattern tends to be similar. A team starts keeping notes in Markdown — in Git, in Obsidian, in a shared folder — and eventually wants something more structured: a tree of pages, search, internal links, revision history. The question is whether the hosted tool will feel like a natural extension of that workflow, or whether it will quietly push them toward a different model.
The things that matter most to this kind of team:
- Writing in actual Markdown, not a block editor with Markdown export
- Content stored as files, not locked into a database or proprietary format
- The ability to leave without pain — export, migrate, or take files elsewhere
- Structured navigation, not just a flat list of pages
- Pricing that makes sense for small teams
The main options
GitBook is the most visible choice for Markdown-oriented teams. The output is clean, the Git integration is good, and the free tier is generous for public docs. But it has gradually moved toward a block-based editor, and it’s more of a documentation publishing platform than an internal team wiki. For private knowledge bases where the audience is your own team, it can feel like more overhead than necessary.
Outline is a solid team wiki with a cloud offering and a self-hosted option. It’s open source, clean, and reasonably focused. The cloud version is $10 per user per month, which adds up quickly for a team of even six or eight people. The editor is Markdown-compatible but block-based internally. Content portability is better than most, but it’s not the same as owning plain text files.
Obsidian Publish is genuinely Markdown-first — it publishes your Obsidian vault as a hosted website. But it’s a publishing tool, not a team wiki. There’s no browser editing, no user roles, no collaborative structure for a team to work in together. It’s built for individuals sharing a personal knowledge base, not for a team maintaining shared documentation. And using Obsidian itself as a shared team workspace has its own friction — we wrote about that separately.
Where the gap is
The honest summary: most hosted options are either block editors with Markdown import, per-user pricing that doesn’t fit small teams, or self-hosting tools that still require a server to run.
There isn’t much in the space of a simple, Markdown-first hosted wiki where the content is actually stored as plain files, priced for small teams rather than per seat.
LeafWiki Hosted
That gap is what LeafWiki Hosted is being built to fill.
LeafWiki stores content as plain .md files on disk — not in a database, not in a proprietary format. The editor is Markdown with live preview. Content is exportable as a ZIP at any time; Git and S3 sync are planned for a later release. If you decide to leave, you take your files with you — no proprietary format to untangle first.
Pricing is per workspace, not per user: $6/month for a solo editor, $19/month for a team of up to 10 editors. Viewers don’t count toward the limit.
A free beta starts in September 2026 — 10 spots, no payment during the beta. If that sounds like what your team has been looking for, get a beta spot.
If you prefer to run your own server, LeafWiki is open source and free to self-host. The hosted version is for teams that want the same thing without the infrastructure.