Full narration of the briefing. Click a section heading to jump the player to that moment.
Unlimited is the least important word in an Oracle Unlimited License Agreement. That sounds like a provocation, and it is the most useful thing anyone can tell you about a ULA, because almost every problem we see comes from customers who read the first word and skipped the rest of the sentence. I am Tom, Claire is with me on the numbers, and this is the Oracle ULA Series from Redress Compliance. Twelve short briefings on what a ULA actually gives you, what it costs, and how to end it well, because how it ends is decided long before it ends.
Here is the whole thing in one sentence. A ULA is a fixed fee for unlimited deployment of a defined product set, across a defined set of legal entities, in defined territories, for a term of three to five years, ending in a certification that converts what you actually deployed into a fixed perpetual licence count. Five parts, and four of them are limits. Products defined, entities defined, territories defined, term defined.
Only the deployment volume is unlimited, and only within those four boundaries. Read your ordering document with that sentence beside it and you will find the boundaries quickly, because they are all written down.
Understand why Oracle offers these, because it explains everything about how they are priced. A ULA is not really a licence sale. It is a support sale. Oracle support runs at twenty two percent of licence value annually, with a default eight percent uplift each year, and once you have certified a large perpetual position that support stream is attached to a much bigger number, for as long as you keep paying it.
So the fee at the front is the visible part, and the annuity behind it is the business. That is not a criticism, it is the model, and knowing it tells you which parts of the deal are actually worth negotiating.
And why do customers take one? Three honest reasons. Genuine growth: you are about to deploy far more Oracle than you hold, and counting every processor as you go would be slower and more expensive. Compliance cover: you have an exposure and the ULA absorbs it.
Or simplicity: one number, one negotiation, no true up conversations for three years. Those are real benefits. But notice that all three depend on deployment actually growing. If your Oracle estate is stable, a ULA is a fixed fee for the right to do something you were not going to do, and the certification at the end is where that becomes visible.
Now the part that matters more than anything else in this series. At the end of the term you certify. You declare how much you have deployed, Oracle checks it, and that number becomes your permanent perpetual entitlement. Not what you might deploy.
What you had running, evidenced, on the day the count froze. That number then governs your licensing position and your support bill for the next decade, long after everyone who negotiated the deal has moved on. It is a single measurement with a very long shadow, and almost nobody prepares for it early enough.
Which is why timing decides the outcome. The certification window itself is short, typically thirty to ninety days around term end, and by then almost nothing can be changed. The work that moves the number happens before it. Start the independent deployment audit twelve months out.
Lock your count at six months. Submit and defend in the final window. Structured preparation of that kind lifts certified quantities by twenty to forty five percent compared with simply reporting whatever the tools happen to show on the day, and that difference is permanent entitlement you either bank or lose.
So here is the move from this briefing, and it takes ten minutes. Find your ULA end date in the ordering document, then mark the date twelve months before it. If that date has passed, your preparation is already late and this series is urgent rather than interesting. Next session we go through what is not in your ULA, because the exposure most customers carry is created by the agreement they believed had removed it.
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