OpenAPI source and stainless.yml structure.
Stainless migration
Move off Stainless without losing your SDK experience.
Bloom reads the files you already own, generates replacement SDK and docs outputs, and gives your team a clear plan before switching providers.
Checks
What Bloom checks
TypeScript and Python SDK shape.
Client constructor and auth settings.
Resource and method names.
Docs dependencies on Stainless-hosted APIs.
Teams
Why teams use it
Stainless customers need a practical path from hosted generation to owned generation.
Official self-hosting can help, but teams still need a managed workflow, report history, docs hosting, and release confidence.
Bloom is a migration and replacement workflow for teams that own their SDK files.
Example output
A real Sendblue run shows the migration shape.
Sendblue source spec parsed into a replacement plan.
Bloom generated the configured TypeScript SDK method set.
Bloom generated the configured Python SDK method set.
The docs site has Stainless Docs Platform dependencies to replace.
| Example | Why it matters | Current result |
|---|---|---|
| Sendblue report run | Runs from OpenAPI plus stainless.yml through TypeScript/Python SDK generation and comparison. | SDK generation works; remaining review is focused on final runtime and docs parity. |
| stainless.yml parser | Reads package names, production repos, auth env vars, README example endpoint, and MCP settings. | TypeScript package `sendblue`, Python package `sendblue_api`, MCP package `sendblue-mcp`. |
| Docs dependency scanner | Finds Stainless Docs Platform package version, hosted API dependencies, SDKJSON readiness, and docs migration work. | `@stainless-api/docs` 0.1.0-beta.134, 2 tasks, 2 review items. |
| Compatibility output | Separates generated method coverage from final SDK-shape review. | 0 missing TS methods, 0 missing Python methods, 42 Python method shapes marked for review. |
Related pages