Bring Your Own License is the most powerful Oracle cost lever in the cloud era. The 2026 guide to authorized clouds, core factor math, license mobility rules, audit traps, and the buyer side framework that holds Oracle to a fair cloud price.
Bring Your Own License is the Oracle cost lever that controls cloud spend across AWS, Azure, OCI, and GCP. The buyer applies an existing Oracle Database, WebLogic, or middleware license to compute capacity in a public cloud and pays only for the underlying infrastructure.
The economics run 32 to 58 percent below the License Included path. The rules are precise. Mistakes trigger audit exposure that wipes out the savings.
This guide reads as a comprehensive buyer side framework. Pair it with the OCI cloud infrastructure licensing, the BYOL vs License Included on Azure article, the approved hard partitioning guide, and the Oracle services practice.
Oracle workloads in the public cloud carry two pricing paths. The customer can buy a License Included compute instance where the Oracle license is bundled into the hourly price. The alternative is Bring Your Own License where the existing Oracle license covers the cloud compute and the buyer pays only the infrastructure rate.
The gap between the two paths runs 32 to 58 percent on most workloads.
Oracle publishes the authorized cloud environments policy that defines which public clouds can host Oracle workloads under BYOL. The current policy authorizes four hyperscalers under specific rules. Cloud workloads on non authorized providers fall back to the full physical core count math, which can multiply the license requirement by 4 to 16 times.
| Cloud | BYOL allowed | Authorized model | Bare metal required |
|---|---|---|---|
| Oracle Cloud OCI | Yes | OCI compute and bare metal | No |
| Microsoft Azure | Yes | Authorized cloud model | No |
| Amazon AWS | Yes | Authorized cloud model | No |
| Google Cloud GCP | Limited | Bare Metal Solution and Google Cloud Oracle | Bare metal only |
| Other clouds | No | Counts physical hosts at full core count | Not authorized |
Oracle workloads on non authorized clouds fall under the standard partitioning policy. Soft partitioning is not recognized. The customer is liable for the full physical core count of every host in the cluster, not just the cores allocated to the Oracle VM. This rule has triggered some of the largest Oracle audit findings on record.
The core factor table determines how many cloud cores one Oracle processor license covers. On authorized clouds, Oracle applies a fixed conversion: two vCPUs equal one processor license when hyperthreading is enabled. On bare metal, the standard core factor table applies.
| Environment | Hyperthreading | Processor license covers |
|---|---|---|
| Authorized cloud, vCPU model | On | 2 vCPUs |
| Authorized cloud, vCPU model | Off | 1 vCPU |
| OCI compute, OCPU model | Default | 1 OCPU equals 2 vCPUs |
| Bare metal Intel Xeon | On | 2 cores |
| Bare metal AMD EPYC | On | 2 cores |
Each authorized cloud carries specific rules for Oracle BYOL. The rules cover instance types, partitioning, license metrics, and the order of operations on license declaration. The summary below captures the 2026 state.
BYOL audit findings are among the largest Oracle audit exposures. The most common traps fall into four categories. The customer who runs the BYOL deployment with documented declarations avoids the trap.
| Trap | Trigger | Impact |
|---|---|---|
| Soft partitioning | VM allocated fewer vCPUs than host | Full host core count billed |
| Non authorized cloud | Workload on non authorized provider | Full physical core count billed |
| License double count | Same license deployed on premises and cloud | Audit finds duplicate use |
| Wrong metric | Named user license deployed as processor | Compliance gap |
| Unauthorized product use | Database EE option not licensed | Per option compliance gap |
License mobility is the process of moving existing Oracle licenses from on premises to authorized cloud. The mobility right is not automatic. It depends on the original purchase agreement, the support contract status, and the documented declaration of cloud deployment.
The choice between BYOL and License Included shapes the cloud Oracle economics. Customers with existing perpetual licenses almost always benefit from BYOL. Customers without existing licenses sometimes find License Included simpler at small scale.
| Dimension | BYOL | License Included |
|---|---|---|
| Up front cost | Existing license sunk cost | None |
| Running cost | Cloud infra rate plus support | Higher hourly rate |
| Audit profile | Customer managed | Cloud provider managed |
| Flexibility | License re used across workloads | Locked to cloud instance |
| Typical savings | 32 to 58 percent | Baseline |
Oracle gives credit on OCI subscriptions against existing perpetual licenses. The credit reduces the OCI consumption cost dollar for dollar. The credit is one of the strongest reasons Oracle estates often choose OCI over AWS or Azure when migrating from on premises.
The eight step checklist below moves an Oracle cloud workload from License Included or unauthorized cloud to BYOL with documented compliance. Open it before any cloud migration project starts.
Oracle authorizes AWS, Microsoft Azure, Oracle Cloud OCI, and Google Cloud GCP under specific rules. AWS and Azure use the authorized cloud model with vCPU based counting. GCP supports Oracle through Bare Metal Solution and the 2025 launched Google Cloud Oracle Database service. Non authorized clouds fall back to full physical core counting.
On authorized clouds with hyperthreading on, two vCPUs equal one Oracle processor license. With hyperthreading off, one vCPU equals one processor license. The math is fixed by the Oracle authorized cloud policy. On OCI compute, one OCPU equals two vCPUs equal one processor license under the standard core factor.
The standard Oracle partitioning policy applies. Soft partitioning is not recognized. The customer is liable for the full physical core count of every host running Oracle workloads, regardless of how many cores the VM uses. This is the single largest Oracle audit trap for non authorized cloud deployments and has triggered findings in the tens of millions of dollars.
Yes. Oracle applies credit on OCI subscriptions against existing perpetual licenses with active support. The credit reduces the OCI consumption cost dollar for dollar. This is one of the strongest reasons Oracle estates often select OCI over AWS or Azure when migrating from on premises Oracle workloads.
Yes, but the options must be separately licensed and the deployment must follow the option specific rules. Partitioning, Advanced Compression, Real Application Clusters, Advanced Security, and Diagnostics Pack all carry their own per processor license requirement. Always run the option audit before a cloud migration to avoid compliance gaps.
BYOL uses an existing Oracle license to cover the cloud workload and the customer pays only the infrastructure rate. License Included bundles the Oracle license cost into the hourly cloud rate. BYOL saves 32 to 58 percent on most workloads but requires an existing license and active support. License Included is simpler at small scale and for short term workloads.
Redress runs the Oracle BYOL work as a 12 to 18 week assessment plus deployment engagement. The work pulls the Oracle license inventory, maps the cloud target environments, runs the vCPU math, scores the audit risk, and builds the deployment declaration. The deliverable is a defended BYOL deployment plan with documented compliance and 24 month watch list.
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 next Oracle license decision. Cloud BYOL math, ULA certification timing, audit defense playbook, and the negotiation envelope used on every engagement.
Used across five hundred plus enterprise software engagements. Independent. Buyer side. Built for enterprise customers running Oracle Database, middleware, and Cloud at scale.
Open the white paper in your browser. Corporate email only.
Open the Paper →The cloud migration plan landed on AWS for a 240 processor Oracle estate. We ran the vCPU math, declared license mobility against the existing support contract, swapped two thirds of the workload to OCI to capture the BYOL credit, and recovered 41 percent of the original License Included envelope across the three year migration plan.
We have run 500+ enterprise clients across 11 publishers. Every engagement starts with one conversation.
Authorized cloud policy movements, vCPU math updates, OCI credit pattern changes, and the wider Oracle commercial signals across every license 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.
