Oracle Cloud@Customer vs Dedicated Region: The 2026 Decision Guide on Services, Cost, Commitment and Exit

Three on-premise OCI options, three distinct buyers

Oracle's marketing collateral often treats ExaCC, Compute Cloud@Customer, and DRCC as a single spectrum: light (ExaCC), medium (CCC), heavy (DRCC). Procurement teams approach the decision as a choice along that spectrum based on workload size. This framing is misleading. The three are best understood as three distinct products serving three distinct buyer profiles.

ExaCC is for database-centric sovereignty buyers. The customer's Oracle estate is database-heavy; the application tier runs elsewhere (on-premise existing stack, public OCI, or AWS/Azure with Interconnect back to ExaCC). The driver is keeping the database data and the database workload inside the data centre.

Compute Cloud@Customer is for application-tier sovereignty buyers. The customer wants OCI compute, object storage, and networking inside the data centre, often paired with a database that lives elsewhere (on-premise existing Oracle, ExaCC, or public OCI). The driver is keeping application workload inside the data centre with OCI's operational model.

DRCC is for full-stack sovereignty buyers. The customer needs broad OCI services - compute, database, OKE, object storage, identity, networking, analytics, AI - all running inside their facility, all operated to the OCI control plane. The driver is operating as if the customer ran their own OCI region.

The selection rule we apply: list the OCI services the customer needs on-premise. If only Exadata, ExaCC. If only compute and object, CCC. If five or more services beyond Exadata, DRCC. The detailed framework is in the Oracle Dedicated Region Guide and the cost framework in Oracle Cloud Licensing Guide.

Service catalogue side-by-side

The service catalogue is what justifies the cost gap. ExaCC and Compute C@C are narrow products. DRCC is a full region. For a customer that genuinely needs 8-10 OCI services on-premise, the ExaCC + CCC + extra-services-via-Interconnect-back-to-public-OCI pattern is operationally complex; DRCC consolidates that into a single platform.

2026 cost comparison: ExaCC vs Compute C@C vs DRCC

The 10x cost gap between ExaCC and DRCC reflects the 10x service breadth. For a customer who only needs Exadata, paying for DRCC is wildly inefficient. For a customer who needs the full OCI catalogue, ExaCC + Interconnect + public-OCI for the missing services often ends up costing more than DRCC because of the operational overhead and the cross-region traffic.

One nuance the marketing material rarely emphasises: ExaCC and Compute C@C share infrastructure design points with DRCC and can be upgraded in-place to DRCC if the customer's needs grow. Oracle has executed multiple ExaCC-to-DRCC conversions in 2024-2026. The customer can start small with ExaCC and graduate.

Commitment and exit mechanics

All three platforms carry minimum-term commitments. The mechanics differ.

ExaCC. Standard 3-year subscription on the activated OCPUs and the Quarter/Half/Full Rack footprint. Early exit typically owes the remainder of the contract value, less Oracle's salvage on the hardware. Negotiation room exists at year 2-3 of a 5-year contract because Oracle's hardware investment is largely depreciated.

Compute Cloud@Customer. Similar to ExaCC in structure. The rack is rented, the OCPUs and storage are metered, and early exit triggers the unbilled portion of the minimum.

DRCC. The minimum-capacity commitment is annual, not monthly, and the 3-7 year minimum is enforced through the MCC mechanism. Early exit from DRCC typically owes 50-75 percent of the remaining MCC. This is the most expensive exit of the three by far. Negotiate explicit termination clauses with a defined cap up-front. See the Oracle Negotiation Guide for the contract framework.

BYOL economics across the three

BYOL is supported on all three. The accounting mechanics differ.

On ExaCC, the customer brings full Database EE Processor licences against the activated OCPUs. The 0.5 core factor applies on Intel-based ExaCC. A 16-core ExaCC activation requires 8 Processor licences plus matching option licences. BYOL drops the effective rate from $0.87/OCPU/hour list to roughly $0.45/OCPU/hour.

On Compute Cloud@Customer, BYOL applies to any Oracle software the customer runs on the compute (WebLogic, GoldenGate, etc.). The OCI subscription covers the compute infrastructure; the customer's software licences cover the Oracle software running on top.

On DRCC, BYOL applies across all the OCI services the customer runs. The same conversion ratios as public-OCI apply: 1 Database EE Processor covers 4 ECPUs on Exadata Cloud Service inside DRCC. The economic effect is the same 50 percent discount as on public-OCI. The wider Licence Optimisation framework organises BYOL across the on-premise OCI options.

Audit defence implications

The on-premise OCI platforms are not audit-free. LMS does still audit Oracle software running inside ExaCC, Compute C@C, and DRCC, and the data they have access to via the OCI control plane is comprehensive.

Three audit-defence priorities apply equally across the three platforms. First, BYOL entitlement must cover the peak ECPU/OCPU usage measured at peak times, not the steady-state. Oracle's LMS scripts read the OCI consumption metrics directly. Second, options activated (Partitioning, ADG, Tuning, Diagnostics) must match the customer's option entitlement; LMS reads DBA_FEATURE_USAGE_STATISTICS through the OCI control plane. Third, any non-Oracle workload running on the same hardware (Compute C@C running customer applications, DRCC running 3rd-party software) does not affect Oracle licensing as long as Oracle's software is isolated; document the isolation in the architecture.

For the wider audit framework see Oracle Audit Guide and the BYOL-specific audit risks at Audit risk in Database@Hyperscaler.

Decision matrix: which on-premise OCI option fits your estate

The matrix shows the three are not substitutes - they are different tools. A buyer who picks ExaCC when they need DRCC will end up with 2-3 separate platforms (ExaCC, Compute C@C, and Interconnect to public-OCI) running in parallel, each with its own contract and operational model. A buyer who picks DRCC when ExaCC would suffice will pay 5-10x the necessary cost for capacity they never use. Pick deliberately. See DRCC Overview for the foundational architectural primer.

Frequently asked questions

What is the difference between Cloud@Customer and Dedicated Region?

Oracle Cloud@Customer is a family of on-premise OCI offerings that deliver a subset of OCI services into the customer data centre: Exadata Cloud@Customer (ExaCC) delivers Exadata database services only; Compute Cloud@Customer delivers OCI compute and object storage. Oracle Cloud Dedicated Region (DRCC) delivers the full OCI region with 100+ services. The choice depends on which OCI services the customer needs inside the data centre - just the database (ExaCC), just compute (CCC), or everything (DRCC).

Which is cheaper: ExaCC, Compute C@C or DRCC?

ExaCC has the lowest entry cost - a Quarter Rack ExaCC X11M lists at roughly $300K/year in cloud subscription plus $100K-$200K/year in facility costs. Compute Cloud@Customer is similar, around $250K-$400K/year all-in. DRCC has the highest minimum commitment at $4M-$8M/year in OCI Universal Credits plus $500K-$1M per rack/year in facility costs. The right comparison is per-service-consumed; for a customer who needs only Exadata, ExaCC is dramatically cheaper than DRCC.

Can I upgrade from ExaCC to DRCC later?

Yes. Oracle has supported in-place upgrades from ExaCC and CCC to DRCC where the customer's facility can accommodate the additional racks. The customer keeps their existing Exadata hardware, Oracle adds the additional racks for the broader OCI services, and the contract converts to a DRCC MCC. The migration is technically straightforward; the commercial conversion is the bigger negotiation.

What is the exit cost from each platform?

ExaCC and Compute C@C carry a 3-year minimum commitment with stated termination fees on early exit - typically the remainder of the cloud subscription value. DRCC has the highest exit cost because the minimum-capacity commitment is much larger; a customer terminating a 5-year DRCC at year 2 typically owes 50-75 percent of the remaining commitment value. Negotiate explicit exit clauses with a defined cap before signing any of the three contracts.

Are there published list rates for ExaCC, Compute C@C and DRCC?

ExaCC list rates are published in Oracle's price list and OCI marketplace - roughly $4,500/month per Quarter Rack OCPU activated, plus storage. Compute Cloud@Customer rates are similar but published per OCPU/hour. DRCC is custom-priced because the minimum-capacity commitment depends on facility footprint and service mix; Oracle does not publish a DRCC list rate. Buyers should benchmark all three against comparable deals at the same spend level, which is the heart of the negotiation.

Related Oracle licensing reading