Vercel Hobby serverless function invocation quota for ISR revalidation

Question

A low-traffic Next.js application on the Vercel Hobby plan uses Incremental Static Regeneration to update cached pages on demand. The goal is to determine whether ISR revalidation requests consume the same monthly serverless function invocation allowance as standard API routes and whether that usage can be bounded before automatic Pro plan billing applies.
Vercel documentation indicates that ISR revalidation executes serverless functions and counts toward invocation quotas, but it does not clearly state whether revalidation traffic is aggregated with standard function invocations or tracked under a separate meter. It is also unclear whether the Hobby plan provides a project-level invocation cap, spending alert, or opt-out from automatic upgrade when the free allowance is approached.
Assuming current Vercel Hobby plan limits and standard Next.js ISR behavior:

Does ISR revalidation draw from the same monthly serverless function invocation quota as standard invocations on the Hobby plan?
Is there a project or account setting to cap revalidation invocations or prevent automatic Pro plan billing when the allowance is nearly exhausted?
Can revalidation usage be isolated in usage metrics before it contributes to overage charges?

Tasadduq Burney · Answer

Confirmed Behavior
ISR revalidation does consume from the same monthly serverless function invocation quota as standard API routes on the Hobby plan. Vercel's Hobby tier provides 100,000 shared invocations per month across all serverless functions, including those triggered by ISR revalidation. These usages are aggregated into a single metric in the dashboard.

Limitation: No Isolation or Capping
There is no project-level setting to cap revalidation invocations or isolate them from standard function usage in billing metrics. The dashboard shows only a combined Serverless Functions usage value, making it impossible to determine how many invocations came from ISR revalidation versus API routes. Additionally, Vercel automatically upgrades accounts to Pro billing the moment the 100,000-invocation allowance is exhausted—there is no warning threshold or opt-out for this behavior.

Practical Steps to Control Usage

Monitor total invocations regularly in the Vercel dashboard's Usage section. Once you approach 100,000, you risk automatic Pro upgrade.
Implement client-side caching with appropriate Cache-Control headers to reduce on-demand revalidation triggers.
Use revalidate strategically in getStaticProps—set longer revalidate intervals for low-traffic pages to reduce invocation frequency.
Consider unstable_revalidate for manual control over when pages are refreshed, avoiding unnecessary revalidation on every request.

Important Caveat
Vercel's quota structure and billing policies may change. The current Hobby plan limits should be verified in the official pricing page and Terms of Service before making deployment decisions.

Vercel Hobby serverless function invocation quota for ISR revalidation

1 answer

Confirmed Behavior

Limitation: No Isolation or Capping

Practical Steps to Control Usage

Important Caveat

Your perspective belongs here.

0 question comments