What it is
The FinOps Foundation defines FinOps as an operational framework and cultural practice that maximises the business value of technology through collaboration between engineering, finance and business teams.
Applied to data and AI, it means treating the cost of a query, a pipeline or a model as something teams can see, attribute and decide about, and not as a bill that arrives afterwards.
Why it matters
In the 2026 State of FinOps survey, 98% of respondents said they manage AI spend, against 31% two years earlier. Cost management has moved from cloud bills to AI and data workloads.
The survey had 1,192 respondents and is of the FinOps community, so it overstates practice in organisations at large. DII read the press release, not the report.
The problem it addresses
DII editorial view
Usage-based platforms turn design choices into bills that arrive later and belong to nobody. Cost is reported in total, not against the product or team that caused it, so nobody can judge whether a workload is worth what it costs.
Business and organisational relevance
DII editorial view
The point is shared accountability. Engineers control what drives cost, finance sees the bill and the business sees the value; none of them can manage it alone.
Practical use cases
- Attributing data and AI platform cost to products or teams
- Reviewing unit cost alongside the value delivered
- Deciding whether a workload is worth what it costs to run
Benefits and opportunities
- Cost becomes a design consideration, not a surprise
- Spending decisions are made by people who can see both cost and value
Risks, limitations and dependencies
- Cost reporting with no one empowered to act on it
- Optimising cost for workloads whose value was never measured
- Shared platforms where cost cannot be attributed to a team
Prerequisites for adoption
DII editorial view
- Cost that can be attributed to a product or team
- A forum where engineering, finance and the business meet regularly
- Some measure of the value each workload delivers
Implementation considerations
- Attribute cost first. Attribute data and AI platform cost to products or teams before trying to reduce it.
- Look at unit cost with value. Review unit cost alongside value at a regular cadence.
- Involve all three groups. Engineering, finance and the business each hold part of the picture.
The DII Radar assessment
Approved DII Radar assessment
DII assesses FinOps for Data and AI Platforms as High relevance, with direction Rising. Its strategic impact is assessed as High and its enterprise adoption as Scaling. It is one of the ten entries on the current Radar.
DII relevance is our assessment of current significance and momentum, based on evidence, market development and adoption. Direction is the observed trajectory of relevance and adoption. Strategic impact is the potential or current significance to enterprise data capability, and enterprise adoption is the extent of current real-world enterprise adoption; together they set the position on the Radar. The Radar is not a prediction, vendor comparison or performance ranking.
Evidence basis: Linux Foundation press release on the State of FinOps 2026 survey, 19 February 2026 (1,192 FinOps practitioners); FinOps Framework (FinOps Foundation).
See FinOps for Data and AI Platforms on the Radar →
What to consider next
DII editorial view
- Attribute data and AI platform cost to products or teams
- Review unit cost alongside value at a regular cadence
- Give someone the authority to act on what the reporting shows
Evidence and references
The sources DII read for this explainer. Each entry gives what the record holds; nothing is added.
- State of FinOps survey press release (State of FinOps 2026) The press release was read; the full report was not. View source for reference 1 (external site)
- FinOps Framework Overview View source for reference 2 (external site)
Last reviewed: October 10, 2026 · Next review proposed for 10 January 2027.