Cloudflare released Vinext 1.0, a framework that lets a Next.js app run on Vite and prerender on Cloudflare's network instead of on the build machine

A Next.js build that prerenders 30,000 pages spends its whole CI budget on a machine that is not serving traffic. Cloudflare released Vinext 1.0 on 2026-09-28, and the release moves that prerender step off the build machine and onto Cloudflare's network. Vinext is a framework that runs a Next.js application on top of Vite, and it now covers enough of Next.js to be worth reading about even for teams who have never used Cloudflare.

Cloudflare says Vinext supports both routers, "App Router and Pages Router compatibility" including hybrid apps, plus React Server Components, Server Actions, API routes, route handlers and middleware. Cache Components using the use cache directive has "limited support"; the company says most surveyed teams did not use it and did not need it to migrate. Cloudflare frames the graduation as "Vinext has grown into a framework that our customers trust and run in production for high-traffic, dynamic applications", and reports "over 99% test compatibility for most customer-requested features across both routing systems".

Cache warming, in place of build-time prerender

The 1.0 headline is cache warming. Instead of rendering every static route on the build machine, Vinext deploys a new Worker version, points it at 0% of production traffic, then requests those pages against the new version so the render happens on Cloudflare's network before the version is promoted to real users. A page that no visitor ever asks for is never rendered. The build finishes without the render step, and the render cost is paid per page, on Cloudflare's servers.

Two things follow from that. Build times stop scaling with the number of prerendered pages, which for a big content site is the largest single line in CI. And a page can be updated on demand without a redeploy, through Vinext's ISR support, which the launch post lists as "ISR with background and on-demand revalidation" and cache invalidation through Cloudflare Workers Cache.

The migration and where it runs

Vinext provides two commands for a Next.js project: npx vinext check inspects the app for anything Vinext does not yet support, and npx vinext init sets it up. Deployment targets include Cloudflare Workers, including the free plan, plus Netlify and AWS Lambda, so a team can adopt Vinext without moving off its current host. Cloudflare also lists OpenTelemetry and Sentry tracing as first-class, along with authentication, MDX, image optimization, fonts, metadata and environment variables.

To hold that surface as Next.js keeps moving, Cloudflare runs the Next.js test suite against Vinext every night, and says an agent reviews the Next.js canary each morning against Vinext's implementation. Both are the company's own claims, not audited numbers.

The trade

A Next.js team facing long builds has three moves: cut what it prerenders, buy more build machines, or move the render step off the build. Vinext takes the third one and gives back Vite's dev server and hot module replacement as a side effect. The cost, for a team already deep in Cache Components, is Vinext's limited support for the use cache directive: worth checking against the actual app before running vinext check in anger.

Source

• Cloudflare: Next.js applications, powered by Vite: introducing Vinext 1.0, 2026-09-28.
• GitHub: cloudflare/vinext.