Oracle Cloud at Customer Licensing: A CIO Playbook (White Paper)
The infrastructure fee is a four year commitment that survives zero consumption, and license included rates run about 3.8 times BYOL. Decide both before you sign, not after.
Prepared by Redress Compliance · June 2026 · Representative Oracle estate scenario (benchmark scenario, not a quote)
Executive Summary
Oracle Cloud at Customer puts Oracle managed cloud hardware inside your data center and bills it like OCI. The structure is hybrid: a fixed infrastructure subscription committed for a minimum four year term, plus metered consumption for every database or compute hour you activate on top of it.
The licensing decision dominates the economics. On Exadata Database Service, Oracle's list rate is roughly $0.81 per OCPU hour under BYOL against $3.10 license included, about 3.8 times more. Whether your existing licenses transfer cleanly, with options and support intact, is worth more than any infrastructure discount.
In our representative 32 OCPU benchmark scenario, five year cost lands at $2.11M on premises, $1.62M on OCI public regions, and $1.75M on Cloud at Customer after Support Rewards. You are paying roughly $28k a year for keeping the hardware in your own hall. That premium is often justified; signing it blind is not.
This paper covers what Cloud at Customer includes and excludes, the license transfer rules, consumption math against traditional license math, the refresh and lock in mechanics, the five year TCO model, and the negotiation moves to make before signature.
What Cloud at Customer Includes, and What It Does Not
Cloud at Customer is a family, not a product. The contract you sign depends on which member you deploy, and the licensing posture differs across them.
| Deployment | What it is | Licensing posture |
|---|---|---|
| Exadata Database Service on Cloud@Customer | Oracle owned Exadata rack in your data center, Gen2 remote control plane, Oracle operates the infrastructure. | Fixed infrastructure fee plus metered database OCPU or ECPU consumption, BYOL or license included. |
| Compute Cloud@Customer | Rack scale OCI compute and storage in your hall for general workloads. | Infrastructure subscription plus OCI style consumption. Oracle software running on it still needs licenses. |
| Autonomous Database on Cloud@Customer | Autonomous Database running on dedicated Exadata infrastructure on premises. | Same hybrid model. ECPU metered, BYOL or license included per database. |
| OCI Dedicated Region | A full OCI region in your facility. The flagship, with a far larger commitment. | Multimillion dollar annual minimum commitment over multiple years, all services metered. |
What the subscription includes: the hardware, Oracle ownership and operation of that hardware, the control plane, infrastructure patching, and break fix. What it does not include: your database licenses under BYOL, the support stream on those licenses, power, space and cooling in your facility, network into your core, migration effort, and disaster recovery capacity, which is a second subscription.
License Transfer Rules: BYOL, Cloud Lift, and the Partition Exception
BYOL is where Cloud at Customer business cases are won or quietly lost. The conversion arithmetic is published and mechanical. The eligibility conditions are not on the slide.
Under Oracle's cloud licensing policy, one Database Enterprise Edition processor license covers two OCPUs of Exadata Database Service. Standard Edition 2 converts at four OCPUs per processor license, with service caps. On ECPU metered services the published ratios are higher in number but equivalent in capacity.
Three conditions matter more than the ratios:
| Condition | The mechanic | The trap if missed |
|---|---|---|
| Active support | Every license you bring must carry active, paid support for the full period it is deployed in the service. | Lapsed support voids BYOL eligibility. Oracle can rebill the gap at license included rates. |
| Option matching | RAC, Partitioning, Advanced Security and the packs must be licensed on premises if you enable them in the service under BYOL. | Enabling RAC on a BYOL database without RAC licenses is a compliance event, metered and visible to Oracle. |
| The repurpose rule | Licenses assigned to BYOL cannot simultaneously cover on premises servers. Transfer means transfer. | Double counting surfaces in the next audit. The Cloud at Customer telemetry makes it trivial to find. |
Cloud Lift is Oracle's funded migration engineering program. It is real and worth taking, but it is scoped by Oracle, staffed by Oracle, and timed to Oracle's quarter. Take the funding, keep your own migration plan, and never let a free service set your cutover date.
The partition exception is the quiet advantage. On premises, Oracle treats VMware and most software partitioning as soft, so you license the full physical estate. Cloud at Customer is an authorized environment where only activated OCPUs count.
Capacity on demand means dormant cores in the rack cost nothing in license terms until you activate them. For estates trapped by the VMware licensing dispute, this exception alone can fund the move.
Consumption Math Versus Traditional License Math
Traditional math is capital plus annuity: buy the processor license once, pay 22 percent support forever, and size for peak. Consumption math is a meter: pay per activated OCPU hour, scale down after quarter end, and let the meter reward elasticity.
The published rates frame the BYOL decision. At Oracle list for Exadata Database Service, per Oracle's Cloud@Customer pricing page:
| Metric | BYOL | License included | Annual at 32 OCPUs |
|---|---|---|---|
| Rate per OCPU hour (list) | $0.81 | $3.10 | BYOL $227k, included $869k |
| What it buys | Service automation and infrastructure software. Your licenses do the rest. | The same, plus the Enterprise Edition Extreme Performance license stack bundled in. | |
| Who should choose it | Anyone with a supported EE estate and the options they actually use. | New workloads with no license inventory, or estates exiting their license base deliberately. |
Two mechanics blunt the elasticity story. First, each database server carries a minimum activation, currently eight ECPUs per node, so the meter never reads zero on a running VM cluster. Second, the infrastructure fee underneath the meter is fixed. Consumption flexes; the floor does not.
Run the crossover honestly. A steady 32 OCPU estate gains little from hourly elasticity; a reporting estate that triples at quarter end gains a lot. The meter rewards variance, not virtue.
Refresh Cycle Mechanics and the Lock In Risk
You never own the rack. Oracle does, and at the end of the four year term you face exactly three doors: renew on the contract then in force, refresh onto the current hardware generation at the price then quoted, or return the machine and migrate everything off it. There is no purchase option.
That third door is the one Oracle prices against. By year four, your databases sit on Oracle owned hardware, integrated into your network, with a migration cost Oracle can estimate as accurately as you can. Renewal pricing reflects that arithmetic, not gratitude.
The non obvious mechanics worth writing into the order before signature:
| Mechanic | Why it bites |
|---|---|
| No mid term reduction | The infrastructure subscription cannot be shrunk during the term. Oversizing on day one is a four year sentence, so size to current need plus one expansion step, never to the five year forecast. |
| Renewal repricing | Year five pricing is uncapped by default. Negotiate a renewal cap and refresh generation pricing at the original signature, while you still have a credible walk away. |
| Telemetry visibility | The control plane reports activated cores and enabled options to Oracle continuously. Compliance disputes shift from audit interviews to Oracle's own dashboards. Keep your BYOL inventory reconciled quarterly. |
Modeling Five Year TCO: On Premises, OCI, and Cloud at Customer
The benchmark scenario: a regulated insurer running a steady 32 OCPU Enterprise Edition estate, BYOL throughout, quarter rack class infrastructure, five year horizon. Existing license support payments are excluded because they are identical across all three options. Benchmark scenario, not a quote.
| Five year cost line ($k) | On premises Exadata | OCI ExaDB Dedicated | Exadata Cloud@Customer |
|---|---|---|---|
| Hardware purchase | 1,050 | 0 | 0 |
| Infrastructure subscription | 0 | 1,020 | 810 |
| Hardware support, facilities, local ops | 1,055 | 0 | 175 |
| Database service consumption (BYOL) | 0 | 1,135 | 1,135 |
| Refresh and migration event | 0 | 0 | 120 |
| Support Rewards offset (25%) | 0 | −539 | −486 |
| Five year total | 2,105 | 1,616 | 1,754 |
Support Rewards is the line most buyers forget. Per Oracle's published program, eligible Universal Credits consumption earns 25 cents per dollar against on premises technology support invoices, and 33 cents for ULA holders.
Cloud at Customer consumption purchased through Universal Credits earns it. The offset assumes your open support bill is large enough to absorb the rewards; in this scenario that is roughly $97k to $108k a year.
The model is sensitive to three inputs: utilization variance (elasticity favors the cloud options), the rewards assumption (no open support bill, no offset), and the year five renewal price on Cloud at Customer, which is why the cap belongs in the original order.
The Negotiation Moves Before Signing
Size the infrastructure to today, not the forecast
The fee cannot be reduced mid term. Buy the smallest configuration that fits current load plus one expansion step, and price the expansion step in the same order.
Cap the renewal and the refresh at signature
Fix year five pricing as a maximum uplift on year four, and lock refresh generation infrastructure pricing now, while walking away is still cheap.
Reconcile the BYOL inventory before cutover
Confirm support status, option entitlements, and the repurpose rule for every license you bring. The platform will report your usage either way; arrive compliant.
Put Support Rewards in the business case and the order
Confirm in writing that your Cloud at Customer consumption is purchased through eligible Universal Credits and earns the 25 or 33 percent rate.
Price the exit on day one
Cost the year four migration off the platform before you sign, and budget it. A funded exit estimate is the only credible renewal leverage you will have.
Take Cloud Lift, keep your own plan
Accept Oracle's funded migration engineering, but hold your own cutover schedule and acceptance criteria. Free services priced your urgency into the deal already.
Our recommendation: treat Cloud at Customer as a four year license negotiation wearing cloud clothing, and negotiate it once, at signature, when your leverage peaks.
- Before signing: reconcile the BYOL estate, model the three way TCO with your own numbers, and write the renewal cap, refresh pricing, and rewards eligibility into the order.
- After signing: review activated cores and enabled options quarterly against your license inventory, because Oracle already is.
Redress Compliance runs this assessment and the negotiation as a fixed scope engagement on the buyer side of the table. Contact us to scope it. We are glad to tie a meaningful part of the fee to delivered value.
