Oracle Cloud at Customer vs Dedicated Region: Which Model Is Right for You?

The Core Distinction: Service Scope

The fundamental difference between Oracle Cloud at Customer (Exadata or Compute) and the Dedicated Region is the breadth of services delivered. Oracle Cloud at Customer devices deliver targeted service subsets — Exadata Cloud@Customer provides Oracle Database services only, and Compute Cloud@Customer provides OCI compute, storage, and container services. The Dedicated Region delivers Oracle's complete OCI service catalogue: every IaaS, PaaS, and SaaS service available in Oracle's public cloud, including Oracle Fusion Cloud applications, deployed entirely within the customer's facility.

A CIO choosing between these models is making a strategic decision about scope: whether the organisation's on-premises cloud needs are centred on specific workload types, or whether a full cloud platform is needed on-premises to serve a broad and diverse application portfolio.

What Exadata Cloud@Customer Delivers

Exadata Cloud@Customer delivers Oracle Database as a managed cloud service — Autonomous Database, Exadata Database Service, and Oracle Database Base Service — running on Oracle-managed Exadata hardware in the customer's facility. It is explicitly and exclusively a database service. No general compute, no containers, no analytics services, no Oracle Fusion SaaS. The scope is narrow and the target workload is precisely defined: Oracle Database workloads requiring Exadata-class performance, Autonomous Database capabilities, or managed Exadata infrastructure without capital expenditure.

What Compute Cloud@Customer Delivers

Compute Cloud@Customer extends the scope beyond databases to include general OCI compute (virtual machines and bare metal), OCI block and object storage, Oracle Container Engine for Kubernetes (OKE), and related IaaS services. It supports application workloads, microservices, and containerised deployments, but does not include Oracle's PaaS services, analytics, AI platforms, or Oracle Fusion Cloud applications. Compute Cloud@Customer is the right choice when the requirement is for cloud-native application infrastructure on-premises, without the full-service scope of the Dedicated Region.

What the Dedicated Region Delivers

The Dedicated Region delivers Oracle's full OCI service catalogue — 200 or more services — as a self-contained, Oracle-managed cloud region in the customer's facility. This includes all compute, storage, and networking services; all Oracle Database services including Autonomous Database; Oracle Kubernetes Engine; Oracle Analytics Cloud; Oracle Integration Cloud; AI and machine learning services; and Oracle Fusion Cloud SaaS applications (ERP, HCM, SCM, CX). No other Oracle on-premises offering provides access to Oracle Fusion Cloud applications in a customer-managed facility — this is exclusive to the Dedicated Region.

Architecture and Control Plane Differences

Beyond service scope, Exadata Cloud@Customer, Compute Cloud@Customer, and the Dedicated Region have meaningfully different architectural characteristics that affect data sovereignty, connectivity requirements, and operational autonomy.

Control Plane Location

Exadata and Compute Cloud@Customer both rely on Oracle's public cloud control plane for management, provisioning, and operational coordination. The data plane — the actual customer data and workloads — remains on-premises, but management traffic passes through Oracle's public cloud infrastructure. This creates a dependency on external connectivity that, while not affecting data residency, means that management operations require outbound network availability to Oracle's cloud endpoints.

The Dedicated Region runs its entire control plane on-premises. Management, provisioning, and service APIs all operate within the customer's facility. Oracle's operations team manages the Dedicated Region remotely through dedicated management channels, but all customer-facing APIs and management portals operate entirely on-site. This architecture provides the highest level of operational independence and is required by organisations whose regulatory environment prohibits any management traffic leaving the facility.

Connectivity Requirements

Exadata and Compute Cloud@Customer require persistent outbound connectivity to Oracle's public cloud management endpoints — typically a redundant pair of 1Gbps internet connections or direct cloud connectivity. Loss of this connectivity does not affect running workloads but does suspend Oracle's ability to manage and patch the system, and may restrict the customer's ability to provision new database or compute resources through the Oracle Cloud Console.

The Dedicated Region does not require connectivity to Oracle's public cloud for customer operations. Oracle's remote management access uses a dedicated, monitored management network path that is entirely separate from customer application networks. Air-gapped deployments with no external internet connectivity can operate a Dedicated Region with Oracle's remote management conducted over a dedicated private line rather than the public internet.

Pricing and Commitment Structures

The pricing models for Oracle Cloud at Customer and the Dedicated Region differ significantly, with the Dedicated Region carrying substantially higher minimum commitments that reflect its broader service scope.

Exadata Cloud@Customer Pricing Model

Exadata Cloud@Customer pricing consists of a fixed monthly infrastructure subscription (approximately $8,000 per month for a Base System at list price) plus hourly consumption charges for database OCPUs used. There is no large upfront commitment requirement — customers pay the infrastructure fee regardless of consumption and add consumption charges based on actual use. Minimum contract terms are typically one to three years. This relatively accessible entry point makes Exadata Cloud@Customer viable for organisations that need managed Oracle Database services on-premises without committing to a full cloud region investment.

Dedicated Region Pricing Model

The Dedicated Region requires a minimum annual spend commitment against which all OCI service consumption is drawn. The current entry-level commitment is approximately $1 million per year over a minimum five-year term, representing a $5 million minimum total commitment. All services within the Dedicated Region are consumed at standard OCI public cloud list prices — there is no on-premises premium for services consumed within the minimum commitment. Consumption above the committed amount is billed at standard OCI rates. Unused commitment within a year is typically lost — it does not roll forward — making it essential that committed amounts are based on realistic consumption modelling.

Support Costs Across Both Models

Under the BYOL model on either Cloud at Customer or the Dedicated Region, the customer maintains active Oracle support for all licences applied to the deployment. Oracle support fees increase by 8 percent annually unless a cap is negotiated as part of the commercial agreement. Over a five-year Dedicated Region term, 8 percent annual increases on a $2 million support base add approximately $940,000 in additional support cost compared to a flat rate — a meaningful variable in Dedicated Region total cost of ownership that should always be modelled before commitment.

Use Case Decision Matrix

Selecting the right Oracle Cloud at Customer model comes down to a clear set of operational and strategic questions. Use this framework to identify the appropriate model for your requirements.

Choose Exadata Cloud@Customer When:

• The primary requirement is managed Oracle Database services on-premises — Autonomous Database, RAC, or high-performance OLTP or data warehouse workloads
• The organisation needs to eliminate the operational burden of managing Exadata hardware without moving database workloads off-premises
• Budget constraints make the Dedicated Region commitment impractical
• Outbound connectivity to Oracle's public cloud is acceptable for management purposes
• The workload profile is exclusively database-centric with no requirement for general compute or broader cloud services on-premises

Choose Compute Cloud@Customer When:

• The requirement spans both database and general application workloads that must remain on-premises
• Cloud-native application development (containers, microservices) needs to run in a customer-controlled facility
• The organisation needs OCI-compatible infrastructure on-premises without the scale and cost of a full Dedicated Region
• Latency between application and database tiers must be minimised by co-locating both in the same on-premises environment

Choose the Dedicated Region When:

• The organisation needs the full Oracle Cloud service catalogue on-premises — including Oracle Fusion Cloud SaaS applications, analytics, AI services, and integration middleware
• Regulatory requirements mandate that all application tiers, management planes, and service APIs operate within the customer's physical facility
• Data sovereignty obligations require full control plane on-premises with no management traffic crossing external network boundaries
• The $5 million minimum commitment is supportable based on realistic modelling of planned service consumption
• The organisation is committed to Oracle as its primary cloud platform and is investing in a long-term on-premises Oracle Cloud presence

Competitive Positioning and Alternatives

Oracle's Cloud at Customer models compete directly with AWS Outposts, Azure Stack Hub, and Google Distributed Cloud for the on-premises cloud market. Oracle's competitive advantage is strongest in environments with existing Oracle Database and application investments — the BYOL licensing economics and Autonomous Database capabilities are difficult for competing platforms to replicate.

For organisations that are not heavily invested in Oracle's software stack, AWS Outposts or Azure Stack Hub may offer better economics for general workloads at lower minimum commitments. Oracle's Dedicated Region is the only on-premises cloud offering that includes Oracle Fusion SaaS applications — no competing on-premises cloud platform offers an equivalent. For Oracle Fusion Cloud customers with on-premises data residency requirements, the Dedicated Region is effectively the only viable option.

The decision between Oracle Cloud at Customer models should always be made with independent commercial analysis. Oracle's sales teams are motivated to recommend the Dedicated Region — it carries higher contract value. Independent advisors who understand Oracle's licensing and commercial mechanics can identify whether the Dedicated Region commitment is commercially justified or whether a more targeted Cloud at Customer model would deliver the same outcomes at a fraction of the cost.