SDK surfaces need method-by-method comparison.
Provider migration
Migrate from Konfig to Sourced
Konfig users care about SDK quality. Sourced keeps that concern, then adds docs previews and a clearer launch workflow. On this page: what to scan in your Konfig 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
Package metadata and import paths need review.
Docs and examples need to come from the OpenAPI source.
Publishing needs dry-run and rollback states.
02Checks
Migration checklist
Inventory existing Konfig SDK packages, repos, and language targets.
Run Sourced compatibility reports against the public SDK surface.
Compare auth, pagination, errors, request params, and response types.
Generate docs previews and verify examples for high-traffic endpoints.
Use staged publishing before swapping customer-facing packages.
03Details
Why Sourced fits
Sourced makes SDK migration measurable instead of guesswork.
Docs previews and SDK previews live in one dashboard.
Unlimited preview generations support repeated cleanup before launch.
Honest trade-off: if Konfig-specific language output is a hard dependency, keep it until Sourced parity is proven for that language.