Showback
Showback is reporting each team's allocated cloud cost back to that team, for visibility and accountability, without moving money between budgets. It shows owners what their choices cost so they can act on it, and unlike chargeback it is not entered into the company's accounts.
In plain English
Think of an itemized utility statement that comes to your flat even though the landlord pays the bill. Nobody charges you, but seeing your heater on the statement changes how long you leave it on.
Worked example
| Cost tagged to Checkout | $20,000 |
|---|---|
| Checkout's share of shared costs | $2,000 |
| Checkout's cost in March | $22,000 |
| Checkout's cost in February | $19,500 |
| Change from February | +$2,500 (13%) |
The report goes to the Checkout team lead and their finance partner. No budget moves: the point is that the team sees the jump and asks why, before anyone else has to.
Why showback matters
Most cloud cost is decided by engineers, but the bill lands with finance. Showback closes that gap: it puts each team's number, and how it is changing, in front of the people who can change it.
The FinOps Foundation treats showback as something every FinOps practice needs, and chargeback as depending on how the company does its accounting. Neither is more mature than the other.
Common mistakes
- Sending a number without context. A total alone invites shrugs. Show the trend, the biggest services and the change from last month, so a team can see what moved.
- Reporting to the wrong people. A report that reaches only finance changes nothing. Send it to the engineering lead who owns the spend, on a regular schedule.
- Hiding shared and unallocated cost. If teams see only their direct cost, the reports won't add up to the bill and trust drops. Show each team's share of shared costs, and report unallocated cost separately.
- Changing the basis from month to month. Use the same allocation rules and cost basis every month, and say which basis it is. Amortized cost usually works best for teams.
Where to find it in AWS, Azure and Google Cloud
| Cloud | What it is called | Where to find it |
|---|---|---|
 AWS | Cost Explorer, Cost Categories and Billing Conductor | Cost Explorer reports grouped by account, tag or Cost Category. AWS Billing Conductor produces pro forma bills per team for showback or chargeback. |
 Azure | Cost analysis and budgets | Cost analysis views grouped by subscription, resource group or tag, budgets per scope, and exports for your own reporting. |
 Google Cloud | Billing reports and the billing export | Cloud Billing reports filtered by project or label, and the billing export to BigQuery for per-team dashboards. |
How CloudYali helps
CloudYali's Showback cost view and team budgets put each team's cloud cost in front of the people who own it, across AWS, Azure, Google Cloud and other providers, with alerts when a team's spend moves.
Related terms
Allocation & accountability
Chargeback
Chargeback is billing each team or business unit for its allocated cloud cost, so the cost lands in that team's budget in the company's accounts. It uses the same allocation as showback, but money actually moves, which is why the rules for shared and unallocated cost must be agreed first.
Allocation & accountability
Cost allocation
Cost allocation is assigning every part of the cloud bill to the team, product or customer responsible for it, using accounts, tags and agreed rules for shared costs. It turns one invoice into numbers each owner can act on, and it is the basis for showback, chargeback and unit economics.
Allocation & accountability
Cost allocation tags
Cost allocation tags are key-value labels, such as team=checkout, attached to cloud resources so their cost can be grouped by owner, product or environment. On AWS a tag key only reaches billing data after it is activated for cost allocation, and tag keys and values are case-sensitive.
Governance & planning
Budget
A budget is a planned spending limit for a period, such as a team's monthly cloud cost, with alerts when actual or forecasted spend crosses thresholds you set, such as 80% and 100%. On AWS, Azure and Google Cloud a budget warns rather than stops spending, unless you attach actions or automation to it.
FinOps foundations
Unit economics
Unit economics is measuring cloud cost per unit of business value, such as cost per order, per customer or per API call, by dividing what a product costs by how much it delivered. It shows whether spend is growing because the business is growing or because the product is becoming less efficient.
Frequently asked questions
What is the difference between showback and chargeback?
Showback reports costs to teams; chargeback bills them, moving the cost into the team's budget in the company's accounts. The numbers can be identical; the consequence differs.
Is showback a step towards chargeback?
Not necessarily. Many companies run showback indefinitely because their accounting doesn't need chargeback, and the FinOps Foundation doesn't rank one as more mature.
How often should showback go out?
Monthly for budgets and planning, with daily or weekly views for engineers. What matters most is a predictable schedule, to people who can act on it.
