Oracle OCI License Included

What is OCI License Included?

OCI License Included is the cloud licensing model where the right to use the Oracle software is built into the hourly or monthly rate of the service, so you do not need to own a perpetual licence in advance. You provision a database, a middleware service, or an analytics service, and the published rate already contains the software entitlement and its support. It is the opposite of Bring Your Own License, where you carry a licence you already own and pay only for infrastructure.

The appeal of License Included is that it converts a capital purchase into pure consumption. There is no perpetual licence to buy, no support contract to maintain separately, and no entitlement to reconcile against deployment. You pay for what you run, when you run it, and you stop paying when you stop. For a net new workload, or for an organisation that holds no spare Oracle licences, this is frequently the cheaper and always the simpler path, as the Oracle OCI licensing pillar explains.

How License Included is billed

License Included is billed through Universal Credits, the same consumption currency that funds the rest of OCI. The service carries a higher per OCPU rate than the equivalent BYOL service, and the difference is the software and support component. You commit to a credit amount, or pay as you go, and the License Included rate draws down those credits as the service runs.

Because the entitlement is metered by Oracle rather than asserted by the customer, License Included removes the reconciliation burden entirely. You cannot be under licensed on a License Included service, because the licence is created and consumed in the same act. That is the structural reason its audit exposure is lower, covered below.

What does the rate bundle?

The License Included rate for a database service typically bundles the database edition and a defined set of options and packs that would be separately chargeable on premise. An Autonomous Database under License Included, for example, includes options such as Partitioning, Advanced Security, and the management packs that an on premise Enterprise Edition customer would license individually. This is a genuine advantage: features that carry large incremental licence costs on premise are simply present in the cloud rate.

The precise bundle differs by service tier, and the detail matters when comparing against a BYOL deployment that would have to license those options separately. The database options on OCI article sets out which options each tier includes, and the Autonomous Database article works through the fully managed case where the bundle is broadest.

Where License Included applies

License Included is available across most OCI platform services: database services including Autonomous Database and Exadata Cloud Service, middleware, analytics, and Java managed services. For each, Oracle publishes both a License Included and a BYOL rate, and the customer elects per service. A single estate commonly mixes the two: License Included for net new and elastic workloads, BYOL for workloads backed by spare perpetual licences.

The managed services are where License Included is most compelling, because the bundled rate also removes the operational burden of patching and tuning. An Exadata Cloud Service under License Included delivers engineered system performance with no licence reconciliation and no infrastructure to manage, which is why it is the default for organisations without a large existing Oracle investment to protect.

When does License Included win?

License Included wins in several common cases. It wins for net new workloads where you hold no spare entitlement, because it avoids a perpetual purchase. It wins for elastic or bursty workloads, because you pay only for the capacity you actually consume rather than licensing peak. It wins where the bundled options would be expensive to buy separately under BYOL. And it wins for short lived workloads, because consumption stops when the workload retires, with no stranded perpetual licence.

It loses, predictably, where BYOL wins: when you hold idle, supported perpetual licences that can be redeployed at the infrastructure rate for a long, stable workload. The full break even is worked in the BYOL versus License Included article, and the choice should be made per workload, not as an estate wide policy.

Support, lock in, and exit

Because support is bundled, License Included has no separate support contract to manage, which is a real simplification. The trade off is lock in of a different kind: the consumption is denominated in Universal Credits, and an annual commitment sized to License Included consumption is a commitment to keep running those services. Migrating off a License Included service later means re acquiring the perpetual licences you never bought, which can be a costly reversal.

This matters most when a License Included strategy is being traded against an Unlimited License Agreement or a large cloud commitment. The flexibility that makes License Included attractive at provisioning time becomes a dependency at renewal time, and the exit cost should be modelled at the outset. The Oracle OCI licensing pillar treats Universal Credits commitments as a lock in mechanism for exactly this reason.

Why audit exposure is lower

License Included carries materially lower audit exposure than BYOL because the entitlement cannot diverge from the deployment. There is no carried licence to over deploy, no option to enable without owning, and no conversion ratio to miscalculate. Oracle meters the consumption directly, so the question an audit asks of a BYOL estate, do you hold enough licences for what you are running, has no answer to dispute on a License Included service.

This does not make License Included risk free at the estate level. A mixed estate still carries the BYOL exposure on its BYOL workloads, and the boundary between the two, especially when a workload migrates from BYOL to License Included or back, is where misclassification can occur. But on a pure License Included service, the structural audit surface is close to zero, which is itself a reason to prefer it for workloads where compliance certainty is worth more than the rate difference. Where a claim spans a mixed estate, the cloud and OCI practice separates the License Included consumption from the BYOL exposure.

The buyer side view

License Included is the model for net new, elastic, short lived, or option heavy workloads, and for any organisation that values compliance certainty and operational simplicity over squeezing the last dollar from a sunk licence. The discipline is to recognise where the bundled options and the absent reconciliation burden genuinely outweigh the higher rate, and to model the exit cost before a Universal Credits commitment turns flexibility into dependency. Decide it per workload against BYOL, size the commitment to real demand, and keep the option to move workloads between models as the estate changes. To model License Included against BYOL across your estate, request a consultation.

License Included and cost predictability

One underrated advantage of License Included is budget predictability. Because the software, support, and infrastructure are a single per OCPU rate, the cost of a workload is a clean function of how much capacity it consumes, with no separate support uplift, no option true ups, and no perpetual amortisation to model. Finance functions that struggle to forecast a BYOL estate, where the cloud rate, the retained support, and the Support Rewards rebate interact, often find License Included simpler to plan against because there is exactly one number per OCPU hour.

That predictability is most valuable for workloads with volatile capacity. A reporting database that runs hot at month end and idle the rest of the month costs, under License Included, precisely what it consumes, scaling its software cost down with its OCPUs. The same workload under BYOL must carry enough perpetual entitlement to cover its peak, paying support on that peak entitlement even in the idle weeks. For genuinely spiky workloads, License Included converts a fixed peak licence cost into a variable one, which is frequently the larger saving even before the rate difference is considered.

Using License Included as negotiation leverage

License Included also changes the negotiating dynamic with Oracle. Because it requires no perpetual purchase, it gives the customer a credible alternative to a large licence order: rather than buying perpetual licences to cover a new programme, the customer can run it on License Included and walk away if the economics sour. That optionality is leverage, and it is worth preserving even when BYOL ultimately wins on a given workload, because the threat of consumption only is what disciplines an Oracle perpetual quote. Where this interacts with a broader ULA negotiation, the ability to move workloads to License Included rather than certifying more perpetual entitlement can materially improve the exit position.

A final practical point: the model election is not permanent. Oracle lets you switch a service between License Included and BYOL, so a workload provisioned as License Included while you lacked spare entitlement can later be flipped to BYOL if you acquire or free up licences, and the reverse holds when perpetual licences are retired. Building this switching into the governance cadence means the estate is never locked into the wrong model by an early decision, and it lets the cost position track the underlying licence position as both evolve. The discipline is to review the election at each renewal and after any material change in owned entitlement, treating model choice as a living decision rather than a one time provisioning default.