TigerFinOps explorer

Spend by cloud

Billed spend per 30 days, invoice basis

How the savings add up

Monthly. Waste the graph found, less what commitments already pay for, plus rate optimization.

Savings by opportunity

Annual. Pale bar is gross, the upper bound; solid is confidence-weighted, the figure to forecast. Select one to see its findings.

By cloud

One detector set on all three clouds — no per-provider rules. Recoverable share of each cloud's resource spend.

Who owns the spend

Share of resource spend with an owner on each dimension, by how that owner was established.

Discounts already in place

List price to what was actually paid.

Traffic leaving its region or cloud

Transfer bills on the sender as a networking line with no destination. Flow logs say where the traffic went; the graph joins the two, and each flow carries its share of what was billed — no price list involved.

Shared costs, charged to who uses them

Showback, not savings. Tagging charges a shared database or gateway to the team that owns it; following the topology charges it to the teams whose workloads depend on it, in proportion to their size. Both views divide the same total.

Largest owners of recoverable spend

Gross annual savings by owner on one dimension.

Cost anomalies

Money already spent — never counted in the savings above. The graph explains each one by what its resources share.

Detecting anomalies…

What if we act on it?

The findings list counts each recommendation on its own. A plan carries several out together, and they interact: shrinking usage shrinks the commitments worth buying, and the order you do them in decides whether a purchase strands. Pick what to act on, and change the thresholds behind the recommendations if your organization needs stricter or looser ones.

Act on

Yearly figures are gross, at the thresholds below.

Thresholds

Usage changes and commitments, together

Who has to act

Monthly saving and findings per team. Commitments are bought estate-wide.

How much work

Monthly saving and findings by effort.

What the graph adds to a billing export

Billing data says what everything costs. Questions about what is attached to what, who relies on what, and where traffic goes are questions about relationships. Each answer below uses this estate's figures, the same ones the CLI reports, beside what billing alone can say.

Savings by the evidence they need

Each finding grouped by the least an estate must supply to find it: its billing export, an inventory of resources and their state, how busy they are, or the relationships between them.

What this does and does not show

The estate is synthetic, and its waste, traps and flows were planted to be found, so the detection rates here prove the mechanism, not real-world accuracy. SQL can answer every one of these questions too, with enough joins; the difference is the shape of the query, not the possibility of it. The figures are the engine's own, identical to gfinops analyze.