Vercel Broadens Stewardship with NuxtLabs

This deal turns Vercel from the company behind the default React deployment path into a broader framework owner with influence over how modern full stack JavaScript is built across both React and Vue. Nuxt gives Vercel a second developer funnel, while Nitro gives it deeper control over the server layer that actually runs APIs, rendering, and AI workloads, which matters because infrastructure revenue starts where frameworks become production traffic.1 2 3 4

• NuxtLabs joined Vercel on July 8, 2025. The team behind Nuxt and Nitro moved under Vercel, and Vercel said both projects would stay open source. That keeps the community trust of MIT licensed tools while shifting full time framework maintenance onto a company with much larger resources.1 2 3
• Nuxt is not a side project. The package is seeing about 1.1M weekly npm downloads today, which makes this a meaningful foothold in the Vue ecosystem. In practice, this means Vercel can now shape the default build and deployment path for a large group of developers who were not starting from Next.js.3 4
• The more strategic asset may be Nitro. Nuxt describes Nitro as a runtime built to run consistently across frameworks and platforms. That gives Vercel a way to matter below the UI layer, where server rendering, APIs, and agent backends run, instead of depending only on Next.js winning the framework war.1 2

Going forward, this points to Vercel building around shared runtime and deployment primitives, not just one framework. If Next.js brought React teams onto Vercel, Nuxt and Nitro can do the same for Vue teams and multi framework workloads, expanding Vercel from a framework specific hosting company into a broader application cloud for AI era web apps.1 2 4