A buyer side guide to Oracle Exadata Cloud at Customer in 2026. How the consumption model works, when Bring Your Own License pays off, and where idle OCPUs quietly inflate the bill.
Oracle Exadata Cloud at Customer puts Exadata hardware in your data center but bills it as a cloud service by OCPU, so the cost lever shifts from processor licenses to scaling discipline and your Bring Your Own License position.
This guide is for Oracle license managers and infrastructure leaders sizing an ExaCC deal in 2026. Read it alongside the Oracle licensing pillar and the Oracle Practice page so the metric and the negotiation stay aligned.
ExaCC keeps Exadata in your data center but shifts billing to a cloud consumption model. You pay for compute by the OCPU per hour, and the database itself comes either license included or under Bring Your Own License.
An OCPU is Oracle's compute unit, roughly one physical core with hyper threading. ExaCC charges by the OCPU you have provisioned, not the OCPU you use, so an idle but provisioned core still bills. Oracle documents the model on its cloud price list.
BYOL pays off when you already own perpetual Database Enterprise Edition and the options the workload needs. The cloud rate drops sharply, but support on the perpetual licenses continues, so the net saving depends on your support base.
ExaCC consumption choices compared
| Choice | What you pay | Best when |
|---|---|---|
| License included | Higher OCPU rate, no perpetual licenses | New workloads, no owned licenses |
| Bring Your Own License | Lower OCPU rate plus annual support | You hold perpetual EE and options |
| Mixed estate | Both rates by workload | Migration in progress |
The bill is driven by provisioned OCPUs, the options you enable, and how disciplined you are about scaling down. Hardware is fixed once installed, so the variable cost is almost entirely the OCPU line.
ExaCC lets you scale OCPUs up and down online. Teams scale up for a peak and rarely scale back. That idle headroom is the single most common source of ExaCC overspend we see.
Options such as partitioning, multitenant, and in memory bill per OCPU. Enabling an option across the full rack when only one database needs it multiplies the cost. License the option to the workload, not the hardware.
Exadata Cloud at Customer, or ExaCC, is Oracle Exadata hardware installed in your own data center but operated as a cloud service by Oracle. You consume it with cloud metering while the machine sits behind your firewall.
ExaCC bills through Oracle Cloud credits by OCPU per hour, with database options layered on top. You can bring existing database licenses under Bring Your Own License or pay the license included rate per OCPU.
It can, when you already hold perpetual Database Enterprise Edition and option licenses. BYOL drops the cloud rate sharply, but you still owe annual support on the perpetual licenses, so the net depends on your support base.
The frequent traps are scaling OCPUs up and forgetting to scale down, paying license included rates while holding unused perpetual licenses, and licensing every enabled database option across the whole rack rather than per workload.
On premises Exadata is a capital purchase you license by processor. ExaCC keeps the same hardware in your room but shifts you to a cloud consumption model, so the lever moves from license counts to OCPU scaling discipline.
Yes. The committed consumption rate, the BYOL discount, and the OCPU floor are all negotiable, especially when ExaCC sits inside a larger Oracle Universal Credits commitment.
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.
ExaCC moves the lever from license counts to scaling discipline. The machine is fixed. The OCPU line is where the money moves.
500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay for the next three years.
One short note on Oracle renewal moves, ExaCC and cloud consumption, ULA posture, and the buyer side moves we are running in client engagements.