Cloudflare Releases Vinext 1.0: Running Next.js Apps on Vite for Portable Deployment

What happened

On September 28, 2026, Cloudflare announced the release of Vinext 1.0 on its official blog, in a post written by James Anderson and Matt “TK” Taylor. Next.js is a framework, a ready-made toolkit developers use to build web applications. Vite is a separate tool for building and running web projects. According to Cloudflare, Vinext launched in February as a week-long, AI-driven experiment to test how far a single engineer could go in reproducing the Next.js framework on top of Vite.

Cloudflare says that over the seven months since then, Vinext has become a framework its customers use in production, meaning on live websites, for high-traffic dynamic applications. The company says version 1.0 brings major improvements in compatibility, stability and caching behavior.

Read the full description

Sources are collected, independently checked, then reviewed by Jev.

What Vinext 1.0 includes

According to Cloudflare, Vinext 1.0 focuses on the features customers need most, rather than fully replicating every recent Next.js feature. Next.js offers two ways of organizing an app's pages, called the App Router and the Pages Router. Cloudflare says many customers still rely on the older Pages Router.

• Routing support: supports the App Router, the Pages Router and hybrid applications, including React Server Components, Server Actions, API routes, route handlers, middleware and client-side navigation.
• Page lifecycle: routes from both routers can be pre-rendered at build time, meaning pages are generated in advance rather than when a visitor asks for them. Responses can be served via page-level ISR (Incremental Static Regeneration, which refreshes pre-built pages in the background) and invalidated by path or tag. output: "export" is supported for fully static sites.
• Observability: provides Next.js-compatible tracing, a way of following requests to diagnose problems, so existing OpenTelemetry and Sentry setups keep working.
• Ecosystem compatibility: implements the public next/* interfaces, supporting common use cases such as authentication, MDX, image optimization, fonts, metadata and environment variables.
• Migration: Cloudflare says only two commands, npx vinext check and npx vinext init, are needed, and the existing project structure is preserved.

Cache warming: moving pre-rendering out of the build

In its announcement, Cloudflare proposes a “cache warming” approach, which fills the cache (stored copies of pages) before visitors arrive. It moves page pre-rendering from build machines to the Cloudflare network. According to the company, a deployment uploads a new Worker version and deploys it at 0% of production traffic, then requests pages from that version. The deployment is promoted only after the cache has been populated. Cloudflare says Vinext can also identify high-traffic pages and add them to the pre-render list.

For sites with a large number of URLs, Cloudflare argues that the build step cannot tell which pages get heavy traffic, so rendering every page may waste a lot of time. In its view, warming the cache on the network before deployment lets the site respond quickly from cache as soon as it goes live. This effect is Cloudflare's claim, and no independent test data is currently available.

What it means for general readers and development teams

Next.js is a widely used web application framework. Vinext aims to keep such applications from being tied to a single deployment platform. General users usually won't notice this kind of change directly, but it may affect the hosting choices and launch speed behind the websites they use.

Development teams should note the limitation Cloudflare itself points out. Next.js 16 treats Cache Components as an important part of the framework's future, while Vinext currently offers only limited support for the “use cache” directive that drives them. Projects that depend on this feature should take particular care.

Browse the latest news in this topic

• Tech news