FinOps Framework
The FinOps Framework is the FinOps Foundation's open model for running a FinOps practice. It sets out principles, personas, the Inform, Optimize and Operate phases, four domains of capabilities, scopes and a crawl, walk, run maturity scale, and practitioners update it every year.
In plain English
Think of a guide to setting up a professional kitchen rather than a single recipe. It tells you which stations a kitchen needs and what good looks like at each, but you choose the menu and which stations to open first.
Worked example
| Understand Usage & Cost, Allocation: team tag coverage | 95.7% |
|---|---|
| Quantify Business Value, Unit Economics: Checkout's cost per order | $0.050 |
| Optimize Usage & Cost, Usage Optimization: cloud waste found | $6,500 |
| Optimize Usage & Cost, Rate Optimization: effective savings rate | 16% |
| Manage the FinOps Practice, Invoicing & Chargeback: cost charged to teams | $110,000 |
Every number in this glossary's examples sits somewhere in the framework. Reading it this way shows the gaps too: Northwind Labs has no forecast yet, so Forecasting is still at crawl.
Why the FinOps Framework matters
It gives teams a shared vocabulary. When finance asks for chargeback and engineering talks about rightsizing, the framework shows where each fits and who's involved, so a new practice doesn't have to invent its own structure.
It's also a maturity map. Each capability can be at crawl, walk or run, and most organizations are at different stages for different capabilities, which helps decide what to improve next.
What's in it
- Principles. Six statements of how a practice behaves, such as teams collaborating and everyone taking ownership of their technology usage.
- Personas. Core personas, such as FinOps practitioners, engineering, finance, product, procurement and leadership, and allied teams that support them.
- Phases. Inform, Optimize and Operate: a loop teams go around continuously.
- Domains and capabilities. Four domains, Understand Usage & Cost, Quantify Business Value, Optimize Usage & Cost and Manage the FinOps Practice, each made up of capabilities such as Allocation, Budgeting or Rate Optimization.
- Scopes and maturity. Scopes set which technology spend a practice covers, from public cloud to SaaS, data centre and AI, and crawl, walk and run describe how mature each capability is.
Common mistakes
- Starting every capability at once. Pick the few that fix your biggest problem today, usually allocation and reporting, and grow from there.
- Aiming for run everywhere. Run isn't the goal for every capability. Move one up only when the extra effort pays for itself.
How CloudYali helps
CloudYali supports capabilities in each domain: Allocation, Reporting & Analytics and Anomaly Management to understand cost; Budgeting and Unit Economics to quantify value; and Usage and Rate Optimization through Cost Savings and Commitments.
Related terms
FinOps foundations
FinOps
FinOps is an operational framework and cultural practice that maximizes the business value of technology, enables timely data-driven decisions, and creates financial accountability through collaboration between engineering, finance and business teams. In practice, the people who spend on the cloud see what it costs, own it, and decide with that cost in mind.
FinOps foundations
Unit economics
Unit economics is measuring cloud cost per unit of business value, such as cost per order, per customer or per API call, by dividing what a product costs by how much it delivered. It shows whether spend is growing because the business is growing or because the product is becoming less efficient.
Allocation & accountability
Cost allocation
Cost allocation is assigning every part of the cloud bill to the team, product or customer responsible for it, using accounts, tags and agreed rules for shared costs. It turns one invoice into numbers each owner can act on, and it is the basis for showback, chargeback and unit economics.
Allocation & accountability
Chargeback
Chargeback is billing each team or business unit for its allocated cloud cost, so the cost lands in that team's budget in the company's accounts. It uses the same allocation as showback, but money actually moves, which is why the rules for shared and unallocated cost must be agreed first.
FinOps foundations
FinOps Open Cost and Usage Specification (FOCUS)
The FinOps Open Cost and Usage Specification (FOCUS) is an open standard for cloud, SaaS and other technology billing data: one set of column names and definitions, such as BilledCost and EffectiveCost, that every provider fills the same way. AWS, Azure and Google Cloud can all export cost data in FOCUS format.
Optimization
Cloud waste
Cloud waste is cloud spend that buys nothing the business needs: idle resources, over-provisioned resources and commitments paid for but not used. It's measured in money rather than resources, and removing it lowers the bill without changing what users get, which is why cost optimization usually starts there.
Frequently asked questions
Who maintains the FinOps Framework?
The FinOps Foundation, part of the Linux Foundation. Practitioners update it through working groups, and a new version is published every year.
What are the three FinOps phases?
Inform, Optimize and Operate. Inform makes costs visible and allocated, Optimize improves rates and usage, and Operate sets goals and processes. Teams cycle through them continuously.
What do crawl, walk and run mean?
They are the maturity levels for each capability: crawl is basic and reactive, walk is repeatable and broader, and run is automated and built into how teams work.
