Tags
Cost-allocation labels for attributing usage and spend.
Studio → Settings → Tags defines the tag keys your organization uses to attribute usage — think AWS cost-allocation tags, not a general-purpose labeling system. Tags applied to a run show up on that usage in the Usage & Cost dashboard, so you can break down spend by client, team, or cost center.
Defining a tag key
A tag definition has:
- Key — lowercase letters, numbers, and underscores only (e.g.
cost_center,client_id). - Allowed values — an optional whitelist. Leave empty to allow any value for that key.
- Enforced — whether a value outside the allowed list is rejected rather than just accepted as-is.
Each definition's usage count reflects live usage data — how many recorded events actually carry that tag key — not a stored counter, so it's always current.
Enforcement is an Enterprise-plan feature
Outside the Enterprise plan, tags are always freeform and advisory — enforced and allowed values are accepted and stored, but nothing is actually rejected for not matching. On Enterprise,
an event tagged with a value outside an enforced key's allowed list is rejected.
Deleting a tag definition
Deleting a definition doesn't touch historical usage data — events already tagged with that key keep their tags; you just stop being able to enforce or manage that key going forward.