| ▲ | kristjansson 3 hours ago |
| 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. |
|
| ▲ | btown 3 hours ago | parent | next [-] |
| 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. |
| |
|
| ▲ | dgellow 3 hours ago | parent | prev | next [-] |
| 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 |
| |
| ▲ | arjvik 3 hours ago | parent | next [-] | | 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? | | |
| ▲ | benesch 3 hours ago | parent [-] | | Yes, that’s right. | | |
| ▲ | lapusta an hour ago | parent | next [-] | | 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. | |
| ▲ | nightpool an hour ago | parent | prev [-] | | That would be great to lead with since it's not present in any of the blog post communication anywhere. |
|
| |
| ▲ | kristjansson 3 hours ago | parent | prev | next [-] | | 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! | | |
| ▲ | dgellow 3 hours ago | parent [-] | | 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 |
| |
| ▲ | britannio 2 hours ago | parent | prev [-] | | Is this public? I'm interested in trying it. |
|
|
| ▲ | implexa_founder 2 hours ago | parent | prev [-] |
| [flagged] |
