The decision rule is an entitlement question before it is a price question: BYOL only beats license-included where you hold matching licenses — edition, options and all — on active Oracle support, and intend to keep that support stream running. Where any of those conditions fail, the license-included rate buys the same service without the counting, and the saving BYOL appears to offer is partly the support bill you were paying anyway.
Published 29 December 2025 · Last reviewed 25 March 2026
Every OCI database service — Base Database, Exadata Database Service, Autonomous Database — is sold under one of two license models, chosen per instance. License-included bundles the database software, the relevant feature tier and its support into the service rate: consume the service, and the licensing question for that workload disappears into the meter. Bring Your Own License applies entitlements you already own against a reduced service rate — you keep paying Oracle support on the brought licenses, and the cloud charges you for infrastructure and service rather than for software you already bought.
The structural difference is what each model does to your balance sheet of entitlements. License-included consumes nothing you own: licenses stay free for on-premise use, and stopping the service stops the cost. BYOL pledges owned licenses to the cloud workload — an entitlement covers one place at a time, so a license backing an OCI instance is not simultaneously available to the datacenter. That bookkeeping is precisely the kind of position a compliance assessment establishes before a migration rather than during an audit.
Note what this comparison is not: it is not the hyperscaler question. In AWS and Azure, Oracle's cloud policy counts two vCPUs per Processor license with no core factor and there is no license-included alternative for the database — BYOL is simply how Oracle software runs there. The model choice in this guide exists only in OCI, where Oracle prices both paths and lets them compete.
This guide is general information about Oracle's OCI license models, not legal or licensing advice; ratios, eligibility and program terms are set by your agreement and Oracle's current cloud licensing documents, which Oracle revises. It names no firms; the firm directory lists Oracle-capable advisors with balanced pros and cons, listed, not ranked.
BYOL runs on published conversion ratios. For Enterprise Edition, one on-premise Processor license covers two OCPUs of a BYOL-eligible service; for Standard Edition 2, one Processor (socket) license stretches to four OCPUs, with SE2 service shapes capped in size — ratios notably more generous than the two-vCPUs-per-license counting the same policy applies to AWS and Azure. Named User Plus entitlements can be brought too, subject to per-OCPU minimums (25 NUP per OCPU on EE-based services), which keeps the metric mechanics alive in the cloud.
Three conditions ride along. First, active support: BYOL requires the brought entitlements to be on current Oracle support for as long as they back the cloud workload — lapsed-support shelfware and estates on third-party support are outside the program. Second, edition and tier matching: bringing licenses into a higher service tier requires owning the options that tier bundles — a BYOL instance exercising compression, partitioning or RAC needs those options held in matching quantities, where license-included simply includes them in the rate. Third, quantity at peak: BYOL entitlements must cover the OCPUs actually consumed, including what autoscaling reaches, not the baseline the migration plan assumed.
On the economics, the BYOL rate removes — indicatively — the large majority of the license-included rate for the same shape, which looks decisive until the support stream is added back. The honest comparison is BYOL-rate-plus-continuing-support against the license-included rate, evaluated over the life of the workload: where support was being paid regardless, BYOL's marginal cost is small; where the alternative was shedding that support line entirely, license-included plus a support exit can model out ahead. How OCI consumption itself is bought — committed Universal Credits or pay-as-you-go — is its own decision, covered in the Universal Credits comparison.
Oracle Support Rewards exists to make the BYOL support condition feel lighter: OCI Universal Credits consumption earns a credit against the on-premise technology support bill — indicatively a quarter of each unit of OCI spend, and a third for Unlimited License Agreement customers. The mechanics matter: rewards offset the support invoice, not the cloud invoice; they cannot take support below zero; and they expire if unused. For a BYOL-heavy estate the effect is real — the support stream BYOL forces you to keep is partly funded by the consumption BYOL drives. For an estate weighing Oracle support against third-party support, Support Rewards is also, factually, a retention instrument: leaving Oracle support forfeits both BYOL eligibility and the rewards — both sides of that trade deserve stating, and this is information, not advice.
ULA holders get the frictionless version during the term: included programs deploy freely into OCI, and the rewards accrue at the higher rate. The reckoning is at certification — whether and how cloud deployments count into the certified quantities is contract-specific, varying from exclusion to averaging rules, and the answer determines what BYOL position exists the day after exit. An estate planning certify-then-BYOL needs that counting rule confirmed in writing before the final year; the dynamics are the subject of the ULA vs PULA and certification vs renewal comparisons.
| MECHANIC | BYOL | LICENSE-INCLUDED |
|---|---|---|
| What you pay | Reduced service rate + continuing on-premise support on brought licenses | Full service rate; software and its support inside the meter |
| Entitlement condition | Owned licenses, matching edition and options, on active Oracle support | None — no on-premise entitlements consumed |
| Conversion | EE 1 Processor → 2 OCPUs; SE2 1 socket → up to 4 OCPUs; NUP per-OCPU minimums | Not applicable |
| Counting burden | Continuous — entitlements vs OCPUs consumed, autoscaling included | None for the workload; cost governance instead |
| Reversibility | License type switchable; licenses return to on-premise use on exit | Switchable to BYOL; stopping the service ends the cost |
| Program interplay | Support Rewards offset the support bill; ULA terms deploy freely | Support Rewards accrue on consumption all the same |
| Typical compliance finding | Options mismatch on tiered services; autoscale beyond entitlements; double-use across cloud and datacenter | Workloads left running; tier above what the workload uses |
| Where it fits | Surplus supported licenses, steady-state workloads, support staying anyway | Net-new, elastic or temporary workloads; no matching entitlements; support exit planned |
BYOL is the natural answer where consolidation, hardware refresh or a ULA certification has left a surplus of supported licenses; where the workload is steady-state enough that entitlements can be sized to peak; and where the support stream is staying for other reasons, making its cost sunk rather than incremental. It preserves the perpetual asset: the day the workload leaves OCI, the licenses go back to work on-premise.
License-included is the natural answer for net-new applications with no matching entitlements, for elastic or short-lived workloads where autoscaling would whipsaw a BYOL position, for tiers whose bundled options you do not own, and for estates deliberately shrinking their on-premise support base — renting the license inside the meter is what makes that exit possible. It is also the pragmatic opening move: start license-included, establish the entitlement position properly, then flip eligible instances to BYOL, since the license type is switchable rather than a one-way door.
The traps are consistent across estates. Keeping support alive on shelfware purely to feed BYOL — paying the support bill to earn the discount — deserves explicit modelling rather than inheritance. Autoscaling and burst capacity breach BYOL ratios silently; entitlements must cover the ceiling, not the average. Options mismatch on tiered services is the finding Oracle's own usage data surfaces most readily. Migration overlap — the same entitlement backing the datacenter and the cloud at once for longer than the transition genuinely requires — converts a tidy plan into a compliance gap. And Support Rewards arithmetic belongs in the model with its expiry and its cap, not as a headline percentage. Pricing all of this against a real workload profile is standard scope for an Oracle cloud cost optimization engagement.
How the consumption itself is bought →
The support stream BYOL depends on →
The editions behind the conversion ratios →
How to pick the firm for this work →
Firms that model BYOL decisions →
Every field guide on the site →
For Oracle Database Enterprise Edition, one on-premise Processor license covers two OCPUs of a BYOL-eligible OCI database service; for Standard Edition 2, one Processor (socket) license covers up to four OCPUs, with SE2 instances capped in size. Named User Plus entitlements can also be brought, subject to per-OCPU minimums (25 NUP per OCPU for EE-based services). The ratios are set by Oracle’s cloud licensing documents and are more generous than the hyperscaler counting rules for AWS and Azure.
Yes. BYOL is conditional on the brought entitlements carrying active Oracle support for the full period of cloud use. That makes the true BYOL cost the reduced cloud rate plus the continuing on-premise support stream — and it means licenses whose support has lapsed, or estates that have moved to third-party support, are not BYOL-eligible. The support condition is the hinge of the whole comparison.
Yes — the license type is a setting on the service, not a one-way door. Instances can generally be changed between BYOL and license-included, which makes the choice revisitable as entitlement positions change: a common sequence starts license-included for speed, then flips to BYOL once a compliance assessment confirms which owned licenses are genuinely free to bring.
OCI Universal Credits consumption earns a credit against the on-premise technology support bill — indicatively a quarter of each unit of OCI spend, rising to a third for Unlimited License Agreement customers. The rewards reduce the support invoice, not the cloud invoice, cannot take support below zero, and expire if unused. For BYOL estates the effect is direct, since BYOL forces that support stream to continue; the mechanics interact with any third-party-support evaluation, covered in the Oracle Support vs third-party support comparison.
Yes. Bringing licenses into a higher OCI database tier requires owning the corresponding option entitlements — a BYOL instance using features of the bundled tiers (compression, partitioning, RAC and so on) needs those options held on-premise with active support, in matching quantities. License-included rates bundle the tier’s features regardless of what you own. Options mismatch is one of the most common BYOL compliance findings.
During a ULA term, deployment in OCI is generally unrestricted for included programs, and ULA customers earn Support Rewards at the higher rate. The pressure point is certification: how cloud deployments count at exit is contract-specific — some agreements exclude or average cloud counts — so an estate planning to certify and then run on BYOL needs the certified quantities and the cloud counting rule confirmed before the term ends, not after.
Deciding what your licenses are worth in OCI — and whether the support stream behind them should live or die — is exactly what an Oracle licensing advisor is for. The directory lists the firms that do this work, with balanced pros and cons, listed, not ranked.
Tell us the vendor, the service you need and where things stand, and we will route your brief to firms that genuinely cover that combination. The directory and matching are free for buyers, no vendor ever sees your brief, and we add no markup.
Our weekly dispatch on vendor audit programs, regional developments and one buyer move. Subscribe to The Licensing Radar.