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 heading Organize 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 heading Update 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 heading Easily track your sandboxes Filter sandboxes by any tag to quickly surface the ones that matter.…