Cloudflare announced the release of ViNext, an experimental framework that reimplements the Next.js API surface directly on top of Vite. A company engineer, with the help of an artificial intelligence model, rebuilt the project in just one week, between February 13 and 20, 2026. The result offers production builds up to 4.4 times faster and customer bundles up to 57% smaller compared to Next.js 16.1.6 with Turbopack. ViNext allows direct deployment on Cloudflare Workers with a single command and is already used in production by some teams.
The project appears as a solution to limitations of deploying Next.js in varied serverless environments. Diferente of adapters like OpenNext, which modify the output of the original build, ViNext rebuilds essential functionality such as file-based routing, server-side rendering, React Server Components, server actions, caching, and middleware. Essa approach uses Vite as a base, a tool adopted by frameworks such as Astro, SvelteKit, Nuxt and Remix. Compatibility covers both App Router and Pages Router, allowing app/ and pages/ directories to work without significant changes.
AI-accelerated development
The creation process involved around 800 sessions with the Claude model of Anthropic. The total cost in API tokens was around $1,100. The engineer defined the initial architecture in a few hours and guided the model to generate the code iteratively. Essa strategy demonstrates how current AI tools can handle complex systems when there is clear documentation, robust testing, and a solid technical foundation like Vite.
ViNext achieved 94% coverage of the Next.js 16 API. Benchmarks public meetings held in CI on GitHub confirm performance improvements. Sites in production, like National Design Studio at cio.gov, have already adopted the framework and report gains in build time and bundle size.
Technical advantages and integration with Cloudflare
ViNext offers simple commands for developers. Após install via npm install vinext, it is possible to run vinext dev for development with hot module replacement, vinext build for production and vinext deploy for automatic deployment on Cloudflare Workers. Native integration with platform services includes KV support for caching in Incremental Static Regeneration (ISR). Desenvolvedores configure custom handlers for caching, with the possibility of future use of the R2 or Cache API.
The cache layer is pluggable, which increases flexibility. Aplicações directly access Durable Objects, KV and AI bindings without workarounds, both in development and production environments in the workerd runtime. The deployment generates automatic configuration of the Worker, simplifying the process compared to traditional solutions.
Benchmarks and performance comparisons
Tests show production build in 1.67 seconds with Vite 8 and Rolldown, versus 7.38 seconds on Next.js with Turbopack. The gzipped client bundle drops from 168.9 KB to 72.9 KB, a 57% reduction. Esses numbers are derived from public and repeatable methodologies. The project plans to evolve with Rolldown in future versions for additional gains.
ViNext supports experimental Traffic-aware Pre-Rendering, which pre-renders only pages with real traffic based on Cloudflare analytics. In one example, 184 pages covered 90% of traffic and pre-rendered in 8.3 seconds when using vinext deploy –experimental-tpr.
Current project limitations
ViNext remains in the experimental stage. Pré-full static rendering at build time is not yet available. Sites 100% statics can find more suitable options in frameworks like Astro. Apesar due to high test coverage, the team recommends caution in large-scale applications until further validation in production.
The community can contribute to the open-source repository. The project encourages proofs of concept on other platforms, such as Vercel, demonstrating runtime-agnostic potential thanks to the Vite Environment API.
Migration and practical examples
An agent-assisted migration tool makes it easy to transition existing Next.js projects. Desenvolvedores add the skill via npx skills add cloudflare/vinext and use commands in compatible editors to automatically convert. Exemplos live shows applications running without manual adaptations.
ViNext strengthens integration with the Cloudflare ecosystem. Aplicações explore native platform features without restrictions imposed by specific toolchains.