A capped ULA limits the unlimited right to a stated ceiling. A hybrid ULA folds cloud rights into the agreement. Both change what you can certify at exit, so the variant you sign matters as much as the unlimited promise itself.
By the Meridian advisory team · Ex Oracle licensing analysts · Updated June 2026
A capped ULA grants unlimited deployment of named Oracle products up to a stated ceiling rather than without limit. You deploy freely until you reach the cap, and deployment beyond it is not covered. At certification you can certify quantities up to the cap, so the cap is also the ceiling on the perpetual entitlement you can capture. A capped ULA is, in effect, a large prepaid pool of licenses dressed in unlimited language.
In a capped ULA the cap is the number that matters. If your realistic deployment will press against it, the unlimited framing is cosmetic and you should price the deal as the fixed pool it really is.
A hybrid ULA folds cloud deployment rights into the agreement so that certain cloud usage counts alongside your on premises deployment. The detail is everything. A hybrid ULA only helps if its cloud language matches where you actually run, because the terms vary on which providers qualify, whether a continuous use period applies, and how cloud instances are measured. A hybrid ULA with cloud terms that exclude your provider gives you nothing for the cloud half of your estate.
The four structures sit on a spectrum from most bounded to most open. The table frames them. Treat it as orientation, since the rights in your case live in your specific agreement.
With a standard ULA the prize at certification is your full defensible deployment, however large. With a capped ULA the prize is your deployment or the cap, whichever is lower. That has two practical consequences. First, deploying beyond the cap during the term wins you nothing extra at exit, so the maximization work is about reaching the cap, not exceeding it. Second, if your deployment falls short of the cap, you certify only what you deployed, not the cap itself, so an unused cap is money you paid for and did not convert.
The buyer side discipline in a capped ULA is therefore to deploy deliberately toward the cap during the term and to document it, so that at exit you certify a number close to the ceiling you bought.
A hybrid ULA can let cloud deployment count toward your certified position, which is valuable if your estate is genuinely split between on premises and cloud. The risk is mismatch. Many ULAs require cloud deployments to run for a continuous period, often described as 365 continuous days, before they count, and contracts differ on which providers qualify. If your hybrid terms count one provider but you run on another, the cloud rights do not reach your workloads. Reading the hybrid cloud clause against your real cloud footprint is the step that decides whether the hybrid label is worth anything to you.
Consider a capped ULA with a ceiling of 100 processor licenses. The figures are illustrative.
The under deployed organisation leaves 40 licenses of paid for headroom unconverted. The over deployed organisation gains nothing for the 30 beyond the cap and, worse, may carry a compliance question on that excess. The organisation that lands at the cap captures exactly what it bought. The cap turns certification into a target, not an open ended count.
It depends on your deployment plan and your contract language. A cap is acceptable when it sits comfortably above your realistic deployment over the term, so you are paying for headroom you will use. A hybrid ULA helps only if its cloud terms count the cloud you actually run. The sound method is to model both against your estate before you sign, because both structures change what you can certify at exit, and the certification is where the value is realised. Our deployment maximization playbook sets out the legitimate moves to reach a cap, and the cloud and partitioning sections that decide what counts.
If you are still getting oriented, read what an Oracle ULA is and how it works and what unlimited really means in a ULA. When you want these variants modelled against your own agreement, the Oracle ULA certification guide is the pillar that brings the certification window together.
A capped ULA grants unlimited deployment of named Oracle products up to a stated ceiling rather than without limit. Deployment beyond the cap is not covered. At certification you can certify quantities up to the cap, so the cap sets the ceiling on the perpetual entitlement you can capture.
A hybrid ULA folds cloud deployment rights into the agreement so that certain cloud usage counts alongside on premises deployment. The exact cloud terms vary, including which providers qualify and any continuous use period, so a hybrid ULA only helps if its cloud language matches where you actually run.
It depends on your deployment plan and contract language. A cap is acceptable when it sits comfortably above your realistic deployment. A hybrid ULA helps only if its cloud terms count the cloud you use. Model both against your estate before signing, because both change what you can certify at exit.