FinOps Framework
What is FinOps Framework?
The FinOps Framework is the FinOps Foundation's model for building a FinOps practice, made up of principles, personas, phases, a maturity model, domains, capabilities and technology categories.
Updated November 2026 · 5 min read
The FinOps Framework describes what a FinOps practice does and how to build one. Rather than prescribing a single method, it offers building blocks that organizations can select from and adapt: principles that guide behavior, personas that define who is involved, phases that describe the cycle of work, a maturity model for measuring progress, and domains and capabilities that list the activities a practice performs. The Framework is maintained by the FinOps Foundation and updated regularly based on input from practitioners.
Most organizations use the Framework as a reference when setting up a FinOps team, assessing their current practice or explaining FinOps to executives and other teams. For IT financial management, the Framework provides a structure for managing consumption-based technology costs that complements existing approaches such as technology business management and IT financial management.
Definition of FinOps Framework
The FinOps Framework is an operational framework published by the FinOps Foundation that defines the components of a FinOps practice and how they fit together. It is non-prescriptive, meaning organizations choose which parts to apply and how deeply, based on where they can get the most value.
The Framework is published under a Creative Commons license and is free to use with attribution. It is revised regularly, with recent updates broadening it from public cloud to other technology categories. The 2026 revision also updated the official definition of FinOps to focus on maximizing the business value of technology as a whole, rather than cloud alone.
Core Components
The FinOps principles are values that guide decisions. The FinOps personas describe the roles involved, including core personas such as engineering and finance and allied personas from related disciplines.
The FinOps phases, Inform, Optimize and Operate, describe the cycle of work. The FinOps maturity model uses Crawl, Walk and Run to describe how developed each activity is.
Domains describe the outcomes of a practice, and each domain contains capabilities, which are the specific activities used to achieve those outcomes.
Domains and Capabilities
The Framework has four domains. Understand Usage and Cost covers data ingestion, allocation, reporting and anomaly management. Quantify Business Value covers planning and estimating, forecasting, budgeting, KPIs and benchmarking, and unit economics.
Optimize Usage and Cost covers architecting and workload placement, rate optimization, usage optimization, sustainability, and licensing and SaaS. Manage the FinOps Practice covers practice operations, governance, assessment, tools, education, invoicing and chargeback, intersecting disciplines and executive strategy alignment.
Each capability page in the Framework describes its purpose, the personas involved, typical measures of success and how it looks at different maturity levels.
Importance of the FinOps Framework in IT Financial Management
The Framework gives organizations a common structure for a discipline that would otherwise be defined differently by every team and vendor.
This shared structure has several practical benefits. It shortens the time needed to design a practice, reduces disagreement about what FinOps includes and makes it easier to choose tools and services that fit.
It also makes FinOps easier to explain to executives, since the Framework sets out what a practice does in terms that connect to business outcomes.
A Common Language
The Framework's terms, such as allocation, rate optimization and unit economics, are used widely across companies, tools and training. Teams that adopt them can communicate more clearly with each other and with vendors.
A shared vocabulary also helps when hiring, since candidates trained in the Framework understand the activities and roles involved.
It makes it easier to compare an organization's practice with others and with industry research, such as the FinOps Foundation's annual survey of practitioners.
Scopes and Technology Categories
Recent versions of the Framework introduced FinOps Scopes, which define the parts of an organization's technology spending that a FinOps practice covers, and technology categories, which describe how FinOps applies to public cloud, SaaS, data center, data cloud platforms and AI.
This reflects a shift from FinOps as a cloud cost discipline to a broader practice for managing the value of technology. It brings FinOps closer to technology business management, which has long covered the whole technology estate.
The 2026 update also emphasized FinOps working alongside related disciplines, including IT financial management, IT asset management and IT service management.
How to Use the FinOps Framework
Organizations use the Framework to plan, assess and improve their FinOps practice. Because it is non-prescriptive, the key is choosing where to start.
Starting with the capabilities that address the organization's biggest problems usually delivers the fastest results. Trying to adopt the whole Framework at once tends to spread effort too thinly and delay visible progress.
Assessing the Current Practice
Review each capability and estimate its current maturity, using the Crawl, Walk and Run descriptions as a guide. Many organizations involve engineering, finance and business stakeholders in this assessment to get an accurate picture.
Identify the capabilities where improvement would deliver the most value, such as allocation if costs cannot be traced to teams, or rate optimization if commitment discounts are not used.
The Framework's guidance on FinOps assessment provides a structured way to repeat this exercise over time.
Planning Improvements
For each priority capability, set a target maturity and define measures of success. The Framework provides typical measures for each capability that can be adapted.
Assign owners from the relevant personas, and work through the Inform, Optimize and Operate phases in short cycles, measuring results and adjusting.
Revisit the assessment periodically, adding capabilities and technology categories as the practice expands. Each new Framework release is also worth reviewing for changes that affect the organization's priorities.
Examples of the FinOps Framework in IT Financial Management
The examples below show the Framework being used to plan a practice.
Both describe common situations rather than specific companies. The first uses the Framework to prioritize, and the second uses it to expand.
In each, the Framework helped the organization focus effort on the most valuable capabilities.
Prioritizing Capabilities
A company's FinOps team uses the Framework to assess its practice. It rates allocation and reporting at Walk, but forecasting and rate optimization at Crawl, with only 30% of eligible compute covered by commitment discounts.
The team prioritizes rate optimization, which offers the largest immediate savings, and forecasting, which finance has asked for. Six months later, both capabilities have moved to Walk. Commitment coverage has risen to 65%, and monthly forecasts are within 6% of actual spending.
Expanding the Scope
Another organization's FinOps practice has covered public cloud for several years. Using the Framework's technology categories, it extends the practice to its largest SaaS platforms and its data cloud platform.
It applies the same allocation, reporting and unit economics capabilities to these new categories, giving leaders a single view of consumption-based technology spending. The FinOps team also begins working with the IT asset management team, which already tracks SaaS licenses.
Conclusion
The FinOps Framework is the FinOps Foundation's model for building a FinOps practice. It includes principles, personas, phases, a maturity model, four domains with their capabilities, and guidance for applying FinOps across technology categories.
In IT financial management, the Framework gives organizations a common language and structure for managing consumption-based technology costs. Assessing current maturity, prioritizing the capabilities that matter most, working in short cycles and expanding scope over time help organizations use it effectively.
Related terms
FinOps Foundation
The FinOps Foundation is a nonprofit project of the Linux Foundation that maintains the FinOps Framework and the FOCUS specification, and supports the FinOps community through training, certification, events and research.
FinOps Principles
The FinOps principles are six guiding values in the FinOps Framework that shape how organizations practice FinOps, covering collaboration, business value, ownership, data, central enablement and variable cost models.
FinOps Personas
FinOps personas are the roles the FinOps Framework identifies as involved in a FinOps practice, including core personas such as engineering, finance and procurement and allied personas from related disciplines.
FinOps Phases
The FinOps phases are the three stages of the FinOps lifecycle, Inform, Optimize and Operate, which teams cycle through continuously to gain visibility, improve efficiency and put changes into practice.