Unlimited deployment is only valuable if you convert it. The growth you deploy and evidence inside the term becomes permanent entitlement at certification. Planned well, it is the difference between a thin count and a full one.
By Daniel Voss · Ex Oracle LMS · 4 June 2026
A ULA gives you unlimited deployment for a fixed fee, and at certification your deployed, evidenced quantity converts to perpetual licences. Growth you put in place during the term therefore becomes free permanent entitlement, because support is fixed and does not rise with the count. Planning that growth deliberately, twelve to eighteen months out, aligns real business demand with the certification opportunity so the number you certify is as complete as the agreement allows.
Many organisations treat the ULA as a flat fee for Oracle software and run their estate exactly as they would have anyway. That mindset leaves value on the table. The unlimited right is a window in which deployment carries no incremental licence cost, and the quantity you have running and can evidence at the end becomes a perpetual entitlement that outlives the agreement. Every processor you deploy and document during the term is a processor you own forever once you certify.
This reframes the planning question. The point is not to inflate numbers artificially, which would never survive an evidence test. The point is to bring forward and properly record the genuine deployment your business will need anyway, so that demand arrives inside the window rather than after it, when each new processor would have to be bought at list. Refresh cycles, consolidation projects, new application rollouts, and capacity headroom that you can stand behind all belong on the certification side of the line if the business case is real.
Start twelve to eighteen months before the term ends. That horizon matters because a defensible count needs more than a live instance on the final day. It needs deployment that has been provisioned, put into genuine use, and recorded with the dates and configuration that prove it existed within the term. Environments that go live in the last weeks of the agreement often lack the running history and the documentation a clean certification rests on, which makes them weak entries even when they are perfectly legitimate.
Planning early also keeps the exercise honest. When growth is mapped to a real roadmap, refresh schedules, and approved projects, it stands up to scrutiny because it reflects what the organisation was always going to do. When it is rushed into the final quarter, it looks like what it is, and Oracle is well practised at telling the difference.
Do not deploy to game a number. Deploy the demand you can defend, on the timeline the business already has, and make sure it lands inside the term with its evidence intact. Legitimate growth, captured in time, is the cleanest value a ULA produces.
The deployment that belongs in a maximization plan is rarely exotic. It is the ordinary demand of a working estate, brought into the window and evidenced properly.
The table below shows how a deliberate plan can shift the certified count for an anonymized example. The figures are indicative and exist to show the logic, not to represent any real engagement, and every figure assumes a genuine business basis and a complete evidence trail.
| Scenario | Certified processors | What changed |
|---|---|---|
| No planning, count at window | 2,000 | Production only, as found |
| Refresh brought into term | 2,600 | Higher core servers deployed in window |
| Non production evidenced | 3,200 | Test, development, and DR documented |
| Planned certified count | 3,200 | Complete, defensible, permanent |
Indicative only. The size of each step depends entirely on the estate, the roadmap, and the wording of the specific agreement. The point is that planned growth and a thorough count can lift the permanent entitlement well above a passive measurement.
The single belief that suppresses certified counts more than any other is that certifying more raises ongoing support. It does not. Support under a ULA is fixed at the agreement level and continues at that level regardless of whether you certify two thousand processors or four thousand. A higher certified count is therefore free permanent value, and choosing to certify less to keep support down is paying the same support for fewer assets. Understanding this changes how aggressively, and how legitimately, an organisation plans its growth inside the window.
Planning growth is the front half of maximization, and it pays off only if the deployments are evidenced and the certified count is then assembled with discipline. Map your roadmap to the window early, then make sure every environment you stand up carries the records a certification needs. For the product level view, see maximizing across database options and packs, lock the estate at the right moment with the freeze window before certification, and ground the approach in our ULA deployment maximization guide.
Book a ULA assessment and we will map your roadmap to the certification window, identify the legitimate growth worth capturing, and make sure every processor you certify is evidenced and permanent.