North’s FinOps Score measures commitment efficiency on a five-point scale. Learn how utilization and Estimated Savings Rate shape your score and how to improve it.
TL;DR
- A FinOps score gives teams a quick benchmark for tracking cloud financial performance and identifying where efficiency can improve.
- North.cloud calculates its score using utilization and the Effective Savings Rate (ESR), then maps performance to a normalized five-point scale.
- Service-level scores are weighted by spend to produce an overall architecture score.
- A score of four or higher represents the top 1% of efficient cloud spenders in North’s benchmark.
- Noros, North’s FinOps AI Agent, explains what is influencing the score and where commitment performance can improve.
- North’s Flexbot and Autobot help teams act on those insights by keeping commitment coverage optimized as usage changes.
The most expensive gaps in cloud spend are often the ones nobody sees. A team renews its Savings Plans, utilization looks healthy, and the dashboard stays green. Six weeks later, usage shifts and some commitments begin delivering less value. The savings gap grows before anyone notices.
This is the visibility problem a FinOps score helps solve. It gives teams a consistent way to track commitment performance as usage and savings change over time.
This post explains what a FinOps score measures, how North calculates it, and how Noros, North’s FinOps AI Agent, helps teams understand and improve their results.
What is a FinOps score?
A FinOps score is a metric used to assess cloud financial performance. Its meaning depends on the framework and the outcomes being measured.
Two common approaches include:
- Google Cloud’s FinOps Hub, which evaluates factors such as commitment coverage and the use of native optimization tools
- The FinOps Foundation’s maturity framework, which assesses organizational capabilities across process, adoption, governance, and automation
North’s FinOps Score answers a narrower question: how efficiently are your cloud commitments saving money?
North calculates the score from its commitment ledger using metrics such as:
- Commitment utilization
- Effective Savings Rate (ESR)
- Savings compared with on-demand pricing
- Service-specific discount potential
The result is a normalized five-point score for each commitment and service. North also combines those results into an overall architecture score.
This makes the FinOps Score a quick benchmark for commitment efficiency. It doesn’t measure rightsizing, anomaly detection, or every part of cloud cost optimization. Instead, it shows how effectively your existing commitments are performing across Amazon Web Services (AWS), Google Cloud Provider (GCP), and Microsoft Azure.
What does the FinOps Score measure?
North’s FinOps Score measures cloud cost optimization, which generally works across two complementary layers: resource optimization and rate optimization.
Resource optimization
Resource optimization reduces how much infrastructure your workloads consume. Common actions include:
- Rightsizing overprovisioned instances
- Removing idle or orphaned resources
- Scheduling workloads to run only when needed
- Redesigning inefficient workloads
Rate optimization
Rate optimization reduces the price paid for the infrastructure you use. The underlying resources remain the same, but discounted pricing lowers their cost.
Common rate optimization options include:
- AWS Savings Plans
- AWS Reserved Instances
- GCP Committed Use Discounts
- Azure Savings Plans
- Azure Reservations
North’s Rightsize feature supports resource optimization through machine learning-powered recommendations. The FinOps Score focuses only on rate optimization and commitment efficiency.
For a deeper look at how both layers work together, see the cloud resource management guide.
How North's FinOps Score works
North calculates the FinOps Score from commitments detected across your AWS, GCP, and Azure accounts. This includes supported commitments purchased directly from cloud providers or managed through North.
The score uses commitment-level metrics such as utilization and ESR. North then normalizes performance by service before assigning scores to individual commitments, services, and the overall architecture.
Each commitment and service receives its own score. North then combines the service-level results into an overall architecture score.
For example, a service representing 70% of commitment spend will affect the architecture score more than one representing 2%. This helps the score reflect the areas that matter most financially.
North’s Coverage page provides the context behind each score. The commitment ledger includes supported AWS, GCP, and Azure commitments purchased directly or managed through North.
For each commitment, teams can review:
- Utilization
- ESR
- Cost per hour
- Month-to-date savings
- Start and end dates
- Historical performance
Teams can also filter commitments, compare previous months, and export the ledger for further analysis. This makes it easier to identify which services are strengthening the architecture score and where commitment performance can improve.
How to improve your FinOps score with North
Improving your FinOps Score means closing the gap between your current commitment performance and the savings potential available for each service. These five actions can help strengthen commitment efficiency.
1. Start with your highest-spend services
The overall architecture score is weighted by spend. Services with the greatest financial impact therefore influence the score most.
A modest ESR improvement on your largest service can matter more than a larger improvement on a smaller one. Start with the services carrying the most commitment spend, then review weaker areas within each service.
Noros, North’s FinOps Agent, can help pinpoint which services are lowering your score. Try asking:
- “Which services are lowering my FinOps Score?”
- “Where is my largest ESR improvement opportunity?”
- “What is driving my lowest service-level score?”
Noros can then compare service-level scores, ESR, utilization, and spend to explain which areas have the greatest impact on your overall result.
2. Improve coverage for predictable usage
Coverage shows how much eligible usage receives commitment pricing. Low coverage leaves more usage exposed to on-demand rates.
The goal is not maximum coverage, but to cover stable baseline usage without creating unnecessary commitment risk.
Try asking Noros:
- “Where do I have commitment coverage gaps?”
- “Which services have predictable on-demand usage?”
- “Where could new commitments improve my score?”
Noros can surface uncovered usage and highlight services where additional coverage may improve rate performance.
3. Protect utilization as usage changes
Utilization measures how much of each purchased commitment is being used. Low utilization means part of that commitment is going unused.
Coverage and utilization describe different problems:
- Low coverage means eligible usage remains on-demand.
- Low utilization means purchased commitments are not fully consumed.
Usage can shift as workloads scale, move, or shut down. Review both metrics to understand whether your commitment posture still matches demand.
Try asking Noros:
- “Which commitments are underutilized?”
- “How are our Reserved Instances performing?”
- “Which commitments are producing the weakest ESR?”
Noros can connect utilization, ESR, and savings data to explain where existing commitments are losing efficiency.
4. Review expirations and historical performance
Commitment efficiency can change quickly when a Savings Plan or Reserved Instance expires. Historical trends also show whether recent changes are improving performance.
Use the CommitmentOps page to:
- Compare current and previous months
- Review upcoming expiration dates
- Track changes in utilization and ESR
- Identify services with declining scores
You can also ask Noros:
- “Are any commitments expiring soon?”
- “How has my FinOps Score changed over time?”
- “Which services declined this month?”
Noros can surface relevant changes and help explain what drove them.
5. Automate ongoing commitment management
Commitment performance changes as infrastructure grows, commitments expire, and usage shifts. Keeping coverage aligned requires regular forecasting, purchasing, and renewal decisions.
North provides two ways to automate that work:
- Flexbot manages commitments on North-owned accounts, giving teams access to three-year discount rates with month-to-month flexibility. North adjusts coverage as usage changes, helping teams capture deeper savings without taking on the same long-term exposure as traditional commitments.
- Autobot manages commitments on customer-owned accounts, building an adaptive ladder of commitments through smaller monthly purchases. Its machine learning-powered engine models usage daily, balances savings with flexibility, and adjusts future purchases as infrastructure evolves.
Flexbot reduces the operational and financial burden of managing commitments directly. Autobot gives teams configurable control while automating the modeling, purchasing, and renewal work behind their strategy.
Noros helps identify what is affecting your FinOps Score. Flexbot and Autobot help improve that performance by keeping commitment coverage closer to current usage over time.
See what your FinOps Score reveals inside North
Commitment efficiency changes as usage shifts, services grow, and agreements expire. A strong score today does not guarantee the same performance next quarter.
North’s FinOps Score provides a consistent benchmark for tracking those changes. It shows where commitments are delivering value and where utilization or ESR may be weakening.
Noros helps explain what is driving the score and where improvement is possible. Flexbot and Autobot help teams act on those findings by keeping commitment strategies aligned with changing usage.
Explore our free tier to see your FinOps Score and uncover your strongest commitment savings opportunities.