Oracle Cloud at Customer puts OCI hardware inside the data center. The contract carries cloud terms, on premise mechanics, and unique exit risk. Read the buyer side reference on the platform and the negotiation playbook.
Oracle Cloud at Customer ships OCI hardware to the data center and runs Oracle Cloud services inside the customer perimeter. The contract reads like a cloud contract on the front page and like an on premise contract in the appendices. The leverage sits in the appendices. The exit terms decide the real flexibility.
Pair this guide with the Cloud at Customer landing page, the Cloud at Customer licensing guide, the Oracle Cloud contracts article, and the ULA decision framework.
Cloud at Customer is the Oracle answer to data sovereignty, latency, and regulatory constraints that block public cloud. The hardware sits in the customer data center. The control plane sits in Oracle. The contract carries cloud terms for the services and on premise terms for the rack.
The cloud terms are familiar. The hardware mechanics are less familiar. The exit terms are unfamiliar. Most buyers default to the standard paper without challenging the appendices. The standard paper favors Oracle on every exit lever.
The rack is Oracle hardware. Oracle owns the rack. The customer leases the capacity. The capacity is expressed in OCPU and storage units. The rack ships and installs at Oracle expense. The capital cost is amortized inside the subscription.
| Rack tier | OCPU capacity | Storage capacity | Typical use |
|---|---|---|---|
| Compact | 200 to 400 OCPU | 200 to 500 TB | Departmental workloads |
| Standard | 400 to 1,200 OCPU | 500 TB to 2 PB | Mid size enterprise estates |
| Large | 1,200 to 3,000 OCPU | 2 to 6 PB | Large enterprise databases |
| Custom | Negotiated | Negotiated | Critical workloads with growth path |
The licensing model has two paths. License Included runs on Oracle controlled pricing per OCPU hour. BYOL applies on premise licenses to the rack at a much lower run rate. The BYOL path needs an evidence file. Without the file the lower rate cannot be defended.
BYOL on Cloud at Customer needs the same evidence file as BYOL on OCI. Edition match, active support, OCPU to processor map, and snapshot held by the buyer. The file is the artifact that defends the BYOL rate in every audit conversation. Refresh quarterly.
Oracle delivers the support, the hardware maintenance, and the control plane. The SLA appendix carries uptime targets and a service credit framework. The exit appendix carries the terms that decide whether the workload can really leave at end of term.
| Element | Buyer position | Oracle default | Plan move |
|---|---|---|---|
| Uptime target | 99.95% minimum | 99.9% default | Raise target with evidence |
| Service credits | Capped per month | Small percentage | Negotiate cap upward |
| Cooperation period | 180 days at end of term | 90 days default | Push for longer cooperation |
| Data egress | Free during termination | Standard egress fees | Free egress window |
| Hardware removal | Oracle at Oracle cost | Sometimes shared cost | Lock Oracle responsibility |
The cost model has four lines. Subscription fee. Universal Credit consumption. BYOL license maintenance. Internal labor. The first two sit in the Oracle order. The last two sit in the buyer plan. All four lines belong in the five year picture.
The five year picture decided the deal. License Included was eighteen percent more expensive than BYOL after the evidence file. The BYOL rate plus the exit terms closed the contract on buyer terms.
The seven step checklist below moves a Cloud at Customer deal from cover page to defended order document.
Data sovereignty, latency, and regulatory constraints are the three common reasons. Some workloads cannot leave the data center for regulatory reasons. Others have latency requirements that public cloud cannot meet. Cloud at Customer is the Oracle answer to those constraints with OCI services on premise.
Yes for most database and middleware workloads. The BYOL run rate is sixty to seventy five percent below the License Included rate. The saving requires an active support contract and an edition match. The evidence file defends the rate in every audit conversation.
Oracle removes the rack. The customer migrates the data and the workloads. The cooperation period in the exit appendix decides how easy that migration is. Push for one hundred eighty days minimum, free egress, and Oracle responsibility for hardware removal at Oracle cost.
Yes. The annual commit and the discount band move on volume, term length, and credible alternative. The same negotiation patterns apply as on public OCI. The rack adds capital amortization to the seller side, which sometimes loosens the discount on the services side.
Three and five years are the common Cloud at Customer terms. One year terms exist but carry low discount. Five year terms carry the highest discount but the lowest flexibility. The buyer position depends on the workload roadmap and the budget horizon.
Redress runs the order document review, the BYOL evidence file, the workload inventory, the five year cost model, the exit appendix negotiation, and the leverage map. Engagements close inside twelve weeks. The work is buyer side. No vendor influence. No sales kickback.
Redress runs Cloud at Customer reviews as part of the buyer side advisory practice. The work covers the order document review, the BYOL evidence file, the workload inventory, the five year cost model, and the renewal negotiation. Engagements close in eight to twelve weeks.
Read the related Vendor Shield, Renewal Program, Benchmark Program, Software Spend Assessment, Benchmarking framework, about us, management team, locations, and contact pages.
A buyer side reference on Oracle Cloud at Customer hardware, licensing, support, SLA, and exit terms. Includes the BYOL evidence file template, the five year cost model, and the negotiation language used across hundreds of Oracle engagements.
Independent. Buyer side. Built for CIOs, CFOs, and procurement leads carrying Oracle Cloud at Customer decisions. No vendor influence. No sales kickback.
Open the white paper in your browser. Corporate email only.
Open the Paper →The five year picture decided the deal. License Included was eighteen percent more expensive than BYOL after the evidence file. The BYOL rate plus the exit terms closed the contract on buyer terms.
We have run 500+ enterprise clients across 11 publishers. Every engagement starts with one conversation.
Universal Credit price movement, BYOL evidence patterns, Cloud at Customer commit scenarios, exit term wins, and the wider Oracle commercial leverage signals across every engagement we run.
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.
