Your Next.js App Is A Hostage Situation. Ransom Monthly.

Your Next.js app is a hostage situation with Vercel. The framework was supposed to simplify your stack — it became your most expensive dependency.

Railway migrated 200 routes off Next.js and their build dropped from 10 minutes to under 2. Vercel will bill you for every pixel. A single badly cached og-image route cost a portfolio company $4,200 in one week. No cap. No mercy.

The Bait: Next.js is the React Framework

One click deploy, edge runtime, image optimization, server components. The pitch is irresistible.

The Vulnerability: Edge is Not Portable

Your edge runtime is Vercel's runtime. Your middleware, your image optimization, your ISR revalidation — all coupled to one provider's pricing table.

The Exploit: Image Optimization is a Bill Line

next/image without proper caching headers becomes a meter. Every pixel rendered on demand, every og-image regenerated — all billed.

The Collateral: Your CFO Gets a Shock

Builds that took 10 minutes now take 2. Bills that were predictable now scale with traffic you don't control.

The Patch: Cloudflare Absorbs It For Free — Or Self-Host

• Cache og-image aggressively (Cache-Control: public, s-maxage=86400)
• Move image optimization to Cloudflare or self-hosted sharp
• Audit your edge function invocations

Tactical Debrief

• Audit your Vercel invoice this week
• Check your build times before and after
• If you're locked, plan the exit: static export + Cloudflare Pages

Engagement: Have you been billed for pixels you didn't know you shipped? Drop your ransom amount in the comments — I read every reply and answer the sharpest ones.

Based on ERR.SYS video essay daily tech rage.