Licensing Oracle Cloud at Customer vs Oracle OCI

Two Deployment Models, One Licensing Framework

Oracle Cloud at Customer (C@C) and Oracle Cloud Infrastructure (OCI) are Oracle's two primary cloud infrastructure offerings. OCI is Oracle's public cloud platform, hosted in Oracle's global data centres. Oracle Cloud at Customer places Oracle-managed cloud infrastructure inside a customer's own data centre while Oracle retains operational responsibility through remote management. A third variant — OCI Dedicated Region — delivers a full OCI region, including all 150+ services, at the customer's chosen location.

Despite their structural differences, both environments share a common licensing framework. Oracle uses the same metric definitions, the same Bring Your Own License (BYOL) rules, and the same License Included service catalogue across both environments. Understanding this shared foundation — and where the differences emerge — is the starting point for any cloud deployment licensing analysis.

The OCPU Metric: The Foundation of Oracle Cloud Licensing

Oracle Cloud Compute is metered in Oracle Compute Units (OCPUs). One OCPU represents one physical processor core with associated hyper-threading. For licensing purposes, Oracle's standard rule is that two OCPUs equal one Oracle Processor license when using Bring Your Own License. This rule applies consistently across OCI public cloud and Oracle Cloud at Customer.

A workload deployed on a VM with four OCPUs therefore requires two Oracle Processor licenses under BYOL. A 16-OCPU virtual machine requires eight Processor licenses. The calculation is straightforward in both environments — no different core factor tables, no cloud-specific adjustments. The same Oracle Processor Core Factor table that applies to on-premises deployments applies to BYOL deployments in both OCI and Cloud at Customer.

Where the environments diverge is in how Oracle counts minimum license requirements, how License Included pricing works, and what your contractual commitments look like.

BYOL vs License Included: How It Works in Each Environment

BYOL in OCI Public Cloud

BYOL in OCI public cloud allows organisations to apply existing on-premises Oracle licenses to cloud-hosted workloads. Oracle's BYOL policy permits an organisation to deploy a licensed product in the public cloud using the same license that covers an on-premises instance, subject to the constraint that the on-premises and cloud deployments are not running simultaneously using the same license. This is sometimes called the "license mobility" provision, and it gives organisations flexibility to shift workloads between on-premises and cloud during migration projects.

BYOL in OCI requires maintaining active Oracle support for the licenses being used. Oracle explicitly requires active support agreements for any license deployed in cloud environments. If you have dropped Oracle Support — or are considering doing so — your ability to use those licenses under BYOL in OCI is constrained.

BYOL in Oracle Cloud at Customer

Oracle treats Cloud at Customer as an extension of OCI from a BYOL perspective. The same 2:1 vCPU-to-Processor rule applies. The same support requirements apply. Where Cloud at Customer differs is that the infrastructure is physically located in your data centre, which means Oracle's operational team manages the hardware and software stack on your premises via secure remote management tunnels. This creates a model where you own the data sovereignty benefit of on-premises infrastructure while Oracle retains operational control of the platform.

For BYOL on Cloud at Customer, organisations must maintain active Oracle support on any licenses brought into the environment, and the licensing calculations are validated against the same rules as OCI public cloud. There is no sub-capacity licensing benefit specific to Cloud at Customer that would allow you to license fewer Processor equivalents than the OCPU count of your deployed workloads.

License Included Services

Both OCI public cloud and Cloud at Customer offer licence-included services for managed Oracle products — primarily Oracle Autonomous Database, Oracle Database Cloud Service, and Exadata Cloud Service. License Included pricing bundles the Oracle software license into the service subscription, eliminating the need for separate on-premises licenses. The pricing premium for License Included over BYOL is typically 50 to 75 percent per OCPU per hour, depending on the service. Over a multi-year commitment this premium is substantial, and the break-even calculation between buying new Oracle cloud licenses versus leveraging existing BYOL entitlements is a central decision in most cloud deployment analyses.

Commitment Structures: The Critical Difference

This is where Oracle Cloud at Customer and OCI public cloud diverge most significantly for enterprise procurement teams.

OCI Public Cloud Commitments

OCI public cloud supports both pay-as-you-go consumption and Universal Credits commitment models. Universal Credits allow organisations to pre-purchase a block of cloud credits consumed across any OCI service, typically with minimum annual commitments and discount tiers based on commitment volume. Commitment terms for Universal Credits are commonly one to three years. Pay-as-you-go requires no commitment and is priced at standard list rates.

This flexibility makes OCI public cloud accessible for organisations that are uncertain about their long-term cloud footprint, or that want to test Oracle cloud services before making a larger commitment. The absence of a five-year minimum is a meaningful operational advantage for organisations at early stages of cloud planning.

Oracle Cloud at Customer and Dedicated Region Commitments

Oracle Cloud at Customer and OCI Dedicated Region require minimum term commitments of five years. Oracle's minimum annual spend commitment for a Dedicated Region has historically been set at approximately $1 million per year, making the minimum total commitment around $5 million over the contract term. These numbers represent Oracle's entry point for the product category — actual deal sizes for enterprise deployments are typically significantly higher.

The five-year commitment structure carries meaningful financial and strategic risk. Organisations that commit to a Cloud at Customer deployment are locking in a significant annual spend obligation for a half-decade. If your Oracle footprint shrinks, if you pursue a migration to an alternative platform, or if business circumstances change, exiting or renegotiating a Cloud at Customer commitment is complex and expensive. This commitment rigidity should be explicitly modelled in any financial analysis of Cloud at Customer relative to OCI public or competing cloud alternatives.

Support Model Differences

In both environments, License Included services include Oracle's managed support for the cloud service itself — Oracle handles patching, upgrading, and operational management of the cloud layer. In Cloud at Customer and Dedicated Region deployments, Oracle's Cloud Operations team manages the physical infrastructure and cloud platform via remote access, even though the hardware is in your data centre.

For BYOL deployments, the support model depends on your existing Oracle support contracts. You continue to rely on Oracle Premier Support (or your chosen third-party support provider, though third-party support creates complexity for BYOL cloud deployments) for software-level support. Oracle's cloud infrastructure support is separate from your software support contracts.

One key operational difference for Cloud at Customer is that Oracle retains physical access requirements — Oracle's team must be able to patch and upgrade the infrastructure hardware and platform stack. This creates a governance consideration for regulated industries with strict access controls around data centre equipment.

Which Model for Which Scenario

OCI public cloud is better suited for organisations with variable workload profiles, limited commitment appetite, ongoing cloud migration programmes, or a desire to test Oracle cloud services before committing to infrastructure-level investment. The pay-as-you-go option in particular provides a low-barrier entry point for Oracle cloud evaluation.

Oracle Cloud at Customer is designed for organisations with firm data sovereignty requirements — regulatory or contractual obligations that prevent workloads from leaving a specific geographic location or a customer-controlled data centre. Regulated industries such as financial services, healthcare, and government are Oracle's primary target for Cloud at Customer deployments. If your data sovereignty requirements are genuine and non-negotiable, Cloud at Customer provides cloud economics and Oracle managed services in a compliant on-premises footprint.

OCI Dedicated Region extends this to organisations that need a full Oracle cloud region — including all IaaS, PaaS, and SaaS services — at their own location. The entry cost and commitment are higher, but the service scope is the broadest of the three models.

Negotiating Oracle Cloud Commitments

Oracle's Cloud at Customer and Dedicated Region contracts are negotiated individually — Oracle does not publish fixed pricing for these products. The commercial terms, including the minimum annual commitment, support provisions, growth mechanisms, and exit clauses, are all subject to negotiation. Organisations that engage Oracle with independent advisory support consistently achieve better commercial outcomes than those who negotiate directly against Oracle's standard term sheet.

Key negotiation areas include the minimum annual commitment structure, flexibility provisions for reducing scope in years two through five, BYOL credit mechanisms for existing on-premises license investments, and break provisions for material changes in business scope. Oracle's sales team is incentivised to maximise the total contract value — independent advisory support ensures the customer's interests in flexibility, cost control, and exit rights are equally well represented.

For OCI public cloud Universal Credits, the negotiation focuses on the commitment tier, discount levels, and credit flexibility provisions. Oracle's published Universal Credits price list is the starting point, not the outcome. Organisations with significant Oracle on-premises footprints have additional leverage in OCI negotiations through the BYOL credit value they bring to the relationship.