Catch a Vercel traffic spike before it hits three meters at once

Cost anatomy

What actually drives your Vercel bill

Multiple separate metered line items

Fast Data Transfer (bandwidth), Function invocations and compute (Active CPU time plus provisioned memory GB-hours), Image Optimization, and build machine time each meter and bill independently. None of them share a cap with the others.

Image Optimization has three sub-meters

Image Optimization itself splits into transformations, cache reads, and cache writes, each with its own included allotment and overage rate.

ISR reads and writes bill separately

Incremental Static Regeneration meters reads and writes as two distinct line items, each with its own included quota and per-million overage price.

Build minutes, by CPU-minute

Build time bills per CPU-minute, rounded up, multiplied by the CPU count of the machine type chosen for the build. A heavier build machine costs more per minute even for an unchanged build.

A traffic spike hits several meters at once

A single viral moment can push Fast Data Transfer, Image Optimization, and ISR revalidations over their allotments simultaneously. None of them show up as one "bandwidth" number until the separate overages reconcile on the invoice.