One is a managed database platform. The other is a complete OCI region. They are sold as neighbors, priced in different shapes, and only one of them lets you scale the bill down.
These two products are sold as neighbors and they are not. Exadata Cloud at Customer is a managed database platform. An OCI Dedicated Region is a complete cloud region. They solve different problems, and they bill in completely different shapes.
Get the shape wrong and you will spend a four year term paying for the wrong kind of flexibility. That is the mistake this page is written to prevent.
Three products, not two. Oracle's Cloud at Customer family runs from a single database machine, through a general purpose compute rack, up to a complete region, and the shortlist usually skips the middle one.
A managed Exadata platform installed in your data center and operated by Oracle. It runs Oracle Database and nothing else, which is the point. You get Exadata storage offload, RAC, and Oracle managed patching without owning the machine.
A complete, self contained OCI region that Oracle installs and runs inside your facility. Oracle's Dedicated Region page describes a footprint starting at three racks and scaling past 450, carrying more than 200 OCI services.
Oracle also sells a single rack Compute Cloud at Customer platform that delivers OCI compute, storage and networking locally without the database machine or the region. It is the right answer more often than it is proposed.
If your requirement is that a handful of applications must run on local cloud infrastructure, and your databases are already handled, this is the cheapest way to satisfy it. Ask for it by name, because it may not be offered.
Exadata Cloud at Customer solves a database problem. A Dedicated Region solves an estate problem. Almost every bad selection we have reviewed came from answering the second question with the first budget, or the reverse.
Match the problem to the platform
| The problem you have | The platform that fits | Why |
|---|---|---|
| Aging on premises Exadata, data cannot leave the country | Exadata Cloud at Customer | Same platform, cloud operating model, no region needed |
| A few applications must run on local cloud compute | Compute Cloud at Customer | One rack, no database licensing entanglement |
| A regulator requires the whole estate and control plane in country | Dedicated Region | Only option with a full local control plane |
| Mixed estate, some Oracle, mostly not, sovereignty mandated | Dedicated Region | Non Oracle workloads need the wider service catalog |
| You want lower Oracle Database cost | Neither, yet | Both are control decisions. Neither is a discount |
Most Exadata Cloud at Customer deals exist because an on premises Exadata is approaching refresh, and the data cannot move. The buyer is not choosing cloud. The buyer is choosing between another capital refresh and a subscription that behaves like one.
That framing matters in the negotiation. You are comparing a four year infrastructure subscription against a hardware purchase plus support, and the fair comparison includes the migration cost of neither.
A Dedicated Region is bought when a rule covers everything, not just the database. Sovereign cloud mandates, defense programs and central bank supervision produce this shape, because they attach to the control plane, not the workload.
If your rule only names the data, a database platform usually satisfies it. If your rule names the operator, the jurisdiction or the physical media, you are in region territory.
Exadata Cloud at Customer bills in two parts. A Dedicated Region bills in one. That single structural difference decides more deals than the headline numbers do.
Oracle's published price list separates the infrastructure from the database compute, and the two behave nothing alike.
There is a floor inside the elastic part. Oracle's pricing page states a minimum of eight ECPU per database node, so the compute line never falls to zero while a node is up.
A Dedicated Region does not present a separate hardware line. You commit to consumption, Oracle sizes the footprint against your forecast, and everything you run draws against that commitment.
The consequence is that there is nothing to scale down. On Exadata Cloud at Customer, idle capacity can be switched off and stops billing. On a region, idle capacity is already paid for by the floor.
Very. Leaving Exadata Cloud at Customer means moving databases, which is a project your team has done before. Leaving a Dedicated Region means moving an estate and a control plane, which is a program almost nobody has rehearsed.
Price the exit before you sign either. If you cannot describe how you would leave in 12 months, you are not choosing a platform. You are choosing a landlord.
This is the clause almost nobody reads. Oracle's Exadata Cloud at Customer price list applies a rack term factor to expansion racks and servers, calculated as 48 divided by the smaller of the remaining rack term in months or 48.
We have seen this discovered in year three, after the capacity plan was already approved. It is not a penalty and it is not hidden. It is simply arithmetic that nobody modeled.
Exadata Cloud at Customer against a Dedicated Region
| Dimension | Exadata Cloud at Customer | OCI Dedicated Region |
|---|---|---|
| What it runs | Oracle Database only | More than 200 OCI services |
| Smallest unit | One base system rack | Three racks |
| Bill shape | Fixed infrastructure plus elastic compute | One consumption commitment |
| Published term | Four year rack term | Five year consumption commitment |
| Can you scale down | Yes, on the compute line | No, the floor is fixed |
| Control plane | Managed from an OCI region | Local, separate from public regions |
| Licensing options | BYOL or license included | BYOL or license included |
| Typical driver | Exadata refresh with residency | Estate wide sovereignty mandate |
The posture is identical in the rules and different in the leverage. Both platforms support bring your own license and license included, drawing on the same Oracle cloud licensing terms.
Conversion rules for owned licenses sit in Oracle's cloud licensing policy. Treat it as a policy document, not a contract term, and keep a dated copy of the version you relied on when you signed.
No. The on premises partitioning policy governs how you count processors on hardware you own. Neither platform meters that way, because Oracle owns the hardware and bills a cloud metric.
Where it still matters is the boundary. If the same licenses also cover owned servers, you need a clean allocation record showing which entitlement is deployed where at any point in time.
On Exadata Cloud at Customer, database compute is elastic and licensing follows it. Scale OCPUs down and both the cloud charge and the BYOL requirement fall with them. Scale up for quarter end and pay for those hours only.
A Dedicated Region has no equivalent. The commitment is set for the term, so the only way to lower the bill is to consume more of what you already bought. That is not cost control. That is consolation.
White Paper · Oracle
Oracle Cloud@Customer Strategy
The 2026 BYOL map for Oracle Cloud@Customer. Read it free.
Answer five questions in order and the platform picks itself. Answer them out of order and the largest deal on the table wins by default.
The common advice is that a Dedicated Region is the strategic choice because it future proofs the estate with the full OCI catalog on site. We disagree. In the selections we advised, buyers who chose a region for a narrow workload set paid a whole region floor to run what a single database platform would have carried, and no unit rate benefit came close to closing that gap. Oracle can add racks in weeks, and it advertises expansion past 450. Buy the platform that matches the workloads you have funded, and let real adoption earn the larger commitment later.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
Do not buy a region to run a database. Buy the platform that matches the workloads you have funded, and let adoption earn the bigger commitment.
Exadata Cloud at Customer is a managed Oracle Database platform in your data center. An OCI Dedicated Region is a complete cloud region carrying more than 200 OCI services with its own control plane. One solves a database problem, the other solves an estate problem.
For a database estate, Exadata Cloud at Customer, by a wide margin, because you are not funding a region you will not fill. For a mixed estate under a sovereignty mandate, a region can be the only option that satisfies the rule at all, which makes the comparison moot.
Oracle's Exadata Cloud at Customer price list shows rack infrastructure on a four year term. Oracle's Dedicated Region FAQ describes a five year consumption based commitment. Compare total contract value across the full term rather than the annual figure.
On Exadata Cloud at Customer, yes, on the database compute line, subject to a stated minimum of eight ECPU per database node. On a Dedicated Region, no. The consumption commitment is fixed for the term and idle capacity is already paid for.
It is a multiplier Oracle applies to expansion racks and servers on Exadata Cloud at Customer, calculated as 48 divided by the smaller of the remaining rack term in months or 48. Adding capacity with 12 months left multiplies the monthly rate by four.
Yes, and the eligibility rules were identical in every comparison we modeled. Both also support license included at separate published rates. BYOL almost never breaks the tie between these platforms, although it consumes most of the evaluation time.
No. The on premises partitioning policy governs processor counting on hardware you own, and Oracle owns the hardware in both cases. What still matters is keeping a clean record of which owned entitlements are deployed on the platform and which remain on your own servers.
Yes. Compute Cloud at Customer delivers OCI compute, storage and networking in a single rack without the database platform or the region. If only a handful of non database applications must run locally, ask for it by name, because it is rarely offered unprompted.
BYOL versus license included on Cloud@Customer, capacity discipline, and the subscription terms to pin before you sign.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
Engage independent buyer side Oracle licensing experts. We do not resell. We do not implement. We sit on your side of the table.
See engagement scope, comparison vs Big4 and resellers, and the buyer side framework.
Visit page →Cloud at Customer is a rack you meter. Dedicated Region is a region you commit to. The licensing read is the same family, but the scale of the commitment is not.
