Showback & Chargeback
Making teams see, or own, the cost of what they run.
5 to work through
-
intermediate
A platform team wants engineering teams to reduce their infrastructure spend. Does showback or chargeback work better, and what determines the answer?
2 min answer -
intermediate
An enterprise is deciding between showback and chargeback for cloud costs. What does each achieve, and what goes wrong with chargeback?
2 min answer -
intermediate
Cloud spend is growing faster than revenue and no individual team feels responsible. How should cost allocation be designed to actually change behaviour?
2 min answer -
advanced
A team reduces its cloud bill 30% by removing a standby replica, then has an outage. What was wrong with the incentive structure?
2 min answer -
advanced
A year into chargeback every product team's reported infrastructure cost is down between 15% and 25%. Company cloud spend is up 8%. Tag coverage is 100% and no commitment expired. Where is the money going, and what would you look at first?
3 min answer
3 terms in this topic
Cost Accountability Model
The arrangement determining whether teams merely see their costs or are financially charged for them, and the behaviour each produces.
conceptShared-Service Commons
The failure mode where cost allocation prices each team's own resources but leaves internal platforms free to use, so teams move cost onto the shared…
practiceShowback and Chargeback
Showing teams their costs, or actually billing them — two different mechanisms with different incentive effects and different failure modes.
Neighbouring topics
Cost & FinOps
General material on the economics of an architecture.
Total Cost of Ownership
Lifetime cost including people, operations, upgrades and exit.
Cloud Pricing Models
On-demand, committed and spot, and the crossover arithmetic.
Reserved & Committed Capacity
Committing the baseline, laddering terms, and expiry as a silent failure.
Spot & Interruptible Capacity
Deep discounts for work that can be interrupted and resumed.
Unit Economics
Cost per request, per tenant, per transaction — the actionable number.
Cost per Request
Fully-loaded per-unit cost, including the lines usually left out.
Storage Costs
Tiering, lifecycle policies, retrieval charges and minimum durations.
Network & Egress Costs
Cross-zone and cross-region transfer that appears on no diagram.
Compute Optimisation
Instance families, utilisation, and architecture that wastes less.
Rightsizing
Matching provisioned resources to observed demand rather than to a guess.
Cost Allocation
Tagging enforced at provisioning, and apportioning shared costs.
Architecture Cost Modelling
Pricing a design before building it, at expected and at ten times volume.
Cost vs Reliability
Each nine costing an order of magnitude, and pricing the failure instead.
Observability Cost
Telemetry bills, cardinality control and retention tiering.
Licence & Vendor Costs
Per-core, per-seat and per-environment terms that shape designs.
FinOps Practice
Inform, optimise, operate — and cost as a design-review criterion.
Waste Elimination
Idle environments, orphaned volumes, forgotten instances, dead data.
Cost Governance
Budgets, anomaly alerts, quotas and preventive policy.