Vercel Hobby serverless function invocation quota for ISR revalidation
0 reputation · 22 Apr 2024, 19:39 UTC
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?