Sankey Cost Breakdown: Reading Where Cloud Spend Flows

A Sankey diagram shows quantities moving between stages, with each band drawn in proportion to the amount it carries. A Sankey cost breakdown applies that to a cloud bill: the columns are dimensions such as provider, account, resource type, and team, and each band is the spend that connects a value in one column to a value in the next. Where a bar chart answers “how much per team”, a Sankey answers “how much of this account’s spend ends up with which team, and through which services”.

How to read one

• Width is cost. The thickest band is the largest flow between two adjacent columns. Compare widths within a column, not across the whole diagram.
• Nodes conserve. What enters a node leaves it. If a node’s outflow looks smaller than its inflow, part of it is going to a bucket you did not expect, such as an unattributed or untagged node.
• Only adjacent columns are linked. A band from Account to Type says nothing about which team that type’s spend reaches; follow it into the next column, or drill in.
• Column order changes the story. Provider, Account, Type, Team shows who pays for which services; Account, Service, Purchase, Team shows how much of each account runs on commitments versus on-demand.

The Sankey in ZopNight

ZopNight’s Cost Reports page has a Trend and Flow toggle on the Cost Breakdown card; Flow renders the period’s spend as a four-column Sankey. The layout dropdown offers Provider, Account, Type, Team (the default); Provider, Account, Service, Team; Provider, Region, Type, Team; Provider, Account, Purchase, Team; and Account, Service, Purchase, Team. Per-resource detail is reached by clicking a node.

The diagram is also the filter. Clicking a node or band narrows the chart and adds a breadcrumb chip; chips back out one column at a time or clear all. Two overlays sit in the header: a savings overlay that marks bands and nodes in proportion to reclaimable spend, and a highlight for spend with no team owner. Hovering shows the dollar value and its share of source and target. Where the dimension is one the recommendations list can filter on, resource type or cloud account, the inspector adds a reclaimable amount that links to those recommendations; for other dimensions it is hidden. The whole view, including layout, drill path, and overlays, lives in the URL, so a copied link reproduces it. Breakdowns are served live from cost records.

Misreads to avoid

• Expecting the invoice total. Team and breakdown views are attributed to discovered resources. Spend that matches no resource, such as taxes, fees, and some networking lines, is added to org-level summary totals when billing sync is connected, but not to breakdowns. A Sankey total can therefore be lower than the bill.
• Reading the savings overlay as a forecast. It shows reclaimable spend from open recommendations, which are separate levers that do not all stack on one resource.
• Treating Unattributed as noise. A wide unattributed band is an allocation gap to fix with ownership and tags.

Using it in a review

Start from the default layout for the month, drill into the widest account, switch to the Service layout to see what drives it, then open the reclaimable link for the largest resource type. The trail of chips doubles as the agenda for the owning team.

Related: cloud cost allocation, showback vs chargeback, and the step-by-step how to read the Sankey cost breakdown.