Exadata Cloud Service and Exadata Cloud at Customer are licensed on the OCPUs you enable, not on the cores physically installed, so scaling the enabled OCPU count up or down is the single biggest lever on your cost.
How is Exadata Cloud licensed?
Exadata Cloud is licensed on enabled OCPUs, the online compute units you switch on within the rack. The hardware ships with a fixed number of cores, but you pay for and license only the OCPUs you enable, and you can scale that number elastically. This is closer to a metered model than to the classic processor license, and it means the enabled count is the figure an auditor and a finance team both care about.
Because the license follows the enabled OCPU count, capacity planning is licensing. Enabling headroom you do not use is paying for licenses you do not need, and the buyer move is to enable to real demand and scale up only when the workload genuinely requires it.
How do Cloud Service and Cloud at Customer differ?
Exadata Cloud Service runs in an Oracle data centre, while Exadata Cloud at Customer puts the same rack in your own data centre with Oracle operating it. The licensing model is the same OCPU based approach in both, but Cloud at Customer keeps the hardware on your premises for data residency or latency reasons, which changes the audit conversation because the machine sits inside your walls.
That physical presence is why entitlement records matter even more with Cloud at Customer. The OCPU enablement history, kept as your own evidence, is what proves the enabled count over time rather than the installed core count an auditor might otherwise reach for.
Exadata Cloud licensing levers
| Lever | Effect on cost | Buyer move |
|---|---|---|
| Enabled OCPUs | Direct, scales the bill | Enable to real demand only |
| Database options | Each enabled option adds cost | Turn on only options in use |
| Bring your own license | Reuses owned licenses | Match owned entitlements to enabled OCPUs |
| OCI commitment | Discounts at the cost of lock in | Size the commitment to verified demand |
Can you bring your own license to Exadata Cloud?
Yes, you can bring your own license to Exadata Cloud, and it changes the economics. Bring your own license lets you apply Oracle Database licenses you already own against the enabled OCPUs, paying a lower infrastructure rate, while License Included folds the license into the service price. For a customer with a large owned Enterprise Edition estate, bring your own license is often the cheaper path.
The compliance point is that bring your own license keeps the counting responsibility with you. The enabled OCPUs must be covered by owned entitlements under the right metric, and a mismatch between enabled capacity and held licenses is exactly the kind of gap a finding exploits.
Where does Exadata Cloud create audit exposure?
Exadata Cloud creates audit exposure where enabled OCPUs, options, and owned licenses fall out of step. Enabling an option such as a management pack across the rack, leaving OCPUs enabled after a project ends, or carrying a bring your own license position that no longer matches the enabled count all produce findings. An OCI commitment taken under audit pressure can also lock in spend that a calmer review would have sized smaller.
The defense is the enablement evidence file and an honest option inventory. Recording what was enabled, when, and against which entitlement turns a potential finding into a documented position you control.
What is the buyer move on Exadata Cloud licensing?
The buyer move is to manage the enabled OCPU count as the primary cost lever, keep the option footprint tight, and reconcile bring your own license entitlements against enabled capacity on a schedule. The elastic model rewards customers who scale enablement to demand and punishes those who leave capacity and options switched on out of habit.
This is buyer side work. We position as an independent buyer side advisory with deep Oracle licensing expertise, and on Exadata Cloud the discipline of enabling only what you use is both a cost control and an audit defense.
A worked example
Consider an anonymized energy company running Exadata Cloud at Customer in its own data centre. A project had enabled extra OCPUs and a management pack across the rack to speed a year end load, and neither was switched off afterwards. Oracle's preliminary finding counted the installed core capacity and the enabled pack at list price, opening the number in seven figures. No client names, sector level example only.
The buyer side defense produced the OCPU enablement history showing the load was short lived, scaled the enabled OCPUs back to steady state demand, and removed the unused management pack. Licensing to the corrected enabled count brought the settled position to a fraction of the opening number.
Where to go next
This piece links up to the Oracle Virtualization Licensing Guide. Keep reading across the cluster:
See our virtualization and cloud licensing work, or get a quote and we will walk through your position.