What is a PULA?
A PULA is a perpetual unlimited license agreement, an unlimited deployment right for named Oracle products that has no fixed end date and no certification event, so the unlimited grant continues rather than converting to a fixed count. A standard ULA runs for a term, usually a few years, and ends with certification, where the buyer declares deployed quantities that become its perpetual entitlement. A PULA removes that endpoint: the unlimited right simply persists, which is why it appeals to organisations expecting sustained growth in the named products.
The absence of a certification event is the defining feature for an audit holder. There is no moment where the buyer has to count and freeze quantities, so the cliff edge that catches standard ULA holders, where out of scope use suddenly becomes liability at certification, does not arrive in the same form. That does not mean a PULA is risk free. It means the risk lives in a different place, namely scope and the conditions attached to the agreement, rather than in a certification deadline.
Does a PULA remove audit risk?
A PULA does not remove audit risk, because the unlimited grant applies only to the products, entities, and territories the agreement names, and everything outside that scope is ordinary licensable use that an audit can find. The unlimited language covers the box the agreement defines, not the whole Oracle estate. A product not on the named list, a subsidiary that was never joined as a party, or use in an excluded territory sits outside the PULA exactly as it would outside a standard ULA, with no entitlement behind it.
This is the trap for PULA holders who read perpetual and unlimited as total coverage and stop watching scope. Because the agreement never ends, there is no forcing event that prompts a scope review, so out of scope deployment can accumulate quietly for years. When Oracle audits, that accumulated out of scope use is the finding. The unlimited grant is genuinely valuable inside the box, but it offers no protection at all outside it, and an audit is built to probe precisely that line.
| Feature | Standard ULA | PULA |
|---|---|---|
| Term | Fixed, usually years | Perpetual |
| Certification | Required at end | None |
| Scope limits | Named products, entities | Named products, entities |
| Main audit risk | Scope plus certification | Scope and conditions |
What should a PULA holder watch for?
A PULA holder should watch the scope boundaries, acquisitions that bring in unnamed entities, the support cost trajectory, and any event that could be read as ending or breaching the agreement. Scope is first because it is the most common finding: deployments of products not named, or by entities not party to the agreement, are out of scope no matter how unlimited the grant feels. Acquisitions are a frequent cause, because an acquired business brings Oracle estate that the PULA does not automatically cover, and joining it requires deliberate contractual work.
Support cost is the second watch item, since Oracle support runs at roughly 22 percent of license fees with annual escalation, and a perpetual agreement can carry a perpetual and rising support stream that deserves its own scrutiny. The third is the agreement's conditions: some PULAs contain terms about changes of control, divestiture, or other events that can affect the unlimited right, so any corporate change should be tested against the document. Each of these is contract dependent, because the specific named scope and conditions exist only in the signed agreement, and any uncertain item should be flagged as contract dependent.
What is the buyer move for a PULA holder facing an audit?
The buyer move for a PULA holder facing an audit is to establish the scope precisely, map current deployments against it, and treat anything outside scope as the real subject of the audit rather than the unlimited products. Because the unlimited grant defends the named products, the productive defense focuses energy where the exposure actually is: the out of scope deployments and any conditions Oracle is relying on. Reading the agreement first, then building the deployment map, tells the buyer exactly which findings have substance and which do not.
From there the audit is a negotiation like any other. Oracle's preliminary findings arrive inflated at list price, and an independent line by line review of findings typically cuts claims by 60 to 80 percent by separating genuine out of scope use from deployments the PULA already covers. The unlimited grant is a powerful shield for everything inside scope, so the buyer who can clearly draw the scope line removes most of the claim immediately and negotiates only what truly falls outside it.
Why does support cost deserve separate attention under a PULA?
Support cost deserves separate attention under a PULA because the agreement is perpetual, so the support stream attached to it is perpetual too and compounds through annual escalation, which can make support the largest long run cost of the deal. Oracle support runs at roughly 22 percent of license fees with annual increases, and matching service level rules can constrain a customer's ability to drop support on part of an estate without affecting the rest. Over a multi year horizon, a perpetual unlimited agreement can lock in a rising support obligation that dwarfs the original license value.
For a PULA holder, the buyer move is to treat support as its own line of analysis rather than an afterthought to the unlimited grant. That means tracking the support base, understanding the matching service level constraints in the agreement, and modeling the escalation over the years the PULA will run. Options such as offsetting support spend through OCI consumption under Support Rewards may apply depending on the arrangement, and any such mechanism is contract dependent and should be checked against the actual terms. Watching support deliberately keeps the perpetual agreement from becoming a perpetual and silently growing cost.
The next step
This article is part of our ULA and Oracle Agreements cluster. Read the pillar, the Oracle license compliance guide, for the full picture, and these related reads: deployments outside ULA scope, and the clauses that decide audit outcomes.