Spend Map
See every cloud dollar, and who it belongs to.
Spend Map brings AWS, Azure and Google Cloud billing into one live view. Slice it by account, service, region, team, product, environment or customer, and drill from a monthly total down to a single resource in a few clicks.
What it does
Built for the engineers who make the change, and the finance team that checks it.
Multi-cloud in one model
AWS CUR, Azure cost exports and Google BigQuery billing export normalised into one schema, so EC2, Virtual Machines and Compute Engine sit side by side.
Tag coverage and fixes
A coverage score per account and team, with the exact untagged resources listed so owners can fix them at the source.
Allocation rules
Where tags are missing, rules assign spend by account, resource group, project, naming pattern or Kubernetes label.
Kubernetes cost
EKS, AKS and GKE cost by cluster, namespace, deployment and label, including idle node capacity.
Finance-ready views
Unblended, amortised and net views, with credits, refunds and marketplace charges shown separately.
Unit costs
Cost per customer, per transaction or per thousand API calls when you send a simple daily business metric.
How it works
Spend Map, step by step.
Good to know
- Drill from total spend to a single resource ID
- Compare any two periods by day, week or month
- Daily refresh with cost data typically under 12 hours old
- Export any view to CSV for finance
- 01
Billing exports are read
We read the detailed billing export for each connected account, subscription and project, refreshed several times a day.
- 02
Costs are normalised
Services, regions and pricing models are mapped into one model, so a dollar on AWS compares cleanly with a dollar on Google Cloud.
- 03
Ownership is applied
Your tags come first. Allocation rules fill the gaps, and anything still unowned is listed as untagged spend.
- 04
Views are shared
Save views for each team, product or customer and share them with a link, or schedule them to email weekly.
Questions
About Spend Map
Do we need perfect tagging first?
No. Spend Map works with the tags you have today and shows the untagged share. Allocation rules cover most gaps while teams improve tagging.
Which billing data do you read?
AWS Cost and Usage Reports, Azure cost management exports and the Google Cloud billing export to BigQuery. No application data is read.
Find your savings free.
Read-only connection · First report usually within a day · No card needed for the report