When your Oracle ULA excludes public cloud or imposes a continuous deployment rule your instances cannot meet, the certifiable value moves to on premises capacity and OCI. The opportunity is still there. It just sits where the contract agrees to count it.
By the Meridian advisory team · Ex Oracle licensing analysts · Updated June 2026
Move the value to where the contract agrees to count it. Cloud counting is contract specific, and many ULAs are unfriendly to third party cloud. Some require deployments in AWS or Azure to run for 365 continuous days before they count toward the certification baseline. Some exclude public cloud entirely. Many are silent on Google Cloud, and silence is not inclusion. If your workloads cannot satisfy those terms, the certifiable estate is your on premises capacity and OCI. Maximization does not disappear when cloud will not count. It relocates, and the organisations that plan for that early keep the full value of the unlimited term.
Read your cloud counting clause first, not last. The wording decides whether your cloud estate is an asset at certification or a number Oracle will discount. Once you know what counts, you can place real workloads where they convert into permanent entitlement.
The reason is in the contract, not the technology. Oracle has refined ULA cloud language over years, and the common patterns all work in its favour at the exit. Understanding which pattern your agreement uses tells you exactly what to do.
This is the most common trap. The clause says that to count toward your certified baseline, a deployment in an authorised cloud must have run continuously for the 365 days before certification. Burst capacity, autoscaled instances, and anything stood up in the final year all fail the test. A large cloud footprint can shrink to almost nothing the moment this rule is applied, which is why reading it early changes the whole plan.
Some agreements simply do not recognise third party cloud for certification. Whatever you run in AWS or Azure, it adds nothing to the count. Where this is the wording, there is no clever reading around it, and the energy is better spent on the estate the contract does recognise.
Where a contract says nothing about a provider, the safe assumption is that it does not count. Buyers sometimes read silence on Google Cloud as freedom. Oracle reads it the other way at the exit. Treat an unaddressed provider as outside scope unless your specific terms say otherwise.
When cloud will not count, two routes carry the maximization opportunity: on premises capacity and OCI. Both are real deployment, both are countable when handled properly, and both reward planning that starts well before the certification window.
Workloads running in public cloud that the contract will not count can often be brought back to on premises hardware where they sit squarely in countable scope. This is not a paper exercise. The workload genuinely runs on your own infrastructure, it is evidenced like any other on premises instance, and it counts. Repatriation takes time and capacity, so it has to be scheduled against the term rather than attempted in the final weeks. Done early, it converts stranded cloud value into permanent entitlement.
It depends on your contract, but OCI is far more often countable than AWS or Azure. Many agreements treat Oracle Cloud deployments more favourably, sometimes without the 365 day constraint that applies to third party cloud. Where your wording supports it and the architecture fits, placing real workloads on OCI in time to count is one of the cleanest ways to grow a certified position when public cloud is closed off. As always, the specific clause governs, so confirm before you move anything.
The numbers below are indicative and shown only to illustrate the mechanics.
| Estate at term end | Raw processors | Counts under this ULA |
|---|---|---|
| On premises production and test | 300 | 300 |
| Disaster recovery, on premises | 80 | 80 |
| AWS, deployed 4 months ago | 160 | 0 (fails 365 day rule) |
| OCI, deployed 14 months ago | 120 | 120 |
Taken at face value the estate looks like 660 processors. Under this agreement, the AWS footprint contributes nothing because it cannot meet the continuous deployment rule, so the naive count is 500. Now apply planning. The 160 processors of AWS workload are repatriated on premises eight months before certification, where they count in full. The certified position rises from 500 to an indicative 660, recovering the value that the cloud clause would otherwise have erased. The difference was not luck. It was reading the clause in time to act on it.
Every move that rescues a count needs runway. Repatriation needs capacity and change windows. An OCI build needs migration time. Begin the cloud counting review in the final eighteen months, not the final quarter, or the options close before you can use them.
Start by reading the cloud counting clause and classifying every cloud workload as countable, conditional, or excluded under your exact terms. For the conditional and excluded workloads, decide between repatriation on premises and a move to OCI based on architecture, cost, and the time you have left. Schedule those moves against the term so each deployment is genuine and settled well before certification. Build the evidence file as you go, because an on premises or OCI instance counts only if you can show it existed and ran within the term. Treat this as a programme that runs over months, not a task for the closing weeks.
This is one half of a larger discipline. To keep the count defensible while you grow it, read legitimate deployment versus gaming the ULA, and to translate a maximized estate into a number your board understands read measuring the value of the certified position. For the complete method, our Oracle ULA deployment maximization guide is the pillar that ties cloud, on premises, and OCI together.
Move the value where it does count. If your agreement excludes AWS and Azure or imposes a continuous deployment rule the workloads cannot meet, the certifiable estate is your on premises capacity and OCI. Build out real workloads there within the term and count those, rather than relying on public cloud instances the contract will not recognise.
It depends on your contract, but OCI is far more often countable than third party cloud. Many agreements treat Oracle Cloud deployments more favourably than AWS or Azure. Confirm the exact wording, then, where the math works, place real workloads on OCI in time to count toward the certification baseline.
Often yes, and it is a common move when public cloud will not count. Workloads running in AWS or Azure can be brought back to on premises hardware so they sit in countable scope at the exit. The deployment must be genuine and evidenced, and the timing must respect your term, so plan it well before the certification window.