A PULA is a perpetual ULA with no certification exit. It trades the one time chance to convert deployment into a fixed entitlement for the certainty of never recounting again. That trade favours a narrow set of buyers, and the decision should assume the agreement is effectively permanent.
A PULA is presented as the simplest of Oracle's unlimited agreements: deploy what you like, forever, and never run a certification again. For the right organisation that simplicity is genuine value. For the wrong one it is a perpetual support obligation with no exit and no offsetting upside. The difference is entirely about your trajectory, your product mix, and how confident you are that both will hold for many years. This article sets out what a PULA is, the trade it asks you to make, and the profile of buyer it actually suits, so you can tell which side of the line you are on before the conversation with Oracle gets that far.
A PULA is a Perpetual Unlimited License Agreement. It grants unlimited deployment of a named set of Oracle products with no end date and no certification step. A standard ULA runs for a fixed term, usually three to five years, and ends with a certification that converts your deployed quantities into a fixed perpetual entitlement. A PULA removes that ending. There is no term to expire, so there is no moment at which you count, declare, and convert. The unlimited right simply continues, and so does the support obligation that funds it. That single structural difference, the absence of a certification exit, is the whole story of when a PULA helps and when it hurts.
A standard ULA has a door marked exit. A PULA does not. Only walk into a room with no exit if you are sure you never want to leave.
In a standard ULA the certification is the buyer's one chance to convert unlimited deployment into permanent, owned value. Handled well, that count often lands far higher than first expected, and the result is a large perpetual entitlement you keep regardless of what you pay in support afterward. A PULA gives that up. You never certify, so you never crystallise a number you own outright; instead you hold an unlimited right that depends on continuing to pay support. In exchange you get certainty: no recount, no exit project, no audit risk window that opens the day after certification, and no anxiety about whether a given deployment will count. The question is whether that certainty is worth more to you than the convertible value you forgo.
A PULA can suit an organisation with sustained, large, and genuinely unpredictable growth across a stable set of Oracle products, where the operational certainty of never recounting outweighs the value of a one time certification. If you expect to keep deploying heavily for many years, never plan to migrate off the products in scope, and would find a recurring exit project genuinely costly to run, the perpetual right can be the cleaner arrangement. It also appeals where the products are deeply embedded and switching is implausible, so the long term support commitment is one you would carry in some form anyway. In those cases the PULA removes friction without removing much value, because the certification value you forgo was always going to be reinvested into more unlimited deployment.
A PULA rarely suits an organisation whose Oracle footprint is flat or shrinking, because the perpetual support obligation then funds an unlimited right you are not using. It does not suit a buyer who may migrate off the products, move workloads to a different platform, or consolidate after an acquisition, because the commitment outlives the need. And it does not suit anyone who values the owned, convertible entitlement that certification produces, since a PULA never produces it. If there is a credible future in which you would want to reduce your Oracle estate or leave it behind, the absence of an exit is a serious cost. The honest test is whether you can picture wanting out within ten years; if you can, a standard ULA with a real certification exit is usually the safer structure.
| Dimension | Standard ULA | PULA |
|---|---|---|
| Term | Fixed, usually three to five years | Perpetual, no end date |
| Exit | Certification converts deployment to fixed entitlement | No certification exit by design |
| Owned value at exit | Large perpetual entitlement you keep | None crystallised; right depends on support |
| Best fit | Most buyers who want a convertible asset | Sustained heavy growth, no plan to ever leave |
| Main risk | Getting the count and timing right once | Perpetual support with no offsetting exit |
Not through certification, because a PULA has no certification exit by design. The practical routes out are to stop paying support and drop to the licenses you can evidence, which forfeits the unlimited right and can expose you to a true up on past deployment, or to negotiate a conversion with Oracle, which is a fresh commercial discussion rather than a built in mechanism. Neither is clean, and neither is guaranteed to be available on terms you like. That is why the decision to enter a PULA should be made as if it were permanent. If the analysis only works because you assume an easy exit later, the analysis does not work.
The PULA decision turns on your long term cost and growth picture, so model both before you commit. Read PULA support fees over the long term for the cost side and hybrid ULAs with cloud rights for a structure that can sit between a standard ULA and a PULA. For the full picture of perpetual and capped agreements, see the PULA guide.
A PULA is a Perpetual Unlimited License Agreement. It grants unlimited deployment of named Oracle products with no end date and no certification step. Because there is no term that ends, there is no exit at which you convert deployment into a fixed perpetual entitlement, so the unlimited right and the support obligation continue indefinitely.
A PULA can suit an organisation with sustained, large, and unpredictable growth in a stable set of Oracle products, where the certainty of never recounting and never running another exit outweighs the value of a one time certification. It rarely suits an organisation whose Oracle footprint is flat or shrinking, or one that may migrate off the products, because the perpetual support obligation then has no offsetting upside.
Not through certification, because a PULA has no certification exit by design. You can stop paying support and drop to the licenses you can evidence, but that forfeits the unlimited right and exposes you to a true up on past deployment. Any exit from a PULA is a negotiation, not a built in mechanism, so the decision to enter one should assume it is effectively permanent.
Book a confidential assessment and we will model your growth, your product mix, and your long term support exposure so the perpetual decision is made on evidence, not on a sales pitch.