Price OCI flexible shapes from separate OCPU-hour and GB-hour meters, including Ampere A1 and the Always Free grant.
OCI prices flexible shapes as two independent meters, so an instance costs OCPUs × the OCPU rate plus GB × the memory rate for every hour it runs. Because 1 OCPU is a full core, an x86 OCPU delivers two vCPUs while an Ampere A1 OCPU delivers one, which is why comparing OCI to per-vCPU pricing elsewhere needs the factor of two applied first. Splitting compute into OCPU and memory meters means you can shrink one without the other, and the free Ampere grant can cover a small always-on fleet entirely — confirm the current per-OCPU and per-GB rates in the Oracle Cloud cost estimator for your region before you budget.
OCI Compute Cost
monthly = instances × hours × (OCPUs × OCPU rate + GB × memory rate), after subtracting the free Ampere OCPU-hours and GB-hours.
monthly = instances × hours × (OCPUs × OCPU rate + GB × memory rate), after subtracting the free Ampere OCPU-hours and GB-hours. OCI prices flexible shapes as two independent meters, so an instance costs OCPUs × the OCPU rate plus GB × the memory rate for every hour it runs. Because 1 OCPU is a full core, an x86 OCPU delivers two vCPUs while an Ampere A1 OCPU delivers one, which is why comparing OCI to per-vCPU pricing elsewhere needs the factor of two applied first.
Splitting compute into OCPU and memory meters means you can shrink one without the other, and the free Ampere grant can cover a small always-on fleet entirely — confirm the current per-OCPU and per-GB rates in the Oracle Cloud cost estimator for your region before you budget.
This calculator takes 8 inputs: Instance shape, OCPUs per instance, Memory per instance, Number of instances, Price per OCPU-hour, Price per GB-hour of memory, Billed hours per month, Apply the monthly Ampere free grant. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.
No. On x86 shapes one OCPU is a physical core with two hyper-threads, so it is billed as one OCPU but shows up as two vCPUs in the guest. On Ampere A1 one OCPU is one physical Arm core and one vCPU, which is why the vCPU total here changes with the shape you pick.