A hosted platform
Mintlify
- You maintain
- Your content, in their web editor or synced from Git
- It runs on
- The vendor's cloud
- It costs
- A free tier, then paid plans with metered AI
- Agent features
- Built in, on the vendor's platform
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.
- Blume vs MintlifyThe open-source Mintlify alternative.Read the comparison
- Blume vs FumadocsYour docs as content, not an app.Read the comparison
- Blume vs DocusaurusThe zero-config Docusaurus alternative.Read the comparison
- Blume vs StarlightAstro docs, with nothing to set up.Read the comparison
- Blume vs NextraThe Nextra alternative with no app to maintain.Read the comparison
Three ways to ship docs.Blume gives you the platform's polish with none of the app.
A framework you own
Fumadocs, Docusaurus, Starlight, Nextra
- You maintain
- Your content, plus the app 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
Run one command in your docs project.
Using Codex? Swap
--claudefor--codex. - 2
Review the agent's edits.
It follows Blume's migration playbook for MintlifyFumadocsDocusaurusStarlightNextra, rewriting your config and pages in place, so you review the whole move as one diff.
- 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