A PULA is sold as the unlimited contract that never ends. The truth is narrower. The product scope is fixed, the certification clause still bites, and the exit math is the only number that matters before signing.
A Perpetual Unlimited License Agreement is a fixed price, fixed scope, no expiry contract that grants unlimited deployment rights for a defined Oracle product list. There is no end date and no scheduled certification. The customer keeps the right to deploy any quantity of the named products in perpetuity.
The trap sits in three places. The product scope is locked at signature, not at the end. The audit clause still applies for any product outside the PULA scope. The exit math runs at signing because the contract has no natural end point.
Read this guide alongside the Oracle knowledge hub, the Oracle advisory practice, the Oracle ULA reference, the PULA exit framework, the ULA decision framework, and the Vendor Shield subscription.
The PULA and the ULA share the unlimited deployment idea. The difference is duration and the certification mechanic. A ULA runs for a fixed term, usually three years. At the end the customer certifies installed quantities and receives that count as a perpetual license.
| Dimension | ULA | PULA |
|---|---|---|
| Term length | Three years typical | No end date |
| Certification | Mandatory at exit | None scheduled |
| Product scope | Fixed at signing | Fixed at signing |
| Support fee | Paid for term, plus exit count | Paid in perpetuity |
| Exit complexity | Certification driven | Buy back driven |
| Best fit | Growth and consolidation | Stable mature estate |
The PULA scope is the contract. Every product the customer wants to deploy must sit on the schedule. Anything missing falls outside and stays inside the regular license and audit regime.
Procurement signs a PULA for Database Enterprise Edition and three option packs, then a development team installs a fourth pack a year later. The audit clause is still live. Oracle bills the unauthorized option pack at list, retroactively, with support back charges.
A PULA carries no scheduled certification. The audit clause survives. Oracle can still audit any product outside the PULA scope at any time. The PULA does not buy peace on adjacent Oracle estates.
Most PULA disputes come from acquisitions. The default scope covers the named entity at signing. An acquisition by that entity inherits Oracle exposure on the prior owner's books, not the PULA scope. The buyer side discipline is to negotiate an MA extension clause at signing for a defined revenue ceiling.
The clause is rare and rarely volunteered. Ask for it before the contract goes to legal.
The PULA license fee is calculated from the customer's current Oracle position plus an expansion premium. Oracle takes the existing license value, projects a three to five year deployment curve, and prices the PULA at a discount to that projected list value.
| Estate size | Current spend | PULA license fee | Annual support |
|---|---|---|---|
| Mid market | $2M to $5M | $8M to $15M | $1.8M to $3.3M |
| Large enterprise | $5M to $15M | $20M to $45M | $4.4M to $9.9M |
| Global enterprise | $15M to $50M | $60M to $150M | $13M to $33M |
Oracle support is paid as a percentage of the PULA license fee, typically 22 percent. The annual uplift sits in the contract. Negotiate the uplift cap and the support base at signing because there is no certification reset down the road.
A PULA has no renewal date. The lever set runs at signing and at any in life amendment. The buy back option becomes the natural exit point if the estate shrinks.
A PULA looks like the contract that ends the audit conversation. It is not. The audit clause stays alive on every product outside the schedule, and the support meter never stops. Sign the PULA on what you will deploy, not on what you might.
The seven step checklist below is the buyer side starting position for any PULA evaluation.
A ULA runs for a fixed term, usually three years, and ends in a certification that converts unlimited use to a perpetual license count. A PULA has no end date and no certification. The customer keeps unlimited rights to the named products in perpetuity, with annual support paid each year.
No. A PULA grants unlimited rights inside the named product schedule only. Oracle keeps the right to audit any product outside the schedule, any options pack that is not licensed, and any deployment on a cloud not listed in the cloud authorization clause. The audit clause survives the unlimited grant.
Oracle prices the PULA from the customer's current spend plus a projected expansion curve, typically three to five years. The license fee usually lands at three to four times the current annual spend. Annual support runs at twenty two percent of the license fee with the contractual uplift each year.
Only if the contract carries an MA extension clause. The default PULA covers the named entity at signing. Acquired companies retain their separate Oracle contracts unless the PULA explicitly extends to a defined revenue ceiling. Negotiate the MA clause before the deal goes to legal.
It can be. The math favors the PULA when the estate is mature, predictable, and likely to remain Oracle heavy for a decade or more. The math turns against the PULA when migration to alternative platforms is on the roadmap or when growth is concentrated outside the named products. Run the comparison before signing.
Redress runs PULA engagements inside Vendor Shield, the Renewal Program, and the Benchmark Program. The work covers the scope schedule, the cloud authorization, the support cap, the MA extension, and the buy back clause. Always buyer side, never Oracle paid.
Redress runs Oracle PULA engagements inside the Vendor Shield subscription, the Renewal Program, the Benchmark Program, and the Software Spend Assessment. The Oracle commercial leadership sits with the founders.
Read the related benchmarking framework, about us, locations, and contact pages.
A buyer side reference on the ULA certification math, the PULA scope schedule, the cloud authorization clause, and the MA extension. Built from hundreds of Oracle engagements.
Independent. Buyer side. Written for CIOs, CFOs, and procurement leaders carrying Oracle estates. No Oracle influence. No sales kickback.
Open the white paper in your browser. Corporate email only.
Open the Paper →A PULA looks like the contract that ends the audit conversation. It is not. The audit clause stays alive on every product outside the schedule, and the support meter never stops. Sign the PULA on what you will deploy, not on what you might.
We have run 500+ enterprise clients across 11 publishers. Every engagement starts with one conversation.
PULA scope schedules, ULA certification patterns, support cap negotiations, cloud authorization clauses, and the wider Oracle commercial leverage signals across every renewal we run.
Once a month. Audit patterns, renewal benchmarks, vendor commercial signals across Oracle, Microsoft, SAP, Salesforce, IBM, Broadcom, AWS, Google Cloud, ServiceNow, Workday, Cisco, and the GenAI vendors. No follow up sales pressure.
Free providers (Gmail, Yahoo, Outlook) cannot subscribe. Work email only. Unsubscribe in one click.
