What Oracle OCI Dedicated Region Actually Is

Oracle OCI Dedicated Region Cloud@Customer (DRCC) is a service that installs a full Oracle Cloud Infrastructure region — including compute, storage, networking, and Oracle Database cloud services — inside your organisation's data centre. Unlike OCI Cloud@Customer (the earlier generation, which delivered a subset of OCI services), Dedicated Region delivers the full OCI commercial catalogue within your four walls. Oracle owns and operates the hardware; you consume it under a cloud subscription model. The oracle oci dedicated region licensing implications of this arrangement are far more complex than Oracle's marketing suggests, and they directly affect how your existing on-premises Oracle licence estate is counted.

This arrangement is distinct from standard public OCI regions in one critical respect: the physical infrastructure resides in your facility. Oracle's licensing team — the License Management Services (LMS) group — treats your facility as your licensed premises. That means the same Oracle licence counting rules that apply to your on-premises data centre apply to the hardware in your Dedicated Region. The full Oracle OCI licensing and pricing framework covers public OCI in detail; this guide addresses the material differences specific to Dedicated Region deployments.

Oracle Dedicated Region Licensing vs Public OCI: The Key Difference

On public OCI, Oracle Database licensing follows the BYOL model: you count only the OCPUs in the specific OCI VM shape running your database, not the underlying physical hosts. A VM.Standard3.Flex shape with 8 OCPUs requires 4 Oracle Processor licences (at the standard 0.5 core factor for Intel), regardless of how many physical cores sit beneath that virtual machine. This is one of the most commercially attractive aspects of public OCI BYOL, and it is the basis on which most Oracle cloud migration business cases are built.

In a Dedicated Region deployed inside your own facility, Oracle's position is different. Because the hardware is in your premises, Oracle applies on-premises counting rules to any Oracle software running on that infrastructure that was not purchased as an OCI cloud service. If you are running Oracle Database Enterprise Edition on Dedicated Region infrastructure under BYOL — applying licences you originally purchased for on-premises use — Oracle's LMS team will count all physical cores on all servers in the Dedicated Region that could run that software. The standard core factor table applies, but the scope of counting expands from the specific shape to the full physical cluster. Before booking a confidential call with our team, most organisations have not modelled this correctly.

ULA and PULA Implications: How Dedicated Region Counts

If your organisation holds an Oracle Unlimited Licence Agreement (ULA) or a Perpetual ULA (PULA), the Dedicated Region deployment creates significant counting obligations at certification. A ULA allows you to deploy Oracle software without counting licences during the ULA term, but at certification — when the ULA expires and you certify your deployment count — every Oracle software instance running in your Dedicated Region must be counted against the perpetual licences you receive on certification day.

Organisations that deployed Oracle Database in a Dedicated Region and assumed the BYOL sub-capacity model applied to their ULA certification have been caught out by this rule. The certification uses the same on-premises counting methodology: all physical cores on all servers that can run the software must be counted unless hard partitioning has been applied. For a Dedicated Region with 48 physical servers each containing 128 cores, the uncapped licence count could be in the thousands of processor licences. Our Oracle ULA certification strategy guide covers how to structure your counting methodology before the certification window opens.

The PULA (Perpetual ULA) has the same certification-time exposure. Organisations considering a Dedicated Region deployment during a live PULA should model the certification impact before any infrastructure is provisioned, not after. The Oracle ULA negotiation playbook provides the framework for structuring a Dedicated Region deployment within a ULA so that it does not create an unexpected certification liability.

Commercial Commitments: What You Are Actually Signing

Oracle Dedicated Region requires a minimum annual spend commitment. As of 2026, Oracle's standard minimum is $3 million per year, with a minimum three-year term — a total minimum commitment of $9 million. Some early Dedicated Region agreements were executed at $4 million annual minimums, and Oracle's commercial floor can vary by region and negotiation leverage. Unlike public OCI Universal Credits, the Dedicated Region commitment is typically structured as an Annual Flex subscription that covers all OCI services consumed on the Dedicated Region infrastructure, including Oracle Database Cloud Service licensing fees if you are not applying BYOL.

The commercial structure means you are committing to a minimum spend regardless of actual consumption, using infrastructure you do not own but that physically sits in your data centre. The Oracle OCI Universal Credits guide explains the consumption mechanics that govern how credits are drawn down against this commitment. Over-commitment is a significant risk: in our experience across 500+ Oracle engagements, Dedicated Region customers frequently over-commit relative to actual workload migration timelines, leaving them with the same under-consumption exposure as public OCI but with on-premises licence counting rules layered on top.

Dedicated Region vs Public OCI BYOL: Which Is Right for Your Workloads

The decision between Dedicated Region and public OCI BYOL should be driven by data sovereignty requirements, latency constraints, and licence estate composition — not by Oracle's sales narrative around "bringing the cloud to you." For organisations with genuine data residency requirements that prevent workloads from leaving their own facility, Dedicated Region can be the right answer. For organisations whose primary motivation is Oracle Database licensing cost reduction, public OCI BYOL almost always delivers a better outcome because the sub-capacity counting model substantially reduces processor licence requirements.

A practical evaluation should compare the all-in cost of three scenarios: continued on-premises deployment with third-party support; migration to public OCI with BYOL; and Dedicated Region deployment with full licence counting. Our Oracle cloud migration readiness assessment models all three scenarios against your specific licence estate and workload profile. The output is a total cost of ownership comparison that accounts for licence fees, support costs, infrastructure costs, and the compliance risk of your current virtualisation configuration — a risk that Dedicated Region does not eliminate if you are running Oracle Database on VMware on the servers adjacent to your Dedicated Region hardware.