What Is FinOps and How to Start in 2026

FinOps is how a company gets the most value from what it spends on technology. The FinOps Foundation defines it as "an operational framework and cultural practice which maximizes the business value of technology, enables timely data-driven decision making, and creates financial accountability through collaboration between engineering, finance, and business teams." In practice, engineers see what their choices cost, finance gets numbers it can forecast, and leadership decides where the money goes. What is FinOps?

To start, put your cost data in one place, give every dollar an owner, fix the waste you can see, and meet once a month to review the numbers. Below: what changed in 2026, the principles, phases, and capabilities of the FinOps Framework, the first KPIs to track, and the four stages the Foundation recommends for a new practice.

What does FinOps stand for?

FinOps joins Finance and DevOps. The Foundation lists other names for the same practice, among them Cloud Financial Management and Cloud Cost Management, and calls "Cloud Financial Operations" an incorrect expansion. It also says FinOps is about value, not only saving money: a team can spend more on a product that earns more and still run FinOps well.

What changed in FinOps in 2026?

• The definition now says "technology" where it used to say "cloud", and the Foundation's mission moved from the value of cloud to the value of technology. 2026 FinOps Framework.
• The Framework added a capability, Executive Strategy Alignment, and renamed six others, among them Usage Optimization (formerly Workload Optimization) and Governance, Policy & Risk (formerly Policy & Governance).
• Technology categories now have their own pages: Public Cloud, SaaS, Data Center, Data Cloud Platforms, and AI. Technology categories.
• FOCUS, the open specification for billing data, reached version 1.4 in June 2026. AWS, Azure, Google Cloud, and Oracle Cloud already export FOCUS data from their consoles, at earlier versions of the spec. FOCUS 1.4 · FOCUS data generators.
• In the State of FinOps 2026, 98% of practitioners manage AI spend, up from 63% in 2025 and 31% in 2024, and FinOps for AI is the top priority for the year ahead. State of FinOps 2026.

The same survey, 1,192 practitioners managing more than $83 billion of annual cloud spend, shows the scope widening past cloud: 90% manage SaaS or plan to, 64% licensing, 57% private cloud, and 48% data center.

What are the six FinOps principles?

The Foundation lists six, in no particular order. FinOps principles.

• Teams need to collaborate.
• Business value drives technology decisions.
• Everyone takes ownership for their technology usage.
• FinOps data should be accessible, timely, and accurate.
• FinOps should be enabled centrally.
• Take advantage of the variable cost model of the cloud.

Ownership is the one that changes behavior most. When the team that launches a resource sees its cost the next day, it sizes the next one differently.

What are the three phases of FinOps?

Inform, Optimize, and Operate. Some vendors call them pillars; the Foundation calls them phases, and teams cycle through them over and over, with different people working different phases at different paces. FinOps phases.

What are the FinOps domains and capabilities?

The Framework groups 22 capabilities into four domains. The domains run in parallel, not as steps in order. FinOps domains.

Who does FinOps?

The Foundation names six core personas: the FinOps practitioner, Engineering, Finance, Product, Procurement, and Leadership. Five allied ones sit around them: IT asset management, IT financial management, IT service management, Security, and Sustainability. In a small company, one person can cover several. FinOps personas.

The practice usually lives in technology. In the State of FinOps 2026, 78% of FinOps teams report to the CTO or CIO, and 81% work as a central team that enables others or as a hub with spokes in each business unit.

How mature does a FinOps practice need to be?

The Foundation measures maturity per capability, as Crawl, Walk, or Run, and says the goal is never Run everywhere: mature the capabilities that bring the most value. Its sample KPIs for three of them. FinOps maturity model.

How do you start a FinOps practice?

The Foundation's Adopting FinOps guide, updated in October 2026, lays out four stages. A practice can start from a leadership mandate, from a team that sees the problem, or from one person. Adopting FinOps.

1. Research

Collect the cost and usage data: the AWS Cost and Usage Report, Azure's usage and charges, Google Cloud's billing export, Oracle Cloud's cost reports. Review your account structure and tags, your rates, and the trend against budget. Look for idle resources, schedules, and rightsizing, compute a few KPIs, and talk to finance and engineering to find your first champions.

2. Propose

Say what you need: approval, budget, people, or a sponsor. Consider a pilot in one business unit, and pitch leadership first, with the current state, a roadmap, and the future you want.

3. Prepare

Decide who is on the team and where it reports. Pick a handful of capabilities to begin with. New practices usually start with data ingestion, allocation, and reporting; forecasting and budgeting; usage and rate optimization; education; and tools. Keep each process to the minimum that works.

4. Launch

Announce the practice, train people, ship the easy savings and show them, roll out the reports, and hold a monthly cost review. Don't try every capability at once.

Each cloud publishes its own starting guide. AWS frames Cloud Financial Management as See, Save, Plan, and Run. Microsoft's implementing guide runs from training through the capabilities to FOCUS and tools. Google's lists four building blocks: accountability, measurement, optimization, and tools. AWS · Microsoft · Google Cloud.

Which FinOps KPIs should you track first?

• Share of cost allocated to an owner. Without it, nobody acts on the rest. Aim for 70% first.
• Commitment discount coverage: the share of steady usage on Savings Plans, Reserved Instances, or committed use discounts.
• Forecast variance: how far the month's actual cost lands from the forecast.
• One unit cost the business understands, such as cost per customer or per transaction.

The Foundation keeps a library of KPI formulas you can adopt as written. FinOps KPIs.

Do you need a FinOps tool to start?

No. AWS Cost Explorer, Microsoft Cost Management, and Google Cloud's cost tools are free, and they're enough for the Research stage. A tool earns its place when you need several clouds, SaaS, and AI in one view, allocation rules your tags can't express, or someone to ship the savings. Our guides compare the FinOps platforms, the open source FinOps tools, and what FinOps tools cost.

How do you learn FinOps?

The Foundation's Introduction to FinOps is a free course of about 30 minutes. The FinOps Certified Practitioner, its entry certification, costs $500 for the self-paced course and exam, with no prerequisites, and stays valid for 24 months. Courses and exams run in English, and the Practitioner also in Japanese. Introduction to FinOps · FinOps Certified Practitioner.

Common mistakes when starting FinOps

• Treating FinOps as a cost-cutting project with an end date, instead of a monthly practice.
• Buying commitments before cleaning up idle resources and rightsizing, which locks a discount onto waste.
• Building reports without owners. A cost nobody owns doesn't go down.
• Leaving SaaS and AI out of scope while they grow faster than the cloud bill.
• Counting estimated savings instead of checking the next bill.

Where LevelFour fits

LevelFour, which we make, puts your Cloud, SaaS, and AI spend in one view, allocates it with virtual tags, and ships the savings it finds: applied in your cloud or SaaS account with access scoped to that one change, as a pull request to your infrastructure code, or as manual steps. Savings Audit confirms each saving on the bill. Cloud Savings costs 30% of realized savings, and plans start at $30 a month.

See what LevelFour can save you in 5 minutes, with read-only access.

Frequently asked questions