Blume vs Redocly.Keep Redocly's linter, own your docs.
Redocly hosts Realm docs on per-seat plans with a page allowance. Blume renders the same OpenAPI, AsyncAPI, and GraphQL specs beside your guides, free and on any host, while redocly lint keeps checking your specs.
npx blume migrate redocly --codex| Blume | Redocly | |
|---|---|---|
| Price | BlumeFree and open source, with no seat limits | RedoclyFrom $10 a seat a month, with 100 pages; Markdown guides cost extra |
| Hosting | BlumeAny host: Vercel, Netlify, Cloudflare, Node, or static files | RedoclyRedocly's cloud, with single-tenant hosting on Enterprise+ |
| Editing | BlumeMarkdown and MDX in your repo, in any editor | RedoclyMarkdoc in Git, edited locally or in Reunite's web editor |
| AI assistant | BlumeAn in-page assistant on the model you choose, billed by your provider | RedoclyOn Enterprise, up to 3,500 questions a month per organization |
| Agent features | Blumellms.txt, Markdown mirrors, and a JSON API by default; an opt-in MCP server | Redoclyllms.txt and Markdown pages by default; a Docs MCP server on Enterprise |
| API references | BlumeOpenAPI, AsyncAPI, and GraphQL, with a Try it playground | RedoclyOpenAPI, AsyncAPI, GraphQL, and SOAP, with Try it and mock servers |
| API linting | BlumeBuild warnings for specs that would render wrong; no ruleset linting | RedoclyOpen-source redocly lint with configurable rules, plus scorecards in Reef |
| Leaving | Blumeblume eject hands you a standalone Astro app | RedoclyMarkdoc in Git; the site renders on Redocly's platform |
Redocly details are from its own pages as of October 7, 2026: Pricing, Reunite editor, AI assistant, MCP server, llms.txt, Linting. Something out of date? Let us know
Your docs come with you.Markdoc becomes MDX, and your linter stays put.
- Markdoc becomes MDX.
- Admonitions become
:::directives, tabs, cards, and accordions become Blume components, and partials become includes. - Sidebars move into folders.
sidebars.yamlgroups become folders with ameta.ts, and a sidebar per section becomes a header tab.- Every API gets a native reference.
- Each OpenAPI description renders with a page per operation, and a generated redirect covers every old operation URL.
- Your lint setup stays.
- A trimmed
redocly.yamlkeeps itsapis,extends, andrules, soredocly lintandredocly bundlerun as before.
Redocly
Blume
- redocly.yamlblume.config.ts
- sidebars.yamlmeta.ts
- {% admonition %}:::info
- {% tabs %}<Tabs>
- {% partial %}<include>
- # H1title
- excludeFromSearchsearch.exclude
When Redocly might suit you better.Blume isn't the right fit for every team.
- You govern many APIs.
- Reef adds an API catalog and scorecards that grade every API against several rulesets, and Reunite can keep an API that fails the baseline out of production. Blume renders specs; it doesn't grade them.
- You want a web editor with visual reviews.
- Reunite lets teammates edit, preview, and review changes in the browser, with every edit committed to Git. Blume is Markdown and MDX in your repo.
- You need reader logins and RBAC.
- Redocly's Enterprise plan adds SSO and guest SSO for readers, with RBAC that also governs AI search and the MCP server. Blume has no reader accounts; private docs use your host's protection.
- 1
Run one command in your docs project.
Using Claude Code? Swap
--codexfor--claude. - 2
Review the agent's edits.
It follows Blume's migration playbook for MintlifyFumadocsDocusaurusStarlightNextraGitBookMkDocsReadMeVitePressFernRedoclyVuePressDocsifyDocusmdBookJekyllGitHub Wiki, 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.
Questions, answered.About moving from Redocly to Blume.
What's the difference between Blume and Redocly?
Redocly hosts your docs and bills per contributor seat, with a page allowance on each plan, and AI search and an MCP server on Enterprise. Blume is free and open source, runs on any host, and has an opt-in AI assistant and MCP server on a server deployment. Redocly CLI keeps working on your specs.
What happens to my Markdoc pages?
They become Markdown and MDX. npx blume migrate redocly --codex converts Markdoc tags to directives and components, moves each page's H1 into its frontmatter title, and rebuilds sidebars.yaml as folders and tabs. Pages that need no component stay .md.
Does `redocly lint` keep working?
Yes. The agent trims redocly.yaml to its lint and bundle settings and leaves @redocly/cli and its CI jobs alone. Decorators don't run when Blume renders a spec, so the agent points the reference at redocly bundle output or an overlay instead.
Can Blume version and translate my docs like Realm?
Yes. Version folders at the root become Blume versions, with a switcher and version-scoped search, and @l10n folders become locale folders. After the move, blume translate fills in every locale with your coding agent.
What doesn't the migration carry over?
Login, RBAC, and SSO; Reunite's editor, reviews, and feedback dashboard; the API explorer's mock server, environments, and saved auth; x-tagGroups names; per-reader content and Markdoc conditionals; and PlantUML and Excalidraw diagrams. The agent reports each one so you can decide what to do with it.
Upgrade your docs with Blume.
Install today and ship a production-grade docs site in minutes. Free and open source, forever.
npx blume init