How Much Does Oracle Cloud@Customer Cost? Real 2026 Pricing, Hidden Line Items and a Worked $3.8M Deal

What Cloud@Customer pricing actually looks like in 2026

Oracle Cloud@Customer is sold as an OCI consumption service - the customer is billed per ECPU-hour or OCPU-hour, plus storage, plus options. That framing is correct for the metering side. It is incomplete for the cost side. The customer signing a Cloud@Customer ordering document picks up four additional cost stacks that do not appear in the headline ECPU rate: a minimum capacity commitment (the floor), a hardware refresh allocation (the depreciation), an infrastructure support fee (the maintenance), and a site/install cost (the deployment). Each is recoverable in the negotiation - none are recoverable after signing.

The framework below decomposes a Cloud@Customer deal into its real cost components and gives you the 2026 reference rates to benchmark your own proposal. The wider on-premise OCI architecture sits in the Oracle Dedicated Region Guide (covering DRCC, ExaCC and Compute Cloud@Customer); the side-by-side comparison is at Cloud@Customer vs Dedicated Region; the broader cloud cost framework sits at Oracle Cloud Licensing Guide.

The four Cloud@Customer families and their meters

Oracle's Cloud@Customer portfolio is not one product. As of 2026 it covers four distinct families, each with its own metering and pricing model. Confusing them in procurement is one of the most common causes of cost overrun.

The rest of this article focuses on the three smaller-footprint families - ExaCC, Database@Customer and Compute Cloud@Customer. For DRCC pricing specifically, see DRCC pricing guide.

ExaCC headline rates - 2026 reference pricing

Exadata Cloud@Customer on the current X11M generation is metered in ECPUs (the smaller-grain unit) or OCPUs (the legacy unit equivalent to 2 ECPUs on Exadata). Oracle's 2026 published rates:

Key reading note: the infrastructure minimum is fixed regardless of CPU activation - the customer who activates 8 ECPUs on a Quarter Rack pays the same infra fee as the customer who activates 100 ECPUs. The ECPU fee is on top.

Database@Customer (formerly Roving Edge / Exadata-on-customer-hardware) rates 2026

Database@Customer is Oracle's newer offering where the customer brings their own approved x86 hardware (Dell, HPE, Cisco UCS) and Oracle ships the Oracle Database service on top, managed via the OCI control plane. The metering is identical to ExaCC at the ECPU level, but the infrastructure cost shifts from Oracle to the customer.

The economic distinction matters: a customer with sunk hardware capital and a 5-year refresh cycle ahead can land Database@Customer materially cheaper than ExaCC over the contract life. The catch: Database@Customer does not include Exadata storage cells, so workloads that require Smart Scan, Storage Indexes, Hybrid Columnar Compression or storage-cell offload will not fit. Those workloads need ExaCC.

Compute Cloud@Customer rates 2026

Compute Cloud@Customer is the VM/container appliance positioned against on-premises VMware or Azure Stack HCI. Pricing is metered in OCPU-hours plus storage:

The CCC value proposition lands cleanly only when the customer has a real on-premises data-residency requirement that cannot be served by Azure Stack HCI or VMware Cloud Foundation. The CCC OCPU rate at $0.025-0.038 is materially higher than equivalent OCI Universal Credit rates in public OCI; the premium is the appliance physically sitting in the customer's facility.

The hidden line items that do not appear in the headline rate

Beyond the published ECPU/OCPU rates, every Cloud@Customer ordering document includes these additional cost stacks. They are not hidden in the sense of secret - they are in the ordering document - but they routinely surprise procurement teams who model only the per-ECPU rate.

Minimum Capacity Commitment (MCC): Cloud@Customer contracts include an MCC that floors annual consumption. On ExaCC, the MCC typically runs $400K-$900K per quarter rack per year on top of the infrastructure fee. On DRCC the MCC routinely runs $4M-$8M per year.

Hardware refresh allocation: Oracle commits to a hardware refresh on a 5-7 year cycle. The refresh cost is baked into the monthly infrastructure fee but accounted on Oracle's balance sheet. The customer should verify the refresh commitment is named (generation and date), not vague (see DRCC negotiation playbook Lever 3).

Infrastructure support fee: Annual support on the Oracle-supplied hardware runs 22 percent of the appliance list price - the same support rate as on-premises Exadata. On a $1.2M Quarter Rack, that is $264K per year on top of the consumption fees.

Site survey and install: One-time professional services fee for the site survey, network provisioning, install and burn-in. Typically $35K-$120K per appliance.

Networking: The customer is responsible for the data centre networking (top-of-rack switches, internet egress, Interconnect to OCI public regions if required). Oracle does not bundle this in the Cloud@Customer price.

Annual rate escalator: Default Oracle ordering documents include an 8 percent annual rate escalator on the OCI services consumed in Cloud@Customer. On a $3M annual consumption, the year-5 effective rate is 47 percent higher than year-1 without negotiated cap. The wider Oracle Negotiation Guide covers escalator caps in detail.

BYOL versus License-Included economics

The BYOL discount on ExaCC and Database@Customer ECPU rates runs roughly 75 percent (from $0.4144/ECPU-hour License-Included down to $0.1008/ECPU-hour BYOL on the standard SKU). For any customer with existing perpetual Oracle Database Enterprise Edition Processor entitlements, BYOL is dramatically cheaper than License-Included on the per-ECPU rate.

The break-even calculation: 1 Database EE Processor = 4 ECPUs of ExaCC. A Processor licence carries $47,500 capital cost + $10,450 annual support. On a 5-year horizon, that is $99,750 per Processor. The annual BYOL ECPU cost on 4 ECPUs (1 Processor equivalent) running 24/7 is $3,532. The annual License-Included cost on the same 4 ECPUs is $14,512. The License-Included premium per Processor equivalent over BYOL is $10,980 per year - which over 5 years is $54,900. So 1 Processor licence pays for itself in BYOL savings inside 18 months of full-time deployment.

The implication: any customer with an existing perpetual licence pool should default to BYOL on Cloud@Customer. License-Included is only economic for net-new ECPU consumption that the customer does not have existing entitlement for. See the BYOL audit-defence framework at Multi-Cloud BYOL rules and the broader Licence Optimisation Guide.

Worked example: 32-OCPU ExaCC quarter rack, 5-year deal

A mid-size insurance customer deploying an ExaCC Quarter Rack X11M with 32 OCPUs (= 64 ECPUs) activated at signing, with BYOL covering 192 ECPUs of consumption from existing perpetual Database EE Processor entitlements (48 Processors). Production workload runs 24/7 against 64 ECPUs; non-production workload bursts on the remaining capacity at 30 percent utilisation.

This is a clean ExaCC deal with disciplined BYOL accounting, negotiated 3 percent escalator cap, and no License-Included consumption. If the same customer had gone License-Included throughout, the 5-year ECPU consumption cost would have been roughly $1.16M instead of $336K - an extra $824K. BYOL is the single largest economic lever on a Cloud@Customer deal.

Five levers that move the all-in Cloud@Customer cost

If the deal model above looks expensive, that is the disciplined version. The undisciplined version routinely runs 30-50 percent higher. The five levers we apply on every Cloud@Customer engagement:

1. Push BYOL coverage to 100 percent. Audit the customer's perpetual licence pool and allocate every available Processor entitlement against ECPU consumption before any License-Included ECPU is purchased.
2. Cap the annual escalator at 0-3 percent. Default ordering documents come with an 8 percent escalator that compounds aggressively over 5 years. The cap is routinely negotiable.
3. Negotiate the MCC ramp. Year-1 MCC at 50-60 percent of full MCC, stepping up over years 2-3 as workload migrates in. Saves 18-30 percent of year-1 cash.
4. Name the hardware refresh. Generation and date. Include a no-penalty exit if Oracle misses the refresh by more than 12 months.
5. Strip the bundled software options. Oracle's default proposal often bundles Diagnostics Pack, Tuning Pack, Partitioning, Advanced Compression and In-Memory at the option-bundle SKU. Strip what the customer does not use - each unused option is $400-$800/ECPU/year of unnecessary spend.

See Oracle Negotiation Guide for the broader procurement playbook, the DRCC cost optimisation playbook for in-flight Cloud@Customer tenancies, and the Cloud Advisory service for a managed engagement.

Frequently asked questions

What is the minimum Cloud@Customer cost in 2026?

The minimum entry point is an ExaCC Quarter Rack at roughly $187K/year infrastructure fee, plus $264K/year hardware support, plus consumption. Practical minimum total run-cost: $550K-$700K per year for a small production deployment with BYOL. Database@Customer can start lower if the customer brings their own approved x86 hardware - around $35K/year for management plane plus consumption.

Why is Cloud@Customer more expensive than public OCI?

Cloud@Customer carries the appliance hardware, hardware support, site presence and operational management overhead that public OCI amortises across thousands of customers in a hyperscale data centre. The premium typically runs 30-50 percent above equivalent public-OCI rates. The customer pays this premium for data residency, latency or regulatory reasons - it is not a discount play.

Does BYOL work the same way on Cloud@Customer as on public OCI?

Yes. The same Oracle Database EE Processor licence covers either public-OCI Exadata Cloud Service or Cloud@Customer ExaCC at the same 1 Processor = 4 ECPU conversion ratio. The customer can mix-and-match BYOL coverage across both platforms within the same licence pool, provided the documentation and CSI allocation is clean. See Multi-Cloud BYOL rules for the audit-defence framework.

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

Cloud@Customer is a single appliance (or small group) deployed at a customer site. Dedicated Region (DRCC) is a full OCI region deployed at a customer facility - multiple Exadata racks plus compute, networking and the full OCI service catalogue. Cloud@Customer runs at $0.5M-$3M per year of MCC. DRCC runs at $4M-$15M per year of MCC. The decision matrix is at Cloud@Customer vs Dedicated Region.

Can I negotiate Cloud@Customer pricing below Oracle's price card?

Yes, routinely. Discount levels run 12-25 percent off Oracle's opening proposal on Quarter Rack ExaCC deals, 18-30 percent on Half Rack deals, and 25-40 percent on Full Rack and multi-rack deals. The drivers are total contract value, term length, competitive positioning (Database@Azure is the most effective competitive threat), and the customer's broader Oracle relationship. See the Oracle Negotiation Guide for the broader discount framework.

Related Oracle licensing reading