FinOps & process
FinOps
The operating practice of managing cloud (and increasingly AI) spend as a shared responsibility between finance and engineering, on an ongoing cadence.
Last updated
Definition
FinOps treats cost the way SRE treats reliability: a discipline with its own metrics, review cadence, and shared ownership between the people who spend (engineering) and the people who account for it (finance), rather than a once-a-quarter finance-only audit. Its core loop is simple: normalize spend into one view everyone trusts, review it on a fixed cadence, act on what's drifting. It scales down to a single rotating owner just as well as it scales up to a dedicated platform team.
The discipline originated around cloud infrastructure spend but applies just as directly to AI/LLM API spend, which is usage-based in the same way and needs the same visibility-plus-cadence treatment, just at a faster tempo given how quickly it can move.
Where it shows up
FinOps shows up as a recurring review of a normalized cost view, typically a dashboard or report both finance and engineering can see and act on together, checked on a fixed cadence rather than as a once-a-quarter audit run by one side of the business alone.
What makes it expensive
The costly mistake is treating cost review as a finance-only, once-a-quarter exercise, missing spend that grew and then shrank again between reviews with nobody actually watching it happen. Buying a dashboard is the easy part of this. The cadence and the named owner are the parts that turn it into a practice.
Related
The invoice is a lagging signal.
A monthly invoice tells you what already happened. CostMon builds a daily baseline, so a spike stands out while you can still act on it.