Oracle's Cloud@Customer marketing positions the platform as 'OCI in your data centre' - implying full feature parity with public OCI. The reality in 2026 is more nuanced. Different Cloud@Customer footprints support different subsets of the OCI service catalogue, and software-licensing rules vary across them. This article maps every major Oracle software product against the four Cloud@Customer families - ExaCC, Database@Customer, Compute Cloud@Customer and Dedicated Region - and flags the gaps that routinely trip up architects when they assume a feature is supported and discover, six months into deployment, that it is not. The data is current to OCI's published service availability matrix as of Q2 2026.
Cloud@Customer is positioned as OCI-in-your-data-centre. Inside that headline are four different products with different service catalogues. A workload that runs in public OCI does not automatically run on ExaCC. A workload that runs on ExaCC does not automatically run on Compute Cloud@Customer. The customer who signs a Cloud@Customer ordering document on the assumption that everything in OCI is available locally will discover the truth in week 8 of the deployment - which is the worst time to discover it.
The catalogue below is the current Q2 2026 picture, cross-referenced against Oracle's published service availability matrix and our own deployment experience across 80+ Cloud@Customer engagements. The wider Cloud@Customer architecture sits in the Oracle Dedicated Region Guide; pricing is at Cloud@Customer cost; the comparison to public OCI is at Cloud@Customer vs OCI public region; the broader licensing framework is at Oracle Cloud Licensing Guide.
Service availability depends on which Cloud@Customer footprint the customer signs for. The four families:
| Family | Hardware footprint | Catalogue scope |
|---|---|---|
| Database@Customer | Customer-supplied x86 hardware | Oracle Database EE/SE2 only (no Exadata features, no OCI compute, no SaaS) |
| Exadata Cloud@Customer (ExaCC) | Oracle Exadata X11M rack | Oracle Database EE + Exadata features + Autonomous Database (Dedicated only, no Serverless) |
| Compute Cloud@Customer (CCC) | Oracle X9/X11 compute appliance | OCI compute, block storage, object storage, K8s, OCI Container Engine - no managed databases |
| Dedicated Region Cloud@Customer (DRCC) | Multiple racks - Exadata + compute + networking | Closest to full OCI parity - 100+ OCI services, full service catalogue minus a handful of edge services |
The rest of this article walks the major Oracle software families and maps each against the four Cloud@Customer footprints.
The Oracle Database stack is the original Cloud@Customer use case - and remains the dominant workload across all four footprints. Service availability in 2026:
| Database product | DB@Customer | ExaCC | CCC | DRCC |
|---|---|---|---|---|
| Oracle Database EE 19c | Yes | Yes | No | Yes |
| Oracle Database EE 21c | Yes | Yes | No | Yes |
| Oracle Database EE 23ai | Yes | Yes (GA Q1 2026) | No | Yes |
| Oracle Database SE2 19c/21c/23ai | Yes | Yes | No | Yes |
| Real Application Clusters (RAC) | Yes (BYOL only) | Yes (BYOL only) | No | Yes |
| Data Guard / Active Data Guard | Yes | Yes | No | Yes |
| GoldenGate (deployed) | Yes (BYOL) | Yes (BYOL or License-Included) | Yes (BYOL only) | Yes |
| Exadata Smart Scan / Storage Indexes | No (no Exadata cells) | Yes | No | Yes |
| Hybrid Columnar Compression | No | Yes | No | Yes |
| In-Memory Column Store | Yes (BYOL option) | Yes (BYOL option or License-Included EE+IM SKU) | No | Yes |
| AI Vector Search (23ai) | Yes (free with EE 23ai) | Yes (free with EE 23ai) | No | Yes |
Two flags. First, Compute Cloud@Customer does not run Oracle Database as a managed service. Customers running CCC who want a database run it inside their own compute VMs and self-manage - which means full BYOL licensing applies, no Oracle managed-service overhead. Second, the database options model on Cloud@Customer follows the public-OCI BYOL rules - the customer either brings perpetual EE Processor licences plus matching option licences, or runs License-Included at the bundled-options ECPU rate. The wider Oracle Database Licensing Guide covers the option-pack rules in depth.
We map your target workload list against the actual Cloud@Customer service catalogue, flag the gaps, and identify the alternative footprint (or DRCC upgrade path) that closes each gap. 1-2 week engagement. Prevents the most expensive Cloud@Customer mistake: signing for the wrong footprint.
Autonomous Database (ADB) is available on Cloud@Customer in two flavours: ADB-Dedicated (Exadata Infrastructure required) on ExaCC and DRCC, and ADB-Serverless which is public-OCI-only and is NOT available on any Cloud@Customer footprint as of 2026.
| ADB variant | DB@Customer | ExaCC | CCC | DRCC |
|---|---|---|---|---|
| ADB-Dedicated (Autonomous Database on Exadata) | No | Yes | No | Yes |
| ADB-Serverless (multitenant Autonomous DB) | No | No | No | No |
| Autonomous Data Warehouse (ADW-Dedicated) | No | Yes | No | Yes |
| Autonomous Transaction Processing (ATP-Dedicated) | No | Yes | No | Yes |
| Autonomous JSON Database | No | Yes (Dedicated only) | No | Yes (Dedicated only) |
| APEX on Autonomous | No | Yes | No | Yes |
The economic implication: customers wanting the cost benefit of ADB-Serverless (shared multitenant ADB, lower per-ECPU rate) cannot get it on Cloud@Customer. They must either run ADB-Dedicated (which carries higher per-ECPU rates) or run in public OCI for the serverless variant. This is one of the few cases where public OCI is materially cheaper than Cloud@Customer for the same workload class.
MySQL HeatWave Database Service is a partial-coverage product on Cloud@Customer:
| MySQL product | DB@Customer | ExaCC | CCC | DRCC |
|---|---|---|---|---|
| MySQL HeatWave Database Service (managed) | No | No | Yes (Q3 2026, beta) | Yes (GA) |
| MySQL HeatWave Lakehouse | No | No | No | Yes |
| MySQL HeatWave GenAI (in-database LLM) | No | No | No | Yes (Q4 2026 roadmap) |
| MySQL Enterprise Edition (self-managed on customer VM) | n/a | n/a | Yes (BYOL) | Yes |
The bottom line: MySQL HeatWave as a managed service is essentially DRCC-only on Cloud@Customer in 2026. Customers who want HeatWave on a smaller footprint must wait for the Compute Cloud@Customer GA in Q3-Q4 2026 or run MySQL Enterprise self-managed in their existing VMs. See the related blog at HeatWave GenAI licensing.
This is where Compute Cloud@Customer (CCC) and Dedicated Region (DRCC) shine, and where ExaCC and Database@Customer are deliberately limited. Service availability:
| Service | DB@Customer | ExaCC | CCC | DRCC |
|---|---|---|---|---|
| OCI Compute (VM) | No | No | Yes | Yes |
| OCI Compute (bare metal) | No | No | No | Yes |
| OCI Block Storage | No | Yes (limited - Exadata storage only) | Yes | Yes |
| OCI Object Storage | No | No | Yes | Yes |
| OCI File Storage | No | No | Yes | Yes |
| OCI Container Engine for Kubernetes (OKE) | No | No | Yes | Yes |
| OCI VCN networking | Limited (DB-tier only) | Limited (DB-tier only) | Yes | Yes |
| OCI Load Balancer | No | No | Yes | Yes |
| OCI FastConnect / Interconnect to public OCI | Yes | Yes | Yes | Yes |
The pattern: Database@Customer and ExaCC are database-tier appliances and intentionally have no general-purpose compute or object storage. CCC fills that gap. DRCC is the only Cloud@Customer footprint that comes close to full OCI compute parity.
This is a deliberately limited story. Oracle's SaaS portfolio (Fusion ERP, HCM, SCM, CX, EPM) is not deployable on Cloud@Customer in any meaningful sense. Oracle's published position: SaaS runs in Oracle's public OCI regions, not in customer-hosted DRCC. The exception is a small set of regulated-industry customers (defence, sovereign banking) where Oracle has agreed bespoke SaaS-on-DRCC arrangements; these are quotation-only and not part of the standard catalogue.
| Application | Any Cloud@Customer footprint? | Notes |
|---|---|---|
| Oracle Fusion Cloud ERP / HCM / SCM | No (standard catalogue) | Bespoke DRCC arrangements possible for regulated customers |
| NetSuite | No | Multi-tenant SaaS only |
| Oracle E-Business Suite (EBS) 12.2 | Yes - self-managed VMs on CCC or DRCC | Customer manages app tier; database tier on ExaCC/DRCC |
| Oracle PeopleSoft | Yes - self-managed VMs on CCC or DRCC | Same pattern as EBS |
| Oracle JD Edwards EnterpriseOne | Yes - self-managed VMs on CCC or DRCC | Same pattern as EBS |
| Oracle Siebel CRM | Yes - self-managed VMs on CCC or DRCC | Same pattern as EBS |
| Oracle Hyperion / EPM (on-premises) | Yes - self-managed VMs on CCC or DRCC | Self-managed install on customer VMs |
| Oracle WebLogic Server | Yes - self-managed on CCC, ExaCC (limited), DRCC | BYOL applies; see Middleware Licensing Guide |
The pattern for legacy Oracle Applications: the database tier sits on ExaCC or DRCC (managed Oracle Database service), the application tier sits in customer-managed VMs on Compute Cloud@Customer or DRCC. The customer handles application install, configuration and lifecycle; Oracle handles the database tier as a managed service. The wider Fusion Cloud Applications Guide covers the SaaS deployment model.
The OCI service catalogue runs to roughly 100+ named services. Cloud@Customer coverage varies dramatically by family. Selected services:
| OCI service | DB@Customer | ExaCC | CCC | DRCC |
|---|---|---|---|---|
| OCI Generative AI Service | No | No | No | Yes (Q3 2026) |
| OCI Vision / Speech / Language | No | No | No | Yes |
| OCI Data Science | No | No | No | Yes |
| OCI Functions (serverless) | No | No | Limited | Yes |
| OCI Streaming (managed Kafka) | No | No | Yes | Yes |
| OCI API Gateway | No | No | Yes | Yes |
| OCI Identity and Access Management (IAM) | Yes | Yes | Yes | Yes |
| OCI Vault (KMS) | Yes | Yes | Yes | Yes |
| OCI Logging / Monitoring | Yes | Yes | Yes | Yes |
| OCI Operations Insights | Yes | Yes | Yes | Yes |
| OCI Data Safe | Yes | Yes | Yes | Yes |
| OCI GoldenGate (cloud-native, managed) | Limited | Yes | Limited | Yes |
| OCI Database Migration Service (ZDM) | Yes | Yes | Yes | Yes |
The customer who wants the full OCI service catalogue on-premises has only one option: DRCC. The smaller Cloud@Customer footprints carry a deliberately curated subset and are not designed to be full OCI replacements.
Five service gaps that routinely catch architects on Cloud@Customer deployments:
The single decision that prevents most of these gaps: confirm the service catalogue against your actual workload list before signing the Cloud@Customer ordering document, not after. The Cloud Advisory service runs this validation as a standard pre-signing review. The Oracle Negotiation Guide covers the broader procurement playbook including service-availability redlines.
Not as a standard offering. Oracle's Fusion SaaS portfolio runs in Oracle's public OCI regions and is not part of the standard Cloud@Customer catalogue. Bespoke Fusion-on-DRCC arrangements have been negotiated for a small number of regulated-industry customers (defence, sovereign banking) on case-by-case quotation terms. For the standard SaaS deployment model see the Fusion Cloud Applications Guide.
Yes, AI Vector Search ships free with Oracle Database 23ai Enterprise Edition on ExaCC. The feature does not require a separate option licence in 2026, though the supporting infrastructure (Diagnostics Pack for usage monitoring, Partitioning for sharding, Advanced Compression for storage efficiency) typically requires the standard EE option licences. See 23ai Vector Search licensing for the full picture.
OCI GoldenGate cloud-native is available on ExaCC and DRCC as a managed service. On Database@Customer and Compute Cloud@Customer the offering is limited - typically self-managed GoldenGate install on customer VMs with BYOL licensing. The cross-cloud GoldenGate replication pattern (ExaCC primary, Database@Azure standby) is supported and is one of the more common 2026 deployment patterns. See GoldenGate hybrid multi-cloud.
Yes, with split-tier deployment. The EBS application tier runs in customer-managed VMs on Compute Cloud@Customer or DRCC. The EBS database tier runs as a managed Oracle Database service on ExaCC or DRCC. The customer handles EBS application install, patching and lifecycle; Oracle handles the database tier. BYOL applies on the application tier - the customer's existing EBS user licences cover the deployment unchanged.
Roughly quarterly for incremental service additions, with major service launches (OCI Generative AI on DRCC, HeatWave GenAI on DRCC) timed against the quarterly OCI release calendar. Customers should re-validate their target service list every 6 months during the deployment phase - what was not available at signing may have been added by deployment. The annual MCC review is a good forcing function for this revalidation.
Twice a month. Oracle cloud, DRCC, ExaCC contract patterns, audit-defence tactics and BYOL maths. Written by former Oracle insiders.
No spam. Unsubscribe any time. Independent - not affiliated with Oracle Corporation.