BYOL or License Included. Find the crossover.

This is a purchasing decision, not a technical one. You are choosing which entitlement the workload runs on, and the answer turns on whether the license you would apply is genuinely free, what your support contract lets you cancel, and how much Support Rewards you give up by spending less.

What are you actually choosing between?

Two ways of paying for the same software. License included bundles the Oracle software rights into the cloud rate as one price. Bring your own license applies entitlements you already own and drops you to a lower infrastructure rate.

Oracle describes both models on its bring your own license page, and the applicable rates sit in the cloud price list. What neither document tells you is which one is cheaper for you, because that depends entirely on your existing contract.

What each model actually carries

What bring your own license forfeits

• Simplicity. You now count entitlements in two places and reconcile them, and Oracle can audit the cloud claim like any other deployment.
• Feature headroom. The higher service tiers switch on options. If you own base Enterprise Edition only, those tiers are closed to you.
• Cloud spend. A lower bill sounds like a win until you look at what your cloud spend was buying you in Support Rewards.
• Flexibility to scale down. Entitlement is a fixed asset. Scaling the service below what you own does not refund anything.

What it gains you

• A materially lower rate on the same service, which compounds across a multiple year commitment.
• Value from sunk cost. Perpetual licenses already paid for keep working instead of sitting idle.
• Portability. The entitlement is yours, so it can move to another cloud, back on premises, or into a renegotiation.
• Negotiating symmetry. A customer who can credibly run either model has two prices to compare. A customer who cannot has one.

How do you find the crossover point?

With one inequality, applied per workload. Bring your own license is cheaper when the rate saving over the term beats the support you have to keep paying to hold the entitlement.

The formula

Let D be the rate difference per unit hour between the two models on the same service, H the unit hours the workload consumes in a year, and S the annual support on the licenses you are dedicating to it. Bring your own license wins when D multiplied by H is greater than S.

• Take D from your own quote, not from a blog. It varies by service, edition, service tier and metering unit.
• Take H from measured usage, including whether the service actually stops overnight. Most production databases do not.
• Take S from your support invoice, not from 22 percent of list. Support is charged on the net fee you actually paid.
• Set S to zero only if you can prove it. If the support cannot be cancelled, it is not a saving available to license included either.

The worked example

• The workload. A production database sized at 16 OCPUs, running continuously, which is 140,160 unit hours a year.
• The entitlement. 8 Processor licenses of Enterprise Edition, carrying a list value of 380,000 dollars.
• The support line. At 22 percent of a list value license fee that is 83,600 dollars a year. Use your real invoice, which will normally be lower.
• An illustrative rate delta. At 0.50 dollars per unit hour, the annual rate saving is 70,080 dollars.
• The verdict. 70,080 is less than 83,600, so license included wins if that support could genuinely be cancelled.
• The break even. 83,600 divided by 0.50 is 167,200 unit hours, or roughly 19 units running continuously.

Rebuild that with your own D and S. The point is not the numbers, it is that the crossover sits at a workload size, and workloads above it favor owned entitlement while workloads below it do not.

The support rule that breaks most termination plans

Oracle's technical support policies include matching service level and pricing following provisions. In plain terms, you generally cannot drop support on a subset of licenses within a support set and keep the same pricing on the rest.

That single rule decides more of these comparisons than the rate card does. If cancelling support on the freed licenses reprices the survivors, the saving you modeled on the license included side does not exist.

What does Support Rewards do to the comparison?

It works against bring your own license, and almost nobody puts it in the model. Spending less on Oracle cloud earns you fewer rewards, and rewards come straight off your technology support invoice.

How the program works

• The earn rate. Oracle's Support Rewards program returns 25 cents for every dollar of Oracle cloud spend, and 33 cents for customers holding an unlimited license agreement.
• What it offsets. Technology license support invoices. It does not offset applications support, and it does not become cash.
• The ceiling. You cannot earn more benefit than your technology support bill, so a large cloud estate with a small support bill wastes the surplus.
• The timing. Rewards accrue on spend and are applied against support renewals, so the two lines sit in different budgets and different owners.

The reversal, worked

Take the same workload from the section above and assume license included costs 1.0 million dollars a year of cloud spend while bring your own license costs 400,000 dollars for the same service.

• Headline saving. 600,000 dollars a year in favor of owned entitlement.
• Rewards earned under license included. 250,000 dollars at 25 cents on the dollar.
• Rewards earned under bring your own license. 100,000 dollars.
• Rewards given up. 150,000 dollars, provided your support bill is large enough to absorb them.
• Net saving. 450,000 dollars, not 600,000. The model was a quarter wrong before anyone negotiated a rate.

Now hold an unlimited license agreement and the earn rate becomes 33 cents. The gap narrows further, and on estates with a very large support base and a modest cloud footprint we have seen it close entirely.

Our Support Rewards guide works through the mechanics, and the commitment sizing question sits in OCI cost optimization.

Which options must you own before you can use owned entitlement?

Every option and management pack the service actually uses. This is where bring your own license quietly fails, because cloud database services enable capability by service tier rather than by request.

Tiers switch features on for you

The higher database service tiers include options such as clustering, multitenant consolidation, partitioning, advanced compression, in memory processing and the diagnostics and tuning packs. Under license included that is what you are paying for. Under owned entitlement it is what you must already hold.

• Match tier to entitlement, not to appetite. Selecting a high tier with only base Enterprise Edition owned creates an exposure on day one.
• Watch the packs. Diagnostics and tuning are commonly enabled by default in database services, and they are separately licensed products on premises.
• Check the standby. A read enabled standby uses a licensable option, and the entitlement must cover both sides.
• Record the decision. Keep the tier, the entitlement mapping and the date in one document, because that document is your audit answer.

The double count trap

Applying a license in the cloud while the same license still runs a workload on premises is the most common finding we see on cloud audits. It looks like a saving because the cloud rate drops, and it is a compliance gap on the on premises side.

Resolve it before migration, not after. The test is simple: name the server the license came off, and name the date it was decommissioned or repurposed.

Where the common advice on bring your own license is wrong

The standard advice is that owned entitlement is always cheaper, so default to it whenever you hold any Oracle licenses. We disagree. In roughly four out of ten cloud migrations Fredrik Filipsson modeled in 2024 and 2025 the owned license was still anchoring an on premises workload that could not be retired, so claiming it in the cloud was a double count rather than a saving. In more than half of the remaining cases the support could not be cancelled cleanly, which changed the crossover completely, and almost none of the models had subtracted the Support Rewards forfeited by spending less. Cheaper on the rate card is not the same as cheaper on the invoice, and it is definitely not the same as cheaper after an audit.

White Paper · Oracle

Oracle on Azure & AWS BYOL

Count the Oracle cloud licence before you commit. Read it free.

Read the white paper

How does Exadata Cloud at Customer change the answer?

It tilts the decision toward owned entitlement, for a reason that has nothing to do with the rate card. These estates already own the heavy options, and the service bundles the Exadata software you would otherwise buy separately.

What the subscription already includes

• The Exadata system software. Bundled into the infrastructure subscription, so owned entitlement covers database and options only.
• The hardware refresh. Priced into the term rather than as a capital cycle you manage.
• Oracle operation of the infrastructure, inside your data center, which is usually why the service was chosen at all.
• A minimum configuration. The smallest shape sets a floor whether or not you consume it, so the term commitment is the real number to negotiate.

Oracle publishes the shapes and the commercial model on the Exadata Cloud at Customer pricing page. Read the subscription term and the minimum shape before the rate.

The metering unit changed, and models did not

Oracle moved its Exadata and autonomous database services from OCPU based metering to ECPU based metering. The two units are not interchangeable, and the entitlement conversion is published per service and per metric.

Confirm which unit your quote is written in and use the conversion for that unit. A comparison built on the older unit will land in the wrong place, and the error runs in whichever direction the shape happens to push it.

Why these estates usually keep their entitlement

• They own the options already. Clustering, partitioning and compression are normal in an Exadata estate, so the tier match is straightforward.
• The support is not going anywhere. The rest of the estate keeps it alive, which zeroes the support term in the crossover.
• The workloads are steady. These are not bursty systems, so the unit hours sit well above any sensible break even.
• The alternative is not public cloud. Data residency drove the decision, so the comparison is against staying on premises, not against another region.

More detail sits in our Exadata Cloud at Customer guide and the wider Cloud at Customer guide.

Four numbers decide this, and the rate card is the smallest of them. Support you cannot cancel, options you do not own, and rewards you stop earning are the other three.

What should a buyer do next?

Decide per workload rather than per estate. Mixing the two models across a portfolio is normal and usually optimal.

1. Inventory the owned entitlements, the options attached to each, and the support set each one sits in.
2. For every license you plan to apply in the cloud, name the server it came off and the date it was released.
3. Ask Oracle in writing what happens to the price of the remaining support if you terminate the freed lines.
4. Take the rate delta between the two models from your own quote, on the metering unit the quote is written in.
5. Compute the crossover, then check the answer against the actual hours the workload runs.
6. Subtract the Support Rewards you forfeit by spending less, capped at your technology support bill.
7. Confirm the service tier you selected only uses options you own, and record the mapping.
8. Choose per workload, then reread the platform question in OCI versus AWS for Oracle workloads and the mechanics in our guide to bringing your own license.

Frequently asked questions

What is the difference between bring your own license and license included?

License included bundles the Oracle software rights into the cloud rate as one price, with Oracle carrying the entitlement. Bring your own license applies entitlements you already own for a lower infrastructure rate, and moves the counting duty and the audit exposure to you.

Is bring your own license always cheaper?

No. It is cheaper only when the rate saving over the term beats the support you must keep paying on the entitlement, and when the license is genuinely released from its on premises workload. Both tests fail often enough that the answer varies workload by workload.

How do I calculate the crossover point?

Multiply the rate difference per unit hour by the unit hours the workload runs in a year, then compare that against the annual support on the licenses you are dedicating to it. If the rate saving is larger, owned entitlement wins.

Can I just cancel support on the licenses I free up?

Usually not cleanly. Oracle's support policies include matching service level and pricing following provisions, so terminating support on part of a support set can reprice the remainder. Ask the question in writing before you build a model that assumes the saving.

How does Support Rewards affect the decision?

It works against owned entitlement. Rewards return 25 cents per dollar of Oracle cloud spend, or 33 cents for unlimited agreement holders, so a lower cloud bill earns less offset against your technology support invoices. Subtract the forfeited rewards from the headline saving.

Do I need to own the database options as well?

Yes, every option and management pack the service uses. Higher service tiers enable clustering, partitioning, compression and the diagnostics and tuning packs, so match the tier to what you actually own rather than to what the workload would enjoy.

What is the double count trap?

It is claiming the same entitlement on premises and in the cloud at the same time. The cloud rate drops, so it looks like a saving, while the on premises side is now short and shows up as a finding in the next audit.

Why does Exadata Cloud at Customer usually favor owned entitlement?

Because those estates already own the heavy options, the support is being kept alive by the rest of the estate, and the workloads run continuously. The Exadata system software is bundled into the infrastructure subscription, so the entitlement only has to cover the database and its options.