The ULA window is the cheapest capacity you will ever buy, because deployment is unlimited and certification is free. Deploying the Oracle capacity you will genuinely need over the next few years before the window closes converts future demand into permanent entitlement, as long as every environment is real and documented.
By the Meridian advisory team, former Oracle LMS and GLAS licensing analysts. Updated 4 June 2026.
Yes, and the contract is what makes it possible. A ULA grants unlimited deployment of its named products for the term, for a fixed fee. Capacity that is genuinely deployed and running within that term can form part of the count you certify at exit. So the planned database servers, the disaster recovery footprint, the capacity headroom your roadmap already calls for over the next two or three years: all of it can be stood up while the unlimited right is live, then certified into permanent entitlement when the window closes. After certification the unlimited right is gone and the same capacity would have to be licensed at full price. Pre building is the act of bringing real future demand inside the window while deployment is still free.
Inside the window, deployment is unlimited and certification is free. Outside it, every processor is a purchase. Pre building moves the growth you already know is coming into the period where it costs nothing to license.
The reason this works is the same reason a higher count is free value. Support fees are fixed at the ULA level and do not move with the number you certify, and there is no charge to certify. So a processor deployed for a real project and certified at exit carries a marginal licensing cost of zero, while the same processor bought after the exit carries full price. We set out that economics in why a higher certified count is free value. Pre building simply applies it to demand you can already see on the roadmap.
The line that matters is genuineness. Capacity built for planned migrations, consolidation projects, disaster recovery, test and development estates, and sensible headroom is real and defensible. Environments stood up only to inflate a number, with no purpose and no use, are not. Oracle measures deployment within the term, and the evidence file behind your count is what proves each environment was real. Build for reasons you can articulate, document them, and the count holds.
Start with what is already funded and on the plan. A migration to a new platform, a consolidation onto Oracle, an application that is scheduled to go live: these are the most defensible deployments because the business case exists independently of the ULA. Bringing their go live forward, or standing up their target environments early, places that capacity inside the window.
Disaster recovery instances of the named products, deployed within the term, are part of the deployment picture and are routinely under built before an exit. If your resilience strategy calls for standby capacity, build it now rather than after the window closes. The same applies to high availability nodes and standby sites.
Where your roadmap shows growth in the next two or three years, provisioning that headroom during the window is legitimate when the demand is real. This is the most judgement heavy category and the one where independent advice matters most, because the headroom must be defensible as planned capacity rather than padding. We work through where that line sits in the maximization mistakes that backfire.
Take an indicative case. An organisation with a database ULA expects to certify 900 processor licenses based on current production. Its roadmap shows a consolidation project, a new disaster recovery site, and planned growth that together need another 400 processors over the next three years. By deploying that capacity inside the window for genuine reasons, the defensible count reaches roughly 1,300. Support is unchanged at both numbers. After the exit, the organisation grows into the 400 it pre built and pays nothing further, because the capacity is already certified. Had it certified 900, the same growth would have meant buying 400 processors at full price. The figures are indicative, but the pattern, pre building real demand inside the free window, is the point.
| Category to pre build | Why it is defensible | Evidence to keep |
|---|---|---|
| Committed projects | Funded, on the roadmap independently | Project plans, go live records |
| Disaster recovery | Part of resilience strategy | Architecture, runbooks, server lists |
| Capacity headroom | Real planned growth | Capacity plans, demand forecasts |
Whether a given deployment qualifies depends on your contract terms and the genuineness of the build, so treat this as a framework to test against your own roadmap.
Pre building takes time, and the window does not wait. Capacity has to be genuinely deployed and running before the certification date, which means the planning has to start well before the ULA ends. The realistic horizon is to begin the maximization work twelve months out, so projects can be brought forward, environments stood up, and evidence assembled without a scramble. The structured timeline sits in the maximization project plan, and the full method lives in our pillar, the ULA deployment maximization guide.
The ULA window is the only time your Oracle deployment is unlimited and free to certify, so it is the right moment to bring forward the growth you already know is coming. Pre build committed projects, disaster recovery, and genuine headroom, document every environment, and certify the larger defensible count. Done with real demand and a clean evidence file, you convert years of future purchases into permanent entitlement at no extra cost.
Yes, within the unlimited right the ULA grants for its named products. Capacity genuinely deployed and running within the term can be part of the certified count, so deploying planned growth before the window closes converts future need into permanent entitlement at no extra licensing cost, provided each deployment is real and documented.
It is legitimate when the deployments are genuine, in use or ready for use, and evidenced. The risk is sham deployments stood up only to inflate a number, which fail under scrutiny. Real environments built for planned projects, disaster recovery, and capacity headroom are defensible and count.
Book a confidential assessment and we will map the capacity worth pre building before your certification closes the door.