Cloudflare Rebuilt Next.js for $1,100. Every Dependency You Trust Is Now Negotiable.

$1,100.

Yeah, that's what it cost Dane Knecht to clone Next.js. One weekend. One guy pointing Claude at the API surface. No team. No planning committee.

Just a weekend and a budget that wouldn't cover two hours of most dev shops' burn rate.

Eight thousand GitHub stars later.

Fifty contributors. 1,700 unit tests. 380 E2E tests. All machine-generated. Production apps built on it render four times faster and ship 57% smaller bundles than the original.

Your subscription tool vendor has no idea their moat just dissolved.

Here's the Stat That's Haunting Me

Greg Brockman told Sequoia that AI coding tools went from 20% to 80% of all code in one month.

One. Andrej Karpathy said he hasn't written a line of code by hand since December. Let that sit.

The industry is framing this like it's a win. I kinda disagree. 80% of code written by AI means 80% of code written by something that doesn't understand your business, your users, your edge cases, or what happens when your Stripe webhook fires twice in the same second.

This isn't celebration material. It's a fire drill.

The Dependency Lock-In You Didn't Know You Signed

Yeah, every SaaS subscription you've got is now a rebuild candidate.

Your ORM. Your email service. That weird internal auth flow your team works around instead of through. The thing that makes you write raw SQL every time you need anything nontrivial.

It all just became possible to replace with something that costs less than your monthly AWS bill and runs in half the time.

Yeah, you don't have to do it today. That's not the point. The point is your vendor knows you couldn't before. They know that now.

That's already changing how renewal conversations go.

Side note: vinext still doesn't support the Pages Router fully.

If you're running a migration, watch that gap. The experiment is real but it's not done yet.

The Part Everyone Skips

Code. Tests. Docs. All AI.

The spec wasn't. Humans wrote what the app should do. AI figured out how to make it happen. That's the whole job now. Not typing. Directing.

I talk to shops every week that skip tests because they're "moving fast." Wrong direction.

Fast means you need tighter constraints, not looser ones. Garbage specs in, garbage code out. The agents are hungry. Feed them something specific.

Your Use Just Changed

The moat was never the code. Everyone knew that. The moat was "you can't afford to rebuild it." That argument is gone now.

When renewals hit, you now know the counter-offer is "we could rebuild this." Not as a threat.

As a fact. Use it accordingly.

Audit your package.json this week. Find the thing that grinds your gears most. Check if it has a clean API surface. That's your candidate. You don't have to pull the trigger. Just know you can.