A Perpetual Unlimited License Agreement grants unlimited deployment of named Oracle products with no expiry and no certification exit. Because the agreement never ends, there is no moment to convert deployment into a fixed entitlement, so the value sits with whoever understands the terms best.
A PULA is a Perpetual Unlimited License Agreement. It grants unlimited deployment of named Oracle products with no expiry date and no certification event. A standard ULA ends after a fixed term and lets you certify your deployed quantities into permanent licenses. A PULA never ends, so that conversion moment never arrives. The unlimited right is permanent, and so is the support fee that comes with it.
Perpetual is not the same as free. A PULA removes the one event where a ULA holder normally captures value, the certification, and replaces it with an open ended commercial relationship. Understanding that trade before you sign, or before you try to leave, is the whole game.
The three structures share the unlimited deployment idea but differ at the boundaries. The table below sets them side by side. Treat it as orientation, not contract advice, because the exact rights in your case live in your specific agreement language.
While a PULA is live, broad deployment is genuinely free value. There is no counted quantity that raises your bill, so deploying across new environments, disaster recovery, test, and growth projects costs nothing extra. For an organisation whose Oracle footprint is large and still expanding, that predictability has real worth.
The other edge is that the same permanence removes your exit. With a standard ULA you reach an end date, certify the deployment you built, and walk away holding perpetual licenses for that count. A PULA holder never reaches that door. Leaving becomes a negotiation in which Oracle holds the structural advantage, because the contract gives you no automatic right to convert and depart.
Support continues at the agreed PULA level and carries the usual annual uplift. Deploying more does not raise it, because support is tied to the fee you already pay rather than to a counted number. That is the same mechanic that makes a higher certified count free under a standard ULA, and it is worth stating plainly: under a PULA you can deploy widely without fear of a support increase. The cost question is not how much you deploy, it is whether you ever want the relationship to end and on what terms.
Yes, but not by right. Because there is no certification event, exiting a PULA is a commercial negotiation rather than a contractual step. Buyers who leave successfully usually build leverage first: a clear and defensible picture of current deployment, a credible plan to cap or reduce future Oracle dependence, and a timeline that does not run against an Oracle deadline. The specific levers available to you depend on your agreement, including any conversion, true up, or termination language it contains.
Our named framework for PULA holders runs in four moves. First, read the contract for any conversion or exit language, because some PULAs contain more than buyers assume. Second, measure the true deployment so you know the perpetual value you would want to preserve. Third, model the cost of staying against the cost and feasibility of leaving over a multi year horizon. Fourth, decide deliberately and, if leaving, sequence the moves so you are never negotiating under a clock Oracle controls.
If you hold a PULA, or you are being offered one as a renewal alternative, the next step is to read your specific terms against your real deployment and model the long run cost. Our PULA advisory service does exactly that, and our Oracle ULA certification guide explains the standard exit a PULA removes. For the related decision facing fixed term holders, see the certify or renew assessment.
A PULA is a Perpetual Unlimited License Agreement. It grants unlimited deployment of named Oracle products with no expiry date and, critically, no certification event. Because the agreement never ends, there is no moment to convert deployment into a fixed perpetual entitlement.
No. A standard ULA ends with a certification that locks in your deployed quantities. A PULA has no such exit by design. Leaving a PULA is a commercial negotiation with Oracle, not a contractual right, so the path out depends entirely on your specific agreement language.
Support continues at the agreed PULA level and rises with the usual annual uplift. Deploying more does not raise your support bill, because support is tied to the fee you already pay, not to a counted quantity. That makes broad deployment free value while the agreement is live.
It can be, for an organisation with large, stable, growing Oracle estates that values predictability over an exit. The risk is that perpetual convenience masks perpetual cost. The decision depends on your deployment trajectory and your contract terms, so model it before you sign.
Book a confidential assessment and we will read your terms against your real deployment, then model the long run cost of staying or leaving.