More granular observability for Vercel Sandbox
Vercel Sandbox now includes detailed resource metrics for compute and networking usage, with visibility across Active CPU, Provisioned Memory, Data Transfer, and session tracking. Users can monitor metrics in the dashboard grouped by sandbox name and session ID, query them via CLI, and attribute costs to specific workloads for better cost optimization.
observability now includes detailed resource metrics, giving you deeper visibility into how your sandboxes consume compute and networking.Vercel Sandbox
From the in your dashboard, you can now monitor:Observability tab
Each metric can be grouped by Sandbox Name and Sandbox Session ID, so you can drill down from aggregate usage to the individual sandbox responsible.
You can also query and visualize metrics via the Vercel CLI:
Metrics are available at both the team and project level and align directly with how , so you can attribute costs to specific workloads and catch unexpected usage early. This is useful for tracking agent workloads that create sandboxes at scale, right-sizing sandbox configurations based on actual utilization, and identifying sandboxes with unexpectedly high data transfer.Sandbox usage is billed
Observability for Sandbox is included on all plans, and manual are available on Pro and Enterprise plans. Learn more in the .queriesSandbox documentation
Measures when your code actively uses the CPU. Active CPU is measured in core-hours and time spent waiting on I/O, such as network requests or model calls, is not billedActive CPU and CPU usage:
Memory allocated to your sandboxes multiplied by runtime, measured in GB-hoursProvisioned Memory:
Total data transferred in and out of your sandboxes, including package downloads and API callsData Transfer:
How many sandboxes are running at any give time, and when sessions are stopped or startedRunning sandboxes and sessions:
Source: original entry ↗