Anthropic Bought the SDK Factory Its Competitors Were Using — and Then Shut Down the Product

On May 18, Anthropic announced it had acquired Stainless — the New York-based startup, founded in 2022, whose software auto-generates production-grade software development kits from an API spec. The reported price was over $300 million. Within the same announcement, Anthropic confirmed it would wind down all hosted Stainless products, including the SDK generator that OpenAI, Google, Cloudflare, Replicate, and Runway had been paying for.

That's a strange combination: buy a company for $300M, then shut off the product your competitors were using. It's also a completely logical one. And if you are a solo operator with SDKs, CI/CD pipelines, or backend integrations touching any of those platforms, the next 90 days just got more interesting.

What Stainless actually was

Most developers have interacted with Stainless's output without knowing it. The startup's core product took an OpenAPI specification and generated idiomatic, production-quality client libraries in TypeScript, Python, Go, Java, Kotlin, and Ruby. Not boilerplate scaffolding — actually good SDKs that felt native in each language, with proper typing, pagination handling, retry logic, and streaming support built in.

This was particularly valuable for AI companies building APIs that needed to maintain client libraries across six-plus languages simultaneously while iterating on their API surface every few weeks. Stainless automated the maintenance burden. It's why OpenAI's Python SDK, Anthropic's own TypeScript client, and Google's Gemini libraries could all stay current despite constant API churn.

The alternative — building and maintaining those SDKs by hand — would cost a team of engineers and months of lag time on every API change.

The competitive geometry here is worth staring at

Anthropic was itself a Stainless customer. So was OpenAI. So was Google. Cloudflare. Replicate. Runway. Anthropic just bought the infrastructure that its three largest AI competitors depend on to distribute their developer tooling.

The $300M acquisition effectively gives Anthropic two things. First, a team that knows how to build and maintain high-quality, multi-language SDK infrastructure — useful for Anthropic's own growing API surface. Second, the ability to decide what the future of that infrastructure looks like for everyone else.

By winding down the hosted product, Anthropic has made a choice: the SDK generator is no longer a neutral service for the industry. It becomes internal tooling. OpenAI and Google aren't exactly going to license it from Anthropic.

Anthropic was careful to say that existing customers still own their generated SDKs and can modify them freely. That's a real protection. But the SDK generator — the thing that kept those libraries current and regenerated them on every API update — is going away.

What actually changes for you

If you are a solo operator, the direct blast radius depends on where you sit in the stack.

You're building on Anthropic's API. Nothing changes immediately. Anthropic's own SDK is now in-house and will get better, not worse. The team that built the tooling is now Anthropic's team.

You're building on OpenAI's API. OpenAI's Python and TypeScript SDKs were generated by Stainless. Those SDKs exist; you own them if you're using them; they will continue to work. The question is what OpenAI does for maintenance going forward. They'll need to either build internal SDK infrastructure or find another approach. Expect some SDK lag or quality inconsistency over the next 6–12 months while they sort that out.

You're building on Cloudflare or Replicate APIs. Same situation. These companies used Stainless to generate clients they were distributing to developers. That distribution continues with existing SDKs, but new API surface or new languages will require them to solve the maintenance problem themselves.

You were using Stainless directly — building your own API and using Stainless to generate your client libraries. You still own what you've generated. But the regeneration workflow is going away. You'll need to either manage SDK updates by hand or migrate to an open-source alternative like Speakeasy or Fern, which offer similar OpenAPI-to-SDK generation.

The honest counter-take

It's possible I'm reading too much intent into what is partly an acqui-hire. Anthropic needed SDK engineering talent and Stainless had the best team for it. The $300M may be as much about the people as the strategic positioning.

It's also possible that OpenAI and Google have enough in-house capability to absorb the SDK maintenance burden without much disruption. Google has thousands of SDK engineers. OpenAI's developer platform team isn't small. The companies most at risk from this move are the smaller API-first startups — Replicate, Runway, and similar — that relied on Stainless precisely because they couldn't staff a dedicated SDK team.

And there's a version of this where Anthropic keeps some form of the SDK generator alive for external use, either open-sourced or as an enterprise product. They've said nothing about open-sourcing it, but they also haven't explicitly ruled it out.

What I'd actually do if I were running an API-dependent product today

First: pin your SDK versions. Whatever version of the OpenAI, Cloudflare, or Replicate SDK you're running that works — lock it in package.json or requirements.txt so an upstream breaking change doesn't hit you automatically. This is basic hygiene but surprisingly many automated setups don't do it.

Second: look at open-source alternatives. Speakeasy and Fern both do OpenAPI-to-SDK generation and are actively maintained. If you were a direct Stainless customer, migrating to one of these is the cleanest path forward. Both have free tiers suitable for solo operators.

Third: watch the GitHub commit history on the SDK you depend on. OpenAI's Python SDK, for example — if commits slow down or the versioning pattern changes, that's a signal that the internal maintenance workflow changed.

The platform risk here isn't dramatic or immediate. But it's real, and it's the kind of thing that becomes obvious six months later when you're chasing a bug introduced by an out-of-date client library that nobody was maintaining.

Sources

• Anthropic has acquired the dev tools startup used by OpenAI, Google, and Cloudflare — TechCrunch
• Anthropic acquires Stainless — Anthropic blog
• Anthropic Stainless Acquisition: $300M+ Developer Tools Deal — EntrepreneurLoop

Fact-check log

• "reported price was over $300 million" → verified (The Information reported $300M+; TechCrunch confirmed; Anthropic did not disclose terms) (source: https://entrepreneurloop.com/anthropic-stainless-acquisition-300m-developer-tools-deal/)
• "founded in 2022" → verified (source: https://techcrunch.com/2026/05/18/anthropic-has-acquired-the-dev-tools-startup-used-by-openai-google-and-cloudflare/)
• "winding down all hosted Stainless products, including its SDK generator" → verified (source: https://techcrunch.com/2026/05/18/anthropic-has-acquired-the-dev-tools-startup-used-by-openai-google-and-cloudflare/)
• "Stainless customers will still own the SDKs they've generated to date and have full rights to modify and extend them" → verified (source: Anthropic spokesperson quoted in TechCrunch)
• "supported TypeScript, Python, Go, Java, Kotlin, Ruby" → verified (source: https://www.anthropic.com/news/anthropic-acquires-stainless)
• "OpenAI, Google, Cloudflare, Replicate, Runway were customers" → verified (source: TechCrunch)
• Speakeasy and Fern as alternatives → accurate as of knowledge; hedged as "actively maintained" rather than citing specific version or funding numbers Run: 2026-05-19 06:00

Voice-check log

• Removed two instances of "it's worth noting" from draft
• Added "I" voice in "What I'd actually do" section — personal angle present
• Checked for title-case H2s — all sentence case ✓
• No LLM-tell phrases detected
• Counter-take section present ✓
• Concrete recommendation in closing ✓ Run: 2026-05-19 06:00