2 OCPU
Covered per EE processor licence under BYOL (Oracle OCI BYOL policy, 2026)
Oracle OCI licensing is the set of rules governing how on-premises Oracle licences apply to Oracle Cloud Infrastructure — through Bring Your Own License (BYOL), License-Included rates, Universal Credits, and Support Rewards. This 2026 guide sets out the BYOL conversion ratios, the License-Included versus BYOL cost math, and the traps that turn an OCI migration into fresh audit exposure.
Not affiliated with Oracle Corporation.
Home › Oracle Cloud Licensing › White Papers › Oracle OCI Licensing Guide 2026
Oracle OCI licensing gives you two paths: License-Included, where the OCI rate bundles the software licence, or BYOL, where you apply owned licences at roughly 75% off the License-Included database rate. Under BYOL, one Database Enterprise Edition processor licence covers 2 OCPUs. BYOL wins for steady, supported workloads; License-Included wins for short or bursty ones. Either way you still owe 22% support on the BYOL licences and must not double-count a licence already consumed on-premises.
An OCI licensing decision is won across finance, cloud architecture and procurement — and lost when any one of them treats the OCI console rate as the real price. Each owns a different lever.
Under OCI BYOL, one Oracle Database Enterprise Edition processor licence entitles you to 2 OCPUs of Oracle Database on OCI. You apply licences you already own to OCI database services at the BYOL rate — about 75% below the License-Included rate — instead of paying for the bundled licence again. The conversion ratio is the core mechanic: size your OCPUs to your owned processor count, not the other way round.
An OCPU (Oracle Compute Unit) is OCI's unit of compute equal to one physical core with hyper-threading. Because BYOL maps 2 OCPUs to a single EE processor licence, a workload that needs 8 OCPUs of database consumes 4 EE processor licences from your entitlement. Get the ratio wrong and you either strand licences or, worse, deploy beyond what you own. Our Oracle cloud licensing guide details the per-product OCPU bands.
BYOL is cheaper than License-Included for steady, long-running Oracle Database workloads, because the BYOL compute rate runs roughly 75% below License-Included. License-Included wins for short, bursty, or temporary workloads, because BYOL still requires you to pay 22% annual support on the underlying licences whether or not the OCI instance is running. The break-even turns on utilisation, not headline rate.
The trap is comparing the BYOL compute rate to License-Included and declaring victory. The honest comparison adds the on-prem support stream you keep paying on the BYOL licences. For a database running 24×7 the BYOL economics are decisive; for a dev/test instance spun up a few hours a week, License-Included with no support obligation usually wins. Our Oracle cloud advisory team builds the break-even per workload.
Oracle Support Rewards is a program that returns a credit against your on-premises Oracle technology support bill for every dollar of OCI spend. The standard rate is $0.25 per $1 of eligible OCI consumption; customers with an active Unlimited License Agreement (ULA) earn $0.33. For a buyer spending $4M a year on OCI, that is $1M–$1.32M offsetting the support invoice — a structural rebate many enterprises under-claim.
Support Rewards quietly reframes the OCI commit: part of every OCI dollar comes back as a reduction in the support line you would pay regardless. It accrues on eligible OCI services — Compute, Storage, Networking, Database and more — and is tracked in the OCI console. Buyers who fold Support Rewards into the renewal math, rather than ignoring it, change the whole cloud-versus-on-prem calculus. See our Oracle support reduction practice.
OCI is sold on Universal Credits — a prepaid pool, billed as an Annual Universal Credit commit or Pay-As-You-Go, that draws down across any OCI service at the published rate. The published rate is a list price, not a floor: enterprise commits routinely net 30–60% off through discounted credit pricing, and larger multi-year commits go deeper. The discount, not the console rate, is what you actually pay.
Universal Credits give flexibility — one commit spans Compute, Database, Autonomous and storage — but the commit size and discount are negotiable line items, not fixed. Oracle will trade a deeper discount for a larger or longer commit, and will bundle the OCI commit with an on-prem renewal to manufacture leverage. Keeping the two negotiations separate, and benchmarking the credit discount independently, is how buyers avoid overcommitting. Our OCI Universal Credits Playbook details the commit mechanics.
The biggest OCI licensing trap is double-counting: applying a single on-premises licence to both your data centre and an OCI BYOL instance simultaneously. One licence covers one deployment at a time. When a workload is migrated to OCI BYOL but the on-prem instance is left running "just in case," the same entitlement is claimed twice — a finding Oracle's License Management Services surfaces immediately in a cloud-era audit.
The discipline is simple but rarely enforced: decommission or formally re-allocate the on-prem deployment before the licence backs an OCI instance, and keep evidence of the reallocation. The same applies to disaster-recovery and standby nodes, which carry their own licensing rules in the cloud. Defending these findings after the fact is far costlier than tagging entitlement correctly up front; our Oracle audit defense team has closed cloud-migration audit claims for a fraction of Oracle's opening number — see our case studies.
No. OCI BYOL uses the 2-OCPU-per-EE-processor ratio, but Oracle's authorized-cloud policy for AWS and Azure counts licences differently — historically 2 vCPUs per processor licence where hyper-threading is on. Oracle@Azure and Oracle Database@AWS run Oracle-managed infrastructure with their own BYOL terms. Never assume an OCI conversion ratio transfers to another cloud; the metric changes with the platform.
This matters because multi-cloud estates routinely mis-apply one platform's ratio to another and either over-buy or fall out of compliance. The authorized-cloud document, not a sales conversation, governs AWS and Azure deployments, and Oracle treats its own engineered OCI environment more favourably than third-party clouds. Benchmark each platform separately; our Oracle BYOL on AWS & Azure guide sets out the per-cloud rules.
The single biggest variable is workload utilisation. Steady, supported workloads favour BYOL; short or temporary ones favour License-Included. The two paths can differ by 75% on compute and a full support stream.
24×7 production database · free, supported EE licences on hand · long-running commit · Support Rewards claimed · on-prem instance decommissioned · ~75% off License-Included compute.
Bursty / dev-test / temporary workload · no spare entitlement · want to avoid retained 22% support · short commit · no on-prem instance to migrate · bundled licence priced into the OCI rate.
On OCI the console rate is never the price — the real number is BYOL plus retained support, minus Support Rewards, against a negotiated Universal Credits discount.
| Model | How it works | 2026 economics |
|---|---|---|
| BYOL | Apply owned EE licences (2 OCPU each) | ~75% off License-Included compute; 22% support retained |
| License-Included | OCI rate bundles the software licence | Best for bursty / temporary; no support obligation |
| Universal Credits | Prepaid commit drawn across services | 30–60% off published rate on enterprise commits |
| Support Rewards | Credit vs on-prem support per OCI $ | $0.25–$0.33 per $1 OCI spend |
| Oracle@Azure / @AWS | Oracle-managed on third-party cloud | Separate BYOL terms; do not reuse OCI ratio |
| Lever | Strength | Caution |
|---|---|---|
| BYOL compute rate | ~75% below License-Included for steady workloads | Only real after netting out retained 22% support |
| Support Rewards | 25–33% of OCI spend offsets on-prem support | Accrues only on eligible services; must be actively claimed |
| Universal Credits | Flexible pool across all OCI services | Unused credits expire; over-commitment destroys the discount |
| Entitlement reuse | No need to re-buy licences already owned | Double-counting on-prem and OCI is a top audit finding |
Under OCI BYOL, one Oracle Database Enterprise Edition processor licence covers 2 OCPUs of Oracle Database on OCI. So an 8-OCPU database instance consumes 4 EE processor licences from your entitlement. Standard Edition follows its own OCPU bands. Size OCPUs to your free processor count, and never count a licence already in use on-premises.
No. BYOL compute runs about 75% below License-Included, but you keep paying 22% annual support on the BYOL licences. That makes BYOL decisive for steady, 24×7 workloads and License-Included better for short, bursty, or dev-test workloads where you would rather avoid the retained support obligation. The break-even is driven by utilisation.
Support Rewards returns $0.25 for every $1 of eligible OCI spend, or $0.33 for customers with an active ULA, as a credit against your on-premises Oracle technology support bill. A $4M annual OCI spend yields $1M–$1.32M against the support invoice. It is tracked in the OCI console and must be actively applied at renewal.
The published OCI rate is a list price, not a floor. Enterprise Universal Credits commits routinely net 30–60% off, and larger multi-year commits go deeper. Oracle trades discount for commit size and term, so benchmark the credit price independently and avoid committing to more credits than you can realistically consume before they expire.
Double-counting — applying one on-premises licence to both the data centre and an OCI BYOL instance at the same time. One licence covers one deployment. Leaving the on-prem instance running after migrating to OCI BYOL claims the same entitlement twice, which Oracle's License Management Services flags immediately in a cloud-era audit.
No. OCI BYOL uses 2 OCPUs per EE processor licence, but Oracle's authorized-cloud policy for AWS and Azure counts licences differently — historically 2 vCPUs per processor where hyper-threading is on. Oracle@Azure and Oracle Database@AWS have their own BYOL terms. Always benchmark each platform separately rather than reusing the OCI ratio.
Benchmarks labelled "Oracle Licensing Experts engagement data, 2026" are drawn from our independent, buyer-side advisory work across 600+ Oracle engagements and $1.8B in Oracle spend advised. Conversion ratios, rates and program terms are taken from Oracle's published 2026 materials and corroborated against achieved positions. Primary sources:
No NDA-bound client figures are disclosed. Representative ranges are benchmarks, not quotes.
The Oracle Licensing Experts Advisory Team is an independent, buyer-side Oracle licensing practice staffed by former Oracle insiders. We benchmark cloud commits, defend audits, and negotiate contracts — 100% on the buyer's side, never reselling Oracle. Learn about our team → · Not affiliated with Oracle Corporation.
Take the 2026 Oracle OCI Licensing Guide into your next cloud migration or commit as a PDF.
We model BYOL against License-Included per workload, size your OCPUs to owned entitlement, claim every dollar of Support Rewards, and benchmark the Universal Credits commit — so you migrate without buying twice or walking into a cloud-era audit.
Oracle pricing, audit and negotiation intelligence — monthly, independent, no Oracle spin.