Contents
Key takeawaysPULA versus ULATen year costSetting the product listDivested businessesSupport and Support RewardsExiting a PULAWhat Oracle will sayWhat we have seenWhen a PULA fitsWhat to do nextFAQAn Oracle PULA is a ULA with no end date and no certification. It removes the certification deadline, and with it your exit, while the product list and the support stream become permanent.
- No end date, no count. A PULA grants unlimited deployment of the named Oracle products indefinitely, without the certification that ends a standard ULA.
- Scope is permanent. The product list fixed at signature is never revisited at a cycle boundary, so a wrong list stays wrong for the life of the agreement.
- Priced properly, the premium is large. On the fee pair we modeled, the perpetual route cost $13.1 million more in ten year present value than certifying the equivalent ULA.
- Divested entities leave unlicensed. Unless carve out terms are drafted at signature, a business you sell holds zero Oracle entitlement on the day it separates.
- Support never stops. Support derived from the fee rises every year and is hard to cut, because the unlimited right cannot be partly handed back.
- Three items before any evaluation. Ask for a same week ULA quote, the support base with a written cap on increases, and the entity list with its M&A treatment.
What is an Oracle PULA, and how is it different from a ULA?
An Oracle PULA is a Perpetual Unlimited License Agreement: a ULA with no end date and no certification event. You may deploy the products named in the agreement without limit, indefinitely, and you never have to count them.
A standard ULA runs for a term, typically three years, and ends in certification. You count what you deployed under audit conditions, that count becomes your perpetual license position, and the unlimited grant ends. The PULA removes that event, and with it the exit the event forced.
| Standard ULA | PULA | |
|---|---|---|
| Term | Typically three years, ending in certification | No end date, no certification event |
| Exit | Certification is a contract right: count your deployments, 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 permanently, so a wrong list stays wrong |
| Support | Derived from the fee, renegotiable at the cycle boundary | A stream with no end date, rarely reducible, rising with every annual increase |
| Pressure point | The certification cliff and Oracle's behavior around it | The lock in, priced into every later negotiation Oracle has with you |
Why do Oracle customers find the PULA attractive?
It removes the certification cliff. Certification is where most ULA anxiety sits: a fixed deadline, a count under audit conditions, and an Oracle team whose conduct around that date shapes the result. A PULA replaces all of it with unlimited deployment of the scoped products, indefinitely.
What do you give up in return?
- Scope flexibility. The product list is set at signature. Under a ULA a wrong list costs you one term, while under a PULA you live with it for good.
- Control of support cost. Support is derived from the fee you pay now and continues with no end date, and it can rarely be cut later.
- The exit. Leaving requires a negotiated certification that Oracle must agree to. You hold no contract right to count and walk away.
- Room in later negotiations. Oracle knows you are locked in, and that knowledge shapes every later purchase, cloud deal and audit of products outside the list.
How much more does a PULA cost than a ULA over ten years?
On the fee pair we modeled end to end, the PULA cost $13,099,117 more in ten year present value than signing the equivalent ULA and certifying it. Certification, with all the work it involves, was the cheaper route by roughly $13 million.
A PULA fee means something only against the ULA fee for the identical product list, quoted the same week. The premium is the gap between those two fees plus the gap between the support streams they create, and what it buys is insurance against a cliff whose cost is mostly preparation.
A worked example with hypothetical numbers
Say Oracle quotes a PULA at $9,000,000 and, the same week, a three year ULA for the same products at $6,000,000. Assume support at 22 percent of each fee, a 3 percent annual support increase on both routes, $400,000 of certification preparation in year 3 of the ULA, and an 8 percent discount rate.
| Cost line | PULA | ULA, then certify | Difference |
|---|---|---|---|
| Upfront fee | $9,000,000 | $6,000,000 | $3,000,000 |
| Support in year 1 | $1,980,000 | $1,320,000 | $660,000 |
| Support in year 10 | $2,583,451 | $1,722,301 | $861,150 |
| Certification preparation | $0 | $400,000 | ($400,000) |
| Ten year total, undiscounted | $31,698,481 | $21,532,321 | $10,166,160 |
| Ten year present value at 8 percent | $25,145,206 | $17,106,406 | $8,038,800 |
Even after paying for certification, the ULA route stays $8,038,800 cheaper in present value. The model also leaves out the support exits that only a certified ULA keeps, which the support section below covers.
Two assumptions deserve scrutiny in your own model. We held the annual increase equal on both routes, although an uncapped PULA can rise faster. We also assumed deployment after year 3 stays within the certified count, and that is the assumption that decides the rare cases where a PULA wins.
When does the premium pay for itself?
The cases are narrow and real: very large Oracle footprints, still growing, deeply committed to Oracle, where deployment grows so fast that every certification would undercount what you need a year later. Everywhere else, a ULA with a prepared certification wins the model.
Why we reject the advice to avoid certification at almost any price
Oracle's pitch, and some advisors, treat certification as a risk worth paying nearly anything to remove. Our experience says otherwise. Certification is work, evidence and negotiation, but it is a defined event with a defined end, and a company that prepares certifies on its own numbers.
Permanence has no end to prepare for. Put a dollar figure on both routes before you decide, and treat fear of the cliff as a cost that preparation reduces. Our ULA certification guide covers that preparation.
The PULA is sold against fear of certification, yet certification ends on a date you know, and permanence gives you no date at all.
Oracle PULA exit guide
How to build a negotiated certification, protect entities you sell and price the support stream inside a perpetual agreement.
Get the white paper →How should you decide which products go into a PULA?
Assume the list you sign is the list you keep. A missing option or an unneeded product costs you one term under a ULA, and every year the agreement runs under a PULA. You pay support on products you stop using, and you buy separately anything you left out.
How to check what you actually run before the list is fixed
- Database options and packs. Query DBA_FEATURE_USAGE_STATISTICS on every database to see which options and management packs have been used, such as Partitioning, Advanced Compression, Diagnostics Pack and Tuning Pack. Read why to run the feature usage report before Oracle's scripts first.
- Middleware. Inventory WebLogic Server, SOA Suite and any other middleware installations, including test and disaster recovery environments.
- Public cloud. List what runs in AWS, Azure or Google Cloud, and ask Oracle in writing whether those deployments sit inside the unlimited grant. The treatment of ULA deployments on AWS is a frequent gap.
- Roadmap. Ask application owners which Oracle products they plan to retire, replace or expand. A product you are migrating away from does not belong on a perpetual list.
- Entities. Confirm which legal entities run Oracle today and which may be sold, merged or added, because the entity list is as permanent as the product list.
What happens to a divested business under a PULA?
It holds zero Oracle entitlement on separation day. The unlimited right attaches to a named entity list, and with no certification event nothing fixes a license position for an entity leaving the group. Its licensing becomes a condition of the sale, negotiated with Oracle on the deal's timetable, when you have the least room to refuse.
Any company with acquisitions or disposals ahead is buying that clause along with the unlimited right. The protections have to be drafted at signature, because Oracle has no reason to add them once the agreement is signed. The comparison with ULA mechanics is set out in our PULA versus ULA pillar and the ULA decision framework.
Contract wording to ask for before you sign
- Divestiture carve out. A departing entity receives a certified perpetual position based on its deployments on the separation date. Without it, the business you sell starts with nothing. Our note on carve out license transfers explains the mechanics.
- Acquisition mechanics. How an acquired company joins the entity list, what it pays to join, and what happens to the Oracle licenses and support contracts it brings.
- Change of control in both directions. What happens to the list if you are acquired, and if you buy a company larger than your own Oracle footprint.
- Cap on support increases. The maximum annual increase written as a sentence in the ordering document, since a percentage on a slide binds Oracle to nothing. See price hold and uplift cap clauses.
- Support Rewards qualification. A sentence stating that the PULA counts as an Unlimited License Agreement for Oracle Support Rewards, for every entity on the list.
- Elective certification. A clause giving you the option to certify on notice, which turns the negotiated exit into a right you hold. Oracle may refuse it, and the refusal tells you what the exit is worth.
Every proposal we modeled was silent on the first three, and that silence is worth money only to Oracle.
How does support work in a PULA, and can you reduce it?
Support is derived from the agreement fee and rises with each of Oracle's annual increases, with no end date. It is rarely reducible, because the unlimited right is indivisible: there is no shelf of licenses you can hand back.
- Matching service levels. Oracle's Software Technical Support Policies require all licenses in a license set to be supported at the same level.
- Repricing. Ending support on part of an order reprices the rest at list less the standard discount, never below what you already paid for the licenses you keep.
Two controls exist, and you write both at signature. The first is the cap on annual increases in the ordering document. The second is Oracle Support Rewards.
How do Oracle Support Rewards apply to a PULA?
Support Rewards credit you for spending on Oracle Cloud Infrastructure through Universal Credits, and the rewards pay down technology support invoices. Customers with a current Unlimited License Agreement accrue rewards at 33 percent of that consumption, against the standard 25 percent.
- Name the PULA. Oracle's program terms refer to a current ULA, so get the PULA named as qualifying at the higher rate in the ordering document.
- Check the entity list. Oracle applies ULA eligibility to the entities included in the agreement, which makes the entity list decide who earns the higher rate.
- Spend them within a year. Rewards are valid for 12 months after they are deposited, and pay as you go OCI accounts do not qualify.
- Know the limits. Rewards pay only the pretax amount of technology support invoices and cannot be exchanged for cash. Our Support Rewards guide has the detail.
Which exits does a PULA close off?
The third control is structural, and it belongs in your cost model. A certified ULA position allows you to move licenses to third party support or use the support drop and reinstatement rules on products you stop using. A PULA forecloses both, and pricing those lost options is part of pricing the PULA.
Can you exit an Oracle PULA once it is signed?
Only through a negotiated certification that Oracle agrees to. A standard ULA gives you the contract right to certify and leave, while a PULA gives you nothing comparable, so the exit depends on building a position that makes Oracle prefer agreement.
That road is longer and less certain than a ULA's defined end date. Start with an accurate deployment count, a clear view of which products you would certify, and a commercial reason for Oracle to say yes. Our PULA exit strategies set out the sequence.
What will Oracle's account team say about a PULA, and how should you reply?
These lines come up in most PULA discussions. Each reply keeps the evaluation on numbers you can check.
- "A PULA removes certification risk for good." Reply: certification is a defined event we can prepare for, so quote the three year ULA for the same list this week and we will price what removing it costs.
- "There is no equivalent ULA quote for this deal." Reply: then we cannot evaluate the PULA, because its fee has nothing to be measured against.
- "Divestitures are handled case by case, and Oracle is always reasonable." Reply: put the treatment in the ordering document, with a certified position for any entity that leaves.
- "Support is derived from the fee in the standard way." Reply: show us the base in dollars and how it was calculated, and write the cap on annual increases into the order.
- "Unlimited customers get the higher Support Rewards rate." Reply: then naming this agreement as qualifying costs Oracle nothing, so add the sentence.
What have we seen in recent Oracle PULA proposals?
Between January 2024 and early 2026, our Oracle team modeled 20 to 30 PULA proposals, and the pattern was absolute. None arrived with enough information to price as sent: each lacked the ULA baseline, the support derivation or the entity treatment needed to judge the perpetual premium.
We now send every proposal back for three lines before we evaluate it:
- The three year ULA fee for the identical product list, quoted the same week.
- The support base in dollars, how it was derived, and a written cap on the annual increase.
- The named entity list, with its treatment on acquisition, divestiture and change of control.
In our experience those three lines make up the whole of the diligence. The deals that produced all three 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.
Where Oracle never produced them, the buyer was being invited to buy a support annuity with no price attached, and there was nothing to negotiate against.
When does a PULA make sense for your company?
A PULA fits a small group of Oracle customers and costs everyone else money. Your own plans, rather than Oracle's pitch, decide which group you are in.
| Your situation | PULA fit | Reason |
|---|---|---|
| Very large Oracle footprint, growing fast, committed to Oracle long term | Possible | Growth after each certification would outrun the certified count |
| Stable or shrinking Oracle use | Poor | You pay a permanent premium for deployment you will not use |
| Acquisitions or disposals likely | Poor unless carve out terms are signed | Entities you sell leave with no licenses |
| Moving workloads to other databases or clouds | Poor | Support continues on products you are leaving |
| Considering third party support in the coming years | Poor | The PULA closes that option |
What to do next
- Before any PULA discussion. Measure what you run: feature usage on every database, middleware installations, public cloud deployments and the entities that use Oracle.
- When the PULA quote arrives. Ask for the same week ULA quote for the identical product list. Without it the perpetual fee cannot be judged against anything.
- Before you model. Get the support base in dollars, its derivation and the cap on increases, written as a sentence in the ordering document.
- Model both routes over ten years. Include certification preparation on the ULA route and price the support exits the PULA closes.
- Before signature. Fix the entity list and its treatment on acquisition, divestiture and change of control, and ask for an elective certification clause.
- In the ordering document. Name the PULA as qualifying for Support Rewards at the ULA rate. Our Oracle practice and the ULA negotiation guide run the full sequence with you.
Is a ULA or PULA decision coming up? Our Oracle ULA certification team counts what you really deploy before Oracle does, for a fixed fee.
Frequently asked questions
What is an Oracle PULA?
A Perpetual Unlimited License Agreement. It works like a ULA, granting unlimited deployment of a fixed list of Oracle products, but it has no end date and no forced certification. The appeal is losing the certification deadline. The price is that scope, support fees and your commercial relationship with Oracle all become permanent.
Is a PULA better than a ULA?
Rarely, once both routes are priced side by side. The perpetual premium insures against a certification whose cost is mostly preparation, and it commits you to support with no end date. It suits only very large, growing Oracle users with a long term commitment to Oracle, where each certification would fall short of next year's deployment.
Can you exit an Oracle PULA?
Not on your own terms. Exit requires a negotiated certification that Oracle has to accept, and there is no contract right to certify and leave as a standard ULA provides. Plan years ahead, and build a commercial case that gives Oracle a reason to agree.
What happens to a divested company under an Oracle PULA?
It has no Oracle licenses from the day it separates. The unlimited right stays with the named entities, and without a certification mechanism nothing converts the departing company's deployments into owned licenses. Its licensing becomes a negotiated condition of the sale, unless carve out language was drafted at signature. In the proposals we reviewed, it never was.
What should a PULA proposal include before we evaluate it?
We return any proposal that lacks three items: a three year ULA fee for exactly the same products, dated the same week; the support base in dollars with its calculation and a written limit on yearly increases; and the entity list with rules for acquisitions, disposals and change of control.
Do PULAs qualify for Oracle Support Rewards at the higher rate?
Get it in writing rather than assume it. Oracle accrues rewards at 33 percent of OCI consumption for customers with a current ULA, against 25 percent for everyone else. Have the PULA named as qualifying in writing at signature, because the eight point difference applies to every OCI dollar you spend while the agreement runs.
How much does an Oracle PULA cost?
There is no list price. Oracle sets a one time fee for the product list and the entities covered, and annual support is derived from that fee and rises every year. The only way to judge the fee is against a ULA quote for the same products, with ten years of support added to each side.