Cloud at Customer trades the public cloud migration for an Oracle managed appliance inside your data centre. The OCPU bands, BYOL math, and audit risk drive the renewal economics.
Oracle Cloud at Customer is the Oracle public cloud stack delivered as a managed appliance inside the customer data centre. The subscription meters in OCPUs and storage TB. BYOL recovers 30 to 50 percent against the License Included rate. The buyer side moves cut the renewal quote by 20 to 40 percent.
Across 60 Cloud at Customer engagements, median saving against the opening Oracle quote ran 32 percent. The math depends on the appliance variant, the on premise license pool, and the term commitment the customer accepts at the order.
Oracle Cloud at Customer is the Oracle public cloud service stack delivered as a managed appliance inside the customer data centre. Oracle owns the hardware. Oracle runs the software. The customer pays a subscription metered in OCPUs, storage, and managed service hours.
The model targets buyers that hold sovereignty, latency, or regulatory constraints that block a public cloud migration. The licensing model differs from on premise Oracle Database, from Oracle Cloud Infrastructure, and from the bring your own license construct that sits across both.
The product line covers three appliance generations. Each carries a different sizing envelope, a different cost band, and a different audit profile. The naming changed twice in three years.
The Cloud at Customer subscription bundles three layers. The bundle creates an audit trap when the customer counts the layers separately at renewal.
Cloud at Customer counts in OCPU, in storage TB, and in selected platform service units. The counting rules look simple on the order document. The reality at the renewal desk is harder.
One OCPU equals one physical Oracle CPU core with hyperthreading enabled. The OCPU rate covers Database Enterprise Edition and a defined option bundle. The bundle changes between metered and unmetered models.
The customer chooses BYOL or License Included at the order. BYOL applies existing on premise Oracle Database licenses against the Cloud at Customer footprint. License Included pays the full OCPU rate with the Oracle software entitlement built in.
Metered usage charges by OCPU hour. Annual Flex commits to a fixed OCPU pool for the year with a discount. Most customers run Annual Flex because the cost predictability matters more than the burst capacity.
Cost bands depend on the appliance generation, the OCPU count, and the term commitment. The numbers below sit in the public Oracle price list with the typical discount applied at the order desk.
X9M quarter rack. 22 OCPU. Annual list runs $720k to $980k before discount. Typical discount runs 25 to 45 percent for a five year term.
X9M half rack. 50 OCPU. Annual list runs $1.6m to $2.4m. Five year discount runs 35 to 55 percent.
Full rack region. Annual list starts at $6m. Five year discount runs 30 to 50 percent. The customer also commits to a minimum cloud consumption.
The Cloud at Customer subscription does not eliminate audit risk. The risk shifts from on premise license counting to subscription compliance and BYOL coverage. Three audit motions arrive on the Cloud at Customer customer.
Oracle runs a BYOL match against the appliance footprint. The audit reads the OCPU consumption against the on premise license pool. Gaps convert to true up charges at the License Included rate.
The included option bundle changes between OCPU tiers. The customer that uses Partitioning, Advanced Compression, or Real Application Clusters on a tier that does not include the option faces a back charge.
Oracle audits the cloud egress and the platform service consumption against the order. Overage charges run at the on demand rate, often 3 to 5 times the committed rate.
Buyers that run BYOL recover 30 to 50 percent of the License Included rate. The strategy works when the customer holds a clean on premise license pool and runs the matching motion at the order and at every renewal.
The buyer maps the on premise license pool against the Cloud at Customer OCPU footprint. The reconciliation runs on the contract terms, not on the Oracle inventory record. Many customers hold options they do not need on the appliance.
At each renewal cycle, the buyer revisits the BYOL versus License Included split. The split changes when the on premise estate shrinks or when the appliance grows beyond the license pool.
Customers inside an Oracle ULA face a BYOL trap. ULA licenses cannot be deployed against Cloud at Customer in some contract forms. The certification at ULA exit must capture the Cloud at Customer deployment.
The Cloud at Customer order document is negotiable. The renewal is negotiable. The mid term true up is negotiable. The buyer that runs the moves recovers 20 to 40 percent against the opening Oracle quote.
Oracle pushes the customer to Annual Flex on a long term commit. The buyer presses for a shorter term, a smaller commit, and the right to flex the OCPU count down at renewal.
Oracle frequently offers cloud credits as a sweetener at the order. The buyer presses for the credits to apply against the Cloud at Customer subscription, not just against Oracle public cloud services.
Oracle list price rises 6 to 8 percent per year. The buyer locks the OCPU rate in the order document for the full term. The lock removes the renewal uplift surprise.
Cloud at Customer cost band reference, five year annual flex term
| Variant | OCPU pool | Annual list | Typical settled | BYOL saving |
|---|---|---|---|---|
| Exadata X9M quarter rack | 22 OCPU | $720k to $980k | $500k to $720k | 35 percent |
| Exadata X9M half rack | 50 OCPU | $1.6m to $2.4m | $1.0m to $1.6m | 40 percent |
| Exadata X9M full rack | 100 OCPU | $3.2m to $4.8m | $2.0m to $3.2m | 42 percent |
| OCI Dedicated Region | Region scale | $6m to $14m | $4m to $8.5m | 30 percent |
| Compute Cloud at Customer | 8 to 32 OCPU | $240k to $720k | $160k to $460k | 28 percent |
The checklist takes the buyer from the current state to the executed plan. Run the steps in sequence. Each step builds the leverage for the next.
Oracle Cloud at Customer is the Oracle public cloud stack delivered as a managed appliance inside the customer data centre. Oracle owns the hardware. Oracle runs the software. The customer pays a subscription metered in OCPUs and storage TB. Three variants cover Exadata Cloud at Customer, OCI Dedicated Region, and Compute Cloud at Customer.
BYOL applies existing on premise Oracle Database licenses against the appliance OCPU footprint. The customer holds the on premise license pool. The Cloud at Customer subscription charges only the managed service rate, not the License Included rate. BYOL recovers 30 to 50 percent of the License Included spend in most engagements.
License Included bundles the Oracle Database software entitlement into the OCPU rate. BYOL applies existing on premise licenses against the appliance and charges only the managed service rate. The split is negotiable at the order. Most customers run a mixed model with BYOL on production and License Included on development.
Three audit motions. BYOL coverage audits read the on premise license pool against the appliance OCPU count. Database option audits read the use of Partitioning, Advanced Compression, and Real Application Clusters against the OCPU tier inclusion. Egress and consumption audits read the cloud egress and platform service use against the order.
ULA licenses do not always deploy against Cloud at Customer in some contract forms. The certification at ULA exit must capture the Cloud at Customer deployment as part of the count. The buyer side runs the Cloud at Customer reconciliation during the ULA exit window, not after.
Annual Oracle list price rises 6 to 8 percent per year. The customer that does not lock the OCPU rate in the order document faces a compound uplift across the term. The lock in the original order, combined with a renewal cap, removes the renewal uplift surprise.
Most orders run a five year term with Annual Flex commit. Three year terms exist with a smaller discount. The buyer side presses for a five year term with a price hold and the right to flex OCPU count down at each anniversary. The flex right is rarely offered without buyer side pressure.
Redress runs the Cloud at Customer practice inside the Vendor Shield subscription and the Renewal Program. The work includes the BYOL reconciliation, the OCPU rate lock, the option mapping, and the renewal negotiation. Engagements typically save 20 to 40 percent against the opening Oracle quote.
Redress runs the Oracle Cloud at Customer practice inside the Vendor Shield subscription, the Renewal Program, the Oracle service line, and the Software Spend Assessment.
Read the related Oracle ULA decision framework, the Oracle Knowledge Hub, the Oracle database licensing guide, the Oracle third party support article, the Oracle ULA exit strategy guide, the benchmarking service, and the Benchmark Program.
The companion playbook covers the Oracle Unlimited License Agreement decision tree, certification mechanics, and the negotiation moves that protect the customer at exit.
Independent. Written for CIOs, CFOs, and procurement leaders. No vendor partner affiliation.
Open the playbook in your browser. Corporate email only.
Open the Paper →Cloud at Customer is not a license sale. It is a subscription against an appliance inside your data centre. The buyer side that runs the BYOL reconciliation and locks the OCPU rate holds the renewal math.
BYOL reconciliation, Annual Flex sizing, and the OCPU rate lock that removes the renewal uplift surprise. Every engagement starts with one conversation.
Cost benchmarks, license rightsizing patterns, and the negotiation moves that worked. Written for buyer side teams running active vendor decisions.
Once a month. Audit patterns, renewal benchmarks, vendor commercial signals across Oracle, Microsoft, SAP, Salesforce, IBM, Broadcom, AWS, Google Cloud, ServiceNow, Workday, Cisco, and the GenAI vendors. No follow up sales pressure.
Free providers (Gmail, Yahoo, Outlook) cannot subscribe. Work email only. Unsubscribe in one click.
