Context
Stainless announced today that they're shutting down their hosted SDK platform and joining Anthropic. They've directed all displaced customers to find alternatives. Their transition page is live at app.stainless.com/transition.
This leaves a real gap for open-source maintainers who relied on Stainless for production-quality SDK generation that includes models, types, resources, authentication, async, pagination, errors, and retries without the budget of a commercial API team. That community is actively looking for a new home right now.
The ask
A free or heavily discounted tier for qualifying open-source projects. Criteria could be simple: public repo, approved license, no commercial revenue.
What's in it for Speakeasy
Stainless built significant brand recognition by powering SDKs for Anthropic, OpenAI, and Cloudflare. Every developer who imported one of those SDKs encountered idiomatic, well-structured generated code and traced it back to the toolchain. That flywheel is now unowned and there's a wave of displaced OSS maintainers looking for somewhere to land as of today.
Context
Stainless announced today that they're shutting down their hosted SDK platform and joining Anthropic. They've directed all displaced customers to find alternatives. Their transition page is live at app.stainless.com/transition.
This leaves a real gap for open-source maintainers who relied on Stainless for production-quality SDK generation that includes models, types, resources, authentication, async, pagination, errors, and retries without the budget of a commercial API team. That community is actively looking for a new home right now.
The ask
A free or heavily discounted tier for qualifying open-source projects. Criteria could be simple: public repo, approved license, no commercial revenue.
What's in it for Speakeasy
Stainless built significant brand recognition by powering SDKs for Anthropic, OpenAI, and Cloudflare. Every developer who imported one of those SDKs encountered idiomatic, well-structured generated code and traced it back to the toolchain. That flywheel is now unowned and there's a wave of displaced OSS maintainers looking for somewhere to land as of today.