Oracle OCI BYOL Licensing Strategy: Maximising Savings from Existing Licences

The Core BYOL Proposition on OCI

Oracle's BYOL programme on OCI is one of the most commercially significant mechanisms for Oracle customers managing cloud migration strategies. When an organisation holds full-use perpetual Oracle licences with active support, those licences can be "brought" to OCI to run the same software in Oracle's cloud without paying Oracle's standard Licence Included pricing. The cost difference between BYOL and Licence Included on OCI is substantial — Oracle prices BYOL compute at roughly half the rate of Licence Included for equivalent Oracle Database workloads.

The financial logic is straightforward: you have already paid Oracle for the licence. BYOL formalises the right to use that existing licence in OCI, so Oracle charges you only for the cloud infrastructure (compute, storage, networking) rather than for both the infrastructure and a new licence fee. For organisations with large Oracle Database estates, the BYOL savings over a three-to-five year cloud migration can run to tens of millions of dollars.

However, BYOL on OCI is not a frictionless cost reduction. The processor-to-OCPU mapping rules, active support requirements, ECPU transition obligations, and compliance tracking requirements all create obligations that must be managed carefully. Organisations that implement BYOL without understanding these rules create cloud compliance exposure that can offset or exceed the intended savings.

The Processor-to-OCPU Mapping Rule

The foundational BYOL rule on OCI is the processor-to-OCPU mapping: 1 Oracle Processor licence entitles the organisation to use 2 OCPUs on OCI. This mapping is specific to OCI and is more favourable than Oracle's rules for third-party hyperscalers (AWS, Azure, Google Cloud), where 1 Processor licence typically maps to 2 vCPUs or 1 physical core depending on the hyperscaler's environment.

To calculate how many OCI OCPUs you can run under BYOL, multiply your Processor licence count by 2. An organisation with 50 Oracle Database Enterprise Edition Processor licences can deploy up to 100 OCPUs on OCI under BYOL. Deploying more than 100 OCPUs would constitute under-licensing — the OCPUs in excess of the 100 BYOL entitlement would need to be covered by Licence Included pricing or additional BYOL licences.

This 2-OCPU-per-Processor rule applies to Oracle Database Enterprise Edition, Oracle Database Standard Edition (where applicable), Oracle Middleware including WebLogic Server, and other Oracle products listed in Oracle's BYOL documentation. The rule is a key reason why OCI is often more cost-effective than competing hyperscalers for existing Oracle customers — the 2-to-1 BYOL ratio on OCI versus the 1-to-1 ratio that applies in AWS and Azure means the same licence pool stretches twice as far on OCI.

Eligible Products for Oracle OCI BYOL

Not all Oracle licences are eligible for BYOL on OCI. Oracle's BYOL programme covers Full Use (FU) licences and some Application-Specific Full Use (ASFU) licences, with important restrictions on the ASFU category.

Full Use Licences

Full Use Oracle licences are the standard perpetual licence type available through Oracle's price list. They authorise the licensee to use the software for any lawful purpose and are eligible for BYOL on OCI without restriction to specific applications. The products commonly eligible for OCI BYOL under Full Use licensing include Oracle Database Enterprise Edition and its options (Advanced Security, Partitioning, Real Application Clusters, and others), Oracle Database Standard Edition 2, Oracle WebLogic Server, Oracle SOA Suite, Oracle GoldenGate, and Oracle Java SE subscriptions.

The key eligibility requirement for Full Use licences is active Oracle support. The BYOL right is tied to the licence being in active support at the time of cloud deployment. A Processor licence that has been placed on Licence Support or had support terminated is not eligible for BYOL on OCI until support is reinstated — and Oracle will charge back support fees for the lapsed period before reinstating.

Application-Specific Full Use (ASFU) Licences

ASFU licences are granted by Oracle to software vendors (ISVs) for embedding Oracle software within their applications. An ASFU licence permits use of Oracle software only within the specific application for which it was granted. The ASFU restriction carries into the cloud: an ASFU licence for Oracle Database bundled with an ISV application can only be brought to OCI if the application is also running on OCI. You cannot use an ASFU Oracle Database licence to run a different workload on OCI.

Organisations that have inherited ASFU licences through acquisitions or bundled software agreements frequently misapply these licences by using them for BYOL deployments beyond their intended application scope. This is one of the more common BYOL compliance findings in Oracle cloud audits.

Active Support: The Non-Negotiable BYOL Requirement

Oracle mandates that any licence used under BYOL on OCI must have an active Oracle support contract. This requirement is not a technicality — it is enforced through Oracle's cloud provisioning processes, and it has direct commercial implications that must be included in any BYOL cost analysis.

When you bring an Oracle licence to OCI under BYOL, you continue paying Oracle annual support on that licence exactly as if it were deployed on-premises. Oracle's annual support fee on perpetual licences increases by 8% per year. An organisation with $2 million in annual Oracle support that migrates 50% of its Oracle estate to OCI under BYOL still pays $2 million in annual support (or more, given the 8% annual escalation) — the cloud migration does not reduce the support bill for BYOL licences.

This has an important implication for total cost of ownership modelling. BYOL savings are real and material, but the full TCO comparison between BYOL OCI and Licence Included OCI must account for the continuing on-premises support cost of the BYOL licences. For many organisations, the break-even analysis also needs to consider whether those on-premises licences have alternative value — as deployment capacity for on-premises workloads that will remain, for disaster recovery, or for future on-premises deployments.

The OCPU to ECPU Transition

Oracle introduced a new compute metric — ECPUs (Elastic Compute Processing Units) — for Autonomous Database services on OCI, alongside the existing OCPU metric. From 28 May 2025, new Autonomous VM Clusters on OCI cannot be provisioned with the OCPU billing metric. All new Autonomous VM Cluster deployments must use the ECPU metric.

The ECPU metric changes the BYOL mapping ratio. Where 1 Processor licence = 2 OCPUs under the OCPU model, the ECPU equivalent is different and must be verified against Oracle's current documentation for each specific Autonomous Database service variant. Organisations with existing OCPU-based deployments should review Oracle's migration guidance and confirm the ECPU equivalent mapping for their specific database configurations before migrating from OCPU to ECPU billing.

For non-Autonomous workloads running on standard OCI VM shapes or dedicated infrastructure, the OCPU billing model continues to apply, and the 1-Processor-to-2-OCPU BYOL rule remains in effect. The ECPU transition is specific to Autonomous Database services and does not change BYOL mechanics for standard database deployments.

Oracle License Manager: Managing BYOL Compliance on OCI

Oracle provides a free, opt-in service called License Manager that allows organisations to track BYOL licence usage across OCI. License Manager provides visibility into BYOL allocations, OCPU consumption against licence entitlements, and resources approaching or exceeding their BYOL licence coverage.

Using License Manager is not a compliance guarantee — it is a governance tool. The system relies on accurate BYOL configuration when OCI resources are provisioned: administrators must correctly designate resources as BYOL versus Licence Included at the time of provisioning. If resources are provisioned as Licence Included when BYOL should have been applied, the savings are lost. If resources are provisioned as BYOL when insufficient licences are available to cover them, the organisation faces compliance exposure.

The most effective BYOL governance approach combines License Manager monitoring with a pre-deployment validation process: before any new OCI resource is provisioned as BYOL, confirm that the available processor licence pool covers the additional OCPUs and update the BYOL allocation records accordingly. This pre-deployment check prevents over-commitment against the licence pool and ensures that compliance documentation is maintained contemporaneously rather than reconstructed after the fact.

BYOL vs Licence Included: Cost Comparison

The financial case for BYOL depends on the specific OCI service, the Oracle product, and the volume of OCPUs required. Oracle publishes different compute rates for BYOL and Licence Included OCI configurations, and the difference varies by service. For Oracle Database Enterprise Edition on OCI, BYOL compute rates are typically 40 to 55 percent lower than Licence Included rates for equivalent compute configurations.

A worked example: an organisation running Oracle Database Enterprise Edition on a 32-OCPU OCI VM shape. Under Licence Included pricing, the combined licence and compute cost might be $15,000 per month. Under BYOL (using 16 existing Processor licences), the compute-only cost might be $7,500 per month — a saving of $7,500 per month or $90,000 per year for a single VM shape. Against an organisation with tens of such deployments, the annual BYOL saving is material.

Against this saving must be offset the continuing annual support cost of the 16 Processor licences — at Oracle's list support rate of approximately $10,500 per Processor licence per year, support on 16 licences is $168,000 per year (increasing at 8% annually). The net BYOL benefit in year one is $90,000 minus the allocation of support cost attributable to this deployment. Total BYOL economics must always be modelled at the full licence portfolio level, not workload by workload in isolation.

Strategic BYOL Deployment Decisions

Organisations approaching an Oracle cloud migration should treat the BYOL versus Licence Included decision as a portfolio-level strategic choice, not a per-workload tactical decision. The strategic questions are: which Oracle products in your licence portfolio have the highest support cost relative to their usage value, how many OCPUs do you need on OCI, and what is the total cost differential between BYOL and Licence Included at your planned cloud scale?

Licences with the highest support cost per unit and the highest planned OCI OCPU consumption should be prioritised for BYOL deployment. Licences for products with low planned OCI usage but significant on-premises deployment requirements should be retained for on-premises coverage. The BYOL election should not deplete the on-premises licence pool to a level that creates on-premises compliance risk.

For independent guidance on BYOL strategy, licence inventory validation, and OCI cost modelling, visit our Oracle Knowledge Hub or contact the Redress Compliance Oracle advisory team.