Oracle Cloud Infrastructure prices compute, database, and license in three different ways at once. Bring Your Own License, License Included, and universal credits each carry a separate trap. Read the math before you sign the commitment.
Oracle OCI blends infrastructure pricing, the OCPU core model, and software licensing into a single bill. The 2026 guide separates the three, prices BYOL against License Included, and names the commitment traps buyers walk into.
Oracle Cloud Infrastructure is not one price. It is three pricing systems stacked on one invoice. The 2026 guide separates compute, the license model, and the commitment.
Get the license model right and the same workload can cost 20 to 35 percent less. Get it wrong and you pay twice for a license you already own.
Bring Your Own License applies an existing perpetual license against OCI consumption, so you pay the infrastructure rate only. License Included bundles the software into the hourly rate.
BYOL typically removes 75 to 80 percent of the License Included database rate. The trade is that you must already hold, and keep paying support on, the underlying license.
Oracle documents the eligible programs on its Bring Your Own License page. Confirm the exact program names before you assume coverage.
The base Database license is only the start. Partitioning, Advanced Security, and the management packs each carry their own BYOL line. Buyers routinely forget them.
One OCPU equals one physical core with two threads, which Oracle treats as two vCPUs. This matters because Database licensing on OCI counts OCPUs, not vCPUs.
OCI compute and license counting at a glance
| Unit | What it is | Database license basis | Buyer note |
|---|---|---|---|
| vCPU | One thread | Not the license unit | Shown in compute pricing |
| OCPU | One core, two threads | One OCPU per processor license band | Halves the apparent count |
| BYOL ratio | Existing license offset | Roughly 75 to 80 percent off | Requires active support |
| License Included | Bundled software | Full hourly rate | No owned license needed |
Enterprise Edition and Standard Edition 2 count OCPUs differently, as set out in the Oracle Database documentation. Standard Edition 2 caps the socket equivalent, so the OCPU math is not uniform across editions.
Autonomous Database moved to the ECPU metric, which is a smaller billing unit than the OCPU. Do not assume the two convert one to one when you model the bill.
Universal Credits is a prepaid annual pool you draw against across OCI services. The commitment sets a floor on spend, not a ceiling.
Unused Universal Credits expire at the end of the term. They do not roll forward. Oversizing the commitment converts directly into waste.
Every dollar of OCI consumption earns Oracle Support Rewards that reduce your on premises Oracle support bill. Oracle sets the rate on its Support Rewards page, and the standard rate is 25 cents per dollar, rising to 33 cents for ULA customers.
Exadata Cloud at Customer uses the same BYOL versus License Included choice. The hardware sits in your data center but the license decision is identical.
The standard Oracle 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 modeled 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 buyer side move is to inventory owned entitlements and support streams first, map them to the OCI workloads that qualify, claim Support Rewards against the on premises bill, and only buy License Included for the net new capacity you genuinely do not own. Simplicity is not free.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
OCI is sold as a single price. It is three. Separate the compute, the license, and the commitment, and two of the three are negotiable before you ever sign.
White Paper · Oracle
The Oracle Buyer Side Framework
The moves we use across Oracle Database, Java and ULA estates. Read it free.
Four moves recur in every well run OCI commitment.
List every owned Database license, option, and pack with its support status. This is the BYOL foundation.
Set the Universal Credits floor to steady state consumption, not the peak forecast. Buy more later at the same rate if you grow.
File for Oracle Support Rewards from month one. The rebate reduces the on premises support invoice directly.
Map every Database option to its OCI BYOL line so nothing is bought twice or left uncovered.
Bring Your Own License applies an existing perpetual license to OCI so you pay only the infrastructure rate. License Included bundles the software into the hourly price. BYOL usually removes 75 to 80 percent of the database rate but requires you to hold and keep supporting the underlying license.
One OCPU equals two vCPUs. The OCPU represents one physical core with two threads. Database licensing on OCI counts OCPUs, so the license count is roughly half the vCPU count you see in compute pricing.
No. Unused Universal Credits expire at the end of the committed term. They do not roll forward, so oversizing the annual commitment converts directly into waste. Size the floor to steady state consumption.
Oracle Support Rewards reduce your on premises Oracle support bill based on OCI consumption. The standard rate is 25 cents per dollar of OCI spend, rising to 33 cents for Unlimited License Agreement customers. You must register to claim the rebate.
Yes, but each option carries its own license line. Partitioning, Advanced Security, and the management packs are not covered by the base Database license. Map every option separately or you will either pay twice or run uncovered.
Yes. Exadata Cloud at Customer uses the same BYOL versus License Included choice as OCI. The hardware sits in your data center but the license decision and the OCPU counting are identical.
No. Autonomous Database moved to the ECPU metric, which is a smaller billing unit than the OCPU. Do not assume a one to one conversion when modeling Autonomous costs against traditional Database licensing.
Double counting. Buyers apply one on premises license against both the data center and OCI BYOL at the same time. A single license cannot cover both. Document the BYOL position clearly so an audit cannot reclaim it.
Oracle ULA exit moves, Java audit defense posture, certification framework, and the buyer side moves across the Oracle Database, Java, and EBS estate.
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.
