Oracle OCI Licensing: The Complete Guide

What is Oracle OCI licensing?

Oracle Cloud Infrastructure, almost always shortened to OCI, is Oracle's public cloud, and Oracle OCI licensing is the set of rules that determine how Oracle software is entitled when it runs there. The central fact is that moving to the cloud does not dissolve the licence obligation; it changes the form it takes. You either carry an existing on premise licence into the cloud under Bring Your Own License, in which case the on premise metrics and rules follow the software, or you consume a License Included service, in which case the right to use the software is bundled into the hourly or monthly rate. Both models are paid for, ultimately, through Oracle's Universal Credits commercial framework.

The reason OCI licensing deserves its own discipline is that Oracle deliberately blends two things that are separate everywhere else: the commercial contract that governs how you buy capacity, and the licensing rules that govern how much software you are entitled to run on that capacity. On premise, a customer buys processor or Named User Plus licences and runs them on hardware they control. In OCI, the capacity, the software entitlement, and the support obligation are braided into a single consumption relationship, and the places where the braid loosens, around BYOL conversion ratios, core counting, and the policy documents that are not contract terms, are exactly where money is won and lost.

This pillar maps the whole surface: the two models and when each is cheaper, how Universal Credits meter usage, how an OCPU translates into a processor licence, how the same software is treated on AWS and Azure under Oracle's authorized cloud policy, and where the cloud quietly creates audit exposure that did not exist on premise. Each section links to a focused article that goes deeper. For the capacity metrics that BYOL inherits, read the Oracle database licensing pillar, and to scope a cloud licence review, our cloud and OCI licensing practice runs the exercise end to end.

The two commercial models: BYOL and License Included

Every Oracle program on OCI is consumed under one of two licensing models, and the choice is a per workload commercial decision rather than a technical one. Under Bring Your Own License, you already own the on premise licence and you carry it into OCI, paying only the lower infrastructure rate for the service. Under License Included, you own nothing in advance and the right to use the software is built into a higher hourly rate. The same Autonomous Database, the same Exadata service, can be run either way, and the cheaper option depends entirely on whether you already hold the underlying licence and support.

The deciding question is whether you hold licences you are already paying support on but not fully using. If you do, Bring Your Own License lets you redeploy that sunk cost in the cloud at the infrastructure rate, and it is almost always the cheaper path for an existing estate. If you are standing up a net new workload with no spare entitlement, License Included avoids a fresh perpetual purchase and converts the cost to consumption. The detailed comparison, including the break even analysis per workload, sits in the BYOL versus License Included article.

The common error is to treat BYOL as automatically cheaper. It is cheaper only when the on premise licence is genuinely spare and you continue paying its support. If you would have to buy the licence anyway, or if you could terminate the support to save cash, the arithmetic changes and License Included frequently wins. This is why the model decision is made workload by workload, not as a blanket policy.

How Universal Credits meter consumption

Oracle sells OCI capacity through Universal Credits, a single prepaid or pay as you go currency that can be spent across almost any OCI service. You commit to a dollar amount, drawn down as you consume compute, storage, database, and platform services at published per hour rates. The commercial appeal is flexibility: the same credits cover Autonomous Database one month and OCI compute the next. The commercial risk is that the commitment is use it or lose it, so an over sized commitment becomes shelfware in cloud clothing.

There are two purchasing shapes. Annual Universal Credits commit a fixed amount for a term in exchange for a discount, with unused credits expiring at the end of the period. Pay As You Go carries no commitment and no discount, billing actual consumption monthly. The trade off, worked through in the Annual Flex versus Pay As You Go article, is the classic one between a discount that requires accurate forecasting and flexibility that costs more per unit. Most estates land on an annual commitment sized to baseline consumption with overage absorbed at pay as you go rates.

The governance discipline is to size the commitment to real, forecastable demand and to monitor the drawdown so that neither expiry nor overage surprises the budget. The commitment management and cost optimization articles cover the operational side, and the Universal Credits article works through the model itself in detail.

How is an OCPU counted against a licence?

When you bring a licence into OCI, the question that decides the cost is how OCI capacity maps to the processor metric the licence is written in. OCI measures compute in OCPUs, where one OCPU historically represents one physical core with hyper threading, equivalent to two vCPUs. Oracle's cloud policy sets out how that capacity converts to a processor licence, and the conversion is the single most consequential number in cloud BYOL.

The practical effect is that the on premise core factor table does not apply in the same way in the cloud. Oracle's authorized cloud policy substitutes its own counting rule, generally the two vCPU rule, which can be more or less favourable than the core factor depending on the processor. The OCPU versus vCPU article works the arithmetic, and the core factor in the cloud article sets out exactly when the policy helps and when it hurts. The detail of which OCI compute shapes carry which counting basis is covered in OCI compute licensing.

Oracle on AWS, Azure, and the cloud policy

OCI is not the only cloud Oracle software runs in, and Oracle treats the others differently. Amazon Web Services and Microsoft Azure are designated Authorized Cloud Environments in an Oracle policy document, which sets a specific counting rule for Oracle licences deployed there: typically two vCPUs equal one processor licence where hyper threading is enabled, with no core factor applied. Google Cloud sat outside that designation for years, which materially changed the licensing question, as the Oracle on Google Cloud article explains.

The decisive point, and the one Oracle sales motions rarely volunteer, is that the Oracle cloud licensing policy is a published policy document, not a contract term. It is not referenced in the OLSA or OMA that most customers signed, and Oracle reserves the right to change it. A customer relying on the two vCPU rule to license a large AWS or Azure estate is relying on a document Oracle can revise, which is a governance risk that must be understood before the architecture is committed. The deployment specifics live in the Oracle Database on AWS and Oracle Database on Azure articles, and the newer first party Oracle Database@Azure service changes the calculus again by putting Oracle hardware inside the Azure data centre.

Support Rewards and the on premise tie

Oracle links cloud consumption back to the on premise estate through Support Rewards, a programme that rebates a portion of OCI spend against on premise technology support fees. For every dollar of OCI consumed, a customer earns a reward, larger for Unlimited License Agreement holders, that can be applied to reduce the annual support bill on perpetual licences. On paper this is a genuine saving; in practice it is also a retention mechanism that makes leaving OCI more expensive than the headline rate suggests.

The buyer side reading is that Support Rewards should be modelled as part of the total cost of the relationship, not banked as free money. A reward that depends on continued OCI consumption is a discount with a leash. The Support Rewards article works through the mechanics and the lock in implications, and it should be read alongside any ULA negotiation where cloud commitments and support are being traded together.

Where cloud creates audit exposure

A frequent and dangerous assumption is that the cloud removes audit risk. It does not; it relocates it. License Included services genuinely reduce exposure because entitlement is bundled and metered by Oracle. BYOL deployments, by contrast, carry every on premise audit risk into the cloud and add new ones: the BYOL conversion was miscalculated, the deployment exceeded the licences carried, options were enabled in the cloud that were never licensed on premise, or the customer relied on a policy counting rule that Oracle later disputes.

The hyperscaler case is sharper still. Running Oracle on AWS or Azure under the two vCPU policy is defensible only as long as that policy holds and the deployment matches it. An estate that scaled elastically beyond its carried licences, a common cloud pattern, can generate a processor shortfall measured against a moving policy. The migration article covers how to baseline before the move, and the audit defence practice handles a cloud claim if one lands. For the options trap specifically, see database options on OCI.

The complete OCI and Cloud cluster

This pillar anchors the OCI and Cloud cluster. Each supporting article below goes deep on one model, metric, platform, or commercial mechanism. Read them alongside this overview to build a complete picture of your cloud licence position.

• Oracle BYOL Licensing, Bring Your Own License: how existing on premise licences move to OCI and authorized clouds.
• OCI License Included, The License Included model, what it bundles, and when it beats BYOL.
• Oracle Universal Credits, The Universal Credits commercial model and how consumption is metered.
• Annual Flex vs Pay As You Go, Annual Universal Credits against Pay As You Go and the commitment trade off.
• Authorized Cloud Environments, Oracle's Authorized Cloud Environment policy for AWS and Azure.
• Oracle Database on AWS, Licensing Oracle Database on Amazon EC2 and RDS under the cloud policy.
• Oracle Database on Azure, Licensing Oracle workloads on Microsoft Azure virtual machines.
• Oracle Database on Google Cloud, Oracle on Google Cloud and the authorized cloud question.
• Oracle Database@Azure, The Oracle Database@Azure service and its licensing model.
• The Oracle Cloud Licensing Policy, The cloud computing policy document and why it is not a contract term.
• Exadata Cloud Service, Licensing Exadata Cloud Service and Cloud@Customer Exadata.
• Autonomous Database, How Autonomous Database is licensed and what BYOL covers.
• OCI Compute Licensing, Licensing Oracle programs on OCI compute shapes and OCPUs.
• OCPU vs vCPU, How OCPUs and vCPUs map to processor licences in the cloud.
• Core Factor in the Cloud, The two vCPU rule and how core factor is applied on cloud instances.
• Database Options on OCI, How options and packs are handled across OCI service tiers.
• Java on OCI, Java SE entitlement on OCI compute and managed services.
• WebLogic on OCI, WebLogic Suite for OCI and BYOL for middleware in the cloud.
• Oracle Support Rewards, How OCI consumption reduces on premise support fees.
• Migrating to OCI, What changes in the licence position when you move workloads to OCI.
• BYOL vs License Included, Choosing between BYOL and License Included on a per workload basis.
• OCI Cost Optimization, Reducing OCI spend without breaching consumption commitments.
• Cloud@Customer, Licensing Oracle Cloud@Customer and Dedicated Region deployments.
• OCI Commitment Management, Managing annual consumption commitments and avoiding overage.

The buyer side view

Oracle cloud licensing rewards the customer who treats the cloud as a continuation of the licence estate rather than a clean break from it. The vendor narrative is that moving to OCI simplifies licensing; the reality is that it changes the metrics and the documents, and the customer who does not track the change pays for the difference. The buyer side discipline is to decide each model on its own arithmetic, to count cores against the policy that actually applies, and to read Support Rewards and Universal Credits commitments as the lock in mechanisms they partly are.

Practically, that means three moves. Decide BYOL versus License Included per workload, using the real status of your on premise licences and support. Size Universal Credits to forecastable demand and govern the drawdown so neither expiry nor overage surprises you. And document the counting basis for every BYOL and hyperscaler deployment against the current policy, so that if Oracle revises the policy or opens an audit, your position is already evidenced. Done this way, the cloud is a cost reduction lever. Done carelessly, it is a new and less visible source of the same old exposure. To scope a cloud licence review, request a consultation.

Migrating workloads to OCI

A migration to OCI is the single best moment to clean up a licence position, and the single most common moment to create a new one by accident. The right sequence is to baseline the on premise entitlement first, decide the model per workload, and only then architect the OCI shapes to match the licences being carried. The wrong sequence, which most projects follow, is to lift and shift first and reconcile the licences afterward, by which point the deployment has already exceeded what was carried.

The migration also resets several clocks. Support on the migrated on premise licences continues under BYOL and can be partly rebated through Support Rewards. Options and packs that were dormant on premise become live and chargeable if enabled in the new shapes. And the elasticity that makes the cloud attractive is precisely what breaches a fixed BYOL count if it is not governed. The migration article sets out the sequence in full, and the Cloud@Customer article covers the hybrid case where OCI runs inside the customer data centre.

Cloud licence governance

Cloud licensing is not a one time decision; it is an ongoing governance task, because consumption and architecture change continuously while the licence position is measured at a point in time. The estates that stay compliant and cost efficient treat the OCI licence position the way a treasury function treats a currency exposure: monitored, forecast, and rebalanced on a schedule rather than examined only when something breaks.

The standing tasks are to track Universal Credit drawdown against the commitment, to confirm that every BYOL deployment still matches its carried entitlement after any scaling event, to keep the counting basis documented against the current policy, and to model Support Rewards as a conditional discount rather than banked savings. The cost optimization and commitment management articles cover the operational cadence, and our cloud and OCI practice can stand up the governance function. To put a standing cloud licence review in place, request a consultation.