StackSpendDocs

Tagging

Group costs across providers with custom labels. Tags let you slice spend by team, project, environment, or any dimension that matters to your business.

What tags are

Tags are custom labels you apply to cost line items. Each tag has a name and a colour. Unlike provider-level grouping (which is built in), tags let you create cross-provider groupings — for example, tagging AWS EC2, OpenAI, and Snowflake spend all as "ML infrastructure" so you can see a single total for that cost area.

Creating tags

Go to Settings → Tags and click Add tag. Give the tag a name (e.g. "Production", "Team: platform") and pick a colour. Tags are available immediately for use in rules and filters.

Auto-tagging rules

Auto-tagging rules apply tags to cost items automatically when they match a condition. You don't need to tag items manually — StackSpend applies the rule on every sync.

Rules can match on any of these dimensions:

DimensionExample
ProviderAll AWS spend → tag "Cloud"
AccountAccount ID 123456789 → tag "Production"
ServiceService name contains "EC2" → tag "Compute"
ProjectProject name contains "staging" → tag "Non-prod"

Rule priority

Rules are evaluated in order. When a cost item matches a rule, that rule fires and evaluation stops for that tag — a higher-priority rule winning prevents lower-priority rules from also firing. Drag rules in Settings to reorder them.

Manual tagging

You can apply or remove tags on individual cost line items from Data Explorer. Manual tags are preserved across syncs — they won't be overwritten by auto-tagging rules unless you explicitly clear them.

Using tags in analysis

Once items are tagged, use them in Data Explorer:

  • Filter by tag — show only items with a specific tag
  • Group by tag — see total spend per tag across all providers
  • Combine with other filters — e.g. tag = "Production" AND provider = AWS

Tags also appear in the Tasks filter list so you can view open alerts by tag.

Tip.Use tags for business-level groupings that cut across providers — "Production vs staging", "Team: data", "Project: new feature". Provider, account, and service groupings are already built in to every view; tags are for the layer above that.
Tagging — StackSpend Docs