Open source must be more than a word

Vercel’s relationship with open source is not a marketing line; it is the foundation of the company’s engineering practice. The stated goal is to build durable commercial products that fund continued open source development — not to sell open source itself. The team’s position is that better default software benefits everyone, whether they are Vercel customers or not. "A rising tide lifts all boats," as the company puts it.

That principle has been tested by Vercel’s own success with Next.js. Building a framework and managed infrastructure together produces an excellent developer experience and broad adoption. But coupling a project tightly to one platform inevitably raises questions about openness and control — even when that coupling is accidental rather than deliberate. Vercel is now responding with an explicit "Open SDK" strategy that defines how its frameworks and tools should behave.

Three commitments

The strategy rests on three commitments the company is asking the community to hold it to:

  • Open by default: Frameworks, SDKs, and tools are built in the open wherever possible, defaulting to the most permissive open source licenses.
  • Loose coupling, high cohesion: Projects should work exceptionally well on Vercel without creating lock-in. The commitment is to tools that are open, portable, and usable on any platform.
  • Innovation, then generalization: Development happens first on Vercel for fast iteration, but once a project matures, the team will invest in making it deployable anywhere.

The logic behind the last point is straightforward: if Vercel delivers great experiences first and removes the lock-in later, customers stay because they choose to, not because they are trapped.

A strategy shaped by real decisions

This position did not emerge from theory. It follows from several concrete observations and product moves:

  • React’s ubiquity: Much of React’s appeal is that it is unopinionated about deployment. Portability is a feature, not a gap.
  • Next.js as a standalone choice: Developers want to run Next.js at full capacity on other managed platforms. Meeting that demand became a north star for the open strategy.
  • The AI SDK: Acquiring the ai npm package name came with an obligation the team says was non-negotiable: the SDK must be platform- and framework-agnostic.
  • Nuxt and NuxtLabs: Now that NuxtLabs has joined Vercel and core Nuxt and Nitro developers work inside the company, Vercel wants to be explicit about being the place open source creators want to build for the open web.

Where the strategy applies

This is not about any single project, and it does not necessarily apply to Vercel’s commercial products. Instead, the strategy is being applied across a growing family of libraries and frameworks, including:

  • Nuxt, bringing the same design principles to the Vue ecosystem.
  • Svelte, with flexible deployment options for high-performance apps.
  • Flags, a portable feature flag system that does not depend on any particular flag provider.
  • Plus Nitro, Turborepo, SWR, and others.

The operating thesis

The wider argument is that the best way to build the web’s future is to invest in open tools, giving developers freedom and confidence while continuing to raise the bar for what is possible without a single platform dependency. The company’s equation is simple: business follows quality, quality follows mission, and the mission is to build a better web for everyone.