Oracle's Perpetual ULA grants permanent unlimited deployment rights without a certification event. The fee is much higher than a standard ULA and the trap lives in the product list, the support uplift and the cap language.
A PULA is a perpetual unlimited license for a defined product list, a defined geography and a defined entity scope. There is no certification event. Whatever you deploy is what you keep, forever.
Oracle introduced the PULA structure to address a real customer problem. Standard ULAs end with a certification event that converts unlimited use into a fixed perpetual quantity. The certification is stressful, the count is contested and the product list freezes at the certified levels. Once certified, growth above that quantity is a new purchase.
The PULA removes the certification event entirely. You pay a higher upfront fee for the right to deploy without limit, forever, across the named product list in the named geography for the named subsidiaries. Audit risk on the in scope products drops to zero. Compliance for in scope products effectively cannot occur.
That sounds like a buyer win, and sometimes it is. The PULA is the right structure for organisations with a stable Oracle product mix, a long planning horizon and an environment that is likely to keep growing on Oracle. It is the wrong structure for organisations heading toward cloud migration, divestiture or a multi vendor strategy. The fee is paid upfront and the optionality is paid for forever.
A standard PULA quote at $14M. After scope negotiation and support cap at 0% the same PULA closed at $8.6M. The product list was tightened from 22 names to 14.
1. Decision support. Before any PULA negotiation we run the math. Three scenarios: certify out of your current ULA, renew the ULA, or convert to PULA. The right answer turns on growth forecast, M&A horizon, cloud migration plan and audit exposure. The PULA only wins when the math says so.
2. Product list discipline. Oracle's first product list is always wider than needed. We tighten it to what your architecture actually uses, with explicit exclusions for products you do not intend to deploy. Every name on the list is paid for. Names off the list cost nothing.
3. Support cap and uplift. The PULA support fee is locked at signature, but the uplift schedule is negotiable. We push for 0% uplift, capped uplift, or CPI linked uplift. On a long horizon deal, this clause is worth more than the upfront fee.
4. Entity scope and cloud rights. Subsidiary clause, M&A clause, divestiture carve outs, BYOL ratios, OCI inclusion, AWS or Azure deployment language. The contract is the deal. We review every clause.
5. Negotiation. Multi round negotiation alongside your team. Concessions tracked. Final contract reviewed line by line before signature. Fixed fee or success fee.
Fixed fee or success fee advisory for new ULAs, ULA exits, PULA conversion and renewal vs certify decisions.
The standard ULA structure, certification event, deployment counting rules, and typical Oracle tactics across the term.
Step by step guide to certifying out of a ULA cleanly. Includes deployment counting methodology, certification templates, and Oracle response patterns.
Pillar guide to ULA negotiation, exit certification, PULA, cloud rights, M&A clauses and renewal vs certify decision tree.
How EE, options, packs and named user metrics behave under a PULA, and what to negotiate at signature.
OMA, order document and PULA amendment review. We flag every dangerous clause and suggest precise edits.
The PULA decision is irreversible. Send the intake and a named lead advisor replies within 48 hours with a scoped engagement letter and a recommended model.
Get a QuoteOracle sales tactics, ULA and PULA case patterns, audit risk shifts. First Monday of every month.