# Showback

## What is a showback?

A showback is a cloud cost visibility practice where teams or departments can see how much of the organization's cloud spending is attributable to them, without being billed or charged for it. The information is shared for awareness, not as a financial transaction.

Unlike with a chargeback, no invoices are raised and no budgets are debited for a showback. Teams see their share of cloud consumption, and what they do with that information is up to them.

## Why organizations use showbacks

When teams have no visibility into what their workloads cost, there's little reason to think about efficiency. A showback brings cost awareness in without the overhead of internal billing.

It tends to come up when an organization is:

- Still early with FinOps and trying to build cost awareness across teams.
- Not ready to deal with the process overhead of chargebacks.
- Getting engineering or product teams to pay attention to cloud usage for the first time.

## How a showback works

A showback depends on cost allocation, which means tagging cloud resources and mapping spending to teams, projects, or environments. Once tagging is consistent, costs can be grouped and reported against those dimensions.

A typical showback report covers:

- The total cloud spending for the period.
- A breakdown by service (compute, storage, data transfers, and more).
- Spending per cloud provider, account, or region.
- Trends over time so teams can see whether usage is growing, stable, or spiking.

## A real-world example

Three product teams share cloud accounts at a software company: payments, analytics, and core platform. The monthly bill comes in at $180,000 combined. Without a showback, that number sits with the finance team, and engineers have no real sense of what their services cost.

With a showback running, this is what the spending for each team looks like:

| Team | Monthly spending | Vs. last month |
|---|---|---|
| Payments | $42,000 | +4% |
| Analytics | $71,000 | +38% |
| Core platform | $67,000 | -2% |

The analytics spike stands out. A data pipeline had been left running in a dev environment over a long weekend. Nobody had flagged it because nobody had a reason to look. The report did not charge anyone, but it surfaced a $12,000 problem before the next billing cycle.

## Showbacks vs. chargebacks

|  | Showback | Chargeback |
|---|---|---|
| Financial impact | None | Costs billed internally |
| Complexity | Low | Higher |
| Best for | Building awareness | Enforcing accountability |
| FinOps maturity | Early stage | More mature |

Many organizations start with showbacks and move to chargebacks over time. Some stick with showbacks in the long term because for a lot of teams, seeing the numbers is enough.

## What it needs to work well

A showback is only as reliable as the tagging behind it. Here are a few things that tend to cause problems:

- Untagged or inconsistently tagged resources leave gaps in attribution.
- Without a tagging policy, reports lose credibility quickly.
- Shared infrastructure like networking or security tooling needs an agreed split method before it can be allocated fairly.

Getting tagging compliance in order before rolling out showbacks saves a fair amount of back and forth.

## Showbacks vs. chargebacks: Which model should you use?

- If the goal is awareness, showbacks are sufficient.
- If teams need real budget consequences to change their behavior, the chargeback model is the better fit.
- Most teams find it worth starting with showbacks and seeing how far visibility alone gets them.