FinOps Framework

What the FinOps Framework is

FinOps is the practice of managing cloud cost as a shared responsibility between engineering, finance and the business, instead of a surprise invoice finance forwards to engineering once a month. The FinOps Foundation, part of the Linux Foundation, maintains the FinOps Framework as the reference model for that practice, and updates it with its community; the current version on the site is the 2026 framework.

How it is organised

• Six principles: teams need to collaborate; business value drives technology decisions; everyone takes ownership of their technology usage; FinOps data should be accessible, timely and accurate; FinOps should be enabled centrally; and take advantage of the variable cost model of the cloud.
• Three phases: Inform (see and allocate cost), Optimize (reduce waste and get better rates) and Operate (make it continuous and part of how the organisation works). Teams cycle through them repeatedly rather than finishing them.
• Four domains and 18 capabilities: Understand Usage and Cost (data ingestion, allocation, reporting and analytics, anomaly management), Quantify Business Value (planning and estimating, forecasting, budgeting, KPIs and benchmarking, unit economics), Optimize Usage and Cost (architecting and workload placement, usage optimisation, rate optimisation, licensing and SaaS, sustainability) and Manage the FinOps Practice (strategy alignment, practice operations, governance, education, invoicing and chargeback, assessment, tooling and intersecting disciplines).
• Personas and maturity: who does what, from engineers to finance and procurement, and a crawl, walk, run maturity approach for each capability.

The Foundation also runs FOCUS, an open specification for cloud billing data, as a related project, so cost data from different providers can be compared in one format.

Why platform engineers should read it

Platform teams usually own the things FinOps depends on: tagging and labelling standards, cost allocation for shared clusters, dashboards, budgets and alerts, autoscaling defaults and the golden paths that decide what size a new service starts at. Knowing the framework lets you build those with a purpose and talk to finance in their terms, for example unit cost per customer or per request rather than total spend.

Prerequisites and time

Basic familiarity with how a cloud provider bills (compute, storage, data transfer, reserved or committed discounts) helps. Reading the framework pages takes an afternoon. Applying one capability, such as allocation for a Kubernetes cluster, takes weeks.

Free or paid

The framework and its capability pages are free to read. The Foundation also sells training and certifications, which are optional.

What you can do after it

• Design a tagging or labelling policy that makes cost allocation possible.
• Build a cost report that shows unit economics, not only totals.
• Explain the difference between usage optimisation and rate optimisation.

Best for: platform, cloud and DevOps engineers who are asked why the bill went up, and want a structured answer.