FinOps

Where the money goes, what is wasted, and which commitments are worth making.

Runs today, on Google Cloud

Connect a Google Cloud project and this module reads it. Today that means:

Disks attached to nothing
Reserved addresses nobody is using
Instances stopped and still costing
Snapshots older than they need to be

It reads Google Cloud only, not AWS or Azure, and it does not track remediation. Everything further down this page is where the module is going, not what it does now. The wider review is work we do as an engagement — FinOps engagement.

THE PROBLEM

Why this module exists

The cloud bill arrives monthly, aggregated, and too late to act on. By the time anyone asks why it rose, the change that caused it is three sprints back.

INTENDED SIGNALS

What it is being built to surface

Descriptions of intent. No findings exist yet, because nothing is connected yet.

Where the money goes

Spend attributed to teams and services, not just accounts.

Waste

Idle resources, orphaned volumes, oversized instances and forgotten environments.

Structural cost

Data transfer, NAT gateways and the architecture decisions that quietly bill forever.

Commitment position

Coverage and utilisation, and whether more commitment is actually warranted.

SCOPE

What the module covers

Spend visibility and forecasting
Waste, idle resources and rightsizing
Kubernetes cost allocation
Data transfer, NAT and commitment optimisation

Tell us what this would need to catch

We are designing this against real environments. If this is a problem you have, the fastest way to shape it is a conversation with the engineers building it.

Talk to an Engineer