Oracle Exadata Cloud at Customer licensing: OCPU, not cores.

Oracle Exadata Cloud at Customer puts Exadata hardware in your data center but bills the software as a metered cloud service, so the licensing question is OCPU consumption and Bring Your Own License, not perpetual cores.

This guide is for database, procurement, and finance leaders sizing an Exadata Cloud at Customer commitment in 2026. Pair it with the Oracle Database licensing guide and the Oracle Practice so the technical and commercial picture align.

How is Exadata Cloud at Customer priced in 2026?

ExaCC is consumed as a cloud service. The rack lives in your data center for data residency, but the database and Exadata software meter as a subscription. The unit is the OCPU, billed per hour or per month.

Oracle sets out the service on its Exadata Cloud at Customer page. The headline is consumption pricing, not a perpetual license on the hardware.

What is an OCPU and why does it matter?

An OCPU is Oracle's compute unit for the service. You enable OCPUs to run workloads and pay for what you enable. Idle OCPUs are the avoidable cost, so the meter rewards scaling to demand.

• Enabled OCPUs: the metered, billable unit on the service.
• Elastic: scale OCPUs up and down with the workload.
• Cost control: turn OCPUs down off peak to cut the bill.

How does Bring Your Own License change the rate?

BYOL applies licenses you already own and charges a lower service rate as a result. License included bundles the license into the rate. When you own database licenses, BYOL is usually the cheaper path.

License included or BYOL, which fits your estate?

The choice depends on what you already own. If you hold Oracle Database licenses with the right options, BYOL converts a sunk cost into a discount. If you do not, license included avoids a fresh license purchase.

Why do options decide the BYOL discount?

BYOL only covers the options your licenses include. Partitioning, Advanced Security, and similar options each need their own entitlement. Assuming full coverage is the common error that turns a BYOL saving into a compliance gap.

How does the committed floor affect cost?

A committed consumption floor sets a minimum you pay regardless of use. Set it too high and you lose the elasticity that justifies the service. Size it to your real baseline demand, not to the vendor's growth forecast.

What should you negotiate on an ExaCC deal?

Push on the OCPU rate, the BYOL discount, and the committed floor together. A low rate paired with a high floor can cost more than a higher rate with a floor sized to your baseline. Model the term as a whole.

What term flexibility is worth holding out for?

Seek the right to rebalance OCPUs and to true down at renewal. Flexibility to scale matters more than a marginal rate cut, because the service only pays off when you can match spend to demand.

What to do next

1. Inventory the Oracle Database licenses and options you already own.
2. Map those licenses to the options your ExaCC workloads will use.
3. Model license included against BYOL on the same OCPU profile.
4. Measure your real baseline OCPU demand across a full month.
5. Size any committed floor to that baseline, not to a forecast.
6. Negotiate the OCPU rate and the BYOL discount as one package.
7. Hold for the right to rebalance OCPUs and true down at renewal.

Frequently asked questions

How is Oracle Exadata Cloud at Customer licensed in 2026?

Exadata Cloud at Customer is consumed as a cloud service billed by OCPU per hour or per month, not by perpetual processor licenses. The hardware sits in your data center, but the database and Exadata software are metered as a subscription, so the meter is OCPU consumption, not server cores.

Can you bring your own Oracle licenses to Exadata Cloud at Customer?

Yes. Bring Your Own License lets you apply existing Oracle Database licenses to reduce the service rate, which is the main lever buyers have. The counting still follows Oracle's BYOL policy, so confirm exactly which options your licenses cover before you assume the discount.

What is the difference between license included and BYOL on ExaCC?

License included bundles the database license into the hourly rate. BYOL strips that out and charges a lower rate because you supply the license. BYOL almost always wins on cost when you already own database licenses, but only for the options those licenses actually cover.

Does Exadata Cloud at Customer count cores like on premises Oracle?

No. ExaCC meters OCPU consumption rather than physical cores, and you can scale OCPUs up and down. That elasticity is the cost control, because you pay for the OCPUs you enable, not for every core in the rack.

Is Exadata Cloud at Customer cheaper than on premises Exadata?

It can be, mainly because you pay for enabled OCPUs rather than the full rack and you avoid a large capital purchase. Whether it is cheaper depends on utilization. A steadily busy estate may favor BYOL on ExaCC, while a lightly used one benefits most from scaling OCPUs down.

What should you negotiate on an Exadata Cloud at Customer deal?

Negotiate the OCPU rate, the BYOL discount, the committed consumption floor, and the term flexibility. The committed floor is the trap, because a high commit removes the elasticity that justifies the service. Size the floor to your real baseline, not to the vendor's forecast.