A PULA is a perpetual unlimited license agreement. It keeps the unlimited deployment of a ULA but removes the certification exit, so you never convert your deployment into a fixed owned count. That single difference changes the economics and the questions you should ask before signing one.
By the Meridian advisory team · Ex Oracle licensing analysts · Updated June 2026
A PULA is a perpetual unlimited license agreement. It grants unlimited deployment of named Oracle products for as long as the agreement remains in force, with no fixed term and no certification event at the end. A standard ULA reaches a term boundary and forces a decision; a PULA simply continues. Because it never ends in the ordinary course, it never reaches the moment where deployment is converted into a defined perpetual entitlement. You hold the unlimited right indefinitely, you pay support against the agreement indefinitely, and you never crystallise a number you own outright. That permanence is the whole point of the structure, and it is also the reason a PULA needs a different kind of analysis than a term ULA.
A PULA is a perpetual ULA with no certification exit. The unlimited deployment looks identical to a term ULA, but the missing exit means you cannot convert to owned licenses on a schedule and cannot use a certification deadline as leverage. Understand that you are buying permanence, not a path to ownership, before you sign.
The differences are structural and they compound. A standard ULA is a fixed term deal, usually three to five years, that ends in a choice between certifying and renewing. Certification converts your deployed quantities into permanent owned licenses, declared in a letter that the contract typically asks a senior executive to sign. From that day you own a fixed count and your support continues at the level you held. A PULA removes that conversion. There is no term end, so there is no certification, so there is no day on which the unlimited right becomes a fixed asset you own.
In a term ULA the clock drives everything. The approach of the term end is what gives a buyer leverage and what creates the once in a cycle opportunity to maximise the certified count. A PULA has no clock. There is no expiry to plan toward, no freeze window, no deadline that concentrates the mind on either side of the table. For a buyer who values certainty above optionality this can be attractive, but it also removes the natural moment to reassess whether the deal still fits.
At a term ULA exit, certification turns deployment into ownership. That is the mechanism that lets a customer walk away from Oracle pricing with a permanent estate. A PULA offers no such mechanism by default. You can deploy without limit, but you never own a counted, perpetual entitlement that stands on its own if the relationship changes. Your rights live and die with the agreement, which makes the contract language around termination, assignment, and corporate change far more important than in a term deal.
Support fees do not fall away in either structure, but the difference in framing matters. After certifying a term ULA you pay support against a fixed, owned count that you could, in principle, reduce or reshape over time. Under a PULA the support obligation continues against the agreement for as long as you hold it, with no certification moment that resets the basis. Over a long horizon that steady, uncapped support stream is often the largest number in the whole arrangement.
The table below sets the two structures next to each other. The specifics always come down to your contract, but the shape of the difference is consistent.
| Feature | Standard ULA | PULA |
|---|---|---|
| Term | Fixed, usually three to five years | Perpetual, no fixed end |
| Exit event | Certify or renew at term end | None built in |
| Convert to owned licenses | Yes, through certification | No, by default |
| Deployment right | Unlimited during the term | Unlimited while in force |
| Support | Continues, fixed at the ULA level after exit | Continues against the agreement indefinitely |
| Natural leverage point | The term end deadline | None, unless negotiated |
There is no built in certification exit, but a PULA is not necessarily a life sentence. An exit, where one exists, is a negotiated conversion rather than a contractual right. A buyer might agree a one time crystallisation of the deployment into a fixed perpetual count, or restructure the agreement in the course of a wider commercial conversation. Whether that is achievable, and on what terms, depends entirely on the specific language of the agreement and on the leverage available at the moment. This is the central practical fact about a PULA: where a term ULA gives you a procedural off ramp, a PULA gives you a problem to negotiate. We cover the moves in negotiating out of a PULA.
Consider an organisation, figures indicative only, weighing a five year ULA against a PULA for the same product set. The ULA lets it certify a measured deployment into owned licenses at year five and then hold support flat against that count. The PULA keeps deployment open forever but leaves support running against the agreement with no conversion. Over a ten to fifteen year horizon the second path often costs more in support alone, even before the lost ownership is counted.
None of this makes a PULA the wrong choice in every case. For an organisation with genuinely unpredictable, fast growing Oracle demand and a strong preference for never revisiting the question, the permanence can be worth real money. The danger is signing one without understanding what has been traded away. A PULA is not simply a longer ULA. It is a different instrument that removes the conversion event and the deadline that give a term ULA its value at exit. The buyer who reads it that way can price it properly. The buyer who treats it as a convenience usually overpays for permanence it did not need.
If a PULA is on your table, or already signed, the next questions are how to value it and how to leave it. Read negotiating out of a PULA for the routes to a conversion, and capped ULAs explained for the other variant that limits the unlimited right. Our PULA guide is the pillar that frames perpetual agreements end to end.
A PULA is a perpetual unlimited license agreement. It grants unlimited deployment of named Oracle products for as long as the contract remains in force, with no fixed term and no certification event. Because there is no exit to certify, the deployment is never converted into a fixed perpetual entitlement the way a standard ULA is at its end.
A standard ULA runs for a fixed term, usually three to five years, and ends in a choice to certify or renew. Certifying converts your deployed quantities into permanent owned licenses. A PULA has no term end and no certification, so you keep unlimited deployment but never own a fixed count and you keep paying support indefinitely against the agreement.
There is no built in certification exit, but a PULA can sometimes be exited through negotiation, typically by agreeing a one time conversion to a fixed perpetual count or by restructuring the agreement. The outcome depends entirely on the specific contract language and on leverage, so a PULA exit is a negotiation rather than a procedural right.