4 ms·
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
by arjvik 4mo ago
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 4mo agoYes, that’s right.
- nightpool 4mo agoThat would be great to lead with since it's not present in any of the blog post communication anywhere.
- lapusta 4mo agoI 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.
- luketaylor 4mo agoNo, the generator itself is being made source-available for previous customers
- lapusta 4mo agoHuh! I see stlc option is added now mentioning "eligible customers", which is great news. I'm curious if we would also get GitHub action?
- dgellow 4mo agoReach 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