FINOPS-SHOWBACK

FinOps Showback cost visibility without billing.

Definition

FinOps Showback vs Chargeback: (1) Showback: costs allocated + reported to teams/BUs via dashboards + reports for awareness, NO actual money charged to BUs internal budgets, central IT/Finance keeps central cloud spend budget, BUs see 'what they cost' transparency. (2) Chargeback: costs allocated + actually charged to BUs internal budgets via internal invoices/accruals, BUs pay for cloud spend from their own budgets, more accountability + cost ownership. (3) Hybrid: partial chargeback (only certain types like compute) + showback (storage, networking). Implementation: Tag-based allocation rules (BU label + team label + environment label etc.), cloud provider Tagging policies + governance, FinOps tools (CloudHealth, Cloudability, Vantage) automate allocation. Showback advantages: easier organisational change management, encourages without forcing budgets restructuring. Showback disadvantages: less accountability, BUs may not actually optimize without financial incentive. Trend: ~60% enterprises Showback, ~30% Chargeback, ~10% Hybrid 2024 State of FinOps.

Origin

Showback + Chargeback concepts historic IT FinOps practice ~2000s legacy on-prem IT cost recovery ; adapted to cloud computing 2014+ ; FinOps Foundation framework 2019+.

Example in context

Spotify FinOps team uses Showback model: monthly emailed report each engineering team (~150 teams) shows 'your AWS spend last month $X', cost dashboards Looker per team, awareness drives engineering teams optimize their own workloads while central infrastructure team owns cloud budget.

Related terms

• FinOps Chargeback — effective billing model.