How BYOL works on OCI, which products qualify, OCPU and vCPU conversion rules, Database and Middleware BYOL mechanics, when Licence Included beats BYOL, Support Rewards and cost benefits, compliance requirements, migration planning, cost forecasting, and the optimisation framework that maximises cloud ROI.
Comprehensive Oracle BYOL guide. Part of the Oracle OCI/Cloud pillar. See also: BYOL vs Licence Included Cost Comparison · CIO Playbook: OCI & BYOL Strategy · OCI Pricing and Oracle Licensing · Managing Licences in OCI Environments.
Oracle's Bring Your Own Licence (BYOL) programme allows organisations to apply existing perpetual Oracle licences to Oracle Cloud Infrastructure (OCI), avoiding the higher Licence Included pricing that bundles software licence fees into the cloud service cost. When applied correctly, BYOL can reduce OCI database and middleware costs by 40 to 70% compared to Licence Included pricing.
However, BYOL introduces significant compliance complexity. The organisation remains responsible for ensuring that every cloud deployment has sufficient licences, that OCPU-to-licence mapping follows Oracle's conversion rules, that edition and option entitlements match what is deployed, and that licences are not double-counted between on-premises and cloud environments. Oracle audits routinely check BYOL deployments. Misconfigurations can trigger true-up demands at full list price.
| BYOL Dimension | Benefit | Risk | Key Rule |
|---|---|---|---|
| Cost reduction | 40 to 70% lower OCI costs vs Licence Included | Only saves money if licences are correctly mapped | Savings apply only to eligible products (Database, selected middleware) |
| OCPU conversion | 1 OCPU = 1 processor licence (clear mapping) | Over-provisioning OCPUs consumes more licences than available | 2 vCPUs = 1 OCPU = 1 processor licence |
| Licence compliance | Reuses existing investment, no new licence purchase | Customer responsible for compliance; Oracle audits BYOL | Must have active support on licences used for BYOL |
| Edition matching | Carry over exact edition entitlements to cloud | Using EE features with SE licence = violation | Database options/packs require separate BYOL entitlement |
| Support Rewards | OCI spend generates credits toward on-prem support | Credits are modest; do not eliminate support obligation | Requires active OCI consumption and eligible support contracts |
BYOL is Oracle's mechanism for allowing customers to reuse perpetual on-premises licences in OCI cloud environments. Instead of paying for both the software licence and cloud infrastructure through Licence Included pricing, the customer brings their existing licence and pays only for the infrastructure component. The result: significantly lower hourly and monthly OCI costs.
| Product Category | Key Products | BYOL Eligible? | Licence Metric | Notes |
|---|---|---|---|---|
| Oracle Database | Enterprise Edition (EE) | Yes | Processor or NUP | Most common BYOL product; includes DBCS and Autonomous |
| Oracle Database | Standard Edition 2 (SE2) | Yes | NUP (per server) | Subject to SE2 socket/OCPU limits |
| Database Options | Diagnostics, Tuning, Advanced Security, etc. | Yes (if separately licensed) | Same as base DB | Must BYOL each option separately; unlicensed = violation |
| Middleware | WebLogic Server | Yes | Processor | Covers OCI Compute VMs and marketplace images |
| Middleware | SOA Suite, OBIEE, ODI | Case-by-case | Processor | Verify eligibility per product before migration |
| Applications | EBS, PeopleSoft, JDE | Generally no | Varies | Application licensing follows separate rules; verify per product |
Understanding OCI's compute unit mapping is essential for correct BYOL licence counting. Oracle uses OCPUs and vCPUs as the basis for cloud resource allocation, and each maps to licence requirements in a specific way.
| Compute Unit | Definition | Licence Equivalence | Key Rule |
|---|---|---|---|
| OCPU | One physical CPU core with hyperthreading | 1 OCPU = 1 Processor licence | Standard mapping for most Oracle products |
| vCPU | One hardware thread (half a physical core) | 2 vCPUs = 1 Processor licence | OCI flexible shapes use vCPU; divide by 2 |
| Bare Metal | Dedicated physical server (all cores) | All OCPUs require licences | Cannot sub-license a portion of bare metal |
| VM.Standard shapes | Fixed OCPU allocation per shape | Licence count = OCPU count of shape | Scaling to larger shape increases requirement |
| VM.Flexible shapes | Customer selects OCPU count (1 to 64+) | Licence count = selected OCPU count | Best for right-sizing to minimise licence use |
| Exadata Cloud Service | Dedicated Exadata infrastructure in OCI | OCPU-based licensing per database | Exadata has specific BYOL rules; verify per deployment |
Worked example: Database Enterprise Edition BYOL. An organisation deploys Oracle Database EE on an OCI VM with 4 OCPUs. Under BYOL, this requires 4 Processor licences. If they also enable the Diagnostics Pack, they need 4 additional Diagnostics Pack Processor licences. If the VM is scaled up to 8 OCPUs, the requirement doubles to 8 Processor licences for each product.
Oracle Database is the most common and highest-value BYOL workload on OCI. Database licences are expensive (Database Enterprise Edition lists at $47,500 per Processor), making the savings from BYOL vs Licence Included substantial.
| Deployment Option | BYOL Model | Licence Requirement | Key Consideration |
|---|---|---|---|
| OCI Compute VM (self-managed) | Customer installs and manages Oracle DB on OCI VM | 1 Processor licence per OCPU | Full DBA control; customer responsible for patching |
| Database Cloud Service (DBCS) | Oracle-managed database; select BYOL at provisioning | 1 Processor licence per OCPU | Oracle handles management; licence cost removed from price |
| Autonomous Database | Fully managed autonomous; BYOL option available | 1 Processor licence per OCPU | Highest automation; verify edition/options match entitlements |
| Exadata Cloud Service | Dedicated Exadata infrastructure with BYOL | OCPU-based per database | Exadata-specific rules; significant BYOL savings for large deployments |
| Database Options/Packs | Each option requires separate BYOL entitlement | Same Processor count as base DB | Diagnostics, Tuning, Advanced Security, RAC: each needs own licence |
The options trap. The most common BYOL compliance issue with databases is deploying features that require separately licensed options (Diagnostics Pack, Tuning Pack, Advanced Security, Active Data Guard, RAC) without holding BYOL entitlements for those options. Oracle's audit scripts specifically detect option usage. Every option enabled on an OCI database instance must have a corresponding BYOL licence.
Oracle middleware products, particularly WebLogic Server and SOA Suite, are also eligible for BYOL on OCI, providing cost savings for organisations migrating enterprise Java applications and integration workloads to the cloud.
| Middleware Product | BYOL Licence Metric | OCI Deployment | Key BYOL Rule |
|---|---|---|---|
| WebLogic Server | Processor (1 per OCPU) | OCI Compute VM, marketplace image, or WebLogic Cloud Service | Clustered: licence every OCPU across all nodes |
| SOA Suite | Processor (1 per OCPU) | OCI Compute VM | All components (BPEL, Mediator) require licensing if deployed |
| Business Intelligence (OBIEE/OAS) | Processor or NUP | OCI Compute VM | Verify BYOL eligibility per specific BI product version |
| Data Integrator (ODI) | Processor or NUP | OCI Compute VM | Verify product-specific BYOL support before migration |
| Identity and Access Management | Processor or NUP | OCI Compute VM | Complex component licensing; verify each component |
Middleware clustering consideration. When deploying WebLogic or SOA Suite in a clustered configuration across multiple OCI VMs for high availability, every OCPU across every cluster member requires licensing. A 3-node WebLogic cluster with 4 OCPUs per node requires 12 Processor licences, not 4. This is the most common middleware BYOL under-licensing scenario.
BYOL is not always the optimal choice. Oracle offers Licence Included pricing where the software licence is bundled into the cloud service cost. In some scenarios, Licence Included is simpler, cheaper, or strategically better.
| Scenario | BYOL Advantage | Licence Included Advantage | Recommendation |
|---|---|---|---|
| Large stable production DB with existing EE licences | 40 to 70% lower OCI cost; reuses existing investment | n/a | BYOL: clear cost winner |
| Short-term project without spare licences | n/a | No licence purchase needed; pay only for duration | Licence Included: avoids permanent cost |
| Dev/test with fluctuating capacity | Lower hourly rate if licences available | Simpler management; no licence tracking | Depends on licence availability |
| Large licence surplus (post-consolidation) | Maximises value of sunk licence costs | n/a | BYOL: turns idle licences into savings |
| Elastic/burst workloads beyond licence capacity | BYOL for baseline | Covers any scale without constraints | Hybrid: BYOL base, LI for burst |
| Oracle Cloud@Customer deployment | BYOL available with C@C rules | LI option also available | Cost-compare per workload |
Oracle incentivises BYOL adoption through OCI pricing structures and programmes like Support Rewards that create additional financial benefits beyond the direct licence cost savings. As OCI spending increases, Oracle applies credits that reduce the annual support bill for on-premises licences. This creates a compounding benefit: BYOL reduces OCI service cost, and OCI consumption reduces on-premises support cost.
| Cost Component | BYOL Model | Licence Included Model | BYOL Saving |
|---|---|---|---|
| DBCS (4 OCPU) hourly rate | ~$0.34/hour (infrastructure only) | ~$1.02/hour (infrastructure + licence) | ~67% lower hourly cost |
| Annual cost (24x7 production) | ~$2,978/month | ~$8,935/month | ~$71,500/year per instance |
| On-prem support (continuing) | ~$41,800/year (4 DB EE Processor licences) | $0 (no on-prem licences) | BYOL requires ongoing support |
| Net annual saving per instance | ~$29,700/year net ($71,500 OCI saving less $41,800 continuing support) | ||
BYOL shifts compliance responsibility to the customer. Oracle trusts that organisations deploying under BYOL have sufficient licences, but verifies through audits. The most common BYOL audit findings involve over-provisioned OCPUs, unlicensed database options, and licences used simultaneously on-premises and in OCI.
| Compliance Risk | How It Happens | Typical Exposure | Prevention |
|---|---|---|---|
| Over-provisioned OCPUs | VM scaled to 8 OCPUs but only 4 Processor licences held | $190K+ per excess OCPU (DB EE list) | Match OCPU count exactly to licences; use flexible shapes |
| Unlicensed database options | Diagnostics or Tuning Pack enabled without BYOL entitlement | $100K to $500K+ per option | Disable unused options; BYOL each option separately |
| Dual deployment | Same licences counted for on-prem server and OCI instance | Full list-price true-up for unlicensed environment | Decommission on-prem before OCI deployment |
| Edition mismatch | Deploying EE features on SE2-covered instance | $47,500/Processor upgrade SE2 to EE | Verify edition at provisioning; lock down EE-only features |
| Expired support | BYOL licences with lapsed support contracts | 150%+ reinstatement fees + BYOL invalidation | Maintain active support; track renewal dates |
Migrating to OCI with BYOL requires licence-aware planning that goes beyond standard cloud migration methodology. The licence dimension adds sequencing constraints, entitlement validation requirements, and cost modelling that must be integrated into the migration programme.
Discovery. Complete inventory of all Oracle licences: products, editions, quantities, metrics, support status, and current deployment locations. Output: licence inventory with BYOL eligibility assessment per product.
Workload assessment. Map each target workload to OCI compute shapes. Calculate OCPU requirements. Identify licence gaps. Output: workload-to-OCI mapping with licence requirements per instance.
BYOL vs LI decision. For each workload, compare BYOL cost (OCI infra + continuing support) vs Licence Included cost. Output: per-workload recommendation with cost justification.
Licence sequencing. Plan migration order to reuse licences: decommission on-prem server, free licence, apply to OCI instance. Output: migration sequence that avoids dual-deployment compliance gaps.
Support alignment. Align OCI go-live dates with Oracle support renewal cycles. Adjust on-prem support contracts as workloads migrate. Output: support cost reduction plan as on-prem footprint decreases.
Provisioning. Deploy OCI instances with BYOL option selected. Verify OCPU allocation matches licence entitlement. Output: BYOL-compliant OCI deployments with documented licence allocation.
Validation. Post-migration compliance check: verify all BYOL instances have sufficient licences, no dual deployment, no unlicensed options. Output: post-migration compliance report with clean BYOL state.
For organisations managing complex Oracle BYOL deployments across OCI and on-premises environments, Redress Compliance provides independent advisory through our Oracle License Management Services, Oracle Audit Defense Service, and Oracle Contract Negotiation Service.
Bring Your Own Licence (BYOL) is Oracle's programme that allows organisations to apply existing perpetual Oracle licences to Oracle Cloud Infrastructure deployments. Instead of paying Licence Included pricing, BYOL customers pay only for cloud infrastructure, reducing OCI costs by 40 to 70% for eligible products.
The primary BYOL-eligible products are Oracle Database (Enterprise Edition and Standard Edition 2), Oracle WebLogic Server, Oracle SOA Suite, and selected other middleware products. Database options and packs are also BYOL-eligible but require separate licence entitlements. Application products (EBS, PeopleSoft) generally follow different licensing rules.
On OCI, 1 OCPU equals 1 physical CPU core with hyperthreading (2 vCPUs). For BYOL, 1 OCPU requires 1 Processor licence for most Oracle products. If you use NUP licensing, the minimum NUP per Processor requirements still apply (25 NUP per Processor for Database EE, 10 for middleware). Flexible VM shapes allow you to select exact OCPU counts to match your available licences.
Yes. Oracle Autonomous Database offers a BYOL pricing option where you bring existing Database Enterprise Edition licences. The OCPU-to-licence conversion follows the same 1:1 rule. Autonomous Database uses Enterprise Edition with specific features enabled. Ensure your BYOL entitlements cover the features in use.
Over-provisioning creates a compliance gap. If an OCI instance uses 8 OCPUs but you only hold 4 Processor licences, the additional 4 OCPUs are unlicensed. Oracle can identify this during an audit and demand true-up at list price, approximately $190,000 per excess OCPU for Database Enterprise Edition, plus back-support fees.
Generally, no. Oracle's standard policy requires that a licence be used in one location at a time unless the contract specifically permits dual deployment. If migrating from on-premises to OCI, decommission the on-prem instance before (or simultaneously with) the OCI deployment to avoid dual-counting.
Licence Included is typically better for short-term or temporary workloads (where purchasing a perpetual licence is not cost-justified), when the organisation has no spare licences, for fully managed services like Autonomous Database where simplicity is prioritised, or for burst capacity that exceeds the organisation's BYOL licence count.
Support Rewards is Oracle's programme that provides credits toward on-premises Oracle support costs based on OCI consumption. As the organisation increases its OCI spending, Oracle applies credits that reduce the annual on-premises support bill. This creates additional financial benefit on top of the direct BYOL cost savings.
Maintain a real-time inventory mapping each OCI BYOL instance to its specific licence source. Track OCPU consumption against licence entitlement continuously. Verify database option entitlements quarterly. Prevent dual deployment by coordinating on-prem decommissioning with OCI provisioning. Conduct quarterly compliance reviews covering all BYOL deployments.
Yes. BYOL requires active Oracle support on the licences being used in OCI. You continue paying the annual support fee (approximately 22% of the licence value) for those licences. However, the OCI infrastructure cost is significantly lower under BYOL, and Support Rewards credits may partially offset the on-premises support cost.
Start with a complete Oracle licence inventory identifying BYOL-eligible products and available quantities. Map each target workload to OCI compute shapes to determine OCPU requirements. Compare BYOL vs Licence Included costs per workload. Plan migration sequencing to reuse licences (decommission on-prem, then deploy to OCI). Align with support renewal cycles to avoid double-payment.
BYOL to AWS and Azure follows different rules than BYOL to OCI. Oracle's licensing policy for authorised cloud environments requires dedicated hosts or specific instance types on AWS/Azure. The OCPU conversion rules differ, and Oracle's partitioning policies may require licensing the full physical host.
The three most common findings are: over-provisioned OCPUs exceeding BYOL licence count, unlicensed database options or packs enabled without separate BYOL entitlement, and dual deployment where the same licences are counted on-premises and in OCI simultaneously. Each can trigger true-up demands at Oracle's full list price.
Oracle RAC on OCI requires licensing every OCPU across every node in the cluster. A 2-node RAC cluster with 4 OCPUs per node requires 8 Processor licences. Additionally, RAC itself requires a separate BYOL entitlement (Oracle RAC option licence). The same per-OCPU requirement applies to the RAC option licence as to the base Database licence.