Test compatibility for most important customer-requested Next.js features (Cloudflare's own figure): Over 99% (Source: Cloudflare, Vinext 1.0 announcement (September 28, 2026))
Copying a framework is the easy part
Cloudflare released Vinext 1.0 on September 28. It is a tool that takes an existing Next.js application and makes it portable. The result can run on Cloudflare Workers, Netlify or AWS Lambda.
The idea to take from this is simple. AI can produce a first copy of a framework quickly. Proving that the copy behaves like the original takes far longer. Trust moves from the code to the test suite.
Cloudflare says Vinext began in February as a week-long experiment. One engineer and a large stack of AI tokens tried to rebuild Next.js on top of Vite, a popular build tool. Cloudflare calls the result "promising, but it was incomplete." Seven months of work followed. Cloudflare says customers now run Vinext in production for high-traffic, dynamic applications.
Scope matters here. Cloudflare says the figure covers "most important customer-requested features." It does not say every Next.js feature passes. Cloudflare also says Vinext has only limited support for "use cache," the directive behind Cache Components, which Next.js 16 promoted. In Cloudflare's account, most teams it spoke to did not use that feature.
Matching behavior is harder than matching names
Cloudflare is candid about where the difficulty lies. Writing a function with the same name as a Next.js one is simple. The hard part is making it change the right pages, cache entries and later requests in the same way.
Its answer is testing. Cloudflare describes thousands of focused tests. Every night it also points the official Next.js end-to-end tests at Vinext, which gives it a running view of compatibility and flags regressions quickly. Users of the open-source project found gaps the tests had missed, and Cloudflare credits that scrutiny for the progress.
AI agents now track the original every day
The more striking part is how the project is kept current. Cloudflare says Next.js canary, the early-release branch, receives new commits daily. An agent starts each day by reading those changes and pulling the diffs. It then files issues for anything that might touch Vinext.
When a test exposes a gap, Cloudflare says agents can find the change across both codebases. They build a reproduction, port the relevant tests and propose a fix. Human maintainers step in for the questions of how Next.js behavior should map onto Vite.
Cloudflare says this review has caught "unsafe caching behaviors." That is a useful admission. The cost of a faithful copy includes the risk that the copy behaves differently in places that matter.
Why this matters to a company running Next.js
Next.js is widely deployed. In WebPulse's September 2026 scan of the Tranco top 10,000 domains, a platform was detected on 2,491 sites. Next.js accounted for 791 of them. That is a sample of popular sites, not the whole web.
For those organizations, Vinext offers a way to change hosting without rewriting the application. Cloudflare says two commands check compatibility and set up the configuration. That could lower the cost of leaving a platform. It also creates a new dependency on a vendor's compatibility work.
Security patches are the sharpest question. NIST's vulnerability database lists 56 CVEs for Next.js, 32 of them in the last 12 months. One is in CISA's Known Exploited Vulnerabilities catalog. These figures describe Next.js, not Vinext. The Cloudflare post does not say how upstream security fixes reach Vinext, so that needs an answer from the vendor.
Questions to put to your team
Cloudflare is a hosting vendor with a stake in this project. The compatibility figures are its own and were not independently verified in the source. Treat them as a starting point for testing.
Ask your engineers which Next.js features your applications rely on. Check them against the compatibility matrix at vinext.dev. Ask whether you use Cache Components, since support there is limited.
Ask how a security fix in Next.js would reach a Vinext deployment, and how fast. Ask who owns that answer inside your organization and at the vendor. Ask whether your own tests can tell you when behavior drifts, especially around caching.
AI can draft a copy in a week. Months of testing are what make it something you can rely on.
Produced by the WebPulse Newsroom with AI assistance from the original reporting credited below, and checked against that source by our editorial review. How we use AI.
Original reporting: Cloudflare.





