Spend · AWS, Google Cloud and Azure
Understand every cloud cost.
Understand AWS, Google Cloud and Azure costs by team. Track budgets, investigate anomalies and see a month-end forecast beside actual spend.
Team · paymentsSeptember, month to date · EUR
direct + allocated + untagged2,363.00
- Direct 1,842.10
- Allocated 402.55
- Untagged 118.35
Billing but gonelast 14 days · 10 resources
ResourceLast seenAmount
i-0…a112 days ago41.20
i-0…b39 days ago27.85
i-0…c93 days ago6.10
Budget 12,000 / month 19.7 % used
Attribution
Give every cost an owner.
Allocation rules map account and tag data to teams. Unallocated costs remain visible, and changing a rule recalculates history.
- AWS billing combines Cost Explorer and Cost & Usage Reports, with a 12-month Cost Explorer backfill.
- Google Cloud billing reads the BigQuery export. Figures distinguish cost before credits from cost after committed-use credits.
- Azure billing reads the subscription's Cost Management export from its storage container.
- Inventory exceptions flag resources still billing after they disappear and resources with no recorded cost.
- Kubernetes attribution uses the pods and nodes last seen; it is a current-placement approximation. Currencies stay separate.
Allocation rulesapplied in order · example
RuleTeamSeptember, EUR
tag team = paymentspayments1,842.10
account 000000000002data3,120.45
tag app = searchsearch402.55
untaggedno team118.35
Month end · team paymentsforecast · EUR
to date2,363.00
forecast, likely4,980.00
range4,610.00 – 5,320.00
last month's error3.1 %
Budget 5,000 / month forecast within
Budgets and the month ahead
Know before the month ends.
Compare actual spend and a month-end forecast with your budget. The forecast shows its range and measured error.
- Team budgets and anomalies reach the same channels as health alerts.
- Trusted Advisor recommendations appear beside the cost view.
- Organisation, team and account views share the same allocation rules.
Spend capabilities
Billing sources
- Cost Explorer ingestion with a 12-month backfill; Cost & Usage Report ingestion and amortization
- BigQuery billing export; costs before credits or after committed-use credits, labelled separately
- Azure Cost Management export, FOCUS or actual and amortized, read daily
Allocation, budgets and forecasts
- Tag allocation rules, inventory exceptions, anomalies, team budgets and Trusted Advisor recommendations
- Kubernetes cost attribution based on the pods and nodes last seen
- Month-end forecasts with ranges and measured error
- Cost changes explained by the movers that sum to the difference, never called causes
- Savings verified, split into usage and rate from the report's own quantities
What Spend does today.
The rows of the capability matrix for Spend, with the same three words the documentation uses.
Spend
- Cost Explorer ingestion with a 12-month backfill; Cost & Usage Report ingestion and amortization available now
- Tag allocation rules, inventory exceptions, anomalies, team budgets and Trusted Advisor recommendations available now
- Kubernetes attribution by the pods and nodes last seen, a current-placement approximation stated beside the figures available now
- Month-end forecasts with their range and measured error, on the tenant, team and account pages available now
- Reconciliation: a month's total from the places that must agree, per currency, with coverage and charge type beside it in development
- Cost change explanation: what moved between two periods, the movers summing to the difference, the changes in the same window beside them and never called causes available now
- Savings verification: a recommendation's saving split into usage and rate from the report's own quantities available now
- Showback out of the product: a page's table as CSV and a weekly digest per team by email in development
- Azure spend: a subscription's Cost Management export — FOCUS, or the ActualCost and AmortizedCost pair — read daily from its one storage container, as the subscription's reader, into the same cost tables, each export configured on Spend's Settings page with its last read available now
- Google Cloud billing: a billing account's detailed usage cost export in BigQuery, read daily by the project holding it into the same cost tables, under the same authority rule, with labels attributed as tags, each cloud in its own currencies on the overview; Google's figures are its cost before credits, or after committed-use credits alone, and the Overview says which; its figures are in the same anomalies, team budgets and month-end forecasts as AWS's available now
Evaluate it with your team.
Tell us which clouds you use and what you want to evaluate. Start with a guided demo and discuss access for your team.