Home · Deal Types · PULA · Perpetual ULA
§ Deal Type 02 · Pool of Unlimited Licenses

The PULA looks unlimited. The clause that matters is in the cap.

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.

Deal file · PULA
StructurePerpetual
CertificationNone
TermForever
Fee profile2x to 3x of ULA
Support upliftOften capped at 0%
Best forLong horizon · stable estate
Article
I

What a PULA actually is.

Structure
Perpetual unlimited

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.

Article
II

PULA vs ULA vs renewal.

Decision matrix
Three structures
Attribute
ULA
PULA
Term
2 to 5 yearsFixed period
PerpetualNo end date
Certification
Required at term endCount converted to perpetual
NoneNo counting event
Upfront fee
LowerFee plus support uplift
2x to 3x higherPremium for perpetual rights
Annual support
Resets at certificationBased on certified quantity
Often capped0% uplift negotiable
Product list
Negotiable at renewalCan adjust at term end
Frozen at signatureLocked forever
Audit exposure
During and afterCertification can be challenged
Eliminated for in scopeOut of scope still audited
Cloud rights
NegotiableBYOL rules apply
Negotiable upfrontWorth more upfront
M&A flexibility
Subsidiary clause limitsNegotiated at signing
BetterPermanent rights extend
Right structure for
Defined growth windowThen certify out
Long horizon stable estateMulti decade Oracle commitment
Article
III

Four PULA traps the deal team rarely flags.

Negotiation pitfalls
Read before signing
§ Trap 01 · Product list freeze
The product list is locked forever.
A PULA names products. Anything not named, you do not have rights to, ever. Oracle's product portfolio changes over time. A PULA signed in 2026 will not cover an Oracle product launched in 2030. The product list deserves a full Oracle architect review before signature.
§ Trap 02 · Support uplift compounding
A 4% uplift compounds for a decade.
Unless capped at 0%, the annual support escalator runs forever. A 4% annual uplift compounds to 80% over fifteen years. The escalator language is more important than the upfront fee on a PULA. Cap at 0% or at CPI is achievable.
§ Trap 03 · Entity scope language
The named entity may not include you in five years.
Acquisitions, divestitures and corporate restructurings can move the legal entity that holds the PULA outside the parent group. The subsidiary and M&A clauses must cover affiliates, successors and assigns, with explicit language for divestiture carve outs.
§ Trap 04 · Cloud rights ambiguity
Public cloud is the silent battleground.
AWS, Azure and Google Cloud deployment is the most common dispute area on PULAs signed before 2022. Modern PULAs must address BYOL conversion ratios, OCI Universal Credits inclusion, and AWS or Azure deployment rules explicitly.
Engagement Outcome

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.

Director of IT ProcurementHealthcare network · Long horizon Oracle commitment
Article
IV

What we do on a PULA.

Engagement scope
End to end

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.

Article
V

Related files.

Read alongside
Most relevant
Service · ULA

ULA Negotiation Advisory

Fixed fee or success fee advisory for new ULAs, ULA exits, PULA conversion and renewal vs certify decisions.

Open service page
Deal type · ULA

Oracle ULA deal structure

The standard ULA structure, certification event, deployment counting rules, and typical Oracle tactics across the term.

Open deal page
Dossier 02

ULA Exit Framework

Step by step guide to certifying out of a ULA cleanly. Includes deployment counting methodology, certification templates, and Oracle response patterns.

Download dossier
Field notes · Pillar

Complete ULA Guide 2026

Pillar guide to ULA negotiation, exit certification, PULA, cloud rights, M&A clauses and renewal vs certify decision tree.

Read pillar
Product · Database

Oracle Database in a PULA

How EE, options, packs and named user metrics behave under a PULA, and what to negotiate at signature.

Open product page
Service · Contract

Contract Review

OMA, order document and PULA amendment review. We flag every dangerous clause and suggest precise edits.

Open service page

Considering a PULA?

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 Quote
The Negotiator

Monthly intelligence.

Oracle sales tactics, ULA and PULA case patterns, audit risk shifts. First Monday of every month.