Oracle Exadata Cloud@Customer (ExaCC): Pricing, Commitment Traps and Negotiation

What Is Oracle ExaCC?

Oracle Exadata Cloud@Customer (ExaCC) is Oracle's Exadata Database Service delivered as a fully managed cloud service on hardware that sits in the customer's own data centre. Oracle installs and retains ownership of the Exadata system — either an X10M or the current X11M generation — and operates it remotely as part of Oracle Cloud Infrastructure. The customer provides the physical space, power, cooling, and network connectivity; Oracle provides the platform, the management, and the database cloud services.

The result is an Oracle-managed cloud database platform that is physically present in the customer's facility. Workloads never leave the customer's data centre, but they are billed, managed, and supported as Oracle cloud services. This combination of on-premises physical control with cloud-managed operations is ExaCC's defining characteristic — and its primary commercial differentiator from both on-premises Exadata (which the customer buys and manages) and Oracle Cloud Infrastructure (where the hardware is in Oracle's data centres).

Who ExaCC Is Designed For

ExaCC is specifically designed for organisations that need Oracle's highest-performance database infrastructure but cannot or do not want to move workloads to Oracle's public cloud data centres. The most common drivers for ExaCC adoption include data residency requirements that mandate data stays within a specific jurisdiction or physical location, latency requirements for applications that need sub-millisecond database response times from on-premises compute, regulatory frameworks (financial services, healthcare, government) that impose constraints on data centre location or management access, and contractual obligations to clients that prohibit third-party cloud storage of their data.

Organisations that do not have at least one of these drivers should typically evaluate Oracle Cloud Infrastructure (OCI) dedicated infrastructure as an alternative to ExaCC, since OCI offers greater flexibility, lower commitment risk, and comparable performance without the 4-year on-premises infrastructure commitment.

The ExaCC Commercial Structure

Oracle ExaCC pricing has two distinct components: a fixed infrastructure subscription fee and a variable compute consumption fee. Understanding these separately is essential for building an accurate total cost of ownership model.

Infrastructure Fee

The infrastructure fee is the fixed monthly cost for the Exadata hardware deployed in the customer's data centre. This fee is committed for a minimum 4-year term and cannot be reduced mid-term. For the X10M generation, Oracle's published Base System infrastructure cost is approximately $8,000 per month; a Full Rack configuration is approximately $43,200 per month. X11M infrastructure is priced differently and typically higher, reflecting the improved hardware specification. The infrastructure fee is payable regardless of actual database workload consumption — it is the floor cost of the ExaCC commitment.

Compute and Database Fees

On top of the infrastructure fee, the customer pays for database compute resources consumed, measured in Elastic Compute Processing Units (ECPUs) on X11M infrastructure or OCPUs on X10M. The compute rate depends on whether the customer uses BYOL or Licence-Included mode. Under Licence-Included, the ECPU rate is approximately five times the BYOL rate, reflecting the bundled database licence cost. Volume commitments at $500,000 or $1 million annual compute spend attract Oracle-standard discounts of approximately 10 and 15 percent respectively.

BYOL vs Licence-Included: The Most Important Decision

The single most financially consequential decision in any ExaCC deployment is whether to use Bring Your Own Licence (BYOL) or Licence-Included pricing. Over a standard 4-year ExaCC commitment, this decision can represent a cost difference of $1.5 million or more for a mid-sized deployment.

BYOL allows the customer to apply existing, active, Oracle-supported on-premises Oracle Database Enterprise Edition licences to the ExaCC compute, reducing the per-ECPU rate by approximately 80 percent compared to Licence-Included. BYOL is the right choice for any organisation with a substantial existing Oracle Database licence estate — typically organisations that have been running Oracle on-premises for several years and have perpetual licences with active support.

Licence-Included bundles the Oracle Database licence into the compute rate. It is appropriate for organisations that do not hold Oracle Database perpetual licences, or for short-term or variable workloads where the licence-included model provides flexibility without a perpetual licence investment. For long-running production databases over a 4-year term, Licence-Included is almost always significantly more expensive than BYOL.

The 4-Year Commitment: What It Means in Practice

Oracle ExaCC's 4-year infrastructure commitment is not a typical subscription that can be cancelled with notice. It is a contractual obligation to pay the fixed monthly infrastructure fee for the full 4-year term. Early termination requires payment of the remaining commitment, often on an accelerated schedule specified in the contract. For an organisation committing to a Full Rack ExaCC at $43,200 per month, the 4-year infrastructure commitment is $2,073,600 — a liability that must be understood and accepted before contract execution.

The 4-year term also has renewal implications. At the end of the initial term, Oracle will offer a renewal at then-current pricing, which will reflect any infrastructure list price increases over the intervening four years. Without a contractually committed renewal cap, the second 4-year term will be priced at Oracle's discretion. Negotiating a renewal price cap — typically 3 to 5 percent annual escalation — at initial contract execution is a standard independent advisory recommendation that Oracle will usually accept in competitive deal situations.

The ECPU Metric and the X11M Generation

Oracle transitioned ExaCC to the ECPU (Elastic Compute Processing Unit) billing metric with the X11M hardware generation. ECPUs replace OCPUs as the compute billing unit, and from May 2025, all new Autonomous VM Clusters on ExaCC are ECPU-only. The minimum ECPU requirement is 8 ECPUs per database node, which establishes a floor cost for any ExaCC database regardless of actual workload size. Organisations evaluating ExaCC for smaller workloads should verify that the ECPU minimum does not make ExaCC cost-ineffective compared to dedicated on-premises infrastructure or OCI alternatives.

When ExaCC Makes Commercial Sense

ExaCC is commercially justified when three conditions are met simultaneously. First, the organisation has a genuine data residency or regulatory requirement that prevents use of Oracle's public cloud data centres. Second, the organisation's database workloads are large enough to justify the infrastructure commitment — typically requiring at least a Base System configuration with meaningful ECPU consumption. Third, the organisation holds sufficient active Oracle Database perpetual licences to use BYOL, capturing the 80 percent compute cost saving relative to Licence-Included.

Where any one of these conditions is not met, alternative approaches — including Oracle Cloud Infrastructure in a geographically appropriate region, on-premises Exadata with perpetual licensing, or non-Oracle database platforms — should be evaluated before accepting the ExaCC commitment.

Five Things to Do Before Signing an ExaCC Agreement

1. Commission an independent BYOL licence count. Before deciding between BYOL and Licence-Included, verify the count of active, supported Oracle Database Enterprise Edition licences available for BYOL qualification. Do not rely on Oracle's BYOL assessment tools, which may apply conversion ratios in Oracle's favour.

2. Model the full 4-year TCO. Build a total cost of ownership model that includes infrastructure fees, ECPU consumption at both BYOL and Licence-Included rates, annual Oracle support escalation at 8% per year on any remaining on-premises licences, network connectivity costs, and early termination liability. Oracle's proposal documents a monthly rate; the full financial commitment is materially larger.

3. Negotiate infrastructure pricing and a renewal cap. Oracle's list infrastructure pricing is a starting point, not a floor. Discounts of 10 to 25 percent are achievable at full rack commitment levels or during Oracle's Q4 window (March through May, Oracle's fiscal year ending May 31). A renewal cap of 3 to 5 percent annual escalation should be a standard negotiating objective.

4. Review early termination provisions. The specific early termination payment schedule in Oracle's standard ExaCC agreement varies and can be more onerous than simply paying remaining monthly fees. All early termination provisions should be reviewed and, where necessary, negotiated before signature.

5. Get independent legal review of Oracle management access rights. Oracle retains remote management access to ExaCC infrastructure for patching and support. Regulated organisations should review what Oracle management access means for their specific compliance framework before committing to ExaCC as a compliant deployment model.