Exadata Cloud at Customer puts Oracle's Exadata cloud infrastructure inside your own data centre, managed by Oracle and billed through OCI Universal Credits on the same consumption model as Exadata in an Oracle region. The cost question is therefore not whether to use Exadata but where it should sit, and the honest answer is that the on premises model pays back only when a genuine constraint keeps the workload in the building and that constraint has value: strict data residency or sovereignty, sub millisecond latency to on premises applications that cannot move, or deep integration with systems that will stay put. Where none of those hold, the same workload in an OCI region usually costs less and gains regional elasticity, so the cloud at customer premium needs justifying by the constraint rather than chosen for comfort. Licensing then reshapes the comparison: bring your own license plus OCI Support Rewards can shift the math materially for an organisation with substantial existing Oracle licenses, so placement and licensing have to be modelled together.
Here is what the model is, when it pays back over OCI, and how licensing changes the answer.
What is Exadata Cloud at Customer?
Exadata Cloud at Customer is the on premises member of the Exadata cloud family. Oracle installs and manages Exadata cloud infrastructure inside your data centre, you run database workloads on it with the same automation and operating model as Exadata in an OCI region, and you pay through OCI Universal Credits on a consumption basis rather than buying hardware outright. The point of the model is to let workloads that cannot physically leave your premises still adopt the cloud Exadata experience and draw down the same Universal Credits commitment that funds the rest of your OCI estate. That unification matters for cost governance, because the on premises database consumption shows up in the same cost and usage reporting and the same commitment drawdown as everything else, so you are not managing a separate capital purchase on a different clock. The trade is that you carry a physical footprint in your data centre, with its power, space, and refresh implications, in exchange for keeping the data local.
When does it pay back over Exadata in OCI?
The decision turns on whether a binding constraint keeps the workload on premises. Three constraints genuinely justify the model. The first is data residency and sovereignty: regulations or contracts that require the data to remain within a specific physical boundary that an Oracle region does not satisfy, where keeping the database in your own facility is the only compliant option. The second is latency: applications that demand sub millisecond response to the database and cannot themselves move to the cloud, where the round trip to a region would break the workload. The third is integration: a database tightly coupled to other on premises systems that will remain in place for the foreseeable future, where splitting them across a network boundary adds cost and fragility. Where one of these holds and matters, Exadata Cloud at Customer earns its premium because the alternative is not cheaper, it is non compliant or non functional. Where none holds, the same Exadata workload in an OCI region typically costs less, because you shed the on premises footprint and gain the elasticity to scale ECPUs and storage to demand rather than provisioning for a local peak. The error is treating cloud at customer as the default for any Oracle database, when it should be the considered choice for the subset of workloads a constraint actually pins down.
A Fortune 500 financial institution ran a large Oracle database estate and assumed all of it needed Exadata Cloud at Customer because some of it did. We split the estate by constraint: a core set of records was bound by data residency and a latency sensitive trading application could not move, and those genuinely justified the on premises model, while a larger set of reporting, analytics, and less coupled databases had no such constraint. We kept the constrained workloads on Exadata Cloud at Customer and moved the unconstrained ones to Exadata in an OCI region, sizing ECPUs to real demand and bringing existing licenses across to lower the rate, with OCI Support Rewards offsetting Oracle support fees. Total Oracle database cost fell by roughly a quarter, driven mostly by the unconstrained workloads shedding the on premises premium and gaining regional elasticity, with no compliance or latency regression on the workloads that stayed. The figures are verified against billing data and anonymised.
How does licensing change the answer?
Licensing can move the comparison as much as placement does, and it has to be modelled alongside it rather than treated as a footnote. The first lever is license included versus bring your own license. License included bundles the Oracle Database license into the consumption rate, which suits organisations without existing licenses, while bring your own license lets you apply licenses you already own to lower the rate, which often favours an enterprise with a substantial Oracle estate and active support. The second lever is OCI Support Rewards, which credit a portion of your OCI spend against your Oracle technology support bill, effectively discounting the support you already pay and improving the economics of running Oracle on OCI in either placement. For an organisation with significant existing licenses and support, the combination of bring your own license and Support Rewards can change which option is cheapest, sometimes making a region move even more attractive and sometimes softening the premium on a constrained on premises workload. The discipline is to model placement and licensing as one decision: the constraint decides where the workload can run, and the licensing position decides how much each viable placement actually costs, so you only pay the cloud at customer premium where a constraint forces it and the licensing math has been worked, not assumed.
Frequently asked questions
What is Exadata Cloud at Customer?
When does Exadata Cloud at Customer pay back over OCI?
How does licensing change the Exadata cost math?
Decide your Exadata placement on the numbers
We split your Oracle estate by constraint, model Exadata Cloud at Customer against Exadata in OCI with bring your own license and Support Rewards, and place each workload where it costs least within its constraints, with no provider commission and answering only to you. Our guarantee is plain: we reduce your cloud spend or we reimburse our service fee, on either a Fixed Fee or a no risk Gainshare basis. Book a strategy call to scope it, and follow more in The Cloud Spend Navigator.
Put a defensible number on your cloud spend.
No provider in the room, no published price list. Tell us your footprint and we will scope the savings against your billing data — we reduce your cloud spend or we reimburse our service fee.
The Cloud Spend Navigator: what changed in cloud pricing, commitments, and FinOps — no vendor spin.