reported adopting cloud-native techniques
CNCF described cloud-native adoption as near-universal among surveyed organizations.
CNCF Annual Cloud Native Survey · 2026 ↗Updated 2026-10-04 · Cloud economics
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.
CNCF described cloud-native adoption as near-universal among surveyed organizations.
CNCF Annual Cloud Native Survey · 2026 ↗The survey included 861 respondents from large cloud-spending organizations.
State of FinOps 2025 · 2025 ↗The 2025 State of FinOps report showed AI cost responsibility expanding quickly.
State of FinOps 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 →