Oracle BYOL vs Licence Included on OCI and Exadata Cloud@Customer: A Cost Comparison Guide

Understanding the Two Models

Before comparing costs, it is important to establish precisely what each model means in the context of Oracle Cloud Infrastructure and Exadata Cloud at Customer. The definitions are simple but have significant implications for how costs are structured and how compliance is managed.

Licence Included

Licence Included means you pay Oracle a single per-OCPU hourly or monthly rate that covers both the cloud infrastructure (compute, storage, networking) and the Oracle Database software licence. You do not need to hold any perpetual Oracle Database licences, and you are not responsible for managing licence compliance against a separate on-premises inventory. The rate is higher than BYOL because it embeds the software licence cost. Licence Included simplifies procurement and compliance management — there is one supplier, one bill, and no separate licence tracking requirement.

Licence Included is available for Oracle Database Enterprise Edition, Oracle Database Standard Edition 2, Oracle Autonomous Database, Oracle Exadata Cloud at Customer, and Oracle Database Cloud at Customer, among other services. New users, growing organisations and workloads that require temporary capacity find Licence Included attractive because there is no up-front perpetual licence investment.

Bring Your Own License (BYOL)

BYOL means you supply existing perpetual Oracle Database licences (with active Oracle support) to cover the software component of your cloud deployment. Oracle charges you a reduced rate covering only the infrastructure — you are not paying Oracle for the software licence because you already own it. The BYOL rate is materially lower than the Licence Included rate for the same service, creating the cost savings that make BYOL attractive for organisations with substantial perpetual licence inventories.

BYOL requires that your perpetual licences have active Oracle support at the standard rate of approximately 22% of net licence fees annually. Oracle increases this support fee by 8% per year. The ongoing support cost of maintaining BYOL eligibility must be factored into the economics — it is not free to keep perpetual licences on support.

Pricing Structure: OCI Database Services

Understanding the price differential between BYOL and Licence Included requires knowledge of how Oracle structures its OCI database pricing. Prices below are indicative at list rates and subject to negotiation — enterprise customers typically pay 30 to 50% below list price for OCI Universal Credits.

Oracle Database Enterprise Edition on OCI

For Oracle Database Enterprise Edition on standard OCI compute (Exadata Database Service on Dedicated Infrastructure), the Licence Included rate is approximately $1.34 per OCPU per hour. The BYOL rate for the same service is approximately $0.32 per OCPU per hour. The difference of $1.02 per OCPU per hour represents the embedded licence cost. Over 720 hours per month (30-day month) at 50 OCPUs, the monthly cost difference is $36,720 — confirming the $36,700 figure cited in the introduction to this article.

The BYOL rate at $0.32 per OCPU per hour represents approximately 24% of the Licence Included rate — which is why BYOL is described as providing approximately 75% savings on the Licence Included price. This ratio holds broadly across Oracle's database cloud services, though the absolute rates vary by service type and region.

Oracle Autonomous Database BYOL and Licence Included

For Oracle Autonomous Database (Autonomous Transaction Processing, Autonomous Data Warehouse, Autonomous JSON Database), the Licence Included rate is approximately $0.3480 per OCPU per hour for ATP, and the BYOL rate is approximately $0.0870 per OCPU per hour — again representing approximately 25% of the Licence Included rate. Autonomous Database BYOL applies one Oracle Database Enterprise Edition Processor licence per 2 OCPUs, the same mapping as standard Oracle Database services on OCI.

Exadata Cloud at Customer Pricing

Exadata Cloud at Customer (ExaCC) operates on Oracle's subscription model, with pricing structured as a combination of base infrastructure charges and OCPU consumption charges. For ExaCC, the BYOL rate is roughly one-quarter of the Licence Included rate — consistent with the broader OCI pattern. For a 16-OCPU deployment, indicative monthly costs are approximately $12,000 per month on BYOL (including approximately $8,000 in infrastructure and $4,000 in OCPU usage) versus approximately $23,000 per month on Licence Included. The $11,000 per month difference compounds significantly over the deployment term.

The Real Financial Model: Including Support Costs

A BYOL analysis that only counts the infrastructure rate differential is incomplete. BYOL requires maintaining active Oracle support on the perpetual licences being applied to the cloud deployment. This support cost must be included in the total BYOL economics to produce an accurate comparison.

Support Cost Calculation for BYOL

For a 50-OCPU OCI deployment using BYOL, you need 25 Oracle Database Enterprise Edition Processor licences (one licence covers two OCPUs on OCI). At a typical net licence value of $120,000 per processor licence (after enterprise discount from the $460,000 list price), the net value of 25 licences is $3,000,000. Annual support at 22% is $660,000 in year one. With 8% annual escalation, year-two support is $712,800, year three is $769,824, year four is $831,410, and year five is $897,923. Total five-year support cost: approximately $3,872,000.

This support cost exists regardless of whether the licences are deployed on-premises, on OCI BYOL, or elsewhere. It is an ongoing Oracle relationship cost, not an incremental BYOL cost. When assessing BYOL economics, the relevant question is whether the licences are already held and supported for other purposes — if they are, their support cost is sunk and should not be charged against the BYOL saving. If licences must be purchased and put on support specifically to enable BYOL, the licence acquisition and support cost must be compared against the alternative of simply using Licence Included.

The Break-Even Analysis for New Licence Purchases

If an organisation needs to purchase new Oracle Database licences specifically to enable BYOL, the economics are less favourable than for organisations with existing perpetual inventory. For a 50-OCPU deployment, purchasing 25 Oracle Database Enterprise Edition Processor licences at $3,000,000 net and paying $660,000 in year-one support creates a total year-one cost of approximately $3,660,000 — against which the BYOL saving of approximately $440,640 per year ($36,720 per month × 12) must be applied. The break-even point where total BYOL costs equal the total Licence Included cost is approximately eight to nine years, depending on assumptions about OCI rate changes and support escalation.

This analysis confirms the core BYOL principle: BYOL produces the best economics for organisations that already hold perpetual Oracle licences with active support, where those licences are being migrated from on-premises deployments to the cloud rather than held redundantly on-premises. Purchasing new licences solely to enable BYOL rarely produces a favourable return for less than a ten-year deployment horizon.

Mixed Models: BYOL and Licence Included in the Same Environment

One of the most useful but underutilised aspects of OCI and Exadata Cloud at Customer is the ability to run BYOL and Licence Included deployments within the same overall environment, even in the same organisation. Oracle does not permit BYOL and Licence Included to be mixed on the same instance of a service — but different databases, different Pluggable Databases (PDBs) or different services within the same physical infrastructure can use different models.

In practice, this means an organisation running Exadata Cloud at Customer for production Oracle Database can licence production databases on BYOL (using their existing perpetual licences) and use Licence Included for development and testing databases where the usage is sporadic, unpredictable or where the organisation does not have sufficient perpetual licences to cover all environments. This hybrid approach optimises cost by applying BYOL to steady-state production workloads and Licence Included to variable non-production workloads.

When Licence Included Makes More Sense

Despite the apparent cost advantage of BYOL, Licence Included is the better choice in several scenarios. For organisations with no existing perpetual Oracle Database inventory, Licence Included eliminates the need for a capital-intensive licence purchase and the associated support obligations. For short-term projects, proof of concept deployments and temporary capacity spikes, Licence Included provides clean pay-as-you-go economics without the overhead of licence management. For new Oracle Database features and options that are not already licensed in the perpetual estate, Licence Included allows access to capabilities that BYOL does not cover. And for development and test environments where Oracle Database is used intermittently, Licence Included avoids committing perpetual licences to non-production workloads that cannot be cost-justified against the licence investment.

Exadata Cloud at Customer vs OCI: BYOL Mechanics

Exadata Cloud at Customer and standard OCI operate on the same OCI platform but have different physical architectures. This affects BYOL compliance in specific ways.

ExaCC Specific Considerations

Exadata Cloud at Customer is physically deployed at the customer's data centre, on Oracle-owned and Oracle-managed hardware that sits inside the customer's facility. The licensing model mirrors OCI — Oracle Database licences apply at the same 1:2 Processor-to-OCPU ratio, and support costs follow the same structure. However, ExaCC's on-premises physical location creates additional compliance considerations. Oracle requires active Oracle support for BYOL on ExaCC. Critically, Oracle will not allow third-party support providers to patch Exadata systems, making the requirement for active Oracle support both a BYOL eligibility condition and a practical system management requirement — ExaCC cannot function without Oracle's quarterly patching infrastructure, which requires active Oracle support.

Flexible OCPU Scaling and BYOL

Both OCI and ExaCC allow OCPU scaling — organisations can increase or decrease the number of active OCPUs up to the physical capacity of their deployment. This flexibility requires careful BYOL management: scaling up OCPUs on a BYOL deployment increases the number of perpetual licences required to maintain compliance. Every two additional OCPUs activated on a BYOL Oracle Database Enterprise Edition deployment requires one additional Processor licence. Organisations that scale OCPUs dynamically must have a process for verifying licence coverage before activation, not after.

Support Rewards: The OCI BYOL Multiplier

OCI's Support Rewards programme creates an additional financial benefit that applies to BYOL deployments and is available only on OCI (not on AWS, Azure or GCP). For every dollar of qualifying OCI consumption, Oracle credits 25 cents (or 33 cents for ULA customers) against Oracle support renewal invoices. This support credit applies to BYOL services under the Universal Credits Model rate card.

For a 50-OCPU BYOL deployment generating approximately $11,520 per month in OCI consumption ($0.32/OCPU/hr × 50 × 720 hrs), standard customers earn approximately $2,880 per month in Support Rewards credits, or $34,560 per year. ULA customers earn $3,810 per month, or $45,720 per year. These credits directly reduce the ongoing Oracle support cost that BYOL requires — further improving the BYOL economics for OCI deployments relative to on-premises equivalents.

On Exadata Cloud at Customer, Support Rewards also apply to eligible consumption charges. The specific rules for ExaCC Support Rewards should be confirmed with Oracle as part of the commercial negotiation, as ExaCC pricing structures can include fixed infrastructure components that may not generate rewards credits in the same way as variable OCPU consumption.

Active Support Requirement and the 8% Escalation Impact

Every perpetual Oracle licence used for BYOL must have active, current Oracle support. Oracle support fees are calculated at approximately 22% of the net licence price actually paid — the discounted price, not the list price. Oracle increases support fees by 8% per year on all technology licences, including Oracle Database. This escalation is contractual and is embedded in Oracle's standard support agreement terms — it is not discretionary.

The 8% annual escalation means that the support cost of maintaining BYOL eligibility grows every year. An organisation paying $660,000 in year-one support for a 25-licence BYOL portfolio pays $897,923 in year-five support — a 36% increase over five years. When modelling BYOL economics over a multi-year cloud deployment, this escalation must be explicitly included. Financial models that use a flat annual support figure will underestimate the cost of BYOL by 15 to 20% over a five-year horizon.

Decision Framework: Choosing Between BYOL and Licence Included

The following framework guides the BYOL vs Licence Included decision across the key scenarios that arise in practice.

Scenario 1: Migration of Existing On-Premises Workloads

If you are migrating existing Oracle Database workloads from on-premises infrastructure to OCI or ExaCC, and your existing on-premises licences will be retired as part of the migration, BYOL is almost certainly the right choice. The perpetual licences are already held and supported. The support cost is being paid regardless. Migrating to BYOL converts a sunk support cost into a BYOL enabler at no incremental licence cost. The OCI infrastructure savings relative to Licence Included are material and immediate.

Scenario 2: Net-New Cloud Deployments Without Existing Licences

If you are deploying Oracle Database in the cloud for the first time, with no existing perpetual inventory to draw on, Licence Included is typically the right starting point. Purchasing perpetual licences to enable BYOL requires eight to ten years to break even, which is a deployment horizon that most cloud-native projects cannot commit to. Start with Licence Included, accumulate cloud spending, and reassess BYOL economics as the deployment grows and matures.

Scenario 3: Hybrid On-Premises and Cloud Deployment

If you are running Oracle Database both on-premises and on OCI or ExaCC simultaneously, the correct BYOL position depends on whether your total perpetual licence inventory is sufficient to cover both deployments. Apply BYOL to cloud deployments only for the licence quantity that is not simultaneously required on-premises. Do not double-count licences across on-premises and cloud environments.

Scenario 4: ULA Certification Planning

Organisations approaching ULA certification should consider their BYOL deployment capacity as part of the certification decision. Certifying a higher licence quantity than current on-premises deployment (within the bounds of actual historical usage) provides a larger perpetual BYOL inventory post-certification. The ULA certification quantity decision is one of the most consequential Oracle licence decisions an organisation makes — our Oracle licensing advisory specialists model this explicitly, and its interaction with future BYOL economics should be explicitly modelled.

Scenario 5: Development and Test Environments

For development, test and staging environments that run Oracle Database on OCI or ExaCC, Licence Included is typically preferred unless you have a large surplus of perpetual licences available. The sporadic usage patterns of non-production environments reduce the BYOL saving per unit time, and the compliance management overhead of tracking BYOL licence allocation across multiple non-production environments can negate the economic benefit.

Compliance Requirements and Audit Considerations

BYOL deployments on OCI and Exadata Cloud at Customer are within Oracle LMS audit scope. The following compliance obligations must be actively managed.

Active Support Verification

Before any BYOL deployment, verify the support status of every perpetual licence being applied to the cloud via Oracle's Customer Support Identifier (CSI) system. Support status is the primary BYOL eligibility check, and it must be verified at the time of deployment, not assumed to be current based on prior experience.

Licence Count Monitoring

Monitor OCPU usage against available BYOL licence inventory continuously. OCPU scaling events — both deliberate administrator actions and automatic scaling triggered by workload management — must be tracked against the licence position. OCI's Licence Manager service supports BYOL tracking on OCI and should be configured for all BYOL deployments.

Third-Party Support Incompatibility

Organisations that use third-party Oracle support (Rimini Street, Spinnaker, or equivalent) for some Oracle Database licences and Oracle support for others must ensure that the BYOL cloud licences are exclusively under Oracle support. Applying third-party-supported licences to OCI BYOL is a violation of both the BYOL conditions and, typically, the Oracle support agreement terms.

On-Premises to Cloud Licence Reallocation

When Oracle Database workloads are migrated from on-premises to OCI BYOL, the on-premises licence obligation ceases once the on-premises software is decommissioned. Until decommissioning is complete, both the on-premises and cloud deployments must be covered by separate licence quantities. Running the same licence simultaneously on-premises and in the cloud — even briefly during a migration window — is a compliance gap if the licence quantity does not cover both positions.

Negotiating BYOL and OCI Commitments

Both BYOL economics and OCI infrastructure costs are negotiable in the context of Oracle commercial discussions. Oracle's fiscal year ends 31 May, and the Q4 window (March to May) is when Oracle's field teams are most motivated to close large deals.

For organisations considering significant OCI deployments under BYOL, the Q4 window offers the best conditions for negotiating annual OCI commit contracts at below-list UCM rates. A larger OCI commit generates more Support Rewards credits (at 25% for standard customers, 33% for ULA holders), which reduce the ongoing Oracle support cost that BYOL requires. Structuring a Q4 OCI commit deal that maximises Support Rewards against existing support obligations is one of the most financially effective Oracle commercial strategies available to large Oracle customers in 2025 and 2026.

The combination of below-list OCI pricing (through negotiated UCM discount), BYOL-reduced cloud costs (at 25% of the Licence Included rate), and Support Rewards credits (at 25% or 33% of OCI spend) creates a compounding cost advantage for Oracle customers that approach OCI commercially rather than accepting Oracle's standard rate card.