A perpetual ULA has no certification exit, which means it never resets and the leverage stays with the vendor. This brief shows what a PULA really costs over time and gives you the leverage review that puts the negotiating position back in your hands.
A perpetual ULA, almost always written as a PULA, removes the certification ending that gives a term ULA its value. There is no moment where unlimited deployment converts into a fixed, owned entitlement, so support continues indefinitely and the vendor keeps the structural advantage. This brief replaces that passive position with a method you can run.
A PULA is not a trap you can exit, but it is an agreement you can manage. Leverage in a perpetual deal comes from knowledge and credible alternatives, not from a contract date. The leverage review rebuilds the position a perpetual agreement is designed to remove.
CIOs, IT asset managers, procurement leads, enterprise architects, and general counsel at organisations holding a perpetual Oracle agreement. The framework is vendor neutral and written from the buyer side, with every figure labelled indicative because the answer depends on your contract.
For the open overview, read the PULA guide. For the deeper analysis, read the economics of a perpetual ULA and the PULA customer definition risk.
When you want the leverage review run on your own perpetual agreement, with your real deployment measured and your support tested, book a confidential assessment and we will run it with you.