FinOps Maturity Model
A framework defining organizational maturity levels — Crawl, Walk, Run — for managing cloud financial accountability, cost optimization, and business value alignment.
The FinOps Maturity Model, developed by the FinOps Foundation, describes a progressive journey through three capability levels — Crawl, Walk, and Run — across the domains of cloud financial management. FinOps (Financial Operations) is the practice and culture that brings together finance, technology, and business teams to make data-driven spending decisions about cloud infrastructure, balancing cost, performance, and business value. As organizations' cloud footprints grow, the absence of FinOps discipline leads to runaway spending, budget overruns, and the inability to connect cloud investment to business outcomes — problems that affect financial reporting accuracy, resource allocation decisions, and strategic planning.
At the Crawl stage, organizations have basic visibility into cloud spending but limited governance. Tagging practices are inconsistent, making cost allocation to business units or products unreliable. Showback reports — informational cost attribution without financial accountability — are beginning to emerge. Forecasting relies on prior-period actuals with minimal capacity planning. Reserved Instance or Savings Plan coverage is low, with most workloads running on on-demand pricing. The primary goal at this stage is establishing a baseline of visibility and beginning to build cross-functional awareness that cloud costs are a shared business responsibility, not solely an IT budget line item.
At the Walk stage, cost allocation is established and reliable. Consistent tagging policies are enforced through automation, and chargeback or showback reports are distributed to product and engineering teams on a regular cadence. Reserved Instance and Savings Plan coverage targets are set and tracked. Engineers are aware of the cost implications of their architectural choices and have access to cost data in the tools they use daily — IDE plugins, dashboards integrated into existing monitoring platforms. Anomaly detection alerts notify engineers and finance partners when spending deviates from forecasts, enabling rapid response to cost events. Unit economics — cost per transaction, cost per user, cost per API call — are defined and tracked for key business capabilities.
At the Run stage, FinOps is embedded in engineering culture and business planning cycles. Cloud costs are forecasted with high accuracy using bottom-up capacity models combined with top-down business growth projections. Real-time cost attribution is available at the resource and workload level, enabling teams to make immediate trade-off decisions. Automated optimization — right-sizing recommendations applied automatically with guardrails, automatic scaling policies tuned to cost-performance curves, intelligent tiering for storage — significantly reduces waste without requiring manual intervention. Cloud unit economics are incorporated into product pricing models, investor reporting, and board-level business performance reviews. For publicly traded companies subject to SOX or financial services firms under DORA, FinOps at the Run level also means that cloud cost controls are auditable financial controls with documented policies, enforcement mechanisms, and exception management processes.
Compliance-Native Architecture Guide
Design principles and a structured checklist for building software that is compliant by default — not compliant by retrofit. Covers data architecture, access controls, audit trails, and vendor due diligence.