Custom tags available in beta on Vercel Sandbox
Vercel has introduced custom tags in beta for its Sandbox environments, enabling users to organize and manage sandboxes at scale. Tags can be used to classify sandboxes by environment, team, or customer and can be updated as needs change. The feature supports filtering for operational use cases like monitoring, billing, and cleanup.
- ▪Custom tags allow users to organize Vercel Sandboxes by environment, team, or customer.
- ▪Tags can be updated dynamically without recreating the sandbox, such as when promoting from staging to production.
- ▪Users can filter sandboxes by tags for dashboards, cleanup scripts, or routing logic.
- ▪The custom tags feature is currently in beta and requires the beta SDK and CLI packages.
Opening excerpt (first ~120 words) tap to expand
1 min readCopy URLCopied to clipboard!Apr 30, 2026As teams scale isolated environments for AI agents, code generation, or dev workflows, keeping track of which sandbox belongs to whom, and why, becomes critical. Custom tags allow you to organize, filter, and manage Vercel Sandboxes at scale. Each sandbox supports up to five tags.Link to headingOrganize by environment, team, or customerTags are flexible by design. Use them to separate staging from production, attribute usage to specific teams, or isolate sandboxes per customer in multi-tenant platforms:1const sandbox = await Sandbox.create({2 name: "my-sandbox",3 tags: { env: "staging" },4});Link to headingUpdate tags as context changesPromote a sandbox from staging to production, reassign ownership, or mark it for cleanup without…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Vercel News.
Discussion
0 commentsMore from Vercel News
