A small acquisition with a big signal
Anthropic recently acquired Stainless, the company that built the developer SDKs for the OpenAI API, Cloudflare, Merge, and others. On the surface it looks like a tidy bolt-on. Read it more carefully and it is a signal about where the competition is actually heading.
For the past couple of years, we have treated model choice as the defining architectural decision. Which model is smartest, cheapest, fastest. But models are converging in capability and getting easier to swap. The thing that is getting harder to swap, and therefore more strategically valuable, is the developer experience layer: the SDKs, the integration patterns, the surface your team actually builds against.
The model is not the moat anymore. The DX layer is.
Why integration choice outlasts model choice
Here is the implication for anyone building, and it is sharper than it first sounds:
- The SDK you pick today defines your ecosystem for years. It shapes how you structure calls, handle errors, manage auth, and think about the provider's primitives.
- "Switch the model" is getting easier. "Switch the integration" rarely is. Swapping a model id is a config change. Re-plumbing every call site, retraining your team, and re-validating behavior across a different SDK is a project.
- Whoever owns your developer interface shapes your roadmap. The abstractions you build on quietly decide what is cheap to do next and what is expensive.
The decision you are making without noticing
Most teams chose their AI SDK because it shipped first and felt clean, not because of a deliberate long-term call. That was a reasonable way to move fast a year ago. It is worth revisiting now, because that early convenience has hardened into a foundation.
The practical move is an honest audit. Look at your stack and ask: which AI lab is quietly becoming part of your foundation through its SDK, and is that intentional? If a single provider owns your developer interface, your error handling, and your integration patterns, you have made a long-term commitment whether you meant to or not.
This is also a design opportunity. If you build a thin abstraction between your application and the provider SDK, you keep the option to switch later. That layer costs a little upfront and buys you strategic flexibility when the landscape shifts again, which it will.
The takeaway
We spent a year treating model selection as the big architectural decision. The next year is going to be about integration choice. The DX layer is where lock-in lives now, and it deserves the same deliberate thought you once reserved for picking a model.
We're here to help founders and teams design and build digital products that are built to scale with you, not slow you down. If you're looking to build something on a foundation you control, get in contact with us today.
So here is the question for your team: is your SDK choice a long-term commitment you have consciously made, or just whoever shipped the cleanest interface first?