A PULA grants unlimited deployment forever and never certifies. That makes it powerful during heavy growth and expensive once growth stops, because the only number that matters is the support stream you pay in perpetuity. Here is how to read the true cost before you sign or renew one.
A PULA is a perpetual ULA. It grants unlimited deployment of named Oracle products with no end date and no certification exit. Because there is no certification event, you never convert deployment into a fixed entitlement and you never stop paying the support stream attached to it. So the economics are not a one time license value. They are the support fee, paid every year, with no natural moment to reset it. Read a PULA as a permanent annuity to Oracle, then decide whether the unlimited right is worth that annuity for the life of your estate.
In a standard ULA the prize is the certified number. In a PULA there is no certified number, so the prize Oracle keeps is the support stream. Value the stream, not the unlimited badge.
A standard ULA runs for a fixed term, usually three to five years, and ends in a choice: certify the deployed quantities into perpetual licenses, or renew. Certification is the exit. It freezes your entitlement, ends the unlimited right, and lets you eventually challenge the support line that sits on top of those licenses. A PULA removes that exit. The unlimited right continues indefinitely, and so does the support obligation that funds it. You gain permanence and lose the one event where a customer normally captures value and regains leverage.
That single structural difference drives everything else. With no certification, there is no deployment maximization moment, no point at which the count is locked in your favour, and no clean path to third party support or to renegotiating the support base. The flexibility that makes a PULA attractive during expansion is the same flexibility that keeps you paying after expansion ends.
Yes, in a specific shape of organization. A PULA can make commercial sense when you expect sustained, heavy growth across the covered products, you have no realistic plan to leave Oracle, and you would otherwise face repeated true up exposure as you expand. The unlimited right removes that exposure entirely while you keep deploying. The catch is that the support stream is permanent, so the saving only holds for as long as deployment keeps climbing fast enough to justify a fixed, ever present fee. Once growth flattens, the math inverts: you are paying an unlimited price for a stable estate you could have certified and held.
Picture two paths for the same database estate. Under a standard ULA, the organization certifies at exit, locks a defensible perpetual count, and then carries support on that fixed base, with room over time to optimize or move to third party support. Under a PULA, the organization keeps the unlimited right but carries the full support stream every year with no exit and no reset. In years of rapid growth the PULA looks cheaper per deployment. In a flat year five and beyond, the standard ULA holder has a fixed, optimizable cost while the PULA holder still pays the perpetual stream. The crossover point is the question. Figures are indicative and depend on your growth curve and the exact contract language.
Support fees on a ULA continue at the agreed level regardless of how much you deploy, and in a PULA there is no certification at which that base is ever re examined in your favour. This is why the perpetual support line deserves more scrutiny than the unlimited right itself. Model it as a perpetuity. Ask what the present value of paying that fee indefinitely actually is, then compare it to the value of an unlimited right you may not fully use after the first few years. Many organizations sign a PULA for the unlimited comfort and never price the annuity they accepted in exchange.
First, your realistic deployment trajectory across the covered products for the next five to ten years, not the optimistic one. Second, the annual support fee and what it compounds to over that horizon. Third, the counterfactual: what you would certify and hold today under a standard ULA, and what carrying support on that fixed base would cost instead. A PULA is the right deal only when the first number stays steep enough to beat the third for a long time.
There is no certification exit built into a PULA, which is precisely what makes it perpetual. Practically, leaving means one of two hard routes. You can stop support, which terminates the unlimited right and leaves you relying on whatever perpetual licenses are actually documented in the agreement, often far fewer than your live deployment. Or you migrate off the covered Oracle products entirely so the unlimited right no longer matters. Both routes need planning measured in years, not months, and both turn on the exact wording of your agreement around documented entitlements, support reinstatement, and customer definition. Assume nothing here without reading the contract.
If a PULA is on the table, or you already hold one and want to know what it is really costing, start with the PULA pillar guide. Then read the PULA customer definition risk and the cap mechanics and the true up to see how the same structures behave in capped agreements.
A PULA is a perpetual ULA. It grants unlimited deployment of named Oracle products with no end date and no certification exit. Because there is no certification event, you never convert deployment into a fixed entitlement and you never stop paying the support stream attached to it. The economics are the support fee paid forever, not a one time license value.
A PULA can make sense when an organization expects sustained, heavy growth across covered products and has no realistic plan to leave Oracle. The unlimited right removes true up risk during expansion. The trade is that the support stream is permanent, so the saving only holds while deployment keeps growing. Once growth flattens, a standard ULA that you can certify out of usually wins.
There is no certification exit built into a PULA, which is what makes it perpetual. Leaving means ending support, which terminates the unlimited right and leaves you reliant on whatever perpetual licenses are documented, or migrating off the covered products entirely. Both paths need careful planning because the contract was written to keep you in. The answer depends on the exact wording of your agreement.
Book a confidential assessment and we will model the support stream, the growth curve, and the standard ULA counterfactual so you know what a perpetual deal truly costs.