Oracle Cloud Infrastructure is the one cloud where your software vendor owns the meter, the hypervisor and the contract. That is why the policy you use for AWS and Azure does not govern it, and why the counting works differently.
Oracle Cloud Infrastructure is the one cloud where Oracle sets both the license rules and the meter. That is why the Authorized Cloud Environments policy you use for AWS and Azure does not apply here, and why the counting works differently.
Oracle Cloud Infrastructure is the only public cloud where your software vendor also owns the meter, the hypervisor and the contract. That is not a complaint. It is the single fact that explains every licensing difference on this page.
Because Oracle runs the platform, it does not need a policy document to tell you how its software is counted. It writes the counting into the service description that forms part of your order.
That makes OCI licensing more contractual and less arbitrary than licensing on AWS or Azure. It also makes it different enough that reusing your hyperscaler model will give you a wrong number in both directions.
It means you apply a license you already own against an OCI service and pay a reduced rate that covers infrastructure rather than software. Oracle publishes the eligible programs on its bring your own license page, and the binding detail sits in the service description for the specific service.
The first path is an ordinary software install. You provision OCI Compute, install Oracle Database yourself, and license it against the OCPUs the instance uses. Oracle is your infrastructure provider and nothing more.
The second path is a managed database service where BYOL is a billing election in the console. Oracle runs the service, and your owned licenses offset the software component of the hourly rate.
Buyers routinely evaluate only the second and third options because those are the ones on the quote. Price the first as well, particularly for non production and for databases you have no intention of modernizing.
Across the estates we modelled in 2024 and 2025, electing BYOL removed roughly 75 to 80 percent of the license included rate for equivalent database capacity. Treat that as an observed price delta, not a rule.
The current gap is published, service by service, in the OCI price list. Model your own workloads against the current numbers rather than a remembered percentage, because Oracle adjusts both sides of the comparison independently.
The prerequisite has not changed and never softens. You must own the license, and you must be paying support on it, for the entire period you claim the reduced rate.
This is where most bring your own license positions actually break. Oracle sells database services in tiers, and the higher tiers bundle database options and management packs into the service.
Elect BYOL on a tier that bundles Partitioning, Advanced Security and the diagnostics packs and you have just asserted that you own all of them. The base Enterprise Edition license does not cover any of them.
What to check before you elect BYOL on a database service tier
| Question | Where the answer lives | What goes wrong if you skip it |
|---|---|---|
| Which options does this tier include? | The service description for that service | You claim BYOL against options you never bought |
| Is the unit OCPU or ECPU? | The current OCI price list | Your entitlement model is off by a whole unit basis |
| What is the published conversion for my edition? | The service description, per edition | You size the commitment against the wrong ratio |
| Is support current on every license I am counting? | Your own support renewal schedule | Eligibility lapses silently and retroactively |
| Is this license also counted on premises? | Your deployment reconciliation | One license covers two places, which it cannot |
The rule to remember is simple. A service tier is a bundle, and under BYOL you own the bundle rather than rent it.
If you do not own an option the tier includes, either buy it, drop to a tier that does not include it, or take license included for that workload. There is no fourth answer.
They are the two billing units OCI uses for compute, and they are not interchangeable. Getting this wrong is the fastest way to build a model that is confidently off by a factor of two.
An OCPU is one physical core with hyperthreading enabled, which OCI presents to the operating system as two vCPUs. Compute shapes are frequently quoted in vCPUs, while database services have historically been quoted and licensed in OCPUs.
The practical consequence is that a shape advertised as 16 vCPUs is 8 OCPUs. Read every Oracle quote for which unit it uses before you compare it to anything.
On premises, the Oracle processor core factor table discounts cores by processor family, which is why an Intel core counts as 0.5 of a processor license.
On OCI that table is not in play. The unit is the OCPU or the ECPU, and the published conversion for your edition and service is the whole calculation.
Teams that carry the 0.5 factor into an OCI model halve their license requirement on paper and then discover the gap at true up. Teams that carry a hyperscaler vCPU rule into an OCI model double it. Both errors are common, and both come from using the wrong document.
Oracle introduced the ECPU as an abstracted compute unit and has been migrating cloud database services onto it since 2023, starting with Autonomous Database. The stated intent is to decouple billing from a fixed physical core.
Which unit applies to your service, edition, generation and region is a moving target. Confirm it in the current OCI price list and the service description for that exact service, and do not carry an OCPU assumption into an ECPU quote.
The licensing consequence is real, not cosmetic. The unit determines how many units one owned processor license covers, so a change of unit changes your entitlement requirement even when the workload has not changed at all.
Because OCI is not an Authorized Cloud Environment, and Oracle says so in its own policy. The document titled Licensing Oracle Software in the Cloud Computing Environment defines a specific list of third party clouds and states that it does not apply to Oracle's own cloud.
That single exclusion is the source of every difference below. On a third party cloud you are governed by a policy. On OCI you are governed by a contract.
It covers Oracle programs running on a defined set of third party clouds, and it sets the counting rule for them. With hyperthreading enabled, two vCPUs count as one processor license, and the core factor table is disapplied.
It is a policy, not a contract term. Oracle publishes it, Oracle revises it, and unless your agreement incorporates it by reference you have no contractual claim on the version you planned against. We work through that exposure on our Oracle cloud licensing policy page.
Your OCI order, the applicable service descriptions, and the Oracle cloud services agreement. The BYOL conversion for each service is stated in that service's description, which is incorporated into what you signed.
That is a genuinely better position for a buyer, and almost nobody uses it. If the conversion matters to your business case, cite the service description clause in the negotiation and ask for the version to be pinned in the order document.
Oracle Database licensing: OCI against the hyperscalers
| Dimension | OCI | AWS and Azure |
|---|---|---|
| Governing document | Service description in your order | A published policy Oracle can revise |
| Counting unit | OCPU or ECPU, per service | vCPU, two per processor with hyperthreading |
| Core factor table | Does not apply | Does not apply |
| License included available | Yes, including Enterprise Edition tiers | Limited, and not for Enterprise Edition on the managed services |
| Support Rewards accrual | Yes, on OCI consumption | None |
| Who sees your usage | Oracle, directly and continuously | Your cloud provider, not Oracle |
Read the last two rows together, because they pull in opposite directions. Support Rewards make OCI cheaper in total cost when you still carry a large on premises support bill.
Direct visibility makes OCI the one platform where Oracle never has to ask what you deployed. Compliance stops being an audit and becomes an invoice reconciliation, which is easier but far less forgiving of a wrong assumption.
For the estate by estate comparison against Amazon, see our OCI against AWS analysis and the mechanics on AWS bring your own license.
This catches experienced teams. Oracle Database at Azure, at Google Cloud and at AWS place Oracle owned OCI hardware inside a hyperscaler data center, connected to your tenancy in that cloud.
The workload runs on OCI infrastructure, so it is licensed as OCI, not under the Authorized Cloud Environments policy. If your model applied the two vCPU rule because the service has "Azure" in the name, the model is wrong.
The same logic runs the other way for Cloud at Customer. The rack sits in your building, and it is still OCI for licensing purposes.
They lock a floor on your spend, not a ceiling on your consumption. Universal Credits is a prepaid pool you draw against across OCI services for the term you committed to.
Unused Universal Credits expire at the end of the term and do not roll forward. Every dollar of oversizing converts directly into waste with no recovery path.
Universal Credits commitments were oversized in nearly two thirds of the deals we reviewed. Oracle sizes to a growth forecast because that is Oracle's job. Sizing to a defensible steady state is yours.
Every dollar of OCI consumption earns credits that retire your on premises technology support bill. Oracle Support Rewards accrue at 25 cents per dollar of OCI usage, rising to 33 cents for unlimited license agreement customers.
Two mechanics matter more than the headline rate. You have to register to claim the rebate, and the rewards can only retire support spend you still have.
That second point cuts against the tidy migration story. Retire the on premises estate aggressively and you also retire the support bill the rewards were going to pay for. Model the two together, over the full term, before you set the retirement schedule.
In five places, and none of them are the unit price. They are all questions of entitlement hygiene that survived the migration unchanged.
Every one of these is cheap to prevent and expensive to unwind. The prevention is the same in all five cases: a written entitlement position, reconciled quarterly, that names which license covers which instance.
Four, and they run in order. Each one makes the next one cheaper.
List every owned database license, option and management pack with its support renewal date. Nothing downstream is defensible without this, and Oracle will happily build the list for you if you do not.
Decide per workload between self managed on OCI Compute, a managed service with BYOL, and license included. Estate wide decisions are always wrong for part of the estate.
Set the Universal Credits floor to steady state consumption and buy growth later at rates locked at signature. Expansion pricing negotiated at signature is worth more than a headline discount.
File from month one and reconcile the rebate against the support invoice every quarter. Unclaimed rewards are the most common free money left on the table in a first year migration.
The standard account team pitch is that license included on OCI is simpler and removes audit risk, so buyers should default to it. We disagree. In roughly seven out of ten OCI estates Fredrik Filipsson modelled in 2024 and 2025, the customer already owned database licenses with active support, which made bring your own license the cheaper position by a wide margin. The deeper problem with the pitch is that it treats OCI as if it were AWS, where the policy risk is real and the contractual protection is thin. On OCI the conversion sits in a service description that forms part of your order, which means the certainty you are being sold at a premium is already available to you for free. Inventory first, elect per workload, and buy license included only for capacity you genuinely do not own.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
On AWS your Oracle licensing is governed by a policy Oracle can rewrite. On OCI it is governed by a service description you signed. Almost nobody negotiates the second one, which is the only one they can.
No. Oracle's cloud licensing policy defines Authorized Cloud Environments as a specific list of third party clouds and states that it does not apply to Oracle Cloud Infrastructure. Licensing on OCI is governed by the service descriptions incorporated into your order instead.
Bring your own license applies a license you already own so you pay a reduced rate covering infrastructure rather than software. License included bundles the software into the hourly price and requires no owned license. Across the estates we modelled, BYOL removed roughly 75 to 80 percent of the license included rate.
One OCPU equals two vCPUs, because an OCPU is one physical core with hyperthreading enabled. Compute shapes are often quoted in vCPUs while database services are quoted in OCPUs, so check the unit on every quote before comparing anything.
No. The processor core factor table governs on premises licensing and is not used on OCI or on the authorized third party clouds. On OCI the calculation is the published conversion for your edition against OCPUs or ECPUs.
Oracle has migrated Autonomous Database and other cloud database services toward the ECPU since 2023, but coverage varies by service, generation and region. Confirm the unit in the current price list and service description for the exact service you are buying rather than assuming a conversion.
No. Unused Universal Credits expire at the end of the committed term and do not roll forward. Size the floor to steady state consumption and negotiate expansion at signature rates instead of committing to a growth forecast.
Oracle Support Rewards accrue at 25 cents per dollar of OCI consumption, rising to 33 cents for unlimited license agreement customers, and retire your on premises technology support bill. You must register to claim them, and they can only offset support spend you still have.
Yes, but every option carries its own entitlement and the higher service tiers bundle several of them. Partitioning, Advanced Security and the management packs are not covered by a base Enterprise Edition license, so map each option in the tier before you elect BYOL.
As OCI, not as Azure. The service places Oracle owned OCI infrastructure inside a hyperscaler data center, so the Authorized Cloud Environments counting rule does not apply even though the service carries a hyperscaler name.
Double counting a license that is still consumed on premises against an OCI bring your own license instance. A single license cannot cover both, and on OCI Oracle sees one side of the picture directly and continuously.
The ten levers that move an OCI universal credit deal, from ramp to discount protection to exit.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
Oracle Cloud Infrastructure rewards the buyer who knows what they already own. The license you hold on premises is the strongest card on the OCI table.
