The Foundation defines FinOps 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.”
The name joins finance and DevOps. The premise is that accountability for technology spend belongs with the teams that create it, not in one central function. FinOps began with cloud billing. The Framework now reaches software, AI, data platforms and the data center as well.
At the sourcefinops.org/framework. Framework content by the FinOps Foundation, licensed under CC BY 4.0.
Teams collaborate. Business value drives decisions. Everyone owns their usage. Data is accessible, timely and accurate. FinOps is enabled centrally. The variable cost model is an advantage.
Inform, Optimize and Operate. They cycle, and different teams work different phases at once.
Understand usage and cost. Quantify business value. Optimize usage and cost. Manage the FinOps practice.
Crawl, Walk and Run, applied capability by capability rather than to the organization as a whole. The goal is the right maturity for the value at stake.
Six core, from practitioner to leadership, and five allied, including IT financial management and TBM.
MagicOrange is a Premier Sponsor and Governing Board member of the FinOps Foundation.
Only two of sixteen Governing Board members have a foot in both ITFM and FinOps, and MagicOrange is one of them.
| Framework element | Where it runs |
|---|---|
| Understand usage and cost | Data Studio, included with every capability: direct billing connections for Azure, AWS and Google Cloud, FOCUS normalization and a formal sign off gate. FinOps adds daily allocation and anomaly detection. |
| Quantify business value | Budgeting and Forecasting for planning and forecasting on live actuals. Enterprise Allocation Modeling for unit economics, fully loaded with the people. |
| Optimize usage and cost | FinOps: commitment coverage and optimization, and an insights and actions tracker that carries workflow, notification and status to a named owner. |
| Manage the practice | The Bill of IT in IT Financial Management for showback and chargeback, posted to the general ledger. AI Studio for assistants that work over your own model. |
| Intersecting disciplines | The point of the platform. FinOps signals land in the same model as the IT financial management allocation and the plan, so the work the Framework describes between them needs no manual hand-off. |
| Technology categories | Seven spend categories in three families: consumed, owned and human. The Framework leaves labor out by design. MagicOrange holds it as one of the seven. |
The Framework’s sustainability capability is not addressed: MagicOrange does not ingest carbon or emissions data. Kubernetes cost enters through the cloud billing feed and is not attributed at pod and namespace level today.
The billing data standard the Framework points to.
The Framework applied to AI spend.
The allied discipline.
Our framework.
