Full narration of the briefing. Click a section heading to jump the player to that moment.
There is a second version of this agreement, and it is sold as the simpler one. The Perpetual Unlimited License Agreement, the PULA. No term end, no certification milestone, no counting exercise, no expiry to plan around. Your deployment rights continue for as long as you keep paying support.
To a team that has just been through a difficult certification, that sounds like relief. I am Tom, Daniel is with me, and this session is what you are actually trading away when you accept it, because the thing being removed is the only exit the ULA ever gave you.
Start with what certification day actually is, because you only appreciate it once it is gone. It is the day your relationship with Oracle is renegotiable. You count what you deployed, it becomes yours permanently, and then you decide: renew, walk away with the perpetual pool, move to third party support, consolidate, migrate. That is genuine optionality, and it arrives on a known date you can prepare for.
A PULA deletes that day. There is no moment when the agreement naturally ends, so there is no moment when you have leverage without manufacturing it.
Then look at the economics, because they run in a direction people find counter intuitive. Under a PULA, once you pass the break even point, every additional deployment is free at the licence layer. That is the attraction. But support is not free, and it is calculated against a licence value that keeps inflating as you deploy.
Five years in, most PULA holders are paying support against a licence value many multiples of what they would have paid at processor list price for the estate they actually run. And unlike a ULA, there is no certification at which that base gets fixed and examined.
Now the limitation that surprises people most. A PULA generally cannot be amended to expand product scope. The product list you sign is the product list you have, permanently. Oracle releases something new, your architecture moves, a team needs a capability that did not exist when you signed, and that is a separate purchase at whatever the price is then, negotiated by a customer with no term end and therefore no leverage.
Combine that with a perpetual support obligation and you have a long relationship with fixed scope and no natural renegotiation point. Price that honestly before you agree to it.
To be fair, there are estates where a PULA is the right answer, and it is worth being precise about which. Very large Oracle deployments that will keep growing indefinitely on a fixed product set, where the organisation is certain Oracle is permanent infrastructure, where the administrative cost of counting genuinely outweighs the flexibility being surrendered, and where nobody is contemplating third party support or a migration. If that is honestly your situation, a PULA can be sensible. If any part of it is aspiration rather than fact, you are buying permanence you do not need, and permanence is the most expensive thing on the price list.
If you do go there, negotiate three things hard, because they are the only levers left afterwards. A support cap, in writing, because support is now a permanent obligation and an uncapped eight percent compounds brutally over an indefinite term. Entity and assignment language that handles acquisitions and divestitures, because the default clauses favour Oracle and you have no term end at which to fix them. And some form of exit or conversion right, even an expensive one, so the agreement has a door.
Also note the PULA does not cover Oracle Cloud Infrastructure workloads by default, which surprises customers who assumed unlimited included the cloud.
The move from this briefing: if a PULA is on your table, write down what your certification day is worth. What would you certify today, what would that perpetual pool be worth, and what would you do with the freedom it buys, including support alternatives. That number is the price of the option you are being asked to surrender, and it belongs in the comparison. Next session: the money, how a ULA is actually priced, and why year five is the number that matters.
See you there.
Redress Compliance works on contingency: our fee is 25 percent of what we save you. Nothing saved, nothing paid. Independent, buyer side only, never vendor funded. Want Redress to contact you? Reach out and we respond the same day.
Talk to a Oracle negotiator