Exadata Cloud@Customer puts Oracle's flagship database platform in your data centre under a cloud subscription model. The 4-year lock-in, minimum OCPU commitments, BYOL vs Licence-Included pricing differential (80% cost difference), and Universal Credits structure create commercial complexity that demands careful analysis before signing. Getting the configuration, commitment level, and licensing model right determines whether ExaCC delivers value or becomes an expensive infrastructure lock-in.
Oracle Exadata Cloud@Customer (ExaCC) is a hybrid cloud service that places Oracle's Exadata database infrastructure (the same hardware used in Oracle Cloud Infrastructure's public cloud) physically inside your data centre, while Oracle manages it as a cloud service. You do not own the hardware. Oracle installs, monitors, patches, and maintains the Exadata rack. You consume database resources through Oracle's cloud control plane, provision databases via OCI APIs and console, and pay through a cloud subscription model rather than a capital purchase.
ExaCC is designed for organisations that need Exadata's performance characteristics (smart storage scans, persistent memory caching, RDMA networking, and Autonomous Database capabilities) but cannot move their data to Oracle's public cloud due to regulatory requirements, data sovereignty constraints, ultra-low latency needs, or organisational policy. The hardware sits in your facility, behind your firewall, connected to your network, but it is managed and updated by Oracle as if it were a cloud region dedicated to you.
This hybrid model introduces a fundamentally different commercial relationship compared to traditional Exadata purchases. On-premises Exadata is a capital asset: you buy the hardware, own it, and pay annual support. ExaCC is a subscription: you pay monthly fees for infrastructure and per-OCPU consumption charges for database compute. There is no ownership, no buy-out option at end of term, and Oracle retains control of the hardware lifecycle. This distinction has significant implications for total cost of ownership, exit strategy, and negotiation leverage that enterprise procurement teams must understand before committing.
ExaCC is currently available in its latest generation configurations (X9M, X10M), featuring Intel Xeon processors, persistent memory (PMEM), RDMA over Converged Ethernet (RoCE) networking, and NVMe flash storage. These are the same hardware specifications used in Oracle's public cloud Exadata services and in purchased Exadata systems, ensuring performance parity between ExaCC and other Exadata deployment models. The generation of hardware deployed at your site is determined by Oracle at installation time and is refreshed at the 4-year renewal, ensuring you always run on reasonably current technology.
Exadata Cloud@Customer is not a product purchase. It is a multi-year service commitment that combines infrastructure subscription, compute consumption, and software licensing into a single commercial relationship. Organisations that evaluate ExaCC using traditional hardware procurement frameworks consistently underestimate the total cost and overcommit on capacity. The correct evaluation framework is total cost of ownership over the full 4-year term, including infrastructure base fees, OCPU consumption, licensing model choice (BYOL vs Licence-Included), support obligations, and renewal risk.
ExaCC deploys a physical Exadata rack in your data centre. The rack configuration ranges from a quarter rack (2 database servers, 3 storage servers) to a full rack (8 database servers, 12 storage servers), with half-rack and multi-rack options in between. Each database server provides a pool of OCPUs (Oracle Compute Units) that you allocate to database instances. Storage servers provide smart flash-cached storage with Exadata's intelligent data processing capabilities.
Oracle maintains a secure network connection from the ExaCC rack to the OCI control plane, typically via VPN or Oracle FastConnect. This connection enables remote monitoring, automated patching, firmware updates, and the cloud management interface. You interact with ExaCC through the same OCI console, APIs, and CLI tools used for public OCI services. Database provisioning, scaling, backup, and lifecycle management all operate through cloud-native interfaces, making ExaCC operationally consistent with public OCI from a management perspective.
Data centre space, power, cooling, physical security. Database creation, schema design, application configuration, user access management, data governance, compliance controls, network integration with internal systems.
Hardware ownership and lifecycle, firmware updates, OS and clusterware patching, storage management, hardware failure remediation, remote monitoring, cloud control plane operation, SLA compliance.
Security is shared: Oracle secures the infrastructure and enables encryption at rest. You secure databases, manage access controls, configure network policies, and maintain application-level security. Both parties collaborate on patching schedules and maintenance windows.
Reliable, low-latency connection to Oracle's cloud is mandatory for management. Oracle FastConnect or site-to-site VPN required. Outbound connectivity failure can impact Oracle's ability to manage and monitor the environment, potentially affecting SLA compliance and your ability to provision new databases or scale OCPUs. Plan for network redundancy.
The operational model shifts infrastructure management to Oracle but does not eliminate the need for Oracle DBA expertise. You still create and manage databases, design schemas, tune application SQL, manage backup strategies (within Oracle's framework), and control user access. If you deploy Autonomous Database on ExaCC, Oracle's automation handles more routine DBA tasks (auto-tuning, auto-indexing, auto-patching), but architectural decisions and application-level database management remain your responsibility.
One frequently underestimated aspect of ExaCC operations is the mandatory network connectivity to Oracle's cloud control plane. If this connection is interrupted, Oracle cannot perform remote management, monitoring, or patching, potentially affecting SLA compliance and your ability to provision new databases or scale OCPUs. The network link must be treated as critical infrastructure with appropriate redundancy. Oracle recommends FastConnect (dedicated private connectivity) over VPN for production ExaCC deployments. The ongoing bandwidth and latency requirements should be factored into the network architecture and cost planning from the outset, as they represent a recurring operational dependency that does not exist with traditional on-premises Exadata deployments.
ExaCC pricing has three distinct components: the infrastructure base fee, the OCPU consumption charge, and the software licensing cost. Each component has its own commercial dynamics and optimisation opportunities.
| Cost Component | Description | Approximate Range |
|---|---|---|
| Infrastructure Base Fee. | Monthly fee for the physical Exadata rack. Covers hardware lease, Oracle management, monitoring, and maintenance. Fixed for the contract term. | ~$8,000/month (quarter rack) to ~$40,000+/month (full rack). |
| OCPU Consumption: Licence-Included. | Per-OCPU-hour charge including Oracle Database licence. No separate database licence required. | ~$1.34/OCPU/hour (~$975/OCPU/month at full utilisation). |
| OCPU Consumption: BYOL. | Per-OCPU-hour charge when you bring existing Oracle Database licences. Dramatically lower rate. | ~$0.32/OCPU/hour (~$230/OCPU/month at full utilisation). |
| Minimum OCPU per Node. | Each database server requires a minimum number of active OCPUs, even when idle. | 8 OCPUs per database server (minimum). |
| Storage. | Included up to a base amount with the rack configuration. Additional storage charged per TB/month. | Varies by configuration. Base storage included; excess at OCI rates. |
| Contract Term. | 4-year standard commitment. No hardware ownership. No buy-out option at end of term. | 4 years minimum. |
The most significant pricing decision is the choice between BYOL and Licence-Included. At list prices, the Licence-Included OCPU rate (~$1.34/hour) is approximately 4x the BYOL rate (~$0.32/hour). For a workload consuming 50 OCPUs continuously, this translates to approximately $48,750/month (Licence-Included) versus $11,500/month (BYOL), a $37,250/month difference, or $447K/year. Over a 4-year term, the cumulative saving from BYOL is approximately $1.79M for just 50 OCPUs. For organisations with existing Oracle Database Enterprise Edition licences that can be redeployed, BYOL is almost always the correct choice for steady-state workloads.
However, BYOL requires that you own the appropriate Oracle Database licences and continue paying annual support on them (22% of the licence fee). The BYOL economics are only favourable if the support cost plus the BYOL OCPU rate is less than the Licence-Included rate. For licences that are already owned and have ongoing support costs regardless of whether they are deployed on ExaCC, the marginal cost of BYOL is effectively just the reduced OCPU rate, making it overwhelmingly cost-effective. For new licence purchases specifically to enable BYOL, the break-even calculation depends on the licence acquisition cost, the expected utilisation period, and the negotiated discount on both the licence and the OCPU rate.
A global insurance group was evaluating Oracle's proposal for Exadata Cloud@Customer to consolidate 45 Oracle Database instances running on aging Dell/VMware infrastructure. Oracle's initial proposal was a full rack with Licence-Included pricing for 200 OCPUs, totalling approximately $2.8M/year ($11.2M over the 4-year term). The organisation already owned 120 Oracle Database Enterprise Edition Processor licences with active support.
Redress Compliance conducted a detailed workload analysis that showed peak consumption of 140 OCPUs across all 45 databases. We recommended a half-rack configuration (4 database servers) with BYOL pricing, using the existing 120 Processor licences (sufficient for 240 OCPUs under the Authorised Cloud Environment BYOL conversion rules). The right-sized OCPU commitment was set at 140 OCPUs with flexibility to burst to 200. We also negotiated a 25% volume discount on the Universal Credits commitment and a 3% renewal cap for the next term.
Result: Final annual cost $1.05M/year (half-rack base fee + 140 OCPUs BYOL + existing support costs) versus the original $2.8M/year proposal. 4-year total: $4.2M versus $11.2M, a $7M saving (37.5% reduction). The organisation also eliminated $1.8M/year in Dell/VMware hardware support and licensing costs, improving net TCO further.
BYOL with existing licences is the single highest-leverage cost optimisation for ExaCC. Combined with right-sizing the rack configuration to actual workload requirements (rather than Oracle's growth projections) and negotiating volume discounts on the Universal Credits commitment, organisations consistently achieve 30 to 50 percent savings compared to Oracle's initial proposals.
The BYOL vs Licence-Included decision is not binary for most organisations. The optimal strategy is typically a blend: BYOL for steady-state production workloads where you already own licences, and Licence-Included for temporary, burst, or new workloads where licence acquisition is not justified. Understanding the conversion rules and support implications is essential for getting this blend right.
BYOL requires Oracle Database Enterprise Edition licences. Standard Edition licences cannot be used on Exadata. The conversion ratio in Oracle's Authorised Cloud Environment is 1 Processor licence = 2 OCPUs for Enterprise Edition. If you own 100 Processor licences, you can cover up to 200 OCPUs on ExaCC under BYOL. Named User Plus licences can also be used, but the conversion is typically less favourable and subject to minimum per-OCPU rules.
Licences used for BYOL must have active Oracle support. Licences where support has been dropped or that are on third-party support (Rimini Street, Spinnaker) are not eligible for BYOL. If you plan to use BYOL, you must continue paying 22% annual support on the relevant licences for the duration of the ExaCC deployment. Factor this ongoing support cost into the BYOL TCO calculation.
Oracle Database Options (Partitioning, Advanced Compression, Advanced Security, Diagnostics Pack, Tuning Pack, etc.) require separate licences under BYOL. They are not included in the base BYOL OCPU rate. Under Licence-Included, the pricing includes the base Database Enterprise Edition licence but typically does not include Options either (check the specific ExaCC service description). If your databases use Options extensively, verify that you have the corresponding licences for BYOL or understand the additional cost under Licence-Included.
Build a detailed TCO model comparing three scenarios: (1) 100% Licence-Included, (2) 100% BYOL with existing licences, (3) blended (BYOL for steady-state, Licence-Included for burst/new). Include infrastructure base fees, OCPU consumption at projected utilisation rates, support costs on BYOL licences, and any new licence acquisition costs. The 4-year TCO, not the monthly rate, is the correct basis for comparison.
ExaCC introduces several commercial risks that are distinct from both traditional on-premises purchases and standard public cloud consumption. Understanding these risks before signing the contract is essential for protecting your organisation's interests over the 4-year term.
Oracle's sales process encourages large annual commitments in exchange for volume discounts. Overcommitting means paying for unused credits that expire at year-end. A $2M annual commitment with 60% utilisation wastes $800K/year, $3.2M over the 4-year term. Always commit conservatively (70 to 80 percent of projected consumption) and negotiate the ability to increase mid-year.
Each additional database server adds minimum OCPU charges (8 OCPUs per server x OCPU rate x 24/7). A full rack (8 database servers) carries 64 minimum OCPUs. At Licence-Included rates, that is $74K/month in floor costs before any actual database work. Right-size to current needs and negotiate expansion rights for growth, rather than provisioning for a projected peak that may never materialise.
Without contractual caps, Oracle can increase pricing at the 4-year renewal. The combination of hardware refresh (newer, more expensive infrastructure) and standard price increases can raise annual costs by 15 to 25 percent. Negotiate renewal price caps (3 to 5 percent maximum increase) or minimum discount guarantees into the original contract.
Over a 4-year term, OCPU usage may grow beyond what existing BYOL licences cover. If OCPU consumption exceeds the BYOL licence entitlement, the excess must be covered by Licence-Included pricing (at 4x the BYOL rate) or additional licence purchases. Monitor BYOL utilisation quarterly to avoid compliance gaps that Oracle could identify during contract reviews.
ExaCC deals are among the largest Oracle cloud commitments an enterprise will make, typically $1M to $5M+ annually over a 4-year term. The scale of investment justifies significant negotiation effort, and Oracle's standard proposals consistently include margin that can be reduced through informed negotiation.
Oracle's initial proposals typically recommend larger configurations than required. Conduct an independent workload analysis to determine actual OCPU and storage needs. Present Oracle with a right-sized requirement. The discount negotiation is more effective when applied to a configuration that accurately reflects your needs, rather than negotiating a percentage off an inflated baseline.
Commit to 70 to 80 percent of projected annual consumption. Negotiate the right to increase the commitment mid-year at the same discount rate if usage exceeds projections. Secure a rollover clause for unused credits (Oracle rarely grants this, but it is worth requesting) or a year-over-year adjustment mechanism. Avoid committing to year-1 levels based on year-4 projections. Negotiate a ramp-up schedule instead.
The 4-year term creates significant switching costs. Oracle knows you are unlikely to migrate away at renewal. Protect against this leverage asymmetry by negotiating renewal price caps (3 to 5 percent), minimum discount guarantees, or the right to convert remaining commitment to public OCI credits if you choose not to renew ExaCC. These protections cost nothing at signing but save hundreds of thousands at renewal.
If your organisation has significant Oracle Database support, middleware licences, or other OCI consumption, bundle the ExaCC commitment with these existing obligations. Oracle's Support Rewards programme (earning cloud credits from support spend) can offset ExaCC costs. A $5M annual support bill can generate $1.25M in Support Rewards credits over the 4-year term, effectively reducing the ExaCC cost by 25%+ if you qualify.
Oracle's fiscal year ends 31 May. ExaCC deals closed in Q4 (March to May) benefit from quota pressure that drives deeper discounts and more favourable terms. For multi-million-dollar ExaCC commitments, the fiscal year-end timing can be worth an additional 5 to 10 percent in discount or significant contractual concessions (expanded environments, additional support credits, waived setup fees).
ExaCC competes with several alternatives, and the correct choice depends on your organisation's specific requirements around data residency, performance, existing Oracle investment, and long-term strategy.
| Alternative | When to Choose Instead of ExaCC | When ExaCC Wins |
|---|---|---|
| OCI Public Cloud (Exadata DB Service). | No data residency constraints. Can tolerate network latency to OCI region. Prefer OpEx flexibility without 4-year hardware commitment. | Strict data sovereignty or regulatory requirements. Ultra-low latency needed. Existing data centre investment to leverage. |
| On-Premises Exadata (purchased). | Want to own the hardware asset. Need full control of lifecycle and refresh timing. 7 to 10 year deployment horizon where CapEx is preferred. | Prefer OpEx model. Want Oracle-managed infrastructure. Plan to migrate to OCI public cloud within 5 years. Staff constraints for infrastructure management. |
| OCI Dedicated Region. | Need a full OCI region on-premises (not just Exadata). Running diverse OCI services (compute, storage, networking) alongside database. | Only need database workloads. Dedicated Region's minimum commitment ($6M+/year) exceeds database-only requirements. |
| AWS/Azure with Oracle BYOL. | Multi-cloud strategy. Non-Oracle applications dominate. Database workloads are smaller and do not need Exadata-specific performance. | Exadata-specific features required (smart scans, persistent memory, Autonomous Database). Large Oracle database estate with performance-sensitive workloads. |
| Database Migration (PostgreSQL, etc.). | Long-term strategy to exit Oracle. Workloads can be re-platformed. New development on non-Oracle technologies. | Deep Oracle PL/SQL investment. RAC, Partitioning, Advanced Security dependencies. Migration cost exceeds 5-year ExaCC TCO. |
ExaCC is the strongest choice when three conditions converge: (1) you have performance-sensitive Oracle Database workloads that benefit from Exadata-specific capabilities, (2) regulatory or operational requirements prevent migration to OCI public cloud, and (3) you have existing Oracle Database licences that can be deployed under BYOL to dramatically reduce the OCPU consumption cost. When all three conditions are met, ExaCC typically delivers better TCO than any alternative over a 4-year horizon.
Exadata Cloud@Customer (ExaCC) places Oracle-owned Exadata hardware in your data centre, managed by Oracle as a cloud service. Unlike public OCI, the hardware is physically in your facility, ensuring data residency, ultra-low latency, and compliance with regulations that prohibit data leaving your premises. You interact with ExaCC through the same OCI console and APIs as public cloud, but the compute and storage run on dedicated hardware under your roof. The key difference is the 4-year infrastructure commitment and the shared responsibility model where you provide data centre facilities while Oracle manages the Exadata infrastructure.
ExaCC costs comprise three components: (1) infrastructure base fee (~$8,000/month for quarter rack to $40,000+/month for full rack), (2) OCPU consumption (Licence-Included ~$1.34/OCPU/hour or BYOL ~$0.32/OCPU/hour), and (3) any additional storage beyond the base allocation. A typical half-rack deployment with 100 OCPUs under BYOL costs approximately $55K to $70K/month. With Licence-Included pricing, the same deployment costs $115K to $145K/month. Enterprise discounts of 20 to 50 percent are common, reducing these figures significantly. The standard commitment is 4 years via Universal Credits.
BYOL is almost always the correct choice for steady-state production workloads if you already own Oracle Database Enterprise Edition licences with active support. The BYOL OCPU rate (~$0.32/hour) is approximately 76% less than Licence-Included (~$1.34/hour). For 50 OCPUs running continuously, BYOL saves approximately $447K/year. The BYOL conversion ratio is 1 Processor licence = 2 OCPUs. Use Licence-Included only for temporary workloads, burst capacity, or scenarios where you do not own (and cannot cost-justify purchasing) the required licences.
ExaCC has two minimum commitments: (1) infrastructure: you must commit to the rack configuration for the full 4-year term (you cannot downsize mid-term), and (2) compute: each database server requires a minimum of 8 OCPUs to be active at all times. A quarter rack (2 database servers) has a minimum of 16 always-on OCPUs. A full rack (8 servers) has a minimum of 64. These minimum OCPUs are charged regardless of actual database utilisation. Additionally, Universal Credits annual commitments typically require spending a minimum amount each year.
At the end of the 4-year term, you either renew the subscription (typically with refreshed hardware) or return the equipment to Oracle. There is no option to purchase the hardware. Without renewal price protections negotiated into the original contract, Oracle can increase pricing at renewal, typically by 10 to 25 percent due to hardware refresh costs and standard price escalation. Negotiate renewal caps (3 to 5 percent) or minimum discount guarantees at the time of initial signing, when your leverage is strongest.
Yes. ExaCC uses the same OCI platform as public cloud, making workload portability relatively straightforward compared to other hybrid options. Databases can be migrated between ExaCC and OCI Exadata DB Service using Oracle Data Guard, RMAN, or Data Pump. Autonomous Database on ExaCC is also compatible with Autonomous Database on OCI public cloud. This portability is a key advantage of ExaCC over third-party cloud BYOL deployments, as it provides a natural migration path to full public cloud if data residency requirements change.
Five priorities: (1) Right-size the configuration to actual workload needs through independent workload analysis, not Oracle's sizing. (2) Commit to 70 to 80 percent of projected Universal Credits consumption and negotiate ramp-up provisions. (3) Use BYOL with existing licences for steady-state workloads. (4) Lock in renewal price caps (3 to 5 percent) and conversion rights at signing. (5) Time the deal to Oracle's Q4 (March to May) for maximum discount leverage. For commitments exceeding $1M/year, independent advisory support typically delivers 5 to 15 percent additional savings versus unassisted negotiation.
Our independent Oracle advisors help enterprises evaluate, negotiate, and optimise Exadata Cloud@Customer deals. From workload analysis and configuration right-sizing to BYOL strategy, Universal Credits structuring, and renewal protection. Typically delivering 30 to 50 percent savings on ExaCC investments.