The FinOps Foundation framework
FinOps is an operational framework and cultural practice that maximises the business value of technology, enables data-driven decisions and establishes financial accountability through collaboration between engineering, finance and the business.
An open framework, not a proprietary method
The official FinOps Foundation framework (principles, personas, domains and capabilities) is applied in every engagement, with no in-house variant that would cut your teams off from the FinOps ecosystem once the engagement ends. The logic mirrors our independence from vendors: the knowledge transferred to your teams must remain portable, not locked into a tool or a method we own.
The framework is presented section by section: the frame, the principles, the cycle, the scopes, the personas, then domains and capabilities. Personas and capabilities, more numerous, reveal their detailed definition on hover or click, and each block links to the official FinOps Foundation documentation.
The vocabulary of the framework
- Principle
- A conviction that shapes how FinOps is practised. Principles do not describe activities: they set the frame within which every other notion sits. There are six of them.
- Phase
- A moment in the working cycle. FinOps runs as a continuous loop across three phases (Inform, Optimize, Operate), and each capability is worked mainly within one of them. The phase answers the question when.
- Scope
- The spend segment the framework is applied to: a product, a cost centre, an environment, or a custom split. Defining the scope means deciding at which scale steering happens, rather than treating all technology spend as one block. The scope answers the question which budget.
- Technology category
- The nature of the technology consumed: public Cloud, AI, SaaS, data platforms, data centre. Each category has its own optimisation levers, indicators and billing constraints, which makes generic recommendations of little practical use. The category answers the question which technology.
- Persona
- A function engaged in the practice, defined by what it decides rather than by a job title. The framework separates core personas, present at every trade-off, from allied personas, called in on their field of expertise. The persona answers the question who.
- Domain and capability
- A domain is an outcome the practice pursues (understand cost, quantify value, optimize, manage the practice): the what. A capability is a concrete activity that gets there: the how. The framework counts four domains grouping twenty-two capabilities.
How these terms fit together
A scope frames the spend under analysis, across one or several technology categories. Personas work on it together, running through the three phases in a loop. On each turn they exercise capabilities that produce the outcomes the four domains aim for. Principles apply throughout, whatever the scope or the maturity level.
A frame between business strategy and technology strategy
Why this framework exists. FinOps is not an isolated IT topic: it bridges business objectives and the technical decisions that commit spend. Every technology trade-off then reads as an economic decision, and every business objective finds an operational translation.
Business Strategy
FINOPS
Technology Strategy
FinOps Principles
These six principles form the cultural foundation shared by every FinOps practice, whatever the scope covered or the maturity reached. They come before tooling and outlast reorganisations.
Teams need to collaborate
FinOps governance does not work in silos. It requires active coordination between engineering, finance and the business on every decision that carries a cost impact.
Business value drives technology decisions
Cost is never judged in isolation, only against the value it produces. Rising spend can be healthy when it tracks growth, flat spend can hide a loss of efficiency.
Everyone takes ownership of their usage
Financial accountability is distributed down to the teams that actually consume the resource, with the visibility and autonomy needed to act.
FinOps data must be accessible, timely and accurate
No steering decision holds up when it rests on incomplete or stale data. This is a prerequisite, not a secondary option.
FinOps is enabled centrally
Standards, tooling and governance policies stay consistent organisation-wide, even when execution is distributed.
The variable cost model of Cloud is an advantage
Pricing flexibility, often seen as a drift risk, becomes a strategic advantage as soon as it is actively steered.
FinOps continuous improvement cycle
Three phases run as a continuous loop, completed faster as the practice matures. Each phase mobilises specific capabilities of the framework.
The Operate phase loops continuously back to Inform.
Which scopes does the framework apply to?
The framework deploys over a defined spend scope, then adapts to the nature of the technology consumed. Optimisation levers differ radically from one category to the next.
Scopes
Custom Scope
A bespoke split when neither product nor cost centre reflects the real organisation.
More on finops.orgProduct
Spend reads by product or service line, as close as possible to the value generated.
More on finops.orgCost Center
Spend reads along the existing budget structure, familiar to finance teams.
More on finops.org
Technology categories
Public Cloud
Usage-billed IaaS and PaaS environments, with the richest commitment landscape.
Learn moreAI & GenAI
Tokenomics, inference cost and model arbitration on a cost-to-performance basis.
Learn moreData Platform
Credit-based or query-based consumption, requiring a dedicated financial reading.
Learn moreSaaS & Licensing
Licences and subscriptions, the most scattered spend for lack of central visibility.
Learn more
Who is engaged in the practice
FinOps is a collective discipline. Some functions sit in every trade-off, others act as relays on their fields of expertise.
The objectives the practice pursues
Four outcome domains, twenty-two operational capabilities. Each capability primarily attaches to one cycle phase, which shows when it is worked on.
Objective: establish reliable visibility and exact attribution of spend, a prerequisite to any decision.
Objective: relate spend to the value produced so trade-offs rest on a ratio, never on a raw amount.
Objective: convert visibility into measurable gains on consumed usage and on the rate paid.
Objective: embed the practice over time through governance, skills and tooling.
IMPLEMENTATION
From reference model to your organisation's trajectory
Maturity assessment
Scoring capability by capability, scope by scope, with priority gaps made explicit.
Target Operating Model
Target roles, RACI, governance cadence and allocation model, aligned with your actual organisation.
Roadmap
Crawl, Walk, Run sequencing over 12 to 24 months, with measurable milestones and explicit capability transfer.