A ULA and a PULA grant the same deployment right. They differ on one thing: whether you keep the moment where the count freezes and the support base can be reset. This pillar prices that difference.
A ULA and a PULA grant the same deployment right. They differ on one thing only: whether you keep the moment where the count freezes and the meter can be reset. This pillar prices that difference so you can choose between the two instruments rather than be sold one.
Both instruments print the same promise. Deploy as much of a named list of Oracle programs as you want, in named entities, for a fee that does not move with the processor count.
The difference sits entirely in the last clause most people read. A ULA has a date on which the counting stops and the entitlement is fixed. A PULA does not.
You are choosing whether to own an exit event or to sell it. Every other difference between the two agreements is a consequence of that one decision.
During the term, a ULA and a PULA behave the same way. You deploy the named programs without counting, you pay a fixed support figure, and you carry the same exposure on anything outside the named scope.
Oracle's own Software Investment Guide describes the unlimited license grant and the certification obligation that closes it. Read the certification paragraph first, because that paragraph is what the PULA deletes.
At ULA expiry you declare deployed quantities and those quantities become perpetual licenses. Three things happen on that single day.
A PULA has none of those three moments. That is the entire trade, stated plainly.
The table below compares the instruments at the level that matters, which is the contract, not the brochure. Every row is negotiable and several rows are where the money actually moves.
Oracle ULA versus PULA, on the dimensions that decide the choice
| Dimension | Standard ULA | PULA |
|---|---|---|
| Forcing event | Term end, on a known date | None. Nothing ever forces a decision |
| Entitlement at the end | Fixed quantity you declare | Unlimited right, no quantity |
| Chance to reset support | Once, at certification | Never, without buying it |
| Who holds the leverage | Shifts to the buyer as the date nears | Stays with Oracle permanently |
| Entry fee, relative | Baseline | Typically 1.4 to 2.2 times the baseline |
| Cost of getting growth wrong | One term of overpayment | Compounds for the life of the company |
| Reversibility | Can become a PULA at any renewal | Reverts only if Oracle is paid to allow it |
| Divestiture behavior | Certified licenses can be assigned | Divested entity usually loses the right |
Because the certification clause is an option, and options have a price whether or not anyone writes it down. When you sign a PULA you sell that option to Oracle and the discount you receive is the premium.
The reset has value in exactly the situations you cannot forecast today. A divestiture, a platform migration, a workload that moves to a competitor engine, a business that shrinks.
Value the option the way you would value insurance. Estimate the probability that your Oracle footprint is materially smaller in seven years, then multiply it by the support you would stop paying.
Inside the term, deployment is free. The first unit above the certified number is full price, at whatever discount you can negotiate under pressure, with support attached to it forever.
That asymmetry is the reason a ULA rewards deploying hard before the freeze and rewards discipline afterwards. A PULA removes both behaviors, which is genuinely simpler and genuinely more expensive when growth stops.
You can start with a ULA and convert to a PULA at any renewal, and Oracle will welcome the conversation. Going the other way requires Oracle to agree to a conversion, and it prices that agreement.
Across the perpetual agreements Fredrik Filipsson has reviewed since 2020, no customer moved from a PULA back to a timed agreement without paying for the privilege. If the choice is close, take the reversible one.
Model both instruments over ten years, not three. Oracle's comparison almost always stops at the point where the perpetual route still looks cheaper.
The example below uses a support base of four million dollars and a four percent escalator. It is illustrative arithmetic, not a quote, and the ranking is what matters rather than the absolute figures.
Ten year cost ranking under three growth assumptions
| Deployment growth on named programs | ULA route, two disciplined terms then certify | PULA route | Which wins |
|---|---|---|---|
| Flat to 5 percent a year | Support resets once, then flat on a fixed count | Full stream compounds for ten years | ULA, clearly |
| 8 to 12 percent a year | Second term needed, second fee paid | No second fee, no reset | Close. Decide on the option value |
| 15 percent a year and sustained | Three terms, rising fee each cycle | One fee, deployment keeps pace | PULA, if the growth is real |
| Growth then a divestiture in year six | Certified licenses can follow the entity | Right usually does not transfer | ULA, decisively |
On the models we have rebuilt, the perpetual route needs sustained compound growth of roughly 12 to 18 percent a year on the named programs across a full decade before it beats two disciplined ULA cycles.
Very few enterprise Oracle estates grow that way for ten years. The ones that do are usually mid program on a database consolidation or carrying a funded acquisition pipeline with Oracle standardization written into it.
Answer five questions before you look at a price. If you cannot answer them with evidence, you are not ready to choose either instrument.
Five clear yes answers is the only pattern that justifies a perpetual agreement. Four yes answers and one doubt points to a ULA with a well drafted certification clause.
Two or fewer points somewhere else entirely, usually to a straight purchase of what you actually run. Work through the ULA decision framework before you accept that unlimited is the right shape at all.
The common advice, from Oracle and from most resellers, is that a PULA is simply a better ULA because it removes the certification risk and ends the counting forever, so any large and growing estate should prefer it. We disagree, and the reasoning is that this advice treats certification as a risk rather than as an asset. Certification is the single moment in the entire Oracle relationship where the buyer, not the vendor, decides what the number is going to be. Selling that moment away for a discount on the entry fee is the most expensive trade in Oracle licensing, and it is the only one nobody puts a price on. Price it, then choose.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
Certification is not a risk you are being spared. It is the one day in the whole relationship when the buyer decides the number.
Different clauses decide the outcome depending on which instrument you sign. Negotiating a PULA as though it were a ULA is the most common drafting error we correct.
Everything you will eventually own is defined by how the certification clause is worded. Four elements decide whether the exit you paid for actually works.
There is no certification to protect, so the negotiable value moves to the two clauses that govern the annuity and the corporate perimeter.
Cap the annual uplift in the same signature that sets the base, and read the assignment language against your own corporate development pipeline. Oracle's technical support policies govern how the stream behaves once it is set.
Contracts are not tested by forecasts. They are tested by the four corporate events that arrive without warning, and the two instruments respond differently to every one of them.
Three of those four events favor the timed instrument. Only the acquisition case is genuinely neutral, and it is the one Oracle raises most often.
Almost never at random. The proposal arrives when Oracle believes your alternatives are temporarily weak, and recognizing the moment is half the defense.
Separate the two conversations. Settle the audit on the audit's own facts, then decide the instrument question on a clean ten year model with no deadline attached.
If Oracle will only price the settlement inside the unlimited agreement, that is information about the settlement, not about the instrument. Read the renewal negotiation tactics before the second meeting.
One has a certification event and the other does not. A ULA ends on a known date, when you declare deployed quantities and they become your permanent entitlement, while a PULA keeps the unlimited right and the support stream running with no moment where the count is fixed.
The entry fee is typically 1.4 to 2.2 times a comparable three year ULA, but the entry fee is not where the difference lands. The lasting cost is the support annuity, which on a perpetual agreement has no event that lets you reset it.
When deployment on the named programs will compound at roughly 12 to 18 percent a year for a decade and a divestiture is implausible. That combination is rare, and it should be evidenced by funded capital plans rather than by a growth narrative.
Only if Oracle agrees, and it prices that agreement. Conversion runs in the other direction easily, which is why a ULA is the reversible choice and should win when the comparison is close.
No, it narrows it. The unlimited right covers only the named programs in the named entities, so options that are not listed, acquired businesses outside the schedule and incorrect cloud counting all remain ordinary audit exposure.
Ten years at minimum. Oracle's own comparison usually stops at three to five years, which is the window in which the perpetual instrument still looks cheaper, and the ranking frequently reverses after that.
Certified perpetual licenses from a ULA can usually be assigned with the entity that uses them, subject to the assignment clause. A PULA's unlimited right generally does not travel, so the divested business needs its own licenses on day one of separation.
On a ULA it is the certification clause, covering the window, the measurement basis, cloud counting and Oracle's acknowledgement. On a PULA it is the support base with a capped uplift, followed immediately by the assignment clause.
Because the support stream is the durable revenue and the perpetual instrument protects it permanently. That is a rational commercial position for Oracle, and it is precisely why the buyer has to build the ten year comparison independently.
With both, chaired by whoever owns the ten year cost line. The instrument question is a capital structure decision disguised as a licensing one, and it is regularly settled by an infrastructure team that will not be present when the annuity is still being paid.
How a perpetual ULA differs from a ULA, the certification traps, and the exit moves that protect value.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
Engage independent buyer side Oracle licensing experts. We do not resell. We do not implement. We sit on your side of the table.
See engagement scope, comparison vs Big4 and resellers, and the buyer side framework.
Visit page →The unlimited right is the easy part. The decision that sets your Oracle cost for a decade is whether you ever want the meter to stop, and only one of these two models lets it.
