When your certification window is inside twelve months, the work begins now. We run the whole exit, from independent baseline to signed letter, so you certify on a maximized count you can defend.
Certification management is the buyer side program that runs your Oracle ULA exit inside the window. We measure your true deployment, maximize the defensible processor count, assemble the evidence file behind every number, prepare the certification letter, and represent you through the exchange with Oracle to a clean sign off. The certified count becomes your permanent entitlement, so the goal is a number that is both complete and defensible.
At the end of an Oracle ULA you declare how many processors you have deployed. That declaration converts to perpetual licenses and the unlimited right ends. Whatever you fail to count, you lose. Whatever you cannot defend becomes audit exposure in the two years that follow. Managing the certification well means entering the window already knowing your number, measured independently, reconciled to your contract, and ready to stand behind.
Independent, evidence grade measurement of your true deployment across databases, options, and packs, including virtualization, disaster recovery, and non production. We measure with methods that hold up under scrutiny rather than inflate risk.
Every environment you are entitled to count, we count. We surface legitimate deployments that are routinely overlooked and position cloud and DR workloads so they count before the window, where your contract allows.
We reconcile the count to your agreement, prepare the certification letter and the supporting position, and sit with you through the exchange with Oracle to close it cleanly.
Your perpetual entitlements are documented and monitored, so a future migration, acquisition, or audit never erodes the position you just secured.
Start within twelve months of your certification date, and ideally nine to twelve months out. That runway lets us baseline the estate, resolve virtualization and cloud questions, repatriate or relocate workloads that need to count, and build the evidence file at a calm pace. We are also brought in weeks before a window closes and still recover meaningful value, but earlier is always cheaper than later.
Certifying a higher number does not raise your support bill. Support continues at the ULA level regardless of the count. We routinely see defensible counts land 1.5 to 2.5 times higher than a client first expected once cloud, DR, and non production are handled properly. These multiples are indicative and depend on the estate and the contract.
Certification mechanics are not uniform. Your customer definition and entity list govern which parts of the group can deploy and count. The territory clause may exclude deployments outside a named geography. Cloud language decides whether AWS or Azure instances count, often only after 365 continuous days, and many contracts are silent on GCP. Oracle's partitioning stance means soft partitioning does not limit scope, so VMware clusters can be swept into the count. We read these clauses first, because the right number lives in the language.
Figures are indicative and verified against signed engagement outcomes, anonymized to protect client terms.
Read the certify or renew decision framework → before you commit, and compare it with ULA renewal negotiation →.
Book a ULA assessment and we will tell you what your certification is really worth, and exactly what we would do to maximize and protect it.