OCI flexible shapes let you choose the precise number of OCPUs and the amount of memory for an instance, independently, rather than picking from a fixed ladder of sizes. The cost benefit is direct: instead of jumping from, say, 4 cores to 8 just to add a little capacity, you set exactly the cores you need and pay per OCPU. On real estates this is one of the largest single compute savings on OCI, because fixed-size instances almost always carry cores that nothing ever uses.
This article is part of our Oracle cloud cluster. For the full set of OCI cost levers, read the complete guide to Oracle Cloud (OCI) cost optimization, the pillar this article links up to. Flexible shapes are a core tool in the Cut step of our See, Cut, Lock, Run method, and they pair directly with rightsizing.
What flexible shapes actually do
A flexible shape exposes OCPU count and memory as settings you choose at launch and can change later, within the shape's supported ranges. Available flexible families have included the AMD E-series and the Arm-based Ampere A1 compute, among others. Because billing is driven by the OCPU and memory you select, the price scales with the resources rather than snapping to predefined tiers. The practical effect: you can size an instance to its real demand instead of to the nearest fixed box above it.
Where the saving comes from
The saving is the gap between the fixed tier you would have picked and the exact size you actually need. Fixed sizing forces rounding up, and rounding up on compute is expensive at scale. A fleet of instances each carrying two or three unused cores adds up to a large, invisible monthly charge. Flexible shapes let you reclaim that gap. The biggest wins come when you migrate an estate of oversized fixed instances onto flexible shapes sized from real utilization, which is exactly the process in the sibling guide on how to rightsize OCI compute shapes.
Switching to a flexible shape does not save money on its own. The saving comes from setting the OCPU and memory to real demand. A flexible shape provisioned generously is just as wasteful as a fixed one. Always pair the shape change with a utilization read.
When to use flexible shapes
Use them as the default for almost any general-purpose workload where you can observe utilization and tune to it: web and application tiers, internal services, batch workers, and most databases that do not require a specialized shape. They are especially valuable for workloads with steady, well-understood demand, because you can size tightly and trust the buffer. For highly variable or bursty workloads, size to the sustained peak and consider scaling out rather than over-provisioning a single large instance.
Want every instance sized to real demand?
We migrate oversized fixed shapes onto flexible shapes set from your actual utilization, across every compartment, and lock the result so it holds. On the performance model, you pay only from realized savings. No savings, no fee.
Book an OCI cost audit →The traps to avoid
The first trap is provisioning a flexible shape as generously as the fixed one it replaced, which captures none of the saving. The second is forgetting that memory and OCPU are set independently, so a memory-bound workload may need more memory at a lower core count, and a compute-bound one the reverse; sizing both to demand is the point. The third is treating the initial size as permanent. Demand changes, so revisit flexible-shape sizing on the same cadence as the rest of your cost review, captured in the OCI cost optimization checklist.
| Aspect | Fixed shape | Flexible shape |
|---|---|---|
| Sizing | Predefined tiers, round up | Exact OCPU and memory |
| Billing | Per tier | Per OCPU and memory chosen |
| Waste profile | Pays for unused cores in the tier | Pays only for sized resources |
| Best for | Workloads that match a tier exactly | Most general-purpose workloads |
OCI flexible shape families, their OCPU and memory ranges, and per-OCPU pricing reflect the platform as of May 2026. Confirm current flexible shape availability and limits in Oracle's documentation before sizing, as shape families and ranges change.
The OCI Cost Optimization Field Guide includes the sizing worksheet for converting utilization data into flexible-shape OCPU and memory settings. It is the downloadable companion to this explainer.
The short version
Flexible shapes let you set exact OCPU and memory and pay per core, eliminating the rounding-up waste built into fixed tiers. The saving comes from sizing to real demand, not from the shape change itself, so always pair the switch with a utilization read and revisit it as demand moves. When you want every instance sized to actual demand by an independent team, that is what our OCI cost optimization service delivers.