Stack the main OCI savings levers — idle resources, right-sizing, Ampere migration and commitments — into one number.
Savings levers overlap, so applying each percentage to the original bill overstates the total badly. This model applies them in sequence — delete the idle, right-size what is left, move a share of that to Ampere, then discount the residual with a commitment — which is both smaller and achievable. Ampere is usually the largest single lever on OCI because the per-OCPU price gap is around 60% and most stateless workloads recompile or run unchanged on Arm, while unattached volumes are pure waste that keeps billing after the instance is long gone. Confirm current rates and your own commitment discount in the Oracle Cloud cost estimator and your Universal Credits agreement.
OCI Cost Optimization
Levers are applied in sequence so they never double-count: idle spend is removed first, right-sizing applies to what remains, Ampere migration to what remains after that, and the commitment discount to the residual bill.
Levers are applied in sequence so they never double-count: idle spend is removed first, right-sizing applies to what remains, Ampere migration to what remains after that, and the commitment discount to the residual bill. Savings levers overlap, so applying each percentage to the original bill overstates the total badly. This model applies them in sequence — delete the idle, right-size what is left, move a share of that to Ampere, then discount the residual with a commitment — which is both smaller and achievable.
Ampere is usually the largest single lever on OCI because the per-OCPU price gap is around 60% and most stateless workloads recompile or run unchanged on Arm, while unattached volumes are pure waste that keeps billing after the instance is long gone. Confirm current rates and your own commitment discount in the Oracle Cloud cost estimator and your Universal Credits agreement.
This calculator takes 10 inputs: Current monthly OCI spend, Share of spend that is compute, Compute that is idle or stopped but provisioned, Compute that is oversized, Saving on each oversized instance, x86 compute that could run on Ampere, Saving from moving to Ampere, Unattached block volumes, Block volume price per GB-month, Discount from an annual Universal Credits commitment. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.
Because they compete for the same spend. An instance that is idle cannot also be right-sized, and an instance you have already right-sized offers less absolute saving when it moves to Ampere. Applying the levers in sequence gives a total you can actually deliver.