Debate Grows Over Frontend Centralization

React's journey began at Facebook in 2011, created by engineer Jordan Walke to handle the platform's complex UI before being open-sourced in 2013. Next.js was introduced in 2016 by Guillermo Rauch's Vercel (then called Zeit) specifically to solve challenges like server-side rendering for the growing React ecosystem. The scale of this ecosystem is significant; by 2024, Vercel's annual revenue reached $100 million, and its platform now powers over 4 million websites for major companies including Apple, Walmart, and Netflix. As of early 2026, Next.js is used by 2.3% of all websites. Concerns over centralization grew after several key members of Meta's React core team joined Vercel in late 2021. This collaboration was pivotal in building React Server Components (RSCs), with the Next.js App Router being its first and primary production implementation, a fact now reflected in the official React documentation's recommendations. The technical side of the vendor lock-in argument centers on specific Next.js features like Middleware, which runs on Vercel's proprietary Edge Runtime, an environment with different APIs from standard Node.js. Similarly, features like Incremental Static Regeneration (ISR) and Image Optimization are deeply integrated with Vercel's infrastructure, making it complex to achieve the same performance on other hosting platforms without significant effort. Vercel counters these concerns by promoting its approach as "framework-defined infrastructure," arguing that developers write code for the framework, not for proprietary Vercel APIs. The company points to its own telemetry data, which suggests that approximately 70% of Next.js applications are deployed on infrastructure outside of Vercel, demonstrating the framework's portability.