Comment by atomicthumbs
6 hours ago
"Hundreds of companies rely on Stainless to generate SDKs, CLIs, and MCP servers—the libraries, command-line tools, and connectors that let developers and agents use an API."
not anymore lol
6 hours ago
"Hundreds of companies rely on Stainless to generate SDKs, CLIs, and MCP servers—the libraries, command-line tools, and connectors that let developers and agents use an API."
not anymore lol
I'm waiting for the Enterprise space to wise up. For anyone who's ever worked with any reasonably large company as a vendor (especially a small one) you know how painful redlines in legal can be. Why TF haven't enterprise made it more painful for these events? Basically state that if the service is purchased/sold/shuttered prior to the contract expiry date that a significant penalty (e.g. full refund) is required and including some portion of investment made to onboard said service/product/tool.
I can't even imagine the money wasted on turn-and-burns in the F1000 alone. The US needs a wake up call with respect to consumer / buyer protections. The life of the snake oil salesman is plentiful these days, and you have a lot of AI-psychotic executives who can't seem to get enough.
> Why TF haven't enterprise made it more painful for these events?
They mostly have. By mostly refraining from dealing with startups and companies they deem either “too young” or "too small" to be reliable partners. And, when they do, imposing long sales cycles.
And thus the enterprise well is poisoned for most startups.
Usually because they need the technology the vendor is selling.
But buyers try to insert this language into partner/ biz dev contracts all the time.
Much less common for sales.
100%.
A place I worked some years ago we even had an escrow foisted on us by our larger partner in the agreement so that they’d be able to continue running the software we were building if we went under.
Honestly, it was a pain in the ass and meant that for them alone we ended up running an older version of the software than we offered to clients because as we developed its capabilities it became ever more integrated into our core platform and we weren’t about to escrow that.
When the agreement came up for renewal at the three year mark we managed to get the escrow clauses removed.
This is why it's good to consider an open-source product backed by an enterprise support company. Growthbook is an example. If they go poof you still have dozens to hundreds of other companies, and open source base, and can collaborate with the other users (companies) to crate a foundation to carry on development if needed. Or just patch it yourself. There's a continuum depending on how critical and how deeply you exploit it.
> Why TF haven't enterprise made it more painful for these events?
Hadn't heard of Stainless before today. Did it have enterprise customers?
"rely" is overly strong in these cases usually (more like "make use of")
what is the value in destroying those relationships? I assume it was acquisition to defend against another company owning a key part of their delivery pipeline, but killing the public product is just bad press.
the relationships and enterprise customers they have are probably wildly blown out of proportion and few if any actually used the product in production.
They can also keep the product running behind the scenes for a select few and just shut down the public facing part
It would be weird if Anthropic were genuinely using it as they say they have been for years but everyone else was a fake customer.
That is WILD to put those statements together in the same article.
What's WILD is people ending up relying on these essentially startup-slops that just serves to give you future technical debt once you have to eventually moved away because they got acquired by $INSERT_BAD_GUY_OF_THE_MONTH
The only people "relying" on this are other startups whose VC benefactors force them to use other products under their portfolio in order to goose up their numbers.
8 replies →
Stainless was a fantastic product; every product/service has to start from somewhere
It may be that there are many projects relying on Stainless, or, as a sibling comment points out, it may be portfolio-based stack selection rather than actual feature dependence.
Either way, it does seem irresponsible and tone deaf for an acquiring/hiring company and an acquired/hired company to send these conflicting signals. If one puts oneself out there as dependable in the face hopes and needs of other, smaller, up-and-coming projects, then a rapid wind-down for $ is incongruent with such a posture.
So much so that, at least for my part, I'd be quite reluctant to hire someone who had engaged in this sort of bob-and-weave pursuit.
They didn’t. The first is from the Stainless blog post, the second is from Anthropic’s.