The Oracle PULA, a ULA that never lets go
A PULA is a Perpetual Unlimited License Agreement: the certification cliff that defines a standard ULA is gone, and so is the exit it forced. What replaces it is permanence, of product scope, of support fees, and of the relationship, which is why the perpetual route has to be priced against the ULA it replaces, not against the fear of certifying.
Prepared by Redress Compliance · August 6, 2026 · Oracle licensing advisory. Based on 20 to 30 PULA proposals modeled 2024 to 2026.
Executive summary
The appeal is real: no certification cliff. A standard ULA ends in a certification event, counting the deployed estate under audit conditions to fix the perpetual position, and the cliff drives most ULA anxiety. The PULA removes it: no end date, no forced count, unlimited deployment of the scoped products, indefinitely.
The trap is permanence. The product list is fixed at signature, so the wrong scope is a permanent problem, not a three year one. Support fees become an unending stream derived from the fee you pay now, rarely reducible later, and exit exists only as a negotiated certification event Oracle must agree to, not as a contract right you hold. On the fee pair we modeled, the perpetual route cost $13,099,117 more in ten year present value than certifying the equivalent ULA.
Divestiture is the clause that breaks it. With no certification event, an entity you sell holds zero entitlement on separation day: the unlimited right stays with the named parent, and the divested business walks out unlicensed. Any enterprise with M&A on its horizon is buying that clause along with the unlimited right.
The proposal quality tells its own story: of 20 to 30 PULA proposals we modeled, not one arrived with enough in it to price. The three lines we send back for, the same week ULA quote for the identical scope, the support base with its derivation and a written uplift cap, and the named entity list with its M&A treatment, are the entire diligence, and the deals that produced all three closed on the buyer's terms.
What a PULA is, against the ULA it replaces
| Standard ULA | PULA | |
|---|---|---|
| Term | Typically three years, ending in certification | No end date, no certification event |
| The exit | Certification is a contract right: count the estate, keep the perpetual position, leave | Exit only through a negotiated certification Oracle must agree to |
| Product scope | Fixed for the term, renegotiable at each cycle | Fixed forever: the wrong list is a permanent problem |
| Support | Derived from the fee, renegotiable at the cycle boundary | An unending stream, rarely reducible, compounding at the uplift |
| The pressure point | The certification cliff and Oracle's behavior around it | The lock in, priced into every future negotiation Oracle has with you |
The pricing test, and the $13 million answer
A PULA fee only means something against the ULA fee for the identical program, quoted the same week, because the perpetual premium is the difference between those two numbers plus the support streams they each generate. On the fee pair we modeled end to end, the perpetual route cost $13,099,117 more in ten year present value than signing the equivalent ULA and certifying it, the certification, with all its work, was thirteen million dollars cheaper than never having to do it.
The arithmetic generalizes: the PULA's premium buys insurance against a cliff whose cost is mostly preparation, while committing to a support annuity whose growth compounds at Oracle's uplift for as long as the agreement lives. The cases where the premium pays are narrow and real: very large estates, genuinely growing, deeply Oracle committed, where deployment velocity would make every certification an undercount. Everywhere else, the ULA with a prepared certification wins the model.
The PULA exit playbook
The negotiated certification method, the divestiture and M&A clause set, the support stream analysis, and the exit sequencing for estates already inside a perpetual agreement.
Get the white paper →The divestiture clause, where permanence breaks
The unlimited right attaches to a named entity list, and with no certification event there is no mechanism that crystallizes entitlements for an entity leaving the group: the business you sell holds zero Oracle entitlement on separation day, and its licensing becomes a condition of the transaction, negotiated with Oracle, on the deal's timeline, at the deal's leverage.
The protections are drafted at signature or never: divestiture carve out language that grants a certified position to departing entities, entity list mechanics for acquisitions, and the treatment of the list on change of control in either direction. Every one of the 20 to 30 proposals we modeled was silent on all three, which is not an accident; the silence is worth money to exactly one party. The comparative mechanics sit in the PULA versus ULA pillar and the ULA decision framework.
- Percentile standing for your exact deal size and industry, from real closed transactions
- Scenario simulation before the call: test alternative terms and see the financial impact of each
- A negotiation playbook, talking points, and a two page executive brief on day one
The support stream, the annuity inside the agreement
The PULA's recurring cost is support derived from the agreement fee, compounding at Oracle's uplift, indefinitely, and rarely reducible because the unlimited right is indivisible: there is no shelf to return. Two controls exist, and both are written at signature: the uplift cap, as a sentence in the ordering document rather than a percentage on a slide, and Support Rewards, where Unlimited License Agreement customers earn 33 percent against the standard 25, provided the PULA is named as qualifying in writing.
The third control is structural and belongs in the model rather than the contract: the third party support route and the support drop mechanics that a certified ULA position permits and a PULA forecloses. Pricing the foreclosed options is part of pricing the PULA, because permanence is precisely the surrender of those exits.
What we saw across PULA proposals, 2024 to 2026
Fredrik Filipsson and the Redress team modeled 20 to 30 Oracle PULA proposals between January 2024 and early 2026, and the diligence pattern was absolute:
Not one arrived with the ULA baseline, the support derivation, or the entity treatment needed to judge the perpetual premium.
The same week ULA quote for identical scope, the support base and uplift cap in writing, and the named entity list with its M&A treatment.
The deals that produced all three lines closed on the buyer's terms, in both directions: some as PULAs with the clauses that make permanence survivable, most as ULAs once the premium had a number attached. The proposals that never produced them were not negotiations; they were invitations to buy an annuity unpriced.
Your first five moves
- Demand the same week ULA quote for the identical product list. Without the baseline, the perpetual fee cannot be judged against anything.
- Get the support base in dollars, its derivation, and the uplift cap as a sentence in the ordering document, not a percentage on a slide.
- Fix the entity list and its M&A treatment: divestiture carve outs, acquisition mechanics, and change of control, drafted before signature or never.
- Model the ten year present value of both routes, certification costs included, foreclosed exits priced. Our modeled pair ran $13.1M apart.
- Name the PULA as Support Rewards qualifying in writing at the 33 percent rate. The Oracle practice and the ULA negotiation guide run the full sequence with you.
Frequently asked questions
What is an Oracle PULA?
A Perpetual Unlimited License Agreement: a ULA with no end date and no forced certification event, granting unlimited deployment of the scoped products indefinitely. The appeal is removing the certification cliff; the price is permanence of scope, support fees, and the Oracle relationship itself.
Is a PULA better than a ULA?
Rarely, on the model. The PULA's premium buys insurance against a certification whose cost is mostly preparation, while committing to an unending support stream: on our modeled fee pair the perpetual route cost $13.1M more in ten year present value. It pays only for very large, growing, deeply Oracle committed estates where every certification would undercount.
Can you exit an Oracle PULA?
Only through a negotiated certification event that Oracle must agree to; there is no contract right to certify and leave as a standard ULA provides. Exit planning for a PULA is therefore leverage construction, building the position that makes Oracle prefer agreement, which is a longer and less certain road than a ULA's defined cliff.
What happens to a divested business under a PULA?
On separation day it holds zero entitlement: the unlimited right stays with the named entities, and with no certification mechanism, nothing crystallizes a position for the departing company. Its licensing becomes a negotiated condition of the transaction unless divestiture carve out language was drafted at signature, which in our proposal file it never was.
What should a PULA proposal include before we evaluate it?
Three lines, and we return proposals without them: the three year ULA fee for the identical product list quoted the same week, the support base in dollars with its derivation and a written uplift cap, and the named entity list with its treatment on acquisition, divestiture, and change of control. The deals that produced all three closed on the buyer's terms.
Do PULAs qualify for Oracle Support Rewards at the higher rate?
Unlimited License Agreement customers earn Support Rewards at 33 percent against the standard 25, and a PULA should be named as qualifying at that rate in writing at signature. On a perpetual support stream the eight point difference compounds for the life of the agreement, which is exactly why it is worth a sentence in the ordering document.
