Oracle Cloud at Customer puts Oracle managed cloud hardware inside your data center, consumed as a subscription. The licensing choices behind it still decide the bill. Here is the buyer framework.
Oracle Cloud at Customer puts Oracle managed cloud hardware inside your own facility on a subscription. The deployment model, the two license paths, and OCPU scaling decide what you actually pay.
Oracle Cloud at Customer puts Oracle managed cloud hardware inside your own data center. You consume it as a subscription, but the licensing choices behind it still decide the bill.
This guide covers the deployment model, the two ways to bring database licenses, and where the cost actually lands.
Cloud at Customer is OCI infrastructure installed and operated by Oracle in your facility. You pay a subscription and Oracle keeps the hardware patched and supported.
The family includes Exadata Cloud at Customer, the broader Dedicated Region, and Compute Cloud at Customer. Each runs the same OCI control plane behind your firewall.
Data residency, latency, and regulatory constraints are the usual drivers. The estate stays on premises while Oracle carries the operational burden, as set out in the Exadata Cloud at Customer documentation.
There are two commercial paths, and the gap between them is large. You either bring your own license or you take license included pricing.
Bring your own license versus license included
| Model | What you pay | Best when | Watch for |
|---|---|---|---|
| Bring your own license | Lower OCPU rate plus existing support | You hold spare Enterprise Edition | Support stream must stay current |
| License included | Higher OCPU rate, no separate license | You lack spare licenses | Long term cost can exceed BYOL |
| Universal Credits | Drawn down by consumption | Variable workloads | Unused commit expires |
Bring your own license applies your existing Database licenses against a lower OCPU rate. Each OCPU consumes license at a published ratio, so model the OCPU count carefully against the Oracle cloud pricing.
License included bundles the database license into the OCPU rate. It removes the entitlement question but costs more per hour, and at steady state it often exceeds the BYOL total.
White Paper ยท Oracle
The Oracle Buyer Side Framework
The moves we use across Oracle Database, Java and ULA estates. Read it free.
The headline subscription is only part of the picture. OCPU scaling, support continuity under the Oracle lifetime support policy, and the minimum commit drive the real number.
OCPUs can be scaled up online to meet demand. That flexibility is useful, but unreviewed scaling is the most common reason a Cloud at Customer bill drifts above forecast.
The subscription carries a minimum term and often a minimum OCPU floor. Negotiate both against a realistic low water mark, not the peak.
The standard Oracle pitch is that license included pricing is simpler and therefore the smart default, because it removes the compliance question. We disagree. In roughly two out of three Cloud at Customer estates we have modeled, a buyer with spare Enterprise Edition licenses paid materially less over a three year term using bring your own license, even after accounting for support. The buyer side move is to model both paths over the full term at realistic OCPU counts, count your existing entitlements honestly, and only choose license included when you genuinely lack the licenses to redeploy. Simplicity has a price, and Oracle prices it well.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
Cloud at Customer moves the hardware into your building. It does not move the licensing leverage onto your side of the table. That you still have to take.
The estate rewards buyers who treat the subscription like a license negotiation, because that is what it is.
Build the three year cost for bring your own license and for license included at realistic OCPU counts. Let the number, not the sales narrative, choose.
Set the minimum OCPU commitment against your steady state low, with headroom bought only when needed. Avoid committing to peak.
Oracle Cloud at Customer is OCI cloud infrastructure that Oracle installs and operates inside your own data center. You consume it as a subscription while keeping the hardware behind your firewall for data residency and latency reasons.
Bring your own license applies your existing Oracle Database licenses against a lower OCPU rate. License included bundles the database license into a higher OCPU rate. Bring your own license is usually cheaper at steady state if you hold spare licenses.
Cloud at Customer is billed by OCPU, the Oracle compute unit, not by physical server size. The recurring charge rises and falls with the number of OCPUs enabled, which can be scaled online.
No. On bring your own license you still consume your Database entitlements and must keep support current. License included removes the entitlement question but at a higher rate. Either way the licensing choice still matters.
Online OCPU scaling lets you raise compute capacity without downtime. It is useful for demand spikes but is the most common reason a Cloud at Customer bill exceeds forecast, because scaling often happens without a review gate.
The main forms are Exadata Cloud at Customer for database workloads, Dedicated Region for a full OCI region in your facility, and Compute Cloud at Customer for general OCI compute. All run the same OCI control plane locally.
Set the minimum OCPU floor to a realistic steady state low rather than your peak. Buy headroom only when needed, govern online scaling with monthly approval, and renegotiate the commit at each renewal against actual use.
Yes, when you genuinely lack spare Enterprise Edition licenses to redeploy. In that case license included avoids buying new perpetual licenses. If you hold the entitlements, bring your own license usually wins over a three year term.
Oracle ULA exit moves, Java audit defense posture, certification framework, and the buyer side moves across the Oracle Database, Java, and EBS estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
