Intel / article

Vercel Sandbox now supports memory observability

Source: vercel.com
Author: Tom Lienard
Date: Published Sep 25, 2026

Context

Vercel added memory usage to the observability data for Vercel , a service that runs untrusted or -generated code in isolated Linux virtual machines (Sandbox documentation). On a sandbox's detail page, charts scale to that sandbox's memory limit and draw a dashed line at 85% of it, showing how close it runs to its ceiling. Overview pages add average, P75 and P95 memory (typical and near-worst-case usage) beside the existing CPU and data transfer figures. Release details.

The same data is available as the memoryUsedBytes measure in custom observability queries, where an alert can be created from a chart, and through the vercel metrics command, either for one linked project or across a team with the all flag. Memory usage can therefore be monitored the way other sandbox metrics already are.

Key takeaways · AI-distilled

The new Memory Usage card reports average, P75 and P95 sandbox memory next to the existing CPU and data transfer metrics, at sandbox, project and team level.
Sandbox detail charts scale the y-axis to that sandbox's memory limit and draw a dashed reference line at 85% of the limit, so headroom before an out-of-memory failure is visible at a glance.
Memory is exposed as the memoryUsedBytes measure in the Observability query builder, where you can build custom queries and alerts, and via `vercel metrics` as vercel.sandbox.memory_used_bytes (add --all for team-wide data).

Terms in this piece · Glossary

sandbox — An isolated environment where AI-generated code or agent actions run without being able to touch anything real.
AI agent — An AI system that doesn't just answer once but works toward a goal in a loop — taking actions, reading the results, and deciding what to do next.

Read the source vercel.com