BYOL, license included, support, the universal credit model, and the decision math at renewal for the Oracle infrastructure stack.
Oracle Cloud at Customer (CCC) and Oracle Cloud Infrastructure (OCI) deliver the same Oracle services on different physical and commercial footprints. CCC runs in the customer data center under Oracle operational control. OCI runs in Oracle commercial regions. The licensing decisions look similar but the commercial outcomes diverge sharply.
This article is the buyer side reference for the Oracle infrastructure licensing decision. Read the related Oracle practice, the OCI licensing article, the CCC licensing guide, and the ULA decision framework.
Cloud at Customer places an Oracle owned, Oracle operated infrastructure stack inside the customer data center. The customer pays a monthly subscription for the rack, the services, and the operational model. Data stays on customer premises. Oracle controls patching, firmware, hypervisor, and the management plane.
Oracle Cloud Infrastructure runs in Oracle commercial regions across the major geographies. OCI carries Oracle's standard public cloud services including compute, storage, database, analytics, and the broader Oracle technology stack. OCI uses universal credits as the commercial commit model.
Both CCC and OCI support two licensing modes. BYOL applies the existing Oracle license to the cloud OCPU consumption. License included bundles the license into the OCPU rate at a premium price.
| Dimension | BYOL | License included | Buyer side note |
|---|---|---|---|
| OCPU rate | Lower base rate | Higher premium rate | BYOL saves 30 to 60 percent on OCPU |
| License source | Existing perpetual license | Bundled into subscription | BYOL requires entitlement to cover OCPU |
| Support | Customer pays separately | Bundled into subscription | Support stays on the existing license |
| Cloud option | Customer chooses the option | Bundled into the OCPU rate | Option pack additions matter |
| Audit exposure | License conversion math | Bundled, no audit on cloud line | BYOL needs careful entitlement tracking |
For Oracle customers with an established perpetual license estate, BYOL captures the licensing investment that is already paid for. License included works for customers entering the Oracle estate fresh or expanding into a workload they do not currently license. The decision is mostly about existing entitlement, not about cloud preference.
Oracle Support continues during BYOL on the existing license. The cloud OCPU rate is a separate subscription. Universal credits provide flexible consumption across all OCI and CCC services under a single annual commit.
Two traps recur in CCC and OCI commercial conversations. The first is overcommit on universal credits to capture a deeper discount. The second is dropping perpetual support before the BYOL math is verified. Both traps unwind the savings the cloud commit was meant to deliver.
Data residency is the most common reason customers select CCC over OCI. Regulators in financial services, healthcare, government, and defense often mandate data on national soil. CCC keeps the data inside the customer data center.
The CCC vs OCI decision matrix runs on six variables. Data residency, latency, scale, existing license investment, multi cloud strategy, and operational model preference.
| Variable | Favors CCC | Favors OCI |
|---|---|---|
| Data residency | Mandated on premises | No specific mandate |
| Latency | Sub millisecond to on prem systems | Standard cloud latency acceptable |
| Scale | Predictable steady state | Variable or bursty workload |
| License investment | Heavy existing estate | New or limited Oracle footprint |
| Multi cloud strategy | Oracle as primary | Oracle alongside AWS or Azure |
| Operational model | Oracle managed rack acceptable | Self managed cloud preferred |
The eight step checklist below moves an Oracle infrastructure decision from vendor proposal to a benchmarked CCC vs OCI envelope.
Usually not on a like for like basis. CCC carries a higher per OCPU rate and a minimum annual commit floor often between $1M and $3M. The CCC choice is driven by data residency, latency, and operational model. OCI handles most other workloads more economically on a pure dollar basis.
Yes. BYOL applies the existing perpetual Oracle license to the cloud OCPU consumption on either CCC or OCI. The OCPU rate drops 30 to 60 percent. Oracle Support continues on the existing license. The customer must hold sufficient entitlement to cover the cloud OCPU consumption.
The minimum commit varies by configuration. Exadata Cloud at Customer typically starts at $1M to $3M per year. The standard CCC configurations run lower. The commit floor is a negotiation lever and varies sharply by customer scale, term length, and competitive context.
Universal credits make the decision more fluid. Credits move between services and across CCC and OCI under a single commit. Customers can run primary workloads on CCC and burst or DR workloads on OCI under the same commit. The flexibility favors hybrid CCC plus OCI architectures.
Overcommitting on the minimum annual envelope to capture a deeper discount. The overcommit forfeits at year end if consumption falls short. The right size approach is to commit to the steady state floor and burst above it at standard rate, rather than overcommit and forfeit.
Yes with planning. The ULA certifies the customer's deployed footprint at termination. The certification feeds into the BYOL math for CCC or OCI. The migration usually benefits from independent buyer side advisory because the ULA certification number anchors the next five to ten years of cloud commercial conversations.
Redress runs the Oracle infrastructure decision workstream across the workload portfolio, license inventory, residency map, and renewal posture. The engagement compares CCC and OCI workload by workload and produces a benchmarked envelope ready for negotiation.
The engagement is independent. Buyer side. Industry Recognized. Five hundred plus enterprise software engagements. Two billion plus in client spend under advisory. Read the related Vendor Shield, the Renewal Program, the Benchmark Program, the Software Spend Assessment, the Benchmarking framework, the about us page, the management team page, the locations page, and the contact page.
A buyer side framework for the Oracle ULA, CCC, OCI, and BYOL conversations. Workload portfolio map, entitlement inventory, residency framework, and the renewal posture playbook.
Used across more than five hundred enterprise software engagements. Independent. Buyer side. Built for Oracle customers running infrastructure or ULA decisions.
Open the white paper in your browser. Corporate email only.
Open the Paper →We mapped the workload portfolio, inventoried the Oracle license estate, modeled BYOL coverage against the proposed OCPU consumption, and ran the CCC vs OCI matrix workload by workload. The hybrid envelope landed 21 percent below the proposed CCC bundle and the BYOL math protected the existing entitlement on every line.
We have run 500+ enterprise clients across 11 publishers. Every engagement starts with one conversation.
OCI commit signals, CCC commercial moves, BYOL telemetry patterns, and the wider Oracle commercial leverage signals across every renewal cycle.
Once a month. Audit patterns, renewal benchmarks, vendor commercial signals across Oracle, Microsoft, SAP, Salesforce, IBM, Broadcom, AWS, Google Cloud, ServiceNow, Workday, Cisco, and the GenAI vendors. No follow up sales pressure.
Free providers (Gmail, Yahoo, Outlook) cannot subscribe. Work email only. Unsubscribe in one click.
