Which team, project or client is driving this spend?
Showback: attribute your spend to the business units that actually own it, using the tags already on your resources — across every cloud account and provider on the platform, not just one.
How it works
What the Allocation tab shows.
One group, every cloud
Create named groups — a team, a project, a client — and, for each provider you use, the tag that identifies that group's resources there. A single group can span AWS, DigitalOcean, Cloudflare and every other connected account at once, so one project's real cost rolls up from wherever it actually runs.
Coverage score
The share of total spend — across all accounts and providers — confidently attributed to a group, versus what's left over. A low score means your tagging has gaps worth closing.
Unallocated vs. untagged
"Unallocated" is spend matching no group yet — usually fixed with a new or wider group rule. Within that, spend with no cost-allocation tags at all is called out separately, per provider, as "untagged" — that share needs the resources themselves tagged, not just a new rule.
"Unallocated" vs. "untagged"
| Unallocated | Untagged | |
|---|---|---|
| Meaning | Spend that matched no group rule | Spend with no cost-allocation tags at all — a subset of Unallocated |
| The fix | Add or widen a group rule to catch it | Tag the underlying resources — no rule can claim what isn't tagged |