As 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 customer

Tags 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:

const sandbox = await Sandbox.create({
  name: "my-sandbox",
  tags: { env: "staging" },
});

Link to headingUpdate tags as context changes

Promote a sandbox from staging to production, reassign ownership, or mark it for cleanup without recreating it:

await sandbox.update({
  tags: { env: "production", team: "infra" },
});

Link to headingEasily track your sandboxes

Filter sandboxes by any tag to quickly surface the ones that matter. This is useful for dashboards, cleanup scripts, or routing logic that needs to find all sandboxes matching a specific environment or team:

const productionSandboxes = await Sandbox.list({
  tags: { env: "production" },
});
console.log(
  "Production sandboxes:",
  productionSandboxes.sandboxes.map((s) => s.name),
); // my-sandbox

Link to headingUse Cases

• AI agents at scale: Tag sandboxes by session, user, or agent run to track which execution environment belongs to which workflow.

• Multi-tenant platforms: Isolate and filter sandboxes per customer or workspace, making billing attribution and cleanup straightforward.

• Team-level visibility: Attribute sandbox usage to specific teams for cost tracking or capacity planning.

This feature is in beta and requires upgrading to the beta SDK and CLI packages. Learn more in the documentation.