OCI Health Score Calculator

Score an OCI tenancy across resilience, cost, security and operations, and see which pillar to fix first.

About OCI Health Score Calculator

Each pillar is scored from coverage percentages you can read out of Cloud Guard, the Vault, Resource Manager and Monitoring, then combined with resilience and security carrying the heaviest weight. Idle spend is penalised four points per percent because, unlike a low Ampere adoption figure, it delivers nothing in return. A single score makes a tenancy comparable month over month and across teams, and the weakest-pillar output converts it into one concrete next action rather than a dashboard nobody opens. Untested backups and unmonitored compartments are the two inputs that most often turn out to be worse than the team assumed.

Formula

OCI Health Score

score = resilience × 0.30 + security × 0.30 + cost × 0.20 + operations × 0.20, where each pillar blends its coverage inputs and idle spend is penalised at four points per percent.

resilience pillar: Availability-domain spread weighted with tested restore coverage
cost pillar: Ampere adoption against a heavy penalty for idle spend
security pillar: Cloud Guard coverage, customer-managed keys and IAM policy review

Worked example

With the default values below, OCI Health Score Calculator returns Overall Health Score of 56.6. Change any input above and every figure here is recalculated in your browser.

Inputs used

Production workloads spread across availability domainsaccepts 0–100 %: 55 %
Volumes with a tested restoreaccepts 0–100 %: 65 %
Compute running on Ampereaccepts 0–100 %: 20 %
Spend on idle or unattached resourcesaccepts 0–100 %: 9 %
Compartments monitored by Cloud Guardaccepts 0–100 %: 70 %
Resources encrypted with customer-managed Vault keysaccepts 0–100 %: 45 %
IAM policies reviewed in the last yearaccepts 0–100 %: 60 %
Resources managed by Resource Manager stacksaccepts 0–100 %: 50 %
Critical resources with an alarmaccepts 0–100 %: 62 %

Results

Overall Health Score: 56.6 / 100
Grade: D — Weak
Resilience Pillar: 60.5 / 100
Cost Pillar: 46.4 / 100
Security Pillar: 59.5 / 100
Operations Pillar: 56.6 / 100
Fix This First: Cost — delete idle and unattached resources, then migrate suitable workloads to Ampere
Risk Band: Medium

Step by step

1Values used
2OCI Health Score
3Overall Health Score= 56.6 / 100
4Grade= D — Weak
5Resilience Pillar= 60.5 / 100
6Cost Pillar= 46.4 / 100
7Security Pillar= 59.5 / 100
8Operations Pillar= 56.6 / 100

Assumptions and limits

The result is derived only from the 9 inputs listed above. Anything not among them is not part of the calculation.
In particular, this calculator does not take inflation, tax or compounding frequency into account.
Figures are rounded for display to 1 decimal place, so totals built from several rounded parts can differ slightly from the unrounded arithmetic.

How these calculators are built and tested is described on the Methodology page. If a figure looks wrong, please report it.

Frequently Asked Questions

How is OCI Health Score calculated?

score = resilience × 0.30 + security × 0.30 + cost × 0.20 + operations × 0.20, where each pillar blends its coverage inputs and idle spend is penalised at four points per percent. Each pillar is scored from coverage percentages you can read out of Cloud Guard, the Vault, Resource Manager and Monitoring, then combined with resilience and security carrying the heaviest weight. Idle spend is penalised four points per percent because, unlike a low Ampere adoption figure, it delivers nothing in return.

Why does OCI Health Score matter?

A single score makes a tenancy comparable month over month and across teams, and the weakest-pillar output converts it into one concrete next action rather than a dashboard nobody opens. Untested backups and unmonitored compartments are the two inputs that most often turn out to be worse than the team assumed.

What values do I need to enter?

This calculator takes 9 inputs: Production workloads spread across availability domains, Volumes with a tested restore, Compute running on Ampere, Spend on idle or unattached resources, Compartments monitored by Cloud Guard, Resources encrypted with customer-managed Vault keys, IAM policies reviewed in the last year, Resources managed by Resource Manager stacks, Critical resources with an alarm. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.