Skip to main content

FinOps Framework

Last updated 2026-06-04

The FinOps Framework, maintained by the FinOps Foundation, organizes cloud financial management into a repeating loop of three phases. Inform delivers visibility, cost allocation, and benchmarking so teams understand what they spend and why, typically through tagging, account structure, and showback reporting. Optimize reduces cost through rightsizing, commitment-based discounts, and eliminating idle or orphaned waste. Operate builds the ongoing processes, governance, and automation that keep costs under control as the organization scales, for example budget alerts, anomaly detection, and policy checks in CI/CD. The framework also defines personas (such as engineering, finance, product, and leadership) and a set of capabilities a maturing practice develops over time, along with principles that emphasize shared ownership and data-driven decisions. Because cloud usage and pricing change constantly, teams cycle through the three phases continuously rather than once. LevelFour automates the Optimize and Operate phases by turning savings opportunities into reviewable pull requests.

Frequently asked questions

What are the three phases of the FinOps Framework?
The FinOps Framework defines three phases in a repeating loop: Inform (visibility, cost allocation, and benchmarking), Optimize (rightsizing, commitments, and eliminating waste), and Operate (governance, automation, and continuous improvement). Teams move through them continuously, not once, because cloud usage and pricing keep changing.
Who maintains the FinOps Framework?
The FinOps Framework is maintained by the FinOps Foundation, a vendor-neutral organization that stewards the practice. It publishes the phases, personas (such as engineering, finance, product, and leadership), capabilities, and guiding principles, giving teams a shared, standardized vocabulary and structure for managing variable cloud spend collaboratively.

Related terms

See also

LevelFour automates this across AWS, GCP, Azure, and Kubernetes with automated infrastructure-as-code pull requests.