Exadata Cloud at Customer is an Oracle cloud service that sits in your data center. The rack is a subscription, the database compute is metered, and unless you choose license included, the Oracle Database licenses on top are still yours to own and support.
Exadata Cloud at Customer is an Oracle cloud service that happens to sit in your data center. You rent the infrastructure, you meter the database compute, and unless you pick license included, the Oracle Database licenses on top are still yours to own and support.
You are buying a cloud subscription with a physical footprint, not a machine. Oracle owns the Exadata rack, installs it in your facility, operates it against the Oracle Cloud Infrastructure control plane, and takes it away at the end of the term.
That distinction decides everything downstream. The hardware never appears on your balance sheet, the database licenses never come with it, and the boundary of what Oracle actually operates is narrower than most buyers assume.
The three separate things buyers keep merging
| Layer | What it is | How it is charged | Who owns the risk |
|---|---|---|---|
| Infrastructure | The Exadata rack, in your room, owned and operated by Oracle | Fixed subscription for the committed term | You, for the term. It bills whether used or not |
| Database compute | Enabled cores on the database servers | Metered per core hour, scaled online | You, monthly, through scaling discipline |
| Database license | Enterprise Edition and every option in use | Bundled in the license included rate, or brought and supported by you | You, permanently, including the audit exposure |
Oracle operates the infrastructure up to the virtual machine cluster boundary: hardware, firmware, storage cells, the network fabric, and the control plane. Everything above that line is yours.
ExaCC is not a managed database service. If your business case assumed the database administration team gets smaller, check that assumption against this boundary before the subscription is signed.
ExaCC solves one problem well: data that cannot leave the building, on a platform that behaves like Oracle's cloud. Regulated industries, data residency rules, and latency to on premises applications are the three reasons we see it chosen.
Oracle documents the platform on the Exadata Cloud at Customer page and the wider family on the Exadata product page. If none of those three reasons apply to you, the public cloud version of the same service is usually simpler.
Two meters run at once, and only one of them responds to anything you do day to day. The infrastructure subscription is a fixed monthly charge tied to a committed term. The database compute charge varies with the cores you enable.
Enabled cores can be scaled down between peaks and, on current generations, a virtual machine cluster can be taken to zero. The database compute meter stops. The rack does not.
That asymmetry is the single most useful thing to understand before you size an ExaCC. An underused rack is not a small bill, it is the same bill with less work done on it.
Oracle has been moving cloud database services from the OCPU to a smaller unit called the ECPU, and the two are not interchangeable. A rate that looks lower per unit is not automatically lower per workload.
Read the metric in your ordering document, not in the marketing page, and rebuild the model in whichever unit the contract names. The service descriptions Oracle publishes with its cloud services contracts are the authoritative text, and current rates sit on the Oracle cloud pricing pages.
No. The infrastructure subscription includes no database licenses whatsoever, and that is the budget surprise on most ExaCC deals. You choose between renting the license inside the compute rate or bringing licenses you already own.
The two license paths on ExaCC, honestly compared
| Dimension | Bring your own license | License included |
|---|---|---|
| Compute rate | Lower per core hour | Higher per core hour |
| What you must already own | Enterprise Edition plus every option you use | Nothing |
| Ongoing support | 22 percent on the underlying licenses, forever | Included in the rate |
| Audit surface | Full. Your entitlements, your evidence | Minimal for the database itself |
| Exit position | You still hold perpetual licenses afterward | You hold nothing when the term ends |
| Best for | Estates with a large existing Oracle position | New workloads, short terms, no spare entitlement |
Bring your own license on Oracle's cloud converts at two OCPUs per Oracle Database Enterprise Edition processor license. The 0.5 core factor is already baked into the cloud unit, which is why the ratio is two and not one.
License included wins in three situations, and they are all worth naming plainly. It wins when you hold no spare entitlements, when the workload is short lived, and when you want the option compliance question to disappear.
It is not a bad product. It is a rental, priced like a rental, and it becomes expensive precisely when the workload turns out to be permanent.
White Paper · Oracle
Oracle Cloud@Customer Strategy
The 2026 BYOL map for Oracle Cloud@Customer. Read it free.
The Exadata service presents the full Enterprise Edition feature set, including the options an on premises buyer would have to purchase separately. Under license included that is fine. Under bring your own license it is the largest exposure on the platform.
Real Application Clusters is the obvious one, because Exadata is a clustered platform by design. Partitioning, Multitenant, In Memory, Advanced Compression, Active Data Guard, and the Diagnostics and Tuning packs are all available to anyone with the privilege to enable them.
What the option stack costs to bring, at 100 enabled OCPUs
| Component | List per processor | Licenses needed | List value you must own |
|---|---|---|---|
| Database Enterprise Edition | $47,500 | 50 | $2,375,000 |
| Real Application Clusters | $23,000 | 50 | $1,150,000 |
| Multitenant | $17,500 | 50 | $875,000 |
| Partitioning | $11,500 | 50 | $575,000 |
| Diagnostics and Tuning packs | $12,500 combined | 50 | $625,000 |
| Total to bring | List prices, before discount | 50 of each | $5,600,000 plus 22 percent a year |
That table is the reason bring your own license is not automatically the cheap path. It is cheap when you already hold that stack and it is fully supported. It is ruinous when you hold Enterprise Edition alone and your teams use the platform as designed.
Feature usage on Exadata is discoverable in the same way as anywhere else, through the option usage views. The difference is that on a shared platform, one team's decision creates the whole estate's liability.
The definitive list of what is an option and what is included sits in the Database Licensing Information manual. Read it against your entitlements before the platform arrives, not after.
The cost moves in three places, and only one of them is the rack you spent three months negotiating. The enabled core count, the option coverage, and the support line on your existing licenses do the rest.
What a bring your own license buyer is actually paying each year
| Line | Behavior | Who controls it |
|---|---|---|
| Infrastructure subscription | Fixed for the whole term | Negotiation, once, at signature |
| Database compute at the BYOL rate | Varies with enabled cores | Operations, every month |
| Support on your own licenses | 22 percent, rising with any uplift | The renewal team, annually |
| Option gaps | Zero until discovered, then very large | Whoever has the privilege to enable them |
Cores scale online to meet demand, which is genuinely useful and genuinely expensive. Every estate we modeled had enabled cores still running weeks after the peak that justified them.
Put a named owner on the scale down, run a monthly review of enabled cores against actual demand, and treat an unexplained increase as an incident. That single discipline recovered a median 17 percent of the database charge in our engagement file.
The standard pitch is that license included is the clean choice because it bundles the options Exadata workloads need. We disagree. In roughly two of three ExaCC estates we 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. But the honest version of that advice has a condition attached: bring your own license only wins if your option entitlements actually match what your teams enable. Inventory the options first, model both paths at realistic enabled core counts including scale down, and let the gap decide. The bundle is convenient, and Oracle prices the convenience.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
ExaCC gives you Exadata performance and a meter that never sleeps. The performance is the product. The meter, the option stack, and the support line you keep paying are the negotiation.
It does not include the database licenses, the database administration, the disaster recovery site, or the power in your own building. Every one of those has appeared as a late surprise in a business case we were asked to review.
Not in the subscription, and who pays instead
| Not included | What it means in practice |
|---|---|
| Oracle Database licenses under BYOL | You own them, you support them at 22 percent, and you evidence them in an audit |
| Database administration | Oracle stops at the virtual machine cluster boundary. Your team still runs the databases |
| A second site for disaster recovery | A standby platform is a second subscription, not a feature of the first |
| Backup capacity | Backup destinations are metered or purchased separately, wherever they land |
| Data center facilities | Floor space, power, cooling, and physical security stay on your budget |
| Non Oracle workloads | The platform runs Oracle Database. It is not general purpose infrastructure |
| Anything after the term | Oracle removes the rack. You keep the data and, under BYOL, the licenses |
ExaCC is operated from the Oracle Cloud Infrastructure control plane, so the rack needs a working connection out to an Oracle region. Your data stays in the building. The operational telemetry and the control path do not.
Security and network teams should see that requirement in writing before signature, because it is the single most common cause of a delayed installation.
Buying an Exadata Database Machine turns the subscription into a capital purchase plus hardware support, and it does not change the database license position one bit. You still license Enterprise Edition and every option on the cores you enable.
The comparison, including what a purchased rack does and does not entitle you to, is set out in our Exadata licensing guide and the wider engineered systems strategy playbook.
Three moves account for most of the money we have recovered on this platform, and none of them is a discount request. They are sizing, option control, and term structure.
The infrastructure charge is fixed, so oversizing it is the one mistake you cannot fix operationally. Size the committed infrastructure to sustained demand, and let the elastic core count absorb the peaks.
Model bring your own license and license included across the whole term, including support on the licenses you already own and a realistic scale down profile. Then model what happens if the workload doubles.
The answer flips more often than buyers expect. A workload that grows makes license included look worse each year, while a workload that shrinks makes stranded perpetual licenses the more painful outcome.
Where the counting itself is the argument, our core factor guide covers how cores become processor licenses on the ground you are converting from.
Oracle ExaCC, or Exadata Cloud at Customer, is an Oracle cloud service delivered on an Exadata rack that Oracle owns, installs in your data center, and operates from the Oracle Cloud Infrastructure control plane. You subscribe to it rather than buying it, and the hardware leaves at the end of the term.
No. The infrastructure subscription includes no database licenses. You either take the license included compute rate, which rents them, or bring your own licenses, which means you own Enterprise Edition plus every option in use and keep paying support on them.
ExaCC bills on two meters. The infrastructure subscription is fixed for the committed term and charges whether or not you run anything. The database compute charge is metered on the cores you enable and can be scaled online, in either license included or bring your own license form.
Two OCPUs are covered by one Oracle Database Enterprise Edition processor license, because the 0.5 core factor is already inside the cloud unit. Covering 100 enabled OCPUs therefore needs 50 processor licenses, roughly $2.4 million at list, and the same ratio applies to every option you use.
The service exposes the full Exadata feature set, including RAC, Partitioning, Multitenant, In Memory, Active Data Guard, and the Diagnostics and Tuning packs. Under license included they are covered by the rate. Under bring your own license you must already own each option that anyone enables.
You can scale the database compute down between peaks, and on current generations a virtual machine cluster can go to zero enabled cores. That stops the compute meter only. The infrastructure subscription continues to bill at the same rate for every month of the committed term.
No. Oracle operates the infrastructure up to the virtual machine cluster boundary, covering hardware, storage cells, fabric, and the control plane. Your team still owns the databases, the performance, the patch windows, the backup configuration, and the compliance position.
The support bill that continues under bring your own license. Buyers model the subscription and the compute rate, then discover they are still paying 22 percent a year on the perpetual licenses underneath. Idle enabled cores after a peak are a close second.
BYOL versus license included on Cloud@Customer, capacity discipline, and the subscription terms to pin before you sign.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
