The bottom line on Oracle OCI licensing
Bottom LineOracle OCI licensing rewards BYOL and punishes the unprepared. On OCI, one Oracle Database Enterprise Edition Processor licence covers 2 OCPUs, cutting the database service rate by roughly 75% versus license-included — but your perpetual licences keep paying 22% annual support in parallel. Right-size your entitlements first, negotiate the Universal Credits commit second, and treat Support Rewards as a discount you bank, not a reason to over-commit.
Oracle's cloud sales motion presents OCI as a frictionless lift off legacy infrastructure. The licensing reality is sharper: OCI changes the metric from cores-times-core-factor to raw OCPUs, and the cost of getting that conversion wrong shows up on every monthly invoice. This guide gives you the math before Oracle gives you the quote.
Key takeaways
- BYOL converts at 2 OCPUs per Processor licence. On OCI, one Oracle Database Enterprise Edition Processor licence covers 2 OCPUs — twice the compute that the same licence buys on AWS or Azure, where the Authorized Cloud Environment policy counts 2 vCPUs (Oracle licensing policy, 2026).
- BYOL cuts the service rate ~75%. An Oracle Database Enterprise Edition workload lists at roughly $4.03 per OCPU per hour license-included versus about $1.34 per OCPU per hour under BYOL (Oracle OCI Price List, 2026) — but the underlying licences still owe 22% annual support.
- Support Rewards bank $0.25–$0.33 per $1. Oracle grants $0.25 of technology support credit for every $1 of OCI consumption, rising to $0.33 for ULA customers (Oracle Support Rewards, 2026), redeemable against your tech support bill down to zero.
- Universal Credits discounts scale with commitment. Committed Universal Credits deals typically earn 10% at the ~$250K annual tier to 35%+ at $10M+, set against Oracle's internal discount floors (OCI Universal Credits, 2026).
- Most OCI quotes are sized to over-committed credits. Across our cloud engagements, the initial Oracle OCI proposal over-states required Universal Credits by 20–40% versus verified workload need (Oracle Licensing Experts benchmark, 2026) — the single largest source of avoidable OCI spend.
What to do this quarter, by seat
CIO Strategy
- Decide BYOL vs license-included per workload, not for the whole estate — the right answer differs by utilisation and licence ownership.
- Refuse to let an OCI migration become a forced re-purchase of licences you already own; demand the BYOL path be priced alongside license-included.
- Tie any multi-year Universal Credits commit to a verified consumption forecast, not Oracle's roadmap deck.
CFO Capital
- Model the parallel 22% support cost that BYOL keeps alive — OCI lowers the service rate, not the support invoice.
- Treat Support Rewards as a hard, bankable offset against tech support, and book it into the OCI business case at the correct $0.25 or $0.33 rate.
- Reject Universal Credits commitments that exceed verified 12-month consumption; unused credits expire and become pure margin for Oracle.
SAM / ITAM Manager Compliance
- Reconcile owned Processor and NUP entitlements to planned OCPU counts before any workload moves — BYOL must stay inside owned licences.
- Map every database option and pack (Diagnostics, Tuning, Partitioning, RAC) that must BYOL alongside the base licence.
- Maintain a live entitlement-to-deployment ledger; mixed BYOL and on-premise estates are a standard audit trigger.
Head of Infrastructure Operations
- Right-size OCPU shapes to real CPU demand — OCI bills per OCPU-hour, so over-provisioning compounds monthly.
- Sequence the OCI move to a hardware refresh or data-centre exit to convert new cost into cost avoidance.
- Validate that your database version and edition are certified for the target OCI service before committing migration dates.
The Oracle OCI licensing framework, question by question
How does BYOL work on Oracle OCI?
BYOL (Bring Your Own License) is the model where you apply on-premise Oracle Processor or Named User Plus licences you already own to OCI, instead of paying the bundled license-included rate. On OCI, one Oracle Database Enterprise Edition Processor licence covers 2 OCPUs. BYOL drops the database service rate sharply, but the perpetual licences keep paying 22% annual support whether they run in your data centre or on OCI.
The conversion unit matters. On-premise, your entitlement is governed by cores multiplied by the Core Factor Table. On OCI, Oracle meters by OCPU — one physical core with hyper-threading — and ignores the core factor entirely. That means you must translate your existing licence position into OCPU capacity before you size a single instance, or you will either strand entitlements or breach them.
Build a one-page BYOL conversion ledger: owned Processor licences × 2 = total OCPUs you can run under BYOL. Size your OCI shapes to that number first; only buy license-included for the overflow. This single document stops most OCI over-purchasing before it starts.
How much does Oracle Database cost on OCI: BYOL vs license-included?
An Oracle Database Enterprise Edition workload on OCI lists at roughly $4.03 per OCPU per hour license-included versus about $1.34 per OCPU per hour under BYOL — close to a 75% cut on the service rate (Oracle OCI Price List, 2026). Autonomous Database Dedicated runs about $1.94 per OCPU per hour license-included for Transaction Processing, dropping to roughly $0.65 with BYOL, at the same 2-OCPU-per-licence mapping.
The headline 75% saving is real but incomplete. Under license-included, the licence and its support are baked into the metered rate and stop the moment you turn the instance off. Under BYOL, you keep paying 22% annual support on the perpetual licences regardless of OCI runtime. For steady-state, always-on workloads where you already own the licences, BYOL almost always wins; for spiky or short-lived workloads, license-included can be cheaper because it carries no parallel support tail.
Across our OCI engagements, the first Oracle proposal over-states required Universal Credits by 20–40% against verified workload demand — the largest single source of avoidable OCI spend we see (Oracle Licensing Experts benchmark, 2026).
What are OCI Universal Credits and how are they discounted?
Universal Credits are Oracle's consumption purchasing model: you commit a dollar pool of OCI spend over one to four years and draw it down against any eligible OCI service at a single negotiated rate. Committed deals typically earn 10% off at the ~$250K annual tier rising to 35%+ at $10M+ (OCI Universal Credits, 2026). Pay-As-You-Go carries no commitment and no discount, billed at list.
The discount is set against Oracle's internal discount floors — the maximum percentage off list a given tier can approve. The lever is term and volume, but the trap is the commit size. Credits that go unused inside the term expire with no refund, so an inflated commitment quietly converts into pure Oracle margin. Negotiate the rate aggressively, then commit conservatively to a number your verified forecast supports.
Decouple the discount rate from the commit size. Lock the best per-unit rate Oracle will approve, then commit to the low end of your forecast with a documented ramp. Oracle wants the headline commitment number; your interest is the rate and the right to grow into it, not to pre-pay for capacity you may never burn.
How does Oracle Support Rewards lower my support bill?
Support Rewards grants $0.25 of technology software support credit for every $1 of OCI Universal Credits you consume, rising to $0.33 per dollar for customers with an active ULA (Oracle Support Rewards, 2026). Those credits are redeemed against your technology support invoice — Database, WebLogic, middleware — and can drive that line toward zero.
Support Rewards is genuine money, but it is also Oracle's most effective tool for deepening OCI dependence. The credits apply only to eligible technology support, never applications support, and they accrue on consumption, so they reward spending more on OCI. Model the reward on your actual projected consumption and let it offset a bill you were going to pay anyway — never let the reward rate justify a larger commit than the workload needs.
"Confirm in the ordering document the exact Support Rewards rate that applies to us — $0.25 or $0.33 — which support lines are eligible, and how unredeemed rewards carry across renewal." Get the rate and eligibility in the contract, not a slide.
Does the Oracle Core Factor Table apply on OCI?
No. On OCI, Oracle licenses by OCPU and the on-premise Core Factor Table does not apply. One Oracle Database Enterprise Edition Processor licence covers 2 OCPUs, and an OCPU is one physical core with hyper-threading enabled. The core factor still governs your on-premise entitlement and therefore your BYOL math, so you must finish the core-factor calculation before you can know how many OCPUs your licences buy.
This shift is easy to misread. A core factor of 0.5 on-premise means one Processor licence already covers two cores there; on OCI that same licence covers 2 OCPUs. The numbers happen to look similar, but they are different mechanisms — confuse them and your BYOL position will be wrong in either direction. Treat the conversion as a deliberate translation step, documented and signed off, not an assumption.
If an Oracle quote sizes your OCI BYOL footprint without first reconciling your on-premise core-factor entitlement, the OCPU count is a guess. Stop and demand the entitlement baseline. Sizing BYOL off an unverified licence position is how customers end up both over-paying and out of compliance at the same time.
Is BYOL on OCI better than BYOL on AWS or Azure?
Yes, for the identical licence. On OCI, one Database Enterprise Edition Processor licence covers 2 OCPUs — equivalent to 4 vCPUs of compute. Under Oracle's Authorized Cloud Environment policy for AWS and Azure, the same licence covers only 2 vCPUs (Oracle licensing policy, 2026). The OCI conversion is roughly twice as efficient, which is exactly the asymmetry Oracle built to make its own cloud the cheapest home for Oracle workloads.
That advantage is real, but it is a magnet, not a gift. The cheaper conversion pulls workloads onto OCI, where Universal Credits and Support Rewards then deepen the commitment. Use the efficiency where it genuinely lowers cost, but price the multi-cloud alternative too — keeping a credible AWS or Azure option is itself a negotiation lever on your OCI rate.
Keep a costed AWS or Azure BYOL scenario in your back pocket even if you intend to land on OCI. The credible threat of running Oracle Database on a competitor cloud — at the worse 2-vCPU ratio but with rival infrastructure discounts — is one of the few things that moves Oracle's OCI pricing.
Do I still owe support, and can Oracle audit my OCI estate?
Yes on both. BYOL applies licences you already own, and those perpetual licences keep carrying the 22% annual support fee whether they run on-premise or on OCI — BYOL lowers the OCI service rate, not your support bill. And OCI is not an audit-free zone: BYOL deployments must stay inside owned entitlements, and Oracle can verify OCPU counts against your licence position.
Mixed estates are the exposure. When the same product runs partly on-premise, partly BYOL on OCI, and partly license-included, the reconciliation gets complex fast, and complexity is where back-licence claims are born. Keep a single, current ledger that maps every entitlement to every deployment, on-premise and cloud, so an Oracle audit finds a defended position rather than a gap.
"Customer's deployment of Programs on Oracle Cloud Infrastructure under BYOL shall be measured solely by OCPU count, and Customer's existing Processor entitlements shall be deemed sufficient up to the ratio of two (2) OCPUs per Processor licence, without re-measurement under the Core Factor Table."
BYOL or license-included — which quadrant are you in?
BYOL, steady-state
Own licences · always-on workloadYou own the Processor licences and the workload runs continuously. BYOL at 2 OCPUs per licence and ~$1.34/OCPU-hr wins clearly; bank Support Rewards on top. Lowest run-rate.
License-included, spiky
Few/no licences · variable workloadBursty or short-lived workloads with no spare entitlements. License-included carries no parallel 22% support tail and stops when the instance does. Cheaper for variable demand.
BYOL + new license-included overflow
Own some licences · growing workloadBYOL the entitlements you own, buy license-included only for the overflow. Blends the lowest service rate with no compliance risk on the net-new capacity.
Re-evaluate before committing
Unclear entitlements · big commit pendingEntitlement position is unverified and Oracle wants a multi-year Universal Credits commit. Stop. Baseline licences and forecast consumption before signing anything.
Decision matrix: the OCI licensing path is set by two axes — licence ownership (BYOL eligibility) and workload profile (steady-state vs spiky) — not by Oracle's preferred commitment size.
Comparing the OCI licensing paths
| Path | Typical rate & conversion | Strengths | Cautions |
|---|---|---|---|
| BYOL on OCI | ~$1.34/OCPU-hr (EE DB); 2 OCPUs per Processor licence | ~75% off service rate; uses owned licences; Support Rewards offset; best conversion of any cloud | Keeps 22% annual support running in parallel; must stay inside owned entitlements |
| License-included on OCI | ~$4.03/OCPU-hr (EE DB); licence + support bundled | No separate licence to own; no parallel support tail; stops when instance stops | Highest hourly rate; poor fit for always-on workloads you could BYOL |
| BYOL on AWS / Azure | 2 vCPUs per Processor licence (Authorized Cloud) | Multi-cloud flexibility; rival infrastructure discounts; a negotiation lever on OCI | Half the OCI conversion efficiency; same 22% support; tighter policy scrutiny |
| Universal Credits commit | 10–35%+ off list by tier; 1–4 year term | Lower per-unit rate; single drawdown pool; funds Support Rewards accrual | Unused credits expire; over-commitment becomes pure Oracle margin |
A Fortune 500 financial-services firm was quoted a three-year, $9M OCI Universal Credits commit positioned as the only viable migration path. We baselined entitlements, BYOL'd the owned Database and WebLogic licences at 2 OCPUs each, right-sized the commit to verified consumption, and banked Support Rewards — cutting the three-year cloud cost by 38%. See related Oracle licensing case studies with hard numbers.
Oracle OCI licensing glossary
- OCI (Oracle Cloud Infrastructure)
- Oracle's IaaS and PaaS cloud platform, licensed by OCPU consumption rather than by the on-premise Core Factor Table.
- OCPU
- Oracle Compute Unit — one physical processor core with hyper-threading enabled, the metering unit for OCI compute and database services.
- BYOL (Bring Your Own License)
- Applying existing perpetual Oracle Processor or NUP licences to OCI instead of buying license-included subscriptions; converts at 2 OCPUs per Processor licence.
- License-Included
- An OCI pricing model where the Oracle licence and support are bundled into the metered rate, with no separately owned licence required.
- Universal Credits
- Oracle's consumption purchasing model where a committed or pay-as-you-go dollar pool draws down against any eligible OCI service at a negotiated rate.
- Support Rewards
- An Oracle programme granting $0.25 of technology support credit per $1 of OCI consumption ($0.33 for ULA customers), redeemable against the tech support bill.
- Authorized Cloud Environment
- Oracle's policy defining how on-premise licences map to AWS and Azure, counting 2 vCPUs per Processor licence versus 2 OCPUs on OCI.
- Annual Universal Credits
- A Universal Credits commitment billed annually over a one-to-four-year term, earning larger discounts than pay-as-you-go.
- Pay-As-You-Go
- An uncommitted OCI consumption model billed at list with no minimum, used for variable or pilot workloads.
- Cloud@Customer
- Oracle hardware running OCI services inside the customer's own data centre, under the same BYOL and license-included rules as public OCI.
- Core Factor Table
- Oracle's on-premise multiplier that converts physical cores into Processor licence requirements; not used on OCI but governs BYOL entitlement math.
- Premier Support
- Oracle's full support tier for perpetual licences, charged at roughly 22% of net licence value per year and payable in parallel under BYOL.
Oracle OCI licensing: frequently asked questions
How does BYOL work on Oracle OCI?
BYOL (Bring Your Own License) lets you apply existing on-premise Oracle Processor licences to OCI instead of paying license-included cloud rates. On OCI, one Oracle Database Enterprise Edition Processor licence covers 2 OCPUs. BYOL cuts the database service rate by roughly 75%, but your on-premise licences keep incurring the 22% annual support fee in parallel.
How much does Oracle Database cost on OCI with BYOL versus license-included?
On OCI, an Oracle Database Enterprise Edition workload lists at roughly $4.03 per OCPU per hour license-included versus about $1.34 per OCPU per hour with BYOL — about a 75% reduction on the service rate (Oracle OCI Price List, 2026). The trade-off is that BYOL keeps you paying 22% annual support on the underlying perpetual licences.
What are OCI Universal Credits?
OCI Universal Credits are Oracle's consumption-based purchasing model: you commit a dollar amount of OCI spend over one to four years and draw it down against any eligible OCI service at a single negotiated rate. Committed deals typically earn 10% to 35%+ off list depending on commitment size and term.
How does Oracle Support Rewards reduce my support bill?
Oracle Support Rewards grants $0.25 of technology software support credit for every $1 of OCI Universal Credits you consume, rising to $0.33 for customers with an active ULA. Those credits offset your tech support invoice — potentially to zero — but only against eligible technology support, not applications support.
Does the Oracle Core Factor Table apply on OCI?
No. On OCI, Oracle licenses by OCPU, not by the Core Factor Table used on-premise. One Enterprise Edition Processor licence covers 2 OCPUs (one physical core with hyper-threading). The Core Factor Table still governs your on-premise and BYOL entitlement math, so you must know your processor counts before sizing OCI.
Is BYOL on OCI better than BYOL on AWS or Azure?
Yes, for the same licence. On OCI, one Database Enterprise Edition Processor licence covers 2 OCPUs, equivalent to 4 vCPUs. Under Oracle's Authorized Cloud Environment policy for AWS and Azure, the same licence covers only 2 vCPUs — half the compute. The OCI conversion is roughly twice as efficient for identical entitlements.
Do I still pay support if I move to OCI under BYOL?
Yes. BYOL applies licences you already own, and those perpetual licences continue to carry the 22% annual support fee whether they run on-premise or on OCI. BYOL lowers the OCI service rate, not your support bill. Only Support Rewards or license-included subscriptions change the support equation.
Can Oracle audit my OCI environment?
Yes. Running on OCI does not exempt you from compliance. BYOL deployments must stay within owned entitlements, and Oracle can verify OCPU counts against your licence position. License-included services are metered by Oracle, but mixed BYOL and on-premise estates remain a common audit trigger, so keep a current entitlement-to-deployment reconciliation.
How we built this guide
This guide reflects Oracle Licensing Experts engagement data from OCI migration and Universal Credits negotiations across financial services, manufacturing, and technology enterprises, combined with current Oracle cloud pricing and policy verified in mid-2026. Benchmarks branded "Oracle Licensing Experts benchmark" derive from our buyer-side engagements and are stated as ranges to protect client confidentiality. Every external figure is attributed to a primary or authoritative source below.
- Oracle Cloud Infrastructure Price List (license-included and BYOL OCPU rates, compute pricing): oracle.com/cloud/price-list (2026).
- Oracle Support Rewards programme ($0.25 standard, $0.33 ULA per $1 of OCI consumption): oracle.com/cloud/rewards (2026) and the Support Rewards FAQ (2026).
- Oracle Autonomous Database — Bring Your Own License (OCPU compute model, 2-OCPU mapping): docs.oracle.com (2026).
- Authorized Cloud Environment conversion (2 vCPUs per Processor licence on AWS/Azure vs 2 OCPUs on OCI): third-party analysis, Pretius, 2026.
- Universal Credits commitment discount tiers (10–35%+ by spend) and BYOL ~75% service-rate reduction: Oracle OCI Price List and Oracle Licensing Experts engagement analysis, 2026.
Download the PDF edition
Take the full Oracle OCI Licensing Guide — the BYOL conversion math, decision matrix, and Universal Credits negotiation levers — as a shareable PDF for your cloud steering committee.
Request the PDF & a briefing →Keep building your OCI position
Free weekly Oracle briefing
Audit alerts, OCI and Universal Credits pricing intelligence, and negotiation tactics — from former Oracle insiders.
Don't let Oracle size your OCI commitment
Get an independent, buyer-side read on your OCI options — BYOL, license-included, and the right Universal Credits commit — before you sign. We model every path against your real entitlements.