Redocly lint rules and bundling settings need to be preserved or replaced.
Provider migration
Migrate from Redocly to Sourced
Redocly is strong for API docs and governance. Sourced is narrower around generated SDKs, docs previews, and launch reports. On this page: what to scan in your Redocly setup, the migration checks Sourced runs, and a preview of the generated SDK and docs you would get.
Unlimited previews. No credit card required.
01Checks
What to check
Markdown docs and API references need route mapping.
Governance checks should become release checks, not just docs warnings.
SDK generation needs a migration report.
02Checks
Migration checklist
Inventory redocly.yaml + the rule pack you extend (recommended, minimal, or your own custom ruleset). Sourced runs a similar set during spec scan.
Export every Markdown doc page outside the auto-generated reference — these need explicit Sourced routes.
List the Redocly bundling outputs (combined OpenAPI, lint reports) and capture them as Sourced artifacts.
Map every reference page URL to its Sourced equivalent for redirects; Redocly default paths differ.
Decide whether to keep Redocly CLI in CI for lint enforcement alongside Sourced's spec scanner, or fully replace.
03Details
Why Sourced fits
Sourced adds SDK generation that Redocly does not (Redocly is docs-only).
Migration report shows the SDK + docs cutover work in one place, not split between docs tool and codegen tool.
Per-API-project pricing replaces Redocly's per-developer + add-on pricing.
Honest trade-off: if your team relies heavily on Redocly's bundling pipeline (multi-file specs, complex governance), evaluate whether Sourced's spec scanner is a sufficient replacement before cutover.