Anthropic acquires Stainless

Original Article ↗ Hacker News Discussion ↗

What Stainless Was and What’s Changing

  • Stainless generated high-quality SDKs, CLIs, docs, MCP servers, Terraform providers, and release pipelines from OpenAPI specs, used by hundreds of companies (Anthropic, OpenAI, Cloudflare, etc.).
  • Following the acquisition, all hosted Stainless products are being wound down; new signups and new SDKs are no longer available.
  • Existing customers:
    • Keep full ownership and rights over already generated SDKs.
    • Are offered a “self-service” transition via a source-available codegen tool (stlc) for eligible customers, usable locally/CI.
    • Can contact a dedicated transition channel for details.

Impact on Customers and Ecosystem

  • Many users are disappointed or frustrated, calling the shutdown a loss for the ecosystem and a warning about relying on startups for core infra.
  • Some see the outcome as relatively benign since code and repos remain and a transition path exists; others describe it as a “rug pull” and future deterrent from similar SaaS tools.
  • Migration is non-trivial because generated SDKs are subtly vendor-specific; some vendors are already pitching migration services and discounts.

Motives and Strategy Behind the Acquisition

  • Widely viewed as an acquihire: Anthropic wants top-tier engineers and tighter control of platform tooling.
  • Several see a strategic angle in removing a shared vendor that also powered OpenAI’s official SDKs; others argue this is just normal competition, not clearly anti-competitive.
  • Some frame this as Anthropic following an “Apple-like” vertical integration play: owning more of the stack developers touch.

Lock-In, Walled Gardens, and Trust

  • Broader resentment toward Anthropic’s recent moves (Claude Code subscription restrictions, client lock-in, changing limits) colors reactions; many see a pattern of increasing walled-garden behavior.
  • Others counter that lock-in is an expected tradeoff for heavily subsidized plans and that APIs remain open for those who want freedom and are willing to pay.

Alternatives and Open Source

  • Mentioned alternatives: Fern (frequently praised), APIMatic, open-source tools (OpenAPI generators, Microsoft TypeSpec), internal pipelines (e.g., WorkOS, large companies’ in-house stacks), and potential future OSS releases.
  • Debate over whether such infrastructure should have been open source from the start versus VC-backed SaaS.

AI Hype, Talent, and Acquisitions

  • Several point out the irony: if LLMs can replace SWE work, why buy a non-AI codegen company and other dev tools (e.g., Bun) instead of “just vibecoding” replacements?
  • One view: acquisitions are the most effective way to identify and hire “founder-level” engineers; another view: success as a startup founder is a poor proxy for being the “world’s best” engineer.
  • Underlying skepticism about AGI narratives and the sustainability of capital-fueled consolidation runs throughout the thread.