Exadata Cloud at Customer runs Oracle's Exadata platform as a cloud service inside your data center. It is billed by OCPU, and the enabled OCPU count, not the hardware, drives the cost.
Oracle ExaCC runs Exadata as a cloud service in your data center, billed by OCPU. The enabled OCPU count, the license path, and the options each workload uses decide what you actually pay.
Exadata Cloud at Customer, or ExaCC, runs Oracle's Exadata platform as a cloud service inside your data center. It is billed by OCPU, and the OCPU count, not the hardware, drives the cost.
This guide covers the billing model, bring your own license versus license included, online scaling, and the buyer moves that control the number.
Exadata Cloud at Customer places Exadata infrastructure in your facility, operated by Oracle as a cloud service. You pay an infrastructure subscription plus a database charge billed by OCPU, as described in the Oracle Exadata documentation.
An OCPU is the Oracle compute unit. Database charges accrue on enabled OCPUs, which you can scale up and down online. The enabled count, not the installed capacity, sets the bill.
The infrastructure subscription is fixed per rack shape and term. The database charge is variable with OCPUs. Buyers often focus on the first and miss that the second is where the cost moves.
As with all Cloud at Customer, you choose bring your own license or license included, and the gap over a multi year term is large.
ExaCC license paths and OCPU effect
| Path | OCPU rate | Best when | Watch for |
|---|---|---|---|
| Bring your own license | Lower | You hold Enterprise Edition and options | Support must stay current |
| License included | Higher | You lack spare licenses | Long term cost can exceed BYOL |
| Option coverage | Varies | Options like RAC and Partitioning | Confirm each option's path |
Bring your own license applies your Database and option entitlements against a lower OCPU rate. On Exadata the option question matters, because RAC, Partitioning, and others must each be entitled or included. Check the cloud pricing ratios.
License included bundles the database and a defined option set into the OCPU rate. It is simpler but at steady state usually exceeds bring your own license for a buyer who already holds licenses.
The cost moves with enabled OCPUs and with the options each workload uses. Both can rise quietly between reviews.
White Paper ยท Oracle
The Oracle Buyer Side Framework
The moves we use across Oracle Database, Java and ULA estates. Read it free.
OCPUs scale online to meet demand, which is the platform's strength and its budget risk. Scale down after peaks, and govern scaling with a monthly review.
Real Application Clusters and Partitioning are common on Exadata and price into the OCPU equation. Confirm whether each is covered by bring your own license or included, and do not pay twice.
The standard Oracle pitch is that license included on ExaCC is the clean choice because it bundles the options Exadata workloads need. We disagree. In roughly two out of three ExaCC estates we have modeled, a buyer who already held Enterprise Edition plus RAC and Partitioning paid materially less on bring your own license across a three year term, even after support. The buyer side move is to inventory your existing options honestly, model both paths at realistic enabled OCPU counts including scale down, and choose license included only where you genuinely lack the option entitlements. The bundle is convenient, and Oracle prices the convenience.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
ExaCC gives you Exadata performance and an OCPU meter that never sleeps. The performance is the product. The meter is the negotiation.
The moves come down to the OCPU count, the license path, and the options.
Enable OCPUs for peak and scale down after. Idle enabled OCPUs are the most common ExaCC waste.
Model bring your own license and license included over the full term, including options and scale down. Let the total decide.
Oracle ExaCC, or Exadata Cloud at Customer, places Exadata infrastructure in your own data center, operated by Oracle as a cloud service. You pay an infrastructure subscription plus a database charge billed by OCPU.
ExaCC is billed in two parts: a fixed infrastructure subscription by rack shape and term, and a variable database charge based on enabled OCPUs. The enabled OCPU count, not the installed capacity, sets the database cost.
An OCPU is the Oracle compute unit. Database charges accrue on enabled OCPUs, which you can scale up and down online without downtime. Idle enabled OCPUs still accrue charges even with no workload.
Bring your own license applies your existing Database and option licenses against a lower OCPU rate and usually wins over a multi year term if you hold the entitlements. License included bundles them at a higher rate but suits buyers without spare licenses.
Options such as RAC and Partitioning are common on Exadata and price into the OCPU equation. You must confirm whether each option is covered by bring your own license or included, so you do not pay for the same option twice.
Set enabled OCPUs to actual demand and scale down after peaks, govern online scaling with monthly approval, choose the cheaper license path on the full term numbers, and confirm option coverage to avoid double paying.
Idle enabled OCPUs left running after a demand peak are the most common ExaCC waste. Because the database charge accrues on enabled OCPUs regardless of workload, scaling down promptly is the simplest saving.
Yes. OCPUs scale online to meet demand, which is a core ExaCC strength. The same flexibility is a budget risk, so scale down after peaks and review scaling monthly to keep the database charge in line with need.
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.
