Reserved capacity on Oracle Cloud Infrastructure is a commitment to specific compute or service capacity over a defined term in exchange for a lower unit rate. It sits alongside the universal credits commit and burn model and the pay as you go model as a third pricing lever. Used well it cuts the cost of stable, predictable workloads. Used carelessly it locks the customer into capacity it does not need. This article sets out how to evaluate and negotiate reserved capacity.
This article is a companion to our cloud negotiation pillar and supports our cloud migration advisory service.
What Reserved Capacity Is
Reserved capacity is a commitment to a defined quantity of a specific resource, such as compute cores or database capacity, over a term of one to three years. In return for the commitment Oracle offers a discount against the pay as you go rate. The customer pays for the reserved capacity whether or not it uses it. The discount rewards the certainty the commitment provides Oracle.
Reserved capacity differs from the universal credits commitment. Universal credits commit a dollar amount that can be spent across any service. Reserved capacity commits to a specific resource at a specific size. The specificity is the source of both the deeper discount and the higher risk. A dollar commitment is flexible. A capacity commitment is not.
When Reserved Capacity Makes Sense
Reserved capacity delivers value for stable, predictable workloads that run continuously at a known scale. A production database that runs at a steady size, a core application that serves a constant user base, or a baseline of always on infrastructure are good candidates. The reservation matches the predictable consumption and the discount is captured cleanly.
The right way to think about reserved capacity is the baseline and peak split. Reserve the baseline that runs continuously and never goes away. Serve the peak with on demand capacity. Customers who reserve the baseline and flex the peak capture the discount without the lock in. Customers who reserve the peak pay for capacity that sits idle most of the time.
Reserved capacity is the wrong choice for variable, bursty, or uncertain workloads. A workload that scales up and down, a project with an uncertain future, or a migration that has not yet stabilised should not be reserved. The reservation locks in capacity the workload may not need, and the discount does not compensate for the idle capacity.
The Term Length Trade Off
Longer reservation terms carry deeper discounts. A three year reservation costs less per unit than a one year reservation. The trade off is flexibility. The three year term locks the customer in for longer and exposes it to the risk that the workload changes, the technology moves on, or the business needs shift.
The disciplined approach is to match the term to the confidence in the workload. A workload the customer is certain will run unchanged for three years justifies a three year reservation. A workload with a less certain future justifies a one year reservation even at a shallower discount. The premium for the shorter term is the price of flexibility, and that price is often worth paying.
The Capacity Type Lock
Reserved capacity is usually tied to a specific shape or generation of resource. When Oracle releases a newer, more efficient instance type, the customer holding a reservation on the older type cannot easily move to the newer one without forfeiting the reservation. Technology refresh cycles can strand a reservation on obsolete capacity.
The negotiation tactic is to seek flexibility to move the reservation to newer capacity types as they are released, or to negotiate a shorter term that aligns with Oracle's hardware refresh cadence. Buyers who lock into a long reservation on a specific capacity type accept the risk that the type becomes obsolete before the term ends.
The Stacking Strategy
The most efficient cloud cost structure stacks the three pricing models. Reserved capacity covers the predictable baseline. Universal credits cover the expected variable consumption. Pay as you go covers the unpredictable peaks. Each layer carries a different price and a different commitment, and the stack matches the price to the predictability of the demand.
Building the stack requires the customer to segment its workloads by predictability, which most organisations do not do by default. The segmentation work is the foundation of an efficient cloud cost position. Our commit and burn article covers the universal credits layer and the OCI universal credits deal page covers the contractual framing.
The Negotiation Levers
Reserved capacity pricing is negotiable like every other element of an Oracle cloud deal. The discount against pay as you go, the flexibility to change capacity types, the treatment of unused reserved capacity, and the renewal terms are all on the table. Oracle's published reserved capacity pricing is a starting point, not a fixed rate, for any customer of meaningful size.
The tactic is to negotiate reserved capacity as part of the overall cloud deal rather than as a standalone purchase. Bundled with a universal credits commitment and a migration funding package, the reserved capacity terms can be improved beyond what a standalone negotiation would achieve. Our Oracle OCI product page covers the platform context.
The Review Cadence
A reservation is not a set and forget decision. The customer should review its reservations against actual utilisation on a regular cadence. Under utilised reservations signal that the customer reserved too much. Consistently exceeded reservations signal an opportunity to reserve more at the next renewal. The review turns the reservation from a fixed cost into a managed one.
The governance discipline should track reservation utilisation alongside the broader cloud consumption picture, with a named owner accountable for the efficiency of the reservation portfolio. Customers who manage reservations actively keep their cloud costs aligned to their actual needs. Our cloud migration advisory service supports this ongoing discipline.
Where to Read Next
For commit and burn mechanics see our commit and burn article. For migration discount tactics see our migration discount article. For the broader cloud strategy see our cloud negotiation pillar. The Oracle Negotiation Playbook covers the full methodology.