What is FinOps?
FinOps is an operational framework and cultural practice for managing variable cloud spend. It brings engineering, finance and business teams together so that spending decisions are made with timely cost data, each cost has an accountable owner, and the organisation gets the most business value from what it spends on cloud.
Why FinOps exists
On-premises infrastructure was bought up front, through a procurement process, a few times a year. Cloud infrastructure is bought by the minute, by engineers, through an API. The people who create cost are no longer the people who approve it — and the bill arrives after the money is spent.
Traditional finance controls do not fit that model. Blocking spend slows engineering down; ignoring it produces a surprise at month end. FinOps is the discipline that sits between the two: give the people creating cost the information to make good decisions, and give finance a reliable view of where the money goes.
The term and its framework are stewarded by the FinOps Foundation, a project of the Linux Foundation, which publishes the framework, its principles and the open FOCUS specification for cost and usage data.
What are the phases of FinOps?
The FinOps Foundation describes a repeating lifecycle of three phases:
- Inform — make cost visible and attributable: who spent what, on which service, for which product. Allocation, showback and forecasting live here.
- Optimise — reduce waste and improve rates: rightsizing, removing idle resources, scheduling non-production environments, and commitment discounts such as reserved capacity and savings plans.
- Operate — make it routine: budgets, policies, anomaly alerts, and decisions taken as part of normal engineering and planning cycles.
Teams cycle through all three continuously, and different parts of the organisation can be at different stages at once.
What does a FinOps practice actually do?
| Activity | The question it answers |
|---|---|
| Cost allocation | Who owns this spend? |
| Showback and chargeback | Does each team see — or pay for — what it uses? |
| Forecasting and budgets | What will we spend, and are we on track? |
| Anomaly detection | Did something change that nobody intended? |
| Rate optimisation | Are we paying the best available price for steady usage? |
| Usage optimisation | Are we running things we do not need? |
| Unit economics | What does it cost to serve one customer, transaction or request? |
Billed cost vs amortised cost
One of the first things a FinOps team learns is that "what did we spend?" has more than one correct answer. Billed cost is what the invoice says for the period. Amortised (effective) cost spreads up-front commitment payments across the periods they cover. A three-year commitment paid up front makes the billed figure spike once; the amortised figure shows the real monthly cost. Mature practices report both and say which one a number is.
Common FinOps mistakes
- Treating it as a cost-cutting project. FinOps is about value, not only reduction; spending more on a growing product can be the right answer.
- Optimising before allocating. Savings are hard to act on when nobody owns the resources they apply to.
- Quoting unsettled numbers. Cloud billing data arrives late and is revised; a partial month presented as final causes false alarms.
- Centralising every decision. A central team enables; the engineers who own the workloads act.
Next steps
- What is cloud cost allocation? — showback, chargeback and tagging
- How Onam FinOps works — reconciled billing data, ownership and savings
- What is a cloud asset inventory? — knowing what you pay for
Frequently asked questions
What does FinOps stand for?
FinOps is a portmanteau of finance and DevOps. It describes the practice of bringing financial accountability to variable cloud spend, by having engineering, finance and business teams make spending decisions together using timely cost data.
Who is responsible for FinOps in an organisation?
Usually a small central FinOps team that sets standards, owns the data and tooling, and negotiates commitments — working with engineering teams who own the workloads and act on recommendations, and finance teams who own budgets and forecasting. Accountability for each cost sits with the team that creates it.
Is FinOps only about reducing cloud costs?
No. The goal is to maximise the business value of cloud spend. Sometimes that means cutting waste; sometimes it means spending more on a product that is growing. The point is that the decision is made deliberately, with good data, by someone accountable.
What is FOCUS in FinOps?
FOCUS, the FinOps Open Cost and Usage Specification, is an open specification for cloud billing data published under the FinOps Foundation. It defines common columns and terms so cost data from different providers can be combined and compared without bespoke translation.