Oracle PULA & Pool of Funds: ULA vs PULA, Support Lock-In & Exit Reality — 2026 Guide

A ULA (Unlimited License Agreement) is a fixed-term Oracle contract granting unlimited deployment of named products in exchange for an upfront fee; at the end of the term you certify usage into perpetual licences. A PULA takes the same unlimited-deployment right and removes the end date and the certification step. Oracle positions this as "certainty" — no audit on the named products, no certification scramble.

The trade is structural. Because there is no certification and no expiry, there is also no future negotiation event — the moment a ULA customer normally uses for leverage. A PULA converts a recurring negotiation into a one-time deal on Oracle's terms, with support locked for the life of the estate. For the fixed-term alternative and its exit mechanics, see our Oracle ULA guide and ULA certification process.

Read the table as a leverage map: the further right you go, the less unlimited the right — but a Pool of Funds keeps your support base proportional to actual purchases, whereas a PULA fixes it forever. See the full negotiation context in our Oracle negotiation guide.

A Pool of Funds suits organisations that know they will buy more Oracle but cannot yet specify what or when. The upside is locked unit pricing and a single approved budget; the downside is that the eligible product scope is constrained, pricing is fixed at order, and unused funds are usually forfeited at the end of the term. Unlike a PULA, your support cost only grows as you actually draw licences — which keeps it proportional but removes the "deploy without counting" freedom. We model a Pool of Funds against ordinary discounted buying in every Oracle contract negotiation.

This is the hidden cost of a PULA. Oracle's Enterprise Support runs at 22% of net licence value per year (Oracle Technology Price List, 2026), and a PULA fixes that base for the life of the estate. There is no certification to reset it and no renewal where you can drop unused products, so the only direction is up — the ~4% annual uplift compounds indefinitely. Over a ten-year horizon, we routinely see PULA support outrun a right-sized, third-party-supported alternative by a wide margin; our Oracle support reduction team quantifies the gap.

Because there is no built-in exit, the customer's options are limited and must be created. You can terminate Oracle support and move to third-party Oracle support — you keep the perpetual licences but lose Oracle updates. You can also fold a PULA renegotiation into a larger Oracle deal (a cloud commitment or a new product purchase) where you hold some leverage. If Oracle is already auditing, control the data first — see our Oracle audit defense service.

The honest test is whether you will genuinely deploy enough of the named products, indefinitely, to justify locking your support base forever. For a stable bank or telco running Oracle Database, RAC and Partitioning across thousands of cores with no exit on the horizon, a well-negotiated PULA can be defensible. For everyone else — anyone consolidating, migrating to cloud, divesting, or uncertain about future Oracle use — the perpetual support lock usually outweighs the certainty. Across 600+ engagements we recommend signing a PULA in fewer than 1 in 5 cases where Oracle proposes one (Oracle Licensing Experts benchmark, 2026). Get an independent read from our Oracle license consultant team before you sign.