Score cloud governance across cost allocation, policy control, commitment management and automation, and get one next action.
Allocation carries the heaviest weight because nothing else in FinOps works without it: you cannot enforce a policy, defend a commitment or explain an anomaly for spend you cannot attribute. Coverage and utilisation are weighted equally in the commitment pillar, since buying more commitments while utilisation is poor makes the position worse rather than better. Governance is invisible until an audit, an overrun or an incident makes it visible, and a single score with a weakest-pillar output turns it into one concrete next action instead of another dashboard. The weights are a sensible default rather than a standard — adjust them to your own operating model.
Cloud Governance Score
score = allocation × 30% + control × 25% + commitments × 25% + automation × 20%, where each pillar is a weighted blend of its own coverage inputs.
score = allocation × 30% + control × 25% + commitments × 25% + automation × 20%, where each pillar is a weighted blend of its own coverage inputs. Allocation carries the heaviest weight because nothing else in FinOps works without it: you cannot enforce a policy, defend a commitment or explain an anomaly for spend you cannot attribute. Coverage and utilisation are weighted equally in the commitment pillar, since buying more commitments while utilisation is poor makes the position worse rather than better.
Governance is invisible until an audit, an overrun or an incident makes it visible, and a single score with a weakest-pillar output turns it into one concrete next action instead of another dashboard. The weights are a sensible default rather than a standard — adjust them to your own operating model.
This calculator takes 9 inputs: Mandatory tag coverage, Teams receiving a showback report, Resources compliant with guardrail policy, Privileged accounts reviewed this quarter, Accounts with a budget and an alert, Commitment coverage, Commitment utilisation, Resources managed by infrastructure as code, Spend covered by anomaly detection. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.
A resource created by hand has no owner, no tags applied consistently and no review trail, so every other governance control has to chase it after the fact. Provisioning through code moves tagging, sizing and policy checks to before the resource exists, which is the only way coverage stays high as the estate grows.