Oracle / ULA
Oracle PULA vs ULA. The 2026 decision pillar.
The PULA never certifies and never ends. The ULA freezes your count and lets you reset support. This pillar shows when each unlimited model wins before the next Oracle proposal lands.
The PULA never certifies and never ends. The ULA freezes your count and lets you reset support. This pillar shows when each unlimited model wins before the next Oracle proposal lands.
An Oracle PULA removes the certification exit that defines a standard ULA, trading a clean walk away for coverage that never ends. This pillar shows how the two unlimited models differ, when each one wins, and where the buyer side leverage actually sits.
Both agreements promise the same thing on the cover. Deploy as much of a named set of Oracle programs as you want, for a fixed fee, without counting every processor.
The difference is what happens at the end. A ULA ends. A PULA does not. That single fact changes the economics, the audit exposure, and the negotiation more than any discount Oracle puts on the table.
A ULA is a term deal. A PULA is a forever deal. The term boundary is the entire story.
A ULA runs for a set term, usually three years. During the term you deploy unlimited quantities of the named programs. At expiry you certify your deployed quantity, and that count becomes your perpetual entitlement.
A PULA carries the same unlimited deployment right, but with no expiry and no certification event. You keep deploying and you keep paying support. There is no moment where the count is frozen and the meter stops growing.
The table sets the core differences against each other. Treat it as a decision frame, not a price sheet, because every clause is negotiable.
Oracle ULA versus PULA at a glance
| Dimension | Standard ULA | PULA |
|---|---|---|
| Term | Fixed, usually 3 years | Perpetual, no end date |
| Exit event | Certification at expiry | None |
| Deployment right | Unlimited during term | Unlimited, ongoing |
| Support after exit | On certified count | Forever, on the agreement |
| Best fit | Shrinking or stable estate | Persistently growing estate |
White Paper ยท Oracle
Certify or Renew Your Oracle ULA?
The buyer side decision map for your next Oracle ULA event. Read it in your browser.
A PULA is priced as a multiple of the support you already pay, not as a fresh license sale. The support base is the anchor.
Oracle sizes the PULA fee from your current support stream and your projected growth. The published technology price list sets the list values the negotiation discounts from.
The value sits in which programs are inside the agreement. Database Enterprise Edition plus a handful of options behaves very differently from a broad bundle. Read the named set before the price.
Oracle prices the PULA against a growth curve. If you accept an aggressive curve, you fund deployment you may never reach. Model your own curve from real capacity plans first.
A PULA wins when growth is real, sustained, and concentrated on the same Oracle programs. It loses the moment the estate stabilizes.
If your Oracle deployment will keep expanding for a decade on the named programs, the PULA can be cheaper than repeated ULA renewals. The unlimited right keeps pace with growth you would otherwise pay to certify each cycle.
If your estate is flat or shrinking, the PULA is a permanent bill for deployment you stopped adding. A ULA lets you certify, freeze the count, and then reduce support against unused entitlements.
Many estates are moving workloads to Oracle Cloud Infrastructure or to other hyperscalers. A perpetual on premises unlimited right can become a stranded cost as workloads leave the data center.
The standard Oracle account team pitch is that a PULA removes audit risk forever and frees you from ever counting Oracle again, so it is the safe choice for any large estate. We disagree. In roughly 7 of 10 PULA proposals we have modeled against the buyer's real plans, the estate was set to stabilize or move to cloud within three to five years, which made the perpetual support stream a permanent cost on deployment that stopped growing. The buyer side move is to price a timed ULA with a disciplined certification against the PULA across a full ten year horizon, then choose on lifetime support, not on the comfort of never counting again.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
The PULA is sold as the end of counting Oracle. For most estates it is the start of paying Oracle forever for growth that already stopped.
You exit a ULA by certification. You do not exit a PULA at all, which is exactly why the entry decision matters so much.
At ULA expiry you declare deployed quantities and Oracle converts them to perpetual licenses. Certify on a clean, defensible production count, supported by accurate measurement, not on the maximum the estate ever touched.
A PULA only ends if Oracle agrees to convert it, usually into a fixed license count, often on terms that favor Oracle. Plan that conversation years ahead, because you negotiate it from a weaker position than a ULA exit.
After a ULA certification you can review the certified estate for unused options and drop support on what you do not run, within Oracle's support policy rules. A PULA gives you no equivalent moment to reset the support base.
The unlimited right protects you only on the named programs, only within the agreed scope. Everything outside that boundary is normal audit exposure.
Deploying a program that is not named, or in an entity not covered, is a breach the unlimited right does not shield. Oracle License Management Services looks first at the edges of scope.
For a ULA exit, where and how programs run changes the certified count. Soft partitioning on VMware can inflate the count Oracle asserts unless you control the measurement against Oracle's partitioning rules.
A PULA reduces routine audit friction on the named programs, but it does not remove exposure on adjacent products, on cloud counting, or on entities outside scope. Treating it as blanket immunity is how breaches happen.
A ULA runs for a fixed term and certifies to a perpetual license count at expiry, while a PULA is perpetual with no certification event and no end date. The ULA lets you freeze the count and reset support, the PULA keeps the support stream running forever.
No. A PULA, the Perpetual Unlimited License Agreement, has no expiry and no certification event. It only ends if Oracle agrees to convert it into a fixed license count, usually on terms that favor Oracle, so the entry decision matters far more than with a ULA.
A PULA can be cheaper only when Oracle deployment will keep growing for a decade on the named programs. For a flat or shrinking estate it is more expensive, because you pay support forever on deployment that stopped expanding while a ULA lets you certify and reduce support.
At ULA expiry you declare deployed quantities and Oracle converts them to perpetual licenses. Certify on a clean, defensible production count backed by accurate measurement, not on the maximum the estate ever touched, because the certified number sets your support cost forever.
Only partly. A PULA reduces routine audit friction on the named programs, but it does not cover products that are not named, entities outside the agreed scope, or cloud counting questions. Treating a PULA as blanket immunity is how compliance breaches happen.
Choose a PULA when growth is real, sustained, and concentrated on the same Oracle programs for a decade or more. Choose a ULA when the estate is stable, shrinking, or moving to cloud, because then a disciplined certification beats a perpetual support stream.
Cloud migration weakens the PULA case. A perpetual on premises unlimited right becomes a stranded cost as workloads move to Oracle Cloud Infrastructure or another hyperscaler, so model both unlimited options against a realistic migration before you commit to a perpetual agreement.
Accepting the first model Oracle proposes without modeling lifetime support cost. Oracle frames the option that maximizes its support annuity, so buyers should build an independent ten year forecast and compare the PULA against disciplined ULA cycles before deciding.
Yes. After a ULA certification you can review the certified estate, identify unused options, and drop support on what you do not run within Oracle's support policy rules. A PULA gives you no equivalent moment to reset the support base, which is a core reason a ULA can win.
Yes. The choice between a ULA and a PULA sets your Oracle cost for a decade, and the model that looks cheaper in year one often loses across the full horizon. Independent buyer side advisory builds the lifetime comparison Oracle will not put in front of you.
Oracle ULA exit moves, Java audit defense posture, certification framework, and the buyer side moves across the Oracle Database, Java, and EBS estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement and IT asset leaders running the next Oracle renewal or ULA cycle.
Engage independent buyer side Oracle licensing experts. We do not resell. We do not implement. We sit on your side of the table.
See engagement scope, comparison vs Big4 and resellers, and the buyer side framework.
Visit page →The unlimited right is the easy part. The decision that sets your Oracle cost for a decade is whether you ever want the meter to stop, and only one of these two models lets it.
