CIOs overseeing Oracle environments must balance legacy on-premises licences with modern cloud subscriptions to optimise cost and agility. This playbook provides a strategic approach for managing Oracle software across hybrid deployments — on-premises, OCI, Cloud@Customer, and Oracle SaaS — covering BYOL, Universal Credits, Support Rewards, workload placement, compliance governance, and negotiation strategy.
Oracle's licensing landscape has evolved from traditional on-premises contracts to a complex mix of on-prem and cloud-based models. On-premises Oracle software (databases, middleware) is typically sold as perpetual licences, measured by processor cores (using Oracle's core factor) or named users. Enterprises pay large upfront fees and ongoing annual support (~20–22% of licence cost) to run software on their hardware indefinitely.
In contrast, Oracle Cloud services use subscription models. OCI charges for compute and database services on an hourly or monthly basis depending on OCPU usage. Oracle Fusion SaaS applications (ERP, HCM) are delivered as cloud subscriptions on a per-user or per-module basis with no on-premises deployment.
Allows organisations to apply existing on-premise Oracle licences to equivalent Oracle Cloud services. Provides licence mobility — customers can move a licence from on-premises to the cloud and back if needed. One Oracle Processor licence covers two OCPUs in OCI, maintaining parity with on-premises.
A pool of cloud credits usable across any OCI services — compute, database, storage, and more. Provides flexibility to scale usage up or down across different services without needing separate fixed subscriptions. Organisations can shift spending between on-premises and cloud as workloads migrate.
Customers earn credits against their on-prem support fees based on OCI usage, effectively reducing support costs by 25% (or 33% for ULA customers) for every dollar spent on Oracle Cloud. This incentivises enterprises to integrate cloud into their Oracle strategy.
Oracle installs cloud infrastructure inside the customer's data centre, but services are billed as cloud subscriptions. Addresses data residency, compliance, and ultra-low latency requirements. BYOL is allowed on Cloud@Customer, meaning clients can apply existing licences to reduce subscription costs.
In a global enterprise, it's common to have a mix of legacy on-prem perpetual licences, OCI VMs and databases, Oracle-managed platforms (Autonomous Database, Cloud@Customer), and SaaS applications (Fusion). Each has different licensing metrics and contracts — physical cores, OCPU hours, user counts. Managing this portfolio requires understanding how these models interact. CIOs must continuously evaluate where each Oracle workload runs best and how to licence it optimally.
| Model | Cost Structure | Pros | Cons | Best For |
|---|---|---|---|---|
| On-Prem Perpetual | Large upfront CapEx + annual support (20–22% of licence cost). Own the rights indefinitely. | Complete control. Cost-efficient long-horizon if fully utilised. No dependency on cloud pricing. | Ties up capital. Requires hardware maintenance. Scaling is slow and expensive. Underused licences become shelfware. | Steady-state 24/7 workloads. Consistent demand. Environment doesn't benefit from cloud elasticity. |
| OCI Licence-Included | Pure OpEx — pay hourly/monthly including software licence in the rate. | No upfront purchase. Ideal for short-term/experimental/variable workloads. Simplified compliance — Oracle ensures licence coverage inherently. | Significantly higher rates than BYOL. No equity — you have no asset when you stop paying. Expensive for long-duration steady usage. | Short-term projects. Seasonal/burst workloads. Organisations lacking existing licences. |
| OCI with BYOL | Existing licence + lower cloud service rate (infrastructure/management fees only). | BYOL rates 80%+ lower than licence-included. Maximises prior investments. Licence mobility — can repatriate on-prem. Lower TCO for multi-year steady workloads. | Requires maintained support contract. Must carefully track usage against entitlements. Only beneficial with spare/transferable licences. | Production systems running 24/7. Heavy existing licence investment. Base-load databases and middleware. |
| Cloud@Customer | Cloud subscription billed for on-prem capacity. Minimum term/capacity commitment typical. | Cloud benefits on-premises. Data locality for regulatory compliance. Parity with OCI. BYOL supported to reduce costs. | Substantial subscription commitment. Large minimum capacity. You commit to OpEx model on-prem. | Regulated/data sovereignty workloads. Latency-critical systems. Organisations wanting cloud model without public cloud. |
| Oracle SaaS (Fusion) | Per-user or per-module subscription. No infrastructure management. | Reduced IT overhead. Always latest version. Simplifies portfolio — fewer products to track. No hardware or patching. | Less customisation flexibility. Retire perpetual licences (lose asset). Must plan timing to avoid paying support + SaaS concurrently. | Mature business process apps. Organisations ready to standardise on cloud. Legacy app upgrade cycles. |
Use each model where it fits best: keep high-performance or sensitive systems on optimised on-prem/Cloud@Customer setups; shift dev/test and elastic workloads to OCI using BYOL + on-demand instances; migrate commoditised business capabilities to SaaS to offload maintenance. Run base-load production databases on reserved OCI instances using BYOL, while using licence-included Autonomous Databases for short-term analytics or burst workloads.
Evaluate each Oracle workload against criteria including performance needs, integration dependencies, customisation, data sensitivity, and regulatory compliance. Maintain a clear decision framework that maps workload characteristics to optimal deployment models.
| Workload Characteristic | Recommended Placement | Licensing Model |
|---|---|---|
| Regulated data / data sovereignty requirements | Cloud@Customer or stay on-prem | BYOL or perpetual on-prem |
| Ultra-low latency with on-site systems | On-premises or Cloud@Customer | Perpetual or C@C subscription |
| Standard workloads with steady 24/7 usage | OCI | BYOL (maximise existing investment) |
| Seasonal, variable, or burst workloads | OCI | Licence-included (on-demand) |
| Development, test, experimental workloads | OCI | Licence-included or Universal Credits |
| Legacy app being phased out | Stay on-prem for now | Maintain existing perpetual |
| Mature business process apps (ERP, HCM) | Evaluate Oracle SaaS (Fusion) | Per-user subscription |
| Older versions / very specific configurations | On-premises | Perpetual on-prem |
Treat your Oracle licences as a portfolio of assets that can be allocated across on-prem and cloud venues. The goal is to ensure every Oracle investment — whether a licence purchase or a cloud subscription dollar — is utilised to the fullest extent.
Map all perpetual licences, cloud subscriptions, and user subscriptions to current usage. Identify underutilised on-prem licences and over-provisioned cloud subscriptions.
If you have underutilised on-prem database licences, leverage BYOL to deploy them in OCI for new workloads instead of buying new licences. Conversely, if you're paying high subscription fees for stable workloads, consider converting to BYOL to cut long-term costs.
Run base production databases on reserved OCI instances using BYOL (benefiting from sunk costs and Support Rewards), while using licence-included Autonomous Databases for short-term analytics or burst workloads.
If the roadmap includes moving systems to SaaS, anticipate how that will free up or change licence needs. A balanced portfolio means maintaining a core of perpetual licences (for negotiating leverage) while steadily increasing cloud subscriptions where they make financial and operational sense.
Regularly adjust entitlements around Oracle contract renewal cycles — drop support for unused products, convert on-premises licences to cloud credits if Oracle offers this option, and renegotiate terms based on shifting usage patterns.
Need help optimising your Oracle hybrid licence portfolio?
Oracle Advisory Services →Make Oracle's incentive programmes work for you. Each Oracle Processor licence you bring to OCI can cover two OCPUs of cloud capacity, and the cloud service rate will be dramatically lower than licence-included.
Use BYOL wherever feasible for consistent workloads. Ensure the licences you bring are equivalent to the cloud service (e.g., Enterprise Edition for an Enterprise DB service) and that you maintain support on them. BYOL cloud service rates can be 80%+ lower than licence-included rates for the same compute capacity — making it the most cost-effective option for heavy, steady use.
Universal Credits let you commit spend to Oracle Cloud in exchange for a discount, then allocate that spend dynamically across OCI services (compute, database, storage, even Cloud@Customer usage) as needed. This flexibility means you can shift workloads or adjust resource levels without being locked into fixed service quotas — valuable when managing a hybrid estate with changing demands.
As you ramp up OCI usage, the credits earned through Support Rewards can significantly offset your on-prem support costs. This essentially gives a discount on continuing to run what must remain on-prem, funded by your cloud adoption. Support Rewards apply to technology licences (database, middleware), not Oracle applications support.
When negotiating with Oracle, seek favourable terms: the ability to transfer cloud credits between Cloud@Customer and OCI, commitments preserving BYOL flexibility, and combined models — for example, negotiate an Oracle ULA for specific products to cover broad on-premises deployment while also securing a pool of universal credits for new cloud projects.
The key is to ensure each Oracle investment — whether a licence purchase or a cloud subscription dollar — is utilised to the fullest extent across your hybrid environment. Factor BYOL, Universal Credits, and Support Rewards into every business case and cost model for moving workloads to OCI or Cloud@Customer.
Hybrid models introduce complexity in tracking usage against entitlements. CIOs should enforce strong governance for licence management and establish a single source of truth for Oracle licence entitlements and deployments.
Use Software Asset Management tools capable of monitoring Oracle usage on-premises (tracking installations, options enabled, CPU counts) and in OCI (BYOL usage declaration, OCPU consumption). Oracle provides tooling in the cloud to declare BYOL usage.
On-prem processor licences use Oracle's core factor table — apply it correctly on physical servers and VMware clusters. In OCI, an OCPU is equivalent to one physical core (two vCPUs). Oracle's policy: two vCPUs per licence for Enterprise Edition databases.
Oracle allows moving licences back and forth between on-prem and cloud, but not double usage. If you declare 10 licences for BYOL in OCI, those 10 processors should not be used concurrently on-premises. Track which licences are deployed where.
Audit your OCI tenancy to list all BYOL instances and verify sufficient allocated licences. Audit on-premises to ensure shifted licences have corresponding decommissioned or relicensed installations. Do this quarterly.
Prevent use of database options or packs that aren't licensed (even if technically available). Ensure deploying Oracle VMs in Azure or AWS adheres to Oracle's licensing guidelines. Cloud architects must know when to select BYOL vs. licence-included in OCI.
Don't neglect Oracle SaaS subscriptions in your portfolio management. Assign responsibility for overseeing SaaS usage and subscriptions (number of users, storage consumed) just as you do for on-prem licences.
Regularly compare SaaS subscription levels to actual business usage. Identify excess capacity that could be negotiated down at renewal, or areas where you need to adjust upward. Remove users who no longer need access to free up subscriptions.
Plan cutover timing to avoid overlapping costs. Coordinate the ramp-down of on-premises support payments with ramp-up of SaaS subscription fees. Leverage Oracle's Customer 2 Cloud programme for potential credits from existing licences toward SaaS fees.
Ensure data from SaaS solutions (Fusion ERP, HCM) is integrated into your IT asset tracking for a holistic view of all Oracle-related expenses. Every dollar should be justified by usage and value, whether infrastructure or applications.
Moving to Fusion Applications may allow you to sunset customisations and third-party add-ons along with their associated licences and support. Prepare SaaS-specific governance: comply with Oracle's usage terms and remove unauthorised access.
Hybrid licensing often spans multiple contracts — licence agreements for on-prem, cloud subscription agreements for OCI, and separate contracts for Cloud@Customer and SaaS. Develop a cohesive negotiation strategy that covers all Oracle engagements.
Use upcoming support renewals as opportunities to evaluate cloud options. Could you reduce support spend by shifting workloads to OCI using Support Rewards? Negotiate expanded BYOL allowances or Universal Credits alongside on-prem renewals.
Oracle may offer discounts on cloud if you renew support, or vice versa. Capitalise by timing all Oracle contract discussions together. Seek bundled agreements — a Universal Credit commitment that also renews support at better terms.
Ensure new contracts include cloud mobility clauses, locked-in BYOL conversion rates, and the ability to transfer credits between Cloud@Customer and OCI. Get written clarity on BYOL usage rights and Cloud@Customer-specific terms.
Oracle's LMS may audit on-premises use, which can now extend to cloud BYOL verification. Maintain documentation through internal audit processes. Consider independent licence compliance expertise for especially complex environments — firms experienced in Oracle audits can simulate an audit and identify gaps.
Every renewal cycle is a chance to realign your portfolio. Evaluate whether to reduce on-prem support proportional to cloud uptake, convert underused licences to cloud credits, or negotiate transition programmes (Customer 2 Cloud) for SaaS migration.
By planning contractually and operationally, you turn audits and renewals from reactive firefighting into proactive opportunities to optimise and realign your Oracle licence portfolio. Engage Oracle account management early with a clear outline of your hybrid strategy.
Inventory all Oracle software deployments across on-premises, OCI/Cloud@Customer, and SaaS. Document licences owned (by product, edition, and quantity) and map to current locations of use. Highlight underutilised licences and areas of potential non-compliance.
Categorise Oracle workloads by criticality, performance needs, compliance requirements, usage volatility, and strategic cloud fit. Identify which workloads are cloud-ready (rehost or replace with SaaS) and which should remain on-prem due to constraints.
For each workload category, decide target platform and licensing model. Create a roadmap: migrate certain databases to OCI with BYOL, move dev environments to OCI licence-included, consolidate on-prem systems, evaluate Fusion Cloud for business functions.
Develop a plan to reallocate licences with workload changes. Determine how many licences freed from decommissioned on-prem systems can be used in OCI. Mark "assigned to cloud" in your records. Coordinate so you don't pay twice.
Open dialogue with your Oracle account team about hybrid plans. Leverage renewal dates for bundled agreements or discounts. Request written clarity on BYOL usage rights and Cloud@Customer terms. Inquire about Customer 2 Cloud transition programmes.
Enable Oracle's licence tracking in OCI, deploy LMS scripts regularly on-prem, or use third-party SAM tools. Establish a governance board or designate a Licence Manager role to oversee compliance and optimisation across departments.
Train cloud architects on BYOL vs. licence-included selection in OCI. Ensure DBAs know to request licences from the pool before spinning up new instances. Brief finance and procurement on cloud bills in the context of licence usage and Support Rewards.
Review cloud consumption and on-prem licence usage at regular intervals: monthly cloud cost reviews, quarterly compliance checks, annual strategic reviews. Adjust allocations as workloads grow or are retired. Track Oracle policy updates that may open opportunities.
Whether you're evaluating BYOL, negotiating OCI commitments, planning a Cloud@Customer deployment, or migrating to Fusion SaaS — Redress Compliance provides expert, independent Oracle advisory.