Oracle PULA Defined

An Oracle Perpetual Unlimited License Agreement (PULA) is an enterprise software contract that grants an organisation the right to deploy an unlimited quantity of specified Oracle products, with no expiration date on those unlimited rights. The "perpetual" in PULA is the defining distinction from a standard Oracle Unlimited License Agreement (ULA): a ULA grants unlimited deployment rights for a fixed term (typically three to five years) before requiring a certification event; a PULA grants those same unlimited rights indefinitely, for as long as the customer continues paying Oracle's annual support fees.

A PULA is structured around a large upfront licence fee — the "deal price" — which represents the commercial value Oracle assigns to the unlimited deployment rights for the covered products. In return for this upfront payment, Oracle does not cap the number of deployments, servers, users, or environments in which you can use the covered products. You can deploy Oracle Database Enterprise Edition on a thousand servers if you choose — the PULA covers it all.

The annual support fee is 22% of the notional licence value established at the time of the PULA. This fee is paid every year, indefinitely, and increases by 8% per year under Oracle's standard support escalation terms. The PULA persists as long as you pay support. If you stop paying support, the unlimited rights terminate and you must certify your current deployment footprint — converting it into a fixed number of perpetual licences at that point.

"A PULA is Oracle's way of converting your organisation into a permanent, high-value support annuity. Unlimited forever is attractive — but 'forever' means paying Oracle 8% more every year with no natural exit unless you engineer one."

PULA vs Standard Oracle ULA: The Key Differences

Understanding the differences between a PULA and a standard Oracle ULA is essential before entering into either agreement. The two models share the concept of unlimited deployment but differ fundamentally in duration, exit mechanics, and long-term financial impact.

Oracle ULA (Standard)

  • Fixed term: typically 3–5 years
  • Certification required at term end
  • Can exit by certifying and dropping products
  • Natural negotiation point at each renewal
  • Support fees based on certified count post-ULA
  • Lower upfront cost than PULA

Oracle PULA

  • Perpetual — no expiry date
  • No mandatory certification event
  • No natural exit built into the agreement
  • No renewal negotiation leverage point
  • Support fees on full PULA value indefinitely
  • Higher upfront cost than standard ULA

The most commercially significant difference is the absence of a natural exit mechanism in a PULA. Under a standard ULA, the expiry of the agreement creates a structured negotiation moment: you can certify your usage, exit the ULA, and reduce your support fee baseline to reflect your actual deployment. A PULA removes this moment. Without an exit event built into the agreement, your support fees continue on the full PULA value indefinitely — even if your actual Oracle deployment declines, or even if you stop using some of the covered products entirely.

It is also important to note that Oracle does not offer anything called an Enterprise Agreement for technology products. Customers sometimes use the term informally, but the recognised Oracle unlimited licensing structures are: the standard ULA, the PULA, the capped-PULA (sometimes called a Perpetual ULA with a deployment cap), and the Oracle Cloud Services (OCS) agreements. There is no formal "Oracle EA" equivalent to the Microsoft EA or SAP ELLA.

How Oracle PULA Support Fees Compound Over Time

The perpetual and compounding nature of PULA support fees is the most underappreciated risk in Oracle PULA agreements. When organisations model a PULA at the point of signing, they typically assess the first-year or five-year support cost. The compounding effect of 8% annual support fee increases over ten or twenty years produces costs that most organisations have not projected when they signed the agreement.

Consider an organisation that signs a PULA with a $5 million licence value in 2020. Annual support in year one is $1.1 million (22%). With 8% annual increases, that figure reaches $1.59 million by year five, $2.34 million by year ten, and $3.44 million by year fifteen — all for the same set of products and the same licensing entitlement. The cumulative support cost over 15 years exceeds $28 million on a $5 million initial licence investment. This is the economics Oracle has engineered into PULA agreements, and it is why proactive exit planning is essential for any enterprise holding a PULA.

Already in a PULA? Have you modelled your 10-year support cost?

Our advisors specialise in Oracle PULA lifecycle management, including exit strategies and support cost optimisation for perpetual unlimited agreements.
PULA Strategy Review →

When a PULA Makes Strategic Sense

Despite its long-term cost dynamics, an Oracle PULA is genuinely appropriate in certain strategic contexts. The scenarios where a PULA provides clear value are characterised by large, fast-growing Oracle deployments with a long-term commitment to the Oracle technology stack.

Rapidly Growing Oracle Footprint

If your organisation is in a period of rapid expansion — through organic growth, acquisitions, or major technology infrastructure build-outs — and that growth requires continuous deployment of Oracle Database or Oracle Fusion Middleware, a PULA eliminates the licence cost of each new deployment. Every additional database server, every additional Oracle Middleware instance is free under the PULA. This zero-marginal-cost growth model can provide material financial benefit for organisations that would otherwise be purchasing Oracle licences repeatedly as they scale.

Acquisition-Heavy Organisations

Organisations with active M&A programmes often find that acquired entities run Oracle software that must be brought into licence compliance. Under standard licensing, each acquisition may trigger a licence true-up. Under a PULA, Oracle software from acquired entities can typically be covered by the unlimited rights immediately, dramatically simplifying post-acquisition integration from a licensing perspective. The PULA terms must be reviewed carefully to confirm that acquired entities' usage qualifies as covered under the agreement — Oracle's definition of "affiliate" coverage varies by contract — but for many M&A-active enterprises, this is a substantial operational benefit.

Long-Term Oracle Platform Commitment

An organisation that has made a strategic decision to remain on Oracle's technology platform — Oracle Database, Oracle Exadata, Oracle Cloud Infrastructure — for the long term, and has no credible plan to reduce its Oracle footprint, may find that a PULA provides the best combination of deployment flexibility and commercial simplicity. The elimination of per-unit licence purchasing, licence true-up complexity, and ULA certification cycles has real operational value for large enterprises with complex Oracle environments.

PULA Exit Strategies: How to Regain Control

The absence of a natural exit mechanism in a PULA does not mean there is no exit. It means the exit must be engineered proactively — you must create the conditions and the contractual moment to exit, rather than waiting for the agreement to expire.

Voluntary Certification and Exit

At any point in a PULA, the organisation can voluntarily certify its Oracle deployment footprint and request to exit the unlimited arrangement. This converts the PULA into a fixed set of perpetual licences at the certified count. If your actual Oracle deployment is significantly smaller than the PULA's notional value, the support fees on the certified licence count may be substantially lower than the PULA support fees — creating immediate savings. The challenge is that Oracle has no obligation to agree to a mid-PULA certification unless the contract includes this right. Pre-negotiating voluntary exit rights as part of the PULA agreement is therefore critical.

Oracle Cloud Migration

Migrating Oracle workloads to Oracle Cloud Infrastructure (OCI) under Oracle Cloud Services (OCS) terms can create an opportunity to restructure PULA economics. Oracle has commercial incentives to help customers move PULA entitlements into OCI consumption, and some organisations have successfully negotiated a rebalancing of their PULA support cost against OCI credits or OCS subscription fees. This approach requires careful commercial analysis — OCI consumption costs must be compared against the PULA support savings — but it is one of the few levers that Oracle itself will engage with proactively.

Reduced Footprint and Renegotiation

If your Oracle deployment has declined materially since the PULA was signed — through rationalisation, cloud migration of non-Oracle workloads, or third-party support for some Oracle products — you have a commercial argument for renegotiating the PULA value at your next Oracle fiscal year end (Oracle's fiscal year ends May 31). Q4 of Oracle's fiscal year (March through May) is the window when Oracle's sales team has the most flexibility to restructure large deals. A well-documented reduction in your Oracle footprint, presented before Oracle's Q4 close, provides the most leverage for PULA renegotiation.

Oracle Fiscal Year: Oracle's fiscal year ends May 31. The Q4 window (March–May) is when Oracle's sales teams have maximum flexibility to restructure PULA and ULA agreements. This is the optimal window for renegotiation or exit discussions.

Common PULA Contract Traps to Avoid

  • No voluntary exit provision: Never sign a PULA without a contractual right to voluntarily certify and exit. Without this clause, Oracle has no obligation to negotiate an exit, leaving you locked in indefinitely.
  • Unclear affiliate coverage: The definition of which legal entities are covered by the PULA's unlimited rights varies by contract. If your organisation grows through M&A, an ambiguous affiliate definition can create compliance exposure for acquired entities' Oracle usage.
  • Product list lock-in: A PULA locks you into paying support on a fixed list of products indefinitely. If Oracle releases newer products that supersede PULA-covered products, you may end up paying support on products you no longer use. Negotiate PULA terms that allow product list updates or substitutions.
  • No usage reduction provisions: Unlike a standard ULA (where certification locks in a fixed count that can go down as well as up), a PULA has no mechanism to reduce support fees if your usage declines. Build contractual provisions for fee reduction or partial exit if deployment decreases below a defined threshold.
  • OCI exclusion gaps: Some PULA agreements cover on-premises deployment but do not explicitly extend to OCI or Cloud at Customer environments. If cloud deployment is in your roadmap, confirm that the PULA covers it before signing.

Evaluating or renegotiating an Oracle PULA?

Redress Compliance has managed Oracle PULA negotiations, certifications, and exits for enterprises across every industry. Get independent advice before you sign.
Talk to a PULA Specialist →

Frequently Asked Questions

Is a PULA the same as an Oracle Enterprise Agreement?

No. Oracle does not offer an "Enterprise Agreement" for its technology products. The closest equivalent is the PULA — but it is structured differently from Microsoft's EA or SAP's ELLA. Oracle's unlimited licensing vehicles are the ULA (time-limited), the PULA (perpetual), and Oracle Cloud Services (OCS) subscription agreements.

What happens if I stop paying support on a PULA?

If you stop paying Oracle support under a PULA, the unlimited deployment rights terminate. You must certify your current Oracle deployment — documenting every deployed instance of the covered products — and that certified count becomes your perpetual licence entitlement going forward. You lose the unlimited rights but retain a fixed licence for what you have already deployed.

Can a PULA cover Oracle Cloud at Customer deployments?

Yes, but only if the PULA contract explicitly includes Oracle Cloud at Customer. Some older PULA contracts were written for on-premises deployment and do not automatically extend to Cloud at Customer. If Cloud at Customer is relevant to your architecture, confirm coverage in the contract language before deployment.

How do PULA support fees compare to standard Oracle support?

PULA support fees are calculated at the same rate (22%) as standard Oracle support — but applied to the full notional PULA licence value, not to individual product licence counts. This means PULA support can be significantly higher than support on an equivalent standard licence portfolio, particularly as the 8% annual escalation compounds over time.