CostMonStart free

Cloud cost

Unallocated spend

The share of a bill that can't be attributed to a real owner, because it isn't tagged, its tag is wrong, or it structurally can't carry a tag at all.

Cloud cost

Last updated

Definition

Unallocated spend is the flip side of tag coverage: whatever dollar amount is left over once you subtract what's attributable to a team, project, or customer. It's driven by three separate gaps: spend that structurally can't carry a tag (egress, support, shared infrastructure, AI API spend with no resource to tag), spend that could be tagged but isn't, and spend that's tagged with the wrong value entirely.

Treating unallocated spend as its own tracked number, rather than folding it into an undifferentiated "Other" line, is what makes it visible enough to shrink over time instead of growing unnoticed as the fleet does.

Where it shows up

Unallocated spend appears as whatever total is left in a cost report once every tagged, attributable dollar amount is subtracted out. It commonly surfaces as an Other or Untagged bucket in a cost allocation dashboard, sitting alongside the named team- and project-level totals it couldn't be sorted into.

What makes it expensive

Folded into an undifferentiated Other line, unallocated spend stops being a number anyone owns or answers for. It then grows quietly alongside the fleet, and no report ever calls that out. Give it its own row and its own trend line. A number with nobody's name against it is the one that grows.

A total nobody owns, nobody fixes.

An unattributed cost stays unowned. CostMon assigns spend to an owner, so someone can act on it.

Esc