Some clarity about existing users/SDKs would go a long way. Otherwise this reads like "we just bought OpenAI's front door and we're EOLing it. Hopefully no one was planning to use it in the future". Petty and pointless.
back
3 comments
Via https://www.stainless.com/blog/stainless-is-joining-anthropi... that's exactly what seems to have happened:
> As we focus on Claude Platform capabilities and connecting agents to APIs, we’ll be winding down all hosted Stainless products, including our SDK generator. Starting today, new signups, projects, and SDKs will not be available.
> If you’re a Stainless customer, visit app.stainless.com/transition for help transitioning from Stainless-managed products to other options. As always, you own the SDKs you’ve generated to date, and have full rights to modify and extend them however you wish.
Looks like contracts (enterprise, even!) matter again
If you have an account you can go to https://app.stainless.com/transition. The team spent a good amount of time working on a way for customers to switch to self-service
I don't have an account but my colleauges do as my company uses the platform.
By self-service, do you mean that the SDK generators are now source-available so they can be run by end users locally?
Yes, that’s right.
That would be great to lead with since it's not present in any of the blog post communication anywhere.
I don't think the generators themselves were open-sourced (only the generated SDKs were already open-source). That leaves three main (recommended) options:
* Manual Maintenance: Returning to the pre-Stainless era.
* Agentic Coding: Works to an extent, but you lose the deterministic, review-free output required to keep an SDK perfectly structured and coherent.
* Open-source Generators: Helpful for basic use cases, but they lack Stainless's full-stack features like multi-language generation and publishing, MCPs, and documentation.
No, the generator itself is being made source-available for previous customers
Huh! I see stlc option is added now mentioning "eligible customers", which is great news. I'm curious if we would also get GitHub action?
Reach out to transition@stainless.com, the team can provide more details and clarify eligibility.
What I can say for sure is that the stlc approach comes with vanilla release–please support for the release flow (I worked on that part) and that stlc has been designed for both local and CI contexts. We also have extensive docs covering all of that
Is this public? I'm interested in trying it.
Could you reach out to transition@stainless.com?
I'm viewing this as a user of non-Ant Stainless SDKs. I don't have an account or relationship with you guys, and thanks to your (excellent!) product, the surfaces I contact don't have a direct dependence on your services. But that surface is intimately informed by the nuances of your product! It'd be nice to allay (or confirm) people's fears about how this might impact your other prominent users!
Good point. FWIW if anyone reading this is a stainless user and is concerned about their situation you can reach out to transition@stainless.com. I check with the team if they can update the article with a mention
On the contrary, destroying other people's things is a fundamental part of high-stakes capitalism. If that's what it is, you're describing it as petty and pointless because it's hurting you (or someone like you).
But hurting people can be the intent. If you're selling toys, you can make a business case for going out of your way to smash other people's toys, and that can become the main activity if it's advantageous enough.
'creating new things to make the world a better place' is marketing to a specific audience. There's other audiences who are just as willing to invest in 'will absolutely ruin any rivals', and that's hardly new. Right now it's very much in vogue but could become very unfashionable as people in general react to its inevitable effects.