ISR PRICING REALITY

Incremental Static Regeneration on Vercel is excellent technology with a real cost curve at scale. The pricing model is per-invocation: each ISR write event has a cost, and the cost compounds with the number of pages and the frequency of revalidation.

On Deluxe Astrology, with roughly 91,000 pages across 30 languages and aggressive revalidation, we hit a multi-million-event ISR billing month in March 2026. The bill was meaningful enough that we changed how we deploy.

Two main drivers: total page count and merge frequency. Each merge to main triggers ISR revalidation across affected pages. With 91K pages and a global content model where most merges affect most pages, a single merge fires roughly six million ISR write events.

The math is brutal at scale. Two merges per day across 91K pages with global affinity equals 360 million events per month. The Vercel ISR pricing tier kicks in well before that.

After the second ISR billing incident in May 2026, we set a hard rule on Deluxe Astrology: two production merges per week, no exceptions outside P0. The cost driver is merge frequency, not route configs, so the lever is operational discipline rather than architectural changes.

Two merges per week, six million events per merge, equals 48 million events per month. Manageable at the tier we run. More importantly, it forces us to batch related changes rather than ship continuously, which has a side benefit of reducing regression frequency.

If the merge-budget approach is not viable, three alternatives:

Move to full SSG with scheduled rebuilds. Build all 91K pages once per day, serve as static. Cost predictable, content fresh within 24 hours. We did not pick this because content updates faster than that on certain endpoints.

Move to a different host with predictable ISR pricing. Cloudflare Pages and Netlify both have models that scale more linearly with usage. The DX is less polished than Vercel but the cost certainty is real.

Reduce the indexable surface. Many programmatic-SEO sites have an indexable surface 2x larger than necessary. A quality gate that drops 30 percent of pages cuts ISR cost proportionally.

For sites under 10,000 pages with moderate revalidation needs, ISR on Vercel is excellent and the cost is small. The pricing curve only bites at six-figure page counts with high merge frequency. Most projects never hit that ceiling.

Plan for the cost if you are scaling toward 50K+ pages. Run the math on expected merge frequency and revalidation cadence. Budget for at least 2x the entry-tier estimate at any scale where ISR is in heavy use.