Cloudflare had already shown a willingness to use Claude for code production through an open-source OAuth library mostly written with Claude. This report takes that pattern from a bounded library to a framework-compatible implementation aimed at reducing dependence on a competing platform.
The work also sits alongside Cloudflare’s later move toward open, TypeScript-oriented web tooling with its MIT-licensed EmDash CMS. Together, the coverage frames developer tooling as a strategic route to attracting workloads, not merely a product feature.
First-order effects
Cloudflare gains a reported Vite-based alternative covering 94% of the Next.js API, giving developers a potential path to retain familiar application interfaces while avoiding Vercel-specific dependence.
The reported $1,100 Claude-token bill makes the cost of AI-assisted framework reimplementation concrete: Claude supplied implementation capacity, while the engineer directed the project and validated compatibility.
Second-order effects
Vercel faces greater pressure to differentiate on managed services, reliability and its proprietary developer experience rather than on Next.js familiarity alone if compatible alternatives become usable.
AI coding-model providers gain a clearer enterprise-facing use case: accelerating compatibility layers and migrations that let infrastructure vendors challenge incumbent software ecosystems.
Third-order effects
If this pattern repeats, API compatibility could become cheaper and faster to reproduce, weakening framework lock-in and shifting competition toward hosting, deployment and integrated tooling.
The strategic value of inference access rises for cloud platforms: models able to generate and revise large codebases can become inputs to ecosystem expansion, though practical adoption will depend on compatibility quality and maintenance over time.
The trend: AI-assisted software development is lowering the cost of rebuilding familiar developer interfaces, making application-framework ecosystems more contestable for infrastructure platforms.
It's Next.js Liberation Day. The #1 request we kept hearing: help us run Next fast and secure, without the lock-in and the costs. So we did it. We kept the amazing DX of @nextjs, without the bespoke tooling, built on @vite. We're working with other providers to make deployment
A senior engineer at Cloudflare rebuilt 94% of Next.js with Claude Code in a week and spent about $1,100 in tokens. This touches on some recurring themes in my recent posts; super ICs, token costs and using the latest models. — They said this wouldn't have been possible just a…
This isn't really a Next.js story. It's an AI story. AI accelerates what @Cloudflare ships and what customers can do on our platform. We're an infrastructure company and we're going to be the best place for humans and AI to deploy. Infrastructure companies win this transition.
cloudflare ported Next.js to vite in a week for $1,100 I don't believe it, but excited to try. It's a drop-in replacement, let me know how it works on your app.
This is the most compelling AI rewrite story I've seen to date. Next.js, but rebuilt with Vite 1 engineer 800 @opencode sessions $1,100 in Claude tokens via API 4x faster builds 57% smaller bundles [image]
> a few days ago a Cloudflare engineer posted this > yesterday they announced they rebuilt Next.js using AI > now open source projects are removing their public test suites brand new world i guess [image]
Conceptually this is more interesting I think than the actual result. Next adds new features, and then this follows suit. Likely to eventually diverge. Call it Next call it Framework X I don't think it matters much. This is a concrete example of two things going on with AI.
We deployed this for https://cio.gov/ and has significantly improved core rendering stats: FCP: 396ms (vinext) vs 504ms (live) Eager JS: 85KB / 3 files vs 384KB / 16 files Who could have guessed gov sites could be running cutting edge software
Feels like Cloudflare also cannot resist the temptation of growth hacking. Their launch post states that vinext has been deployed to prod, and later in the post, they backpedal to admit it's not production-ready. Disappointingly disingenuous from Cloudflare [image]
He's crashing out because they're getting around vendor lock-in for the shit framework he started Vercel is such a clown company Migrate to Cloudflare [image]
My other takeaway from Cloudflare rewriting Next.js in Vite is that it was possible largely due to Next.js' comprehensive test suite, so for job security, it's best us software engineers band together and agree no more writing tests
Cloudflare: Huge tech post about their re-write Next to work with Vite, using AI, which gives crazy easy onboarding path for Next users to move to Cloudflare. Vercel: shares migrate guide with zero benefits on why you'd actually want to vercel outside of “vendor lockin”
We rebuilt Next.js in a week. No, really. The team ported the framework to run natively on Workers to prove what's possible with edge-first architecture. Dive into the technical hurdles we solved to eliminate Node.js dependencies. https://blog.cloudflare.com/ vinext/
What legacy web software should we rebuild on @Cloudflare Workers next to make faster and more secure? Post your requests! At $1,100 and a week's work each, we've got time and budget to do a bunch...
We've identified, responsibly disclosed, and confirmed 2 critical, 2 high, 2 medium, 1 low security vulnerabilities in Cloudflare's vibe-coded framework Vinext. We believe the security of the internet is the highest priority, especially in the age of AI. Vibe coding is a useful
I cannot stop thinking about the implications that Cloudflare / Vinext has on commercial open source, and in general, the cost of migrations, rewrites, and maintenance. One engineer, with AI, proved to be ~100x as efficient as before. This will have plenty of ripple effects
Due to how these bug bounty programs work, we're getting paid for the discoveries by Cloudflare / Matthew. Please reply with interesting AI and cybersecurity research teams or open source projects we should donate the funds to!