Ask HN: What are Stainless users doing now that Anthropic has killed it?

5 pointsubutler3 comments

Hey HN, Two days ago, Anthropic bought Stainless and then immediately killed it. Stainless offered the ability to take an OpenAPI spec and automatically turn it into SDKs in almost any language, plus an MCP server.

My company makes legal AI models that we serve through an API. All our SDKs we're generated by Stainless. Those SDKs are in active use in production and, come September, will need to be maintained by someone other than Stainless.

We're not the only ones in this boat. OpenAI and Google also relied on Stainless.

What are other users planning on doing now that Stainless is gone?

We're hoping that a competitor or open-source community ends up taking on the mission of ensuring backwards compatibility or, at the very least, as seamless a migration as possible. If that doesn't get pulled off soon though, we may be forced into either completely breaking existing code or else maintaining everything by hand — the very thing Stainless was meant to take off our plate.

Has anyone else thought of better options yet?

View on HN

1. Do a seamless migration where we apply a few custom code patches to tighten the delta between the generated code to the point that this becomes as close to a backwards compatible a change as feasible. 2. Re-build workflow configuration from the Stainless paradigm (cloud based) to the Speakeasy paradigm (CLI/GitHub Action based) so this is extremely hands-off.