Skip to content
Blume
Esc
↑↓navigate↵open⌘Jpreview

How Blume compares.Side by side.

What each tool costs, where it runs, what it gives your readers and their agents, and what moving to Blume looks like. Where another tool fits better, each page says so.

Three ways to ship docs.Blume gives you the platform's polish with none of the app.

A hosted platform

Mintlify, GitBook, ReadMe, Fern, Redocly, GitHub Wiki

You maintain
Your content, in their web editor or synced from Git
It runs on
The vendor's cloud; self-hosting only on some enterprise plans
It costs
A free tier or trial, then paid plans, with AI often extra
Agent features
Whatever the vendor builds in, often gated by plan or credits

A framework you own

Docusaurus, MkDocs, Fumadocs, Starlight, VitePress, Nextra, Docus, VuePress, mdBook, Jekyll, Docsify

You maintain
Your content, plus the project around it
It runs on
Any host you choose
It costs
Free and open source
Agent features
Mostly plugins, or route code that lives in your app

Blume

The framework is the template

You maintain
Just your content
It runs on
Any host, as static files or a server
It costs
Free and open source
Agent features
llms.txt, Markdown mirrors, and a JSON API by default; an MCP server and your skills when you opt in
Migrate from
  1. 1

    Run one command in your docs project.

    Using Claude Code? Swap --codex for --claude.

  2. 2

    Review the agent's edits.

    It follows Blume's migration playbook for , rewriting your config and pages in place, so you review the whole move as one diff.

  3. 3

    Preview the result.

    Run npx blume dev, then read the agent's summary of anything it dropped or approximated.

Upgrade your docs with Blume.

Install today and ship a production-grade docs site in minutes. Free and open source, forever.

npx blume init