The FinOps Framework 2026 update is the FinOps Foundation's latest annual revision, and it continues the 2025 shift from a cloud-only discipline to a broader technology-value practice. The headline change is a new Capability, Executive Strategy Alignment, in the Manage the FinOps Practice domain, which formalizes the link between FinOps and executive decisions. The Scopes construct introduced in 2025 is deepened, with richer guidance and more Technology Category pages, and the Framework explicitly addresses the convergence of FinOps with adjacent disciplines such as sustainability. The three phases, Inform, Optimize, and Operate, are unchanged. For most teams the practical takeaway is that FinOps is now expected to cover SaaS, licensing, and data center spend alongside public cloud, and to tie that work to executive strategy. We map these changes onto the same See, Cut, Lock, Run method we run across 500+ environments for a 31% average bill reduction.
The FinOps Framework 2026 update is the FinOps Foundation's current-year revision of the model that defines how organizations run cloud and technology cost management. It builds directly on the 2025 release, which added Scopes and broadened the language beyond cloud, and it sharpens that direction with a new capability and deeper guidance. This article explains exactly what changed, what carried over from 2025, and what it means in practice. It is part of our practical introduction to FinOps, the cluster this article links up to.
What is the FinOps Framework?
The FinOps Framework is the FinOps Foundation's reference model for the discipline, built from Principles, Domains, Capabilities, Phases, Maturity, Personas, and now Scopes. The Framework organizes the work into four Domains, Understand Usage and Cost, Quantify Business Value, Optimize Usage and Cost, and Manage the FinOps Practice, and a set of Capabilities within each. Teams cycle through three Phases, Inform, Optimize, and Operate. It is revised annually, and the 2025 and 2026 updates are the most significant changes since the Principles were first written in 2019.
What changed in the 2026 FinOps Framework?
The 2026 update reflects a more mature understanding of how Scopes work in practice, not just as a way to segment spending but as the mechanism that translates business strategy into FinOps activity. The 2026 revisions introduce three substantive changes. First, a new Capability, Executive Strategy Alignment, lands in the Manage the FinOps Practice domain, formalizing the connection between FinOps and executive decision-making that mature practices had built organically. Second, the Scopes construct is deepened with richer guidance and additional Technology Category pages, so FinOps applies cleanly across public cloud, SaaS, licensing, and data center spend. Third, the Framework explores the convergence of FinOps with interconnected disciplines, the clearest example being sustainability, which we cover in what GreenOps is and how it relates to FinOps. Several Capabilities were also updated to be inclusive of all Technology Categories rather than cloud alone.
What carried over from the 2025 update?
The 2026 update is an evolution of the 2025 release, so the 2025 changes are the foundation it builds on. In 2025 the Foundation added Scopes as a core element, updated four Principles for the first time since 2019 to acknowledge non-cloud cost data, and renamed two Domains by dropping the word cloud: Understand Cloud Usage and Cost became Understand Usage and Cost, and Optimize Cloud Usage and Cost became Optimize Usage and Cost. The Phases, Inform, Optimize, and Operate, were not changed in either year. If you adopted the 2025 model, 2026 is an extension rather than a rebuild.
FinOps Framework changes 2025 to 2026 at a glance
| Element | 2025 update | 2026 update |
|---|---|---|
| Scopes | Added as a core element | Deepened with richer guidance and more Technology Categories |
| Capabilities | Language broadened beyond cloud | New Executive Strategy Alignment capability added |
| Domains | Two renamed to drop "cloud" | Capabilities made inclusive of all technology categories |
| Principles | Four updated, first change since 2019 | No further principle changes |
| Converging disciplines | Acknowledged | Formalized, sustainability the lead example |
| Phases | Inform, Optimize, Operate (unchanged) | Inform, Optimize, Operate (unchanged) |
Verdict: the direction of travel is consistent. FinOps is no longer scoped to public cloud, it is a technology-value discipline that now expects executive alignment and crosses into adjacent practices.
Adopting the 2026 Framework on real spend?
Our cloud cost audit maps your current practice onto the 2026 Framework domains and scopes, then sequences the moves that turn the model into a lower bill. On the performance model, you pay only from realized savings. No savings, no fee.
Book a cloud cost audit →What does the 2026 update mean for your practice?
In practice the 2026 update tells you to widen the lens and raise the altitude. Widen the lens because Scopes and the broadened Capabilities mean SaaS, licensing, and data center spend now sit inside FinOps, not outside it, which is also why billing standardization through FOCUS matters more than ever. Raise the altitude because Executive Strategy Alignment expects FinOps outcomes to connect to executive priorities, not just engineering tickets. Both of these are operating-model questions, which is why the place to start is an honest read of where you sit today, using the FinOps cost maturity model, the sibling guide to this one. From there, a FinOps implementation sequences the capabilities into the Lock and Run stages of our See, Cut, Lock, Run method so the framework becomes operating reality rather than a slide.
The FinOps Operating Model Blueprint translates the 2026 Framework domains, scopes, and capabilities into a concrete operating model with owners, cadence, and reporting.
Common questions about the FinOps Framework 2026 update
What is new in the 2026 FinOps Framework?
The 2026 FinOps Framework adds Executive Strategy Alignment as a new Capability in the Manage the FinOps Practice domain, deepens the Scopes construct with richer guidance and more Technology Category pages, and formalizes the convergence of FinOps with adjacent disciplines such as sustainability. It also updates several Capabilities to apply across all technology categories, not just public cloud.
What are FinOps Scopes?
A FinOps Scope is a defined segment of spending across technology categories, aligned to a business construct such as a product, cost center, or environment, that guides how FinOps is applied to maximize technology value. Scopes were added as a core element in the 2025 Framework and deepened in 2026 to act as the mechanism that translates business strategy into FinOps activity, beyond just public cloud.
Did the FinOps phases change in 2026?
No. The three FinOps phases remain Inform, Optimize, and Operate, the iterative lifecycle teams cycle through. The 2025 and 2026 updates changed the Principles, Domains naming, Scopes, and Capabilities, but the Inform, Optimize, Operate phases were not renamed or restructured.
Written by Morten Andersen and reviewed by Fredrik Filipsson, applying our See, Cut, Lock, Run method. Independent and vendor neutral.
Cloud pricing and service behavior change frequently. Verify the specifics in this guide against the providers’ own current documentation and the FinOps Foundation: FinOps Foundation Framework ↗ and FinOps Rate Optimization capability ↗. This article also reflects Cloud Cost Room’s hands-on, vendor-neutral engagement experience.