in public-cloud spend represented by respondents
The survey included 861 respondents from large cloud-spending organizations.
State of FinOps 2025 · 2025 ↗Updated 2026-10-04 · Compliance
A source-first view of control coverage, exception discipline and the freshness of operating evidence. Published findings provide context; the measurement framework shows what to calculate inside your own environment.
01 / Published evidence
Each figure links directly to the organization that published it. Vendor telemetry and community surveys are labelled rather than blended into one invented industry average.
The survey included 861 respondents from large cloud-spending organizations.
State of FinOps 2025 · 2025 ↗IBM reported this global average in its 2026 Cost of a Data Breach research.
IBM 2026 Cost of a Data Breach · 2026 ↗GitHub’s dataset shows most day-to-day organizational development happens privately.
GitHub Octoverse 2025 · 2025 ↗02 / Your baseline
Use these formulas consistently for at least one complete operating cycle. Keep scope, exclusions and collection dates beside the result.
Automated controls ÷ applicable controls × 100
Median days an approved exception remains open
Evidence items inside their refresh window ÷ all required items × 100
03 / Interpretation
Segment results by environment, workload owner and business criticality. A falling average can hide one critical service getting worse; a rising count can simply reflect better discovery.
Related benchmarks
Gritt can map the data sources, calculate a defensible baseline and implement the changes behind it.
Build the baseline →