BYOL reuses licenses you already own at a lower cloud rate. The conversion ratio and the support you keep paying decide whether that is a real saving or two bills for one workload.
Bring Your Own License lets you apply Oracle licenses you already own to a cloud service and pay a reduced rate for the infrastructure. The alternative is license included, where the license is bundled into the hourly price and you own nothing at the end.
The decision looks like a simple rate comparison and it is not. BYOL only pays when you own the licenses, keep support current, size the conversion correctly, and are honest about how many hours the workload actually runs. Each of those carries a trap.
The primary sources for this page are Oracle's own: the Oracle BYOL program page, the Oracle cloud licensing policy, the OCI price list, the Oracle Technology Global Price List, and the Oracle Database Licensing Information manual.
BYOL lets you apply full use licenses you already own to an equivalent cloud service and pay only the reduced BYOL infrastructure rate. The word doing the work in that sentence is full use, because not every Oracle license is one.
Start with the license type printed on the ordering document, not with the product name. Two entitlements for the same database version can behave completely differently.
What can and cannot be brought
| Entitlement | Eligible for BYOL | What to check first |
|---|---|---|
| Full use Database Enterprise Edition, Processor metric | Yes | Support is current and the territory covers the cloud region |
| Full use Database Enterprise Edition, Named User Plus metric | Yes, with cloud minimums | The 25 per Processor floor still applies against the converted count |
| Standard Edition 2 | Yes, with hard instance ceilings | Eight vCPU maximum on the named third party clouds |
| Database options and management packs | Yes, separately | Each option needs its own entitlement matched to the base count |
| Application Specific Full Use | Generally no | Use is restricted to the named application, not to your own workloads |
| Embedded Software License | No | The license lives inside a third party product and cannot be redirected |
| Licenses inside an uncertified unlimited agreement | Depends on the ULA text | Whether cloud deployments count at certification, and whether they are capped |
BYOL is not a transfer, a trade in, or a credit. Your licenses stay yours, your support contract stays live, and Oracle simply charges less for the infrastructure because you are not buying the license twice.
It also does not suspend anything. The support bill continues at 22 percent of the original net license fee, indexed at renewal, for as long as you hold the entitlement. That fact is the whole economics of this decision.
Oracle licenses are granted for a defined territory. Running a BYOL workload in a cloud region outside that territory is a contract issue rather than a policy issue, and contract issues do not settle with a well argued email.
Differently on Oracle's own cloud than on anybody else's, and that difference is the single most common modeling error we correct. On OCI the unit is the OCPU. On Amazon, Azure and Google Cloud the unit is the vCPU.
An OCPU is one physical core with hyperthreading enabled, which presents as two vCPUs. So one Enterprise Edition Processor license covers two OCPUs on OCI, and the same license covers two vCPUs on an Authorized Cloud Environment.
Read those two sentences again, because they are not the same amount of compute. Two OCPUs is four vCPUs of capacity. The identical license buys you twice as much processing on Oracle's cloud as it does on Amazon's.
What one Enterprise Edition Processor license buys, by platform
| Platform | Counting unit | One Processor license covers | Core factor applies? |
|---|---|---|---|
| On premises x86 server | Physical core | 2 physical cores at factor 0.5 | Yes |
| Oracle Cloud Infrastructure | OCPU | 2 OCPUs, which is 4 vCPUs of capacity | Not applicable, OCI has its own terms |
| AWS, Azure or Google Cloud, hyperthreading on | vCPU | 2 vCPUs | No |
| AWS, Azure or Google Cloud, hyperthreading off | vCPU | 1 vCPU | No |
| Standard Edition 2 on a named third party cloud | Socket, derived from vCPU | 4 vCPUs per socket, 8 vCPU ceiling | No |
The OCI conversion sits in the service descriptions and the cloud price list, which Oracle updates without notice. The third party cloud counting rule sits in the cloud licensing policy, a unilateral document that has been revised several times.
Neither is a contract term. Capture the version you modeled against, with the date, and keep it. When the policy changes, that snapshot is the only thing that shows what you reasonably relied on.
The most common sizing failure is counting entitlements and assuming the workload fits. Convert first, then size, then check the option entitlements match the converted base count.
When the workload runs enough hours to absorb the support you are paying anyway. That is the whole test, and it is arithmetic rather than judgment.
Take 20 Processor licenses of Enterprise Edition. At list that is $950,000 of license and about $209,000 of annual support. Under BYOL those 20 licenses convert to 40 OCPUs on OCI.
Now divide the support bill by the OCPU hours you will actually consume. That gives you the real cost of the license component of a BYOL instance, which the cloud invoice never shows you.
What your existing support actually costs per OCPU hour
| Run pattern | Hours per year | OCPU hours on 40 OCPUs | Support cost per OCPU hour |
|---|---|---|---|
| Continuous production, 24 hours a day | 8,760 | 350,400 | $0.60 |
| Extended business hours, 10 hours, five days a week | 2,600 | 104,000 | $2.01 |
| Quarter end and project bursts | 720 | 28,800 | $7.26 |
| Provisioned but rarely used, one hour a day | 365 | 14,600 | $14.32 |
If the gap between the license included rate and the BYOL rate is smaller than the number in the right hand column, license included wins. On a bursty workload that gap is never $7 per OCPU hour.
A continuously running database spreads the support bill across 8,760 hours, so the effective license cost per hour collapses. You are also buying nothing new, which keeps capital out of the decision entirely.
Oracle Support Rewards credits a share of your OCI spend against your Oracle technical support invoices, at 25 cents per dollar for most customers and 33 cents for those with an unlimited licensing agreement.
That materially changes the comparison. On $500,000 of annual OCI consumption, the rewards offset is $125,000 against a support bill you were paying regardless, and it applies to OCI spend whether the instance is BYOL or license included.
Model it explicitly, and model what happens when the OCI spend stops. Rewards that disappear leave the full support bill behind them.
White Paper · Oracle
Count the Oracle cloud licence before you commit. Read it free.
Paying twice, converting wrong, and assuming support can be trimmed later. All three are quiet, and all three surface at the worst possible moment.
Decide which specific licenses back the cloud workload and retire the rest properly, in line with the Oracle support terms. Supported licenses that back nothing are pure cost with no compliance benefit.
The obvious plan is to migrate half the estate to cloud under BYOL and drop support on the other half. Oracle's support policies prevent that through matching service levels and repricing.
Yes, and the mechanism is simple double use. The same Processor license cannot back an on premises deployment and a cloud instance at the same time, however briefly.
The standard advice is that BYOL always beats license included because the hourly rate is lower. We disagree, and the arithmetic above is why. In a large share of the migrations we ran, license included won for short or bursty workloads, because the support on the underlying licenses runs all year while the instance does not. A lower hourly rate on licenses you keep supporting is not a saving, it is two bills for one workload. Model both options against real run hours and the support you are already paying, then decide workload by workload rather than adopting a single estate wide policy that suits the vendor more than it suits you.
Not automatically, and this is the assumption that costs the most. The favorable counting rule you modeled belongs to a specific platform under a specific Oracle document, and both can move.
The vCPU rule applies only to the services Oracle names as Authorized Cloud Environments: Amazon EC2, Amazon RDS, the Microsoft Azure Platform and Google Cloud Platform. Anywhere else, the on premises rules return.
That is not a small change. On premises rules count physical cores in the host, which in a multi tenant cloud you neither control nor can measure. Our cloud counting reference works through what that means in practice.
OCI is not governed by the cloud licensing policy at all. It runs under Oracle's own service terms, and the OCPU conversion there is a commercial term Oracle can revise in a future service description.
A repatriation from cloud to a shared hypervisor is where BYOL gains evaporate. The counting boundary changes from a vCPU you chose to a cluster you did not, on Nutanix AHV, on Hyper V and on VMware alike.
If an unlimited licensing agreement is running, read its cloud clause before you deploy. Some ULAs exclude public cloud deployments from the certification count, some cap them, and some are silent, which is its own problem.
Certification is a one time measurement with permanent consequences. Our Oracle ULA guide covers the sequence, and the cloud clause is worth reading twice.
BYOL does not reduce what you owe Oracle. It changes where you pay it. The support line is the part that never turns off.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
Oracle Bring Your Own License lets you apply licenses you already own to an equivalent cloud service and pay a reduced infrastructure rate instead of the bundled license included price. The licenses stay yours, and so does the support bill.
They translate owned licenses into the cloud provider's compute unit. On Oracle Cloud Infrastructure one Enterprise Edition Processor license covers two OCPUs, and on Amazon, Azure or Google Cloud it covers two vCPUs where hyperthreading is enabled and one where it is not.
No, and treating it as a rule costs money. BYOL wins on steady workloads that consume many hours, while license included frequently wins on short, seasonal or project workloads, because support on the underlying licenses runs whether the instance does or not.
Yes, at the usual 22 percent of the original net license fee, indexed at renewal. Active support is a condition of using BYOL, so the support line is not something you can pause while the workload is idle.
Generally no. An Application Specific Full Use entitlement restricts the database to a named application, so it cannot be redirected to your own workloads on a cloud instance. Embedded Software License entitlements are more restricted still.
Not on the named third party clouds. Oracle states that the core factor does not apply in Authorized Cloud Environments, which is why a migration from favorable hardware can increase the license requirement even though the workload has not changed.
Yes, most often through double use during a migration. The same license cannot back an on premises deployment and a cloud instance at once, and the parallel run window is where that quietly happens.
Rarely without a penalty. Oracle's matching service level and repricing rules mean terminating support on part of a support set usually triggers a recalculation on the remainder, so plan any reduction into the contract before the migration rather than after it.
You are exposed, because the cloud licensing policy is a unilateral Oracle document that states it is not incorporated into any agreement. The only durable protection is to write the counting rule and the conversion ratio into your ordering document or an amendment.
The vCPU counting rule, the SE2 cloud caps, options stacking, and BYOL versus license included across both clouds, with worked numbers.
Independent. Buyer side. Built for Oracle customers running the next renewal cycle.
Open the white paper in your browser. Corporate email only.
Open the Paper →A lower rate on idle licenses you keep supporting is two bills for one workload.
We have run 500+ enterprise clients across 11 publishers. Every engagement starts with one conversation.
Oracle Database benchmarks, ULA exit patterns, Java audit posture, and OCI commitment math from every Oracle engagement we run on the buyer side.
