Skip to content
Calcrivo

OCI Health Score Calculator

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

Inputs

%
%
%
%

Penalised hard, because it buys nothing at all.

%
%
%
%
%

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

  1. Values used

    Production workloads spread across availability domains = 55 %; Volumes with a tested restore = 65 %; Compute running on Ampere = 20 %; Spend on idle or unattached resources = 9 %; Compartments monitored by Cloud Guard = 70 %; Resources encrypted with customer-managed Vault keys = 45 %; IAM policies reviewed in the last year = 60 %; Resources managed by Resource Manager stacks = 50 %; Critical resources with an alarm = 62 %

  2. 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.

  3. Overall Health Score

    = 56.6 / 100

  4. Grade

    = D — Weak

  5. Resilience Pillar

    = 60.5 / 100

  6. Cost Pillar

    = 46.4 / 100

  7. Security Pillar

    = 59.5 / 100

  8. Operations Pillar

    = 56.6 / 100

How it works

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

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.

You might also need