CDN Request CPU Duration is the measurement of CPU processing time per CDN Request. CDN Requests of 10ms or less in duration do not incur any additional charges. CPU Duration is metered in increments of 10ms.

The number of read units to the Vercel Data Cache. Learn More

The number of times your team applied flag overrides. Learn More

The amount of time that your Deployments have spent being queued or building. Learn More

How many times a build was issued for one of your Deployments. Learn More

The number of checkBotId() calls that ran Deep Analysis. Basic validation and requests that do not call checkBotId() are not charged. Learn More

The number of times your Edge Functions received requests. Included in Compute Infrastructure: Function Invocations. Learn More

Billing units for Edge Functions: blocks of 50ms of CPU time. Learn More

The average time your Edge Functions have spent computing responses to requests. Learn More

The data transfer between Vercel's CDN to Vercel Compute. Learn More

The time saved by using local or remote cached artifacts. Learn More

The number of downloaded and uploaded artifacts. Learn More

The total size of all successfully downloaded and uploaded artifacts. Learn More

The amount of data that your Deployments have received or sent. Learn More

The number of requests your Deployments have received. Learn More

The number of times that a request to your Vercel Functions could not be served because the concurrency limit was hit. Learn More

The number of times your Vercel Functions received a request (does not include Cache Hits). Learn More

The number of Span Units used by Vercel Tracing. Learn More

The amount of storage used by deployments. Learn More

The amount of storage used by your OCI image repositories.

The number of times your Edge Middleware received a request. Learn More

The average time your Edge Middleware has spent computing responses to requests. Learn More

The volume of logs and events generated by your projects. Learn More

The total execution time of your Vercel Functions not running on Fluid. Learn More

The number of write units to the Vercel Data Cache. Learn More

The number of build CPU minutes consumed. Learn More

The number of AI Gateway trace events delivered to your drains. Learn More

The total CPU time of your Vercel Functions running on Fluid. Learn More

The number of build slots consumed by on-demand builds. Learn More

The number of billable build minutes consumed. Learn More

The amount of storage used by Vercel Functions of your deployments. Learn More

The number of application requests that read flag configuration. Learn More

The amount of data that Vercel Data Cache has received or sent for your projects.

The number of revalidations requests to the Vercel Data Cache.

The total provisioned memory duration of your Vercel Functions running on Fluid. Learn More

The number of times your cron jobs were invoked.