Custom tags available in beta on Vercel Sandbox
By Steven Van ·
Vercel Sandbox now lets teams attach up to five key-value tags per sandbox to filter and manage them at scale, in beta.
Vercel Sandbox now supports custom tags in beta, letting teams attach up to five key-value pairs to each sandbox to categorise it by environment, team, or any other criteria. Tags can be set when a sandbox is created, changed later, and used to filter results when listing sandboxes.
Tags are set with Sandbox.create(), changed with sandbox.update() (which replaces the whole tag set, so every tag to keep must be passed again), and used to narrow Sandbox.list() results, one tag at a time. The Sandbox CLI mirrors this with a repeatable --tag key=value flag on sandbox create, sandbox config tags, and sandbox list.
Vercel points to three uses: tagging sandboxes by session, user, or agent run for AI workflows at scale; isolating and filtering sandboxes per customer in multi-tenant platforms; and attributing sandbox usage to specific teams for cost tracking. The beta requires upgrading to the beta Vercel Sandbox SDK and CLI packages.