proomt

Search

Search posts, papers, and topics

All posts

VercelMehul Kar1 min readrelease notesintro

Deployments now show billable duration and CPU minutes

Read on vercel.com

Summary

Vercel added billable duration and CPU‑minutes metrics to deployment views (dashboard, `vc inspect`, and REST API). Billable duration = build + post‑build time rounded up to the next minute; CPU minutes = billable duration × vCPU count. CLI v59.23.1+ shows a breakdown (e.g., 5m 9s build, 3m 21s post‑build → 9 min billable → 270 CPU‑minutes on a 30 vCPU machine).

  • Deployments now expose usage‑related metrics (billable minutes, CPU minutes) in UI, CLI, and API.
  • Billable duration is the sum of build and post‑build time, rounded up to whole minutes.
  • CPU minutes are calculated as billable minutes multiplied by the machine’s vCPU count.
  • Upgrade the Vercel CLI to ≥ 59.23.1 and run `vc inspect <deployment>` to see the breakdown.

Understanding per‑deployment resource consumption helps teams control costs and optimize build pipelines, especially when scaling across many deployments or high‑vCPU build machines.

3/10
devopsobservabilityperformance

Related reading

  4. Secure Compute and Static IP builds start 64% faster

    Vercel’s Secure Compute and Static IP builds now start 64% faster by using prewarmed containers, cutting the time from deployment creation to build start from 6.7 s to 2.4 s. The change is automatic and requires no user action.

    Vercelvercel.com1 minrelease

  6. How Factory scaled its cloud backend to one billion monthly requests on Vercel

    Factory runs its entire SaaS backend on a single Next.js app deployed to Vercel, handling about a billion API requests per day with 350 ms p95 latency. They achieve this with Vercel’s Fluid compute to avoid cold starts, built‑in observability and WAF for security, and internal automation (“Droids”) that let non‑engineers deploy tools without extra infrastructure.

    Vercelvercel.com4 min