Oracle Exadata Cloud@Customer (ExaCC) Licensing Guide

What Is Oracle Exadata Cloud@Customer?

Oracle Exadata Cloud@Customer (commonly referred to as ExaCC) is Oracle's Exadata Database Service delivered as a managed cloud service within the customer's own data centre. Oracle ships, installs, and retains ownership of the Exadata hardware — typically an X10M or X11M generation system — and the customer consumes database resources as a cloud service, measured in Elastic Compute Processing Units (ECPUs) or Oracle CPU hours, with a subscription structure that mirrors Oracle Cloud Infrastructure (OCI) pricing.

The fundamental value proposition of ExaCC is the combination of cloud operating model — subscription pricing, Oracle-managed patching and operations, elastic compute scaling, and consumption-based billing — with on-premises infrastructure. For organisations that cannot move their database workloads to a public cloud data centre due to data residency requirements, latency constraints, regulatory obligations, or existing data centre investments, ExaCC offers a path to Oracle's highest-performance database platform without the public cloud exposure.

Oracle manages ExaCC remotely. The customer provides data centre space, power, cooling, and network connectivity, but Oracle retains administrative access to the infrastructure. This is an important commercial and operational nuance: from a licensing perspective, ExaCC workloads are treated as Oracle Cloud services, not as on-premises workloads, which has implications for how existing on-premises Oracle licences can be leveraged and how support costs compound over the contract term.

Infrastructure Tiers and Sizing

Oracle ExaCC is available in several hardware configurations, with the current generation being the X11M (released in 2025) and the previous generation X10M. The infrastructure tier determines the fixed monthly infrastructure fee, which is a committed cost regardless of compute consumption.

Exadata X11M — Current Generation

The X11M generation is Oracle's most recent ExaCC hardware, featuring AMD EPYC processors in database servers and Oracle's proprietary intelligent storage servers. A base X11M configuration provides 380 available processor cores, 5.6 million SQL read I/O operations per second, and 2 TB per second of memory bandwidth. The X11M uses ECPUs as its compute billing metric, with a minimum of 8 ECPUs per database node.

Exadata X10M — Previous Generation

The X10M remains in active deployment and is priced differently from the X11M. Oracle's published infrastructure pricing for an X10M Base System — two database servers and three storage servers — is approximately $8,000 per month. A full rack X10M configuration scales to approximately $43,200 per month for the infrastructure component. These prices represent the fixed committed infrastructure fee before any compute or licence costs are added.

Configuration Scaling

ExaCC infrastructure is available in multiple configurations between Base System and Full Rack. Oracle also offers the ability to expand infrastructure within a rack over time, providing some flexibility in initial deployment size. However, the infrastructure subscription is committed for a minimum four-year term regardless of the initial configuration size, and scaling down is not permitted mid-term — only scaling up is supported within the infrastructure commitment.

BYOL vs Licence-Included: The Economics

Oracle ExaCC offers two licensing models for database workloads: Bring Your Own Licence (BYOL) and Licence-Included. Choosing correctly between these two models is the single most consequential licensing decision in an ExaCC deployment, and the commercial difference is substantial.

Licence-Included Model

Under the Licence-Included model, the Oracle Database Enterprise Edition licence (and any relevant options) is bundled into the per-ECPU hourly rate. The customer pays a single per-ECPU rate that covers both the cloud infrastructure consumption and the Oracle software licence right. This model is appropriate for organisations that do not hold existing Oracle Database Enterprise Edition licences, or for short-term workloads where purchasing licences would not be cost-effective.

The Licence-Included rate on ExaCC is approximately five times the BYOL rate per ECPU. For long-running production databases, this premium is significant. An organisation running a production Oracle Database on ExaCC under Licence-Included for four years — the minimum infrastructure commitment term — pays for the Oracle software licence effectively four times over, which is materially more expensive than purchasing perpetual licences upfront and using BYOL.

BYOL Model

Under BYOL, the customer brings existing on-premises Oracle Database Enterprise Edition perpetual licences to ExaCC. Oracle applies the BYOL discount to the per-ECPU rate, reducing it to approximately one-fifth of the Licence-Included rate. Only active, fully supported Oracle licences qualify for BYOL on ExaCC — licences on third-party support contracts or licences where the customer has lapsed support do not qualify.

The BYOL economics are compelling for any organisation with a meaningful perpetual Oracle Database licence estate. The difference between BYOL and Licence-Included on ExaCC for a medium-sized deployment of 50 OCPUs over four years is in the range of $1.5 to $2 million at list price, representing the most significant cost variable in ExaCC deployment planning.

BYOL Conversion Considerations

Oracle's BYOL conversion for ExaCC uses a specific processor count conversion factor. Existing on-premises Oracle Database licences are counted in Named User Plus (NUP) or Processor metrics. On ExaCC, the BYOL entitlement is expressed in ECPUs, with Oracle's documented conversion ratio applying. Organisations considering BYOL should conduct a formal licence count to confirm they have sufficient active, supported licences to cover the ExaCC deployment before committing to BYOL pricing at contract execution.

A critical point: once an ExaCC contract is executed under BYOL, Oracle will require the BYOL licence count to be maintained at the contracted level for the duration of the commitment. Any lapse in support on the underlying on-premises licences — including failure to pay the annual support renewal — will disqualify those licences from BYOL status and potentially require the customer to migrate to Licence-Included pricing at the significantly higher rate.

ECPU Billing: The New Compute Metric

Oracle transitioned ExaCC to the ECPU (Elastic Compute Processing Unit) billing metric in 2025, replacing the legacy OCPU (Oracle CPU) metric that had been used in previous Exadata generations. Understanding the distinction between these metrics is important for organisations migrating from X9M or X10M infrastructure, or for any comparison between ExaCC and on-premises Exadata licensing.

What Is an ECPU?

An OCPU was defined as the equivalent of one physical processor core with hyper-threading enabled — making it equivalent to two vCPUs in x86 compute. An ECPU, by contrast, is not tied to a specific physical hardware unit. Oracle introduced ECPUs as a durable pricing metric that remains stable as the underlying processor generation changes. The practical implication is that the number of ECPUs required for a given workload is determined by Oracle's conversion table rather than by direct hardware mapping, and the ECPU rate per hour can be adjusted by Oracle without the currency of the metric itself changing.

OCPU to ECPU Transition

From May 28, 2025, all new Autonomous VM Clusters on ExaCC use ECPUs only. Existing OCPU-based Autonomous VM Clusters can be converted to ECPU without downtime, via service request. For new X11M infrastructure, ECPUs are the only available metric. Oracle's documentation confirms that X11M and Exadata Cloud@Customer X11M exclusively use ECPUs, while X10M and earlier generations use OCPUs. This metric split means that organisations with mixed-generation ExaCC deployments may be managing two different compute billing metrics simultaneously during any transition period.

Minimum ECPU Commitment

Oracle's ExaCC subscription requires a minimum of 8 ECPUs per database node at any given time. This minimum is not a floor that can be avoided by deprovisioning databases — it applies at the VM cluster level and means that even very small workloads on ExaCC carry a fixed minimum compute cost that may exceed the compute actually consumed. Organisations that use ExaCC for workloads that could otherwise run on smaller infrastructure should model whether the ECPU minimum makes ExaCC cost-competitive for their specific scenario.

The 4-Year Infrastructure Commitment and Its Implications

Oracle ExaCC Infrastructure subscriptions require a minimum 4-year commitment. This is not a negotiating position — it is Oracle's standard commercial term for ExaCC, reflecting Oracle's need to recover hardware and installation investment over a fixed period. Understanding what this 4-year commitment means for commercial flexibility, cost structure, and strategic options is critical for any organisation considering ExaCC.

What the 4-Year Commitment Covers

The 4-year term applies to the infrastructure subscription — the fixed monthly fee for the Exadata hardware. The ECPU and database resource subscriptions layered on top of the infrastructure are typically structured as annual or multi-year consumption commitments, but these can, in principle, be adjusted at the annual renewal point within the 4-year infrastructure commitment. The infrastructure cost is committed; the compute cost has more flexibility.

Early Termination

Oracle's standard ExaCC agreement includes provisions for the remaining infrastructure subscription commitment to be payable as a lump sum in the event of early termination. This means that an organisation that decides to exit ExaCC at the two-year mark of a four-year commitment will owe Oracle the remaining two years of infrastructure fees at the time of termination. The financial exposure from early termination should be explicitly modelled and included in any ExaCC business case, and the specific early termination provisions should be reviewed and negotiated before contract execution.

Renewal Dynamics

At the end of the 4-year infrastructure term, Oracle will offer renewal at then-current pricing. Since Oracle support fees for on-premises products increase at 8 percent per year compound, and ExaCC infrastructure pricing is subject to Oracle's standard escalation, the renewal rate for a second 4-year term will be materially higher than the initial commitment rate. Negotiating a price cap on the renewal rate — or securing the right to extend at a fixed uplift — is an important commercial protection that most customers fail to request at initial contract execution.

Autonomous Database on ExaCC

Oracle Autonomous Database is available on ExaCC as Autonomous Database on Dedicated Infrastructure (ADB-D). This provides the self-managing, self-securing, and self-repairing capabilities of Oracle Autonomous Database on the ExaCC hardware in the customer's data centre. From a licensing perspective, Autonomous Database on ExaCC is priced differently from the standard Oracle Database Enterprise Edition workloads on ExaCC.

Autonomous Database is Licence-Included only — there is no BYOL option for Autonomous Database on ExaCC. This means that organisations cannot leverage existing Oracle Database perpetual licences to reduce the cost of Autonomous Database workloads on ExaCC. The Licence-Included rate for Autonomous Database on ExaCC includes the machine learning and autonomous management capabilities as well as the database licence, but the per-ECPU rate is higher than standard Database Enterprise Edition Licence-Included pricing.

Organisations considering a mixed ExaCC deployment — some workloads on standard Oracle Database Enterprise Edition with BYOL, others on Autonomous Database Licence-Included — should model the cost of each workload type separately and ensure that the commercial terms reflect the mixed licensing structure accurately.

Data Residency and Regulatory Compliance Drivers

The primary business driver for ExaCC over Oracle Cloud Infrastructure is data residency and regulatory compliance. ExaCC allows organisations to keep their data within their own data centre — within a specific jurisdiction, within a specific physical security perimeter, or within an infrastructure environment that satisfies sector-specific regulatory requirements — while still consuming Oracle-managed cloud database services.

Common regulatory drivers include financial services regulations that prohibit customer data from leaving a specific country or jurisdiction, healthcare data privacy laws (HIPAA, GDPR) that require specific data handling controls, government and public sector security classifications that mandate on-premises data processing, and contractual obligations to clients that prohibit third-party cloud data storage. ExaCC satisfies these requirements because the physical hardware sits in the customer's data centre and Oracle's management connection traverses the customer's network under the customer's security controls.

However, organisations should be aware that ExaCC's data residency guarantees are dependent on Oracle's management connectivity model. Oracle retains remote management access to the ExaCC infrastructure for patching, monitoring, and support purposes. The data itself does not leave the customer's data centre, but Oracle personnel have remote management access to the platform. Highly regulated organisations should review Oracle's management access protocols and the contractual provisions governing Oracle's remote access rights before committing to ExaCC as a compliance-satisfying deployment model.

Eight Commercial Traps to Avoid

1. Signing BYOL Without a Formal Licence Count: Oracle will accept a BYOL commitment on the basis of the customer's licence representation. If the actual licence count subsequently proves insufficient, Oracle will demand either additional licence purchases or migration to Licence-Included pricing at significantly higher rates. A formal, documented licence count conducted before ExaCC contract execution is non-negotiable.

2. Allowing On-Premises Support to Lapse: BYOL qualification on ExaCC requires that the underlying on-premises licences are on active Oracle support. If support is lapsed — even temporarily — BYOL status can be challenged. Organisations that intend to migrate entirely to ExaCC and cancel on-premises support should structure their Oracle agreements to maintain BYOL qualification throughout the transition period.

3. Underestimating the ECPU Minimum: The 8 ECPU per database node minimum applies regardless of actual workload. Small workloads that could run economically on a single-node server will carry the same minimum ECPU cost as larger production databases. ExaCC is not cost-competitive for small or intermittent workloads.

4. No Early Termination Clause Review: Standard Oracle ExaCC agreements require payment of the remaining infrastructure commitment on early termination. The specific provisions vary by contract, and some versions of the agreement include accelerated payment schedules that are significantly more onerous than simply paying the remaining monthly fees. All early termination provisions should be reviewed and negotiated before signature.

5. Not Negotiating a Renewal Price Cap: Oracle's standard ExaCC agreement includes no cap on renewal pricing. At renewal, Oracle will propose pricing at then-current rates, including any infrastructure list price increases over the 4-year term. A cap on renewal escalation — typically 3 to 5 percent per year — should be a standard negotiating objective at initial contract execution.

6. Confusing ExaCC with Exadata On-Premises Licensing: ExaCC workloads are treated as Oracle Cloud services, not as on-premises workloads. This means that the favourable licensing provisions available for on-premises Exadata — including Oracle Real Application Clusters (RAC) all-inclusive pricing on certain Exadata configurations — may not apply to ExaCC. The applicable licensing rules for ExaCC workloads should be explicitly confirmed in the contract.

7. Not Modelling Network Connectivity Costs: ExaCC requires dedicated high-bandwidth, low-latency network connectivity between the Exadata infrastructure and Oracle's management network. Oracle specifies the network requirements, but the customer is responsible for provisioning and funding the connectivity. Network costs are material for ExaCC deployments and are frequently absent from initial business cases.

8. Single-Vendor Infrastructure Planning: The 4-year ExaCC commitment creates a significant lock-in to Oracle as the database infrastructure provider. Organisations that are simultaneously evaluating AWS RDS, Azure SQL Managed Instance, or Google Cloud Spanner for database workloads should factor the opportunity cost of the ExaCC commitment into their cloud strategy planning.

Negotiation Strategy for Oracle ExaCC

Oracle ExaCC negotiations involve four distinct commercial levers: infrastructure pricing, compute pricing, BYOL conversion terms, and contract flexibility provisions. Independent advisory experience across ExaCC engagements shows that each lever can yield meaningful savings when approached systematically.

Infrastructure Pricing

Oracle's ExaCC infrastructure list pricing is not fixed. Oracle's published pricing represents the starting point for negotiation, not the achievable rate. Discounts of 10 to 25 percent below list infrastructure pricing are achievable for organisations committing to full rack or multi-rack deployments, for organisations in Oracle's Q4 window (March through May, when Oracle's fiscal year ends May 31 and account teams have strong incentive to close deals), and for organisations with significant existing Oracle relationships that provide commercial leverage. The infrastructure subscription should be negotiated as a fixed monthly fee with a documented renewal cap, not as a list-price schedule subject to unilateral revision.

Compute Pricing

ECPU rates for both BYOL and Licence-Included are subject to volume-based discounts. Oracle's standard volume thresholds for ExaCC discounting are approximately $500,000 annual compute commitment (approximately 10 percent discount) and $1 million annual commitment (approximately 15 percent discount). These thresholds are Oracle's published guidance and represent the minimum achievable discount, not the ceiling. Organisations committing to multi-year ECPU volumes should negotiate the annual compute commitment as part of the initial ExaCC contract rather than accepting the default consumption pricing.

BYOL Conversion Terms

The BYOL conversion agreement — the contractual provision that establishes BYOL qualification and the applicable discount — should explicitly state the conversion ratio between on-premises processor licences and ExaCC ECPUs, the conditions under which BYOL status is maintained, the remediation process if on-premises licence count changes, and the specific versions and editions of Oracle Database that qualify for BYOL. Ambiguity in BYOL conversion terms is a consistent source of commercial disputes in ExaCC deployments.

Contract Flexibility

Contract provisions that protect commercial flexibility include a capped annual escalation on infrastructure fees (3 to 5 percent), a defined renewal option at a specific price or price cap, documented early termination liability including any accelerated payment provisions, explicit network management access protocols for Oracle remote management, and the right to scale compute commitments at annual renewal without penalty.

Advisory Recommendations

For organisations evaluating or deploying Oracle ExaCC, the following recommendations reflect independent advisory experience across ExaCC engagements in EMEA and North America.

Conduct a formal Oracle licence count before ExaCC negotiations begin. The BYOL decision — which can represent $1.5 million or more in cost differential over a 4-year term — cannot be made without accurate knowledge of the current active, supported Oracle licence estate. This audit should be independent of Oracle's own BYOL assessment tools, which may apply conservative conversion ratios in Oracle's favour.

Model the full 4-year total cost of ownership, including infrastructure fees, ECPU consumption, support costs at 8 percent annual escalation, network connectivity, and potential early termination liability. Oracle's ExaCC proposals typically present a simplified monthly rate that obscures the compounding effect of these cost components over the commitment term. An independent TCO model, developed before negotiations, provides the analytical foundation for challenging Oracle's commercial position.

Use Oracle's Q4 window for major negotiations. Oracle's fiscal year ends May 31, making the March through May period Oracle's most commercially motivated quarter. ExaCC negotiations initiated in Q4 consistently achieve better pricing and more favourable contract terms than equivalent negotiations conducted in Oracle's Q1 or Q2.

Do not accept Oracle's standard ExaCC agreement without legal and commercial review. The standard Oracle Cloud Services Agreement and Oracle ExaCC-specific terms contain provisions — including remote management access rights, early termination acceleration, and renewal pricing — that require careful legal review before execution. Independent advisory support on ExaCC commercial terms consistently identifies clauses that require negotiation or modification before signature.

Evaluate ExaCC against Oracle Database Service on OCI dedicated infrastructure for workloads where data residency requirements can be addressed through OCI's Government Cloud or regional cloud deployments. For some organisations, the lower infrastructure cost and greater compute flexibility of OCI dedicated infrastructure is a more cost-effective alternative to ExaCC, even accounting for OCI data centre proximity requirements.