A ULA is a fixed fee for unlimited deployment, and certification is the one moment you convert that deployment into permanent value. Deployment maximization is the discipline of capturing all of it. This guide explains the levers, the limits, and why support stays flat while the count climbs.
Deployment maximization is the disciplined work of certifying every defensible deployment of your named products before a ULA ends, so the perpetual count is as high as the contract and the evidence allow. It captures entitlement you have already paid for through the fixed fee, including cloud, disaster recovery, and non production deployments that are routinely overlooked. It is not about counting usage that is not real.
You paid a fixed fee for unlimited deployment. Maximization is simply refusing to leave the unlimited part uncounted. Every defensible processor you certify is value you have already bought.
The economics are unusually one sided in your favor, and worth stating plainly. There is no fee for certification itself. Support fees continue at the ULA level regardless of the certified count, so a higher number does not raise your support bill. That means every additional defensible processor is free value, captured once and held forever. Certified counts often land 1.5 to 2.5 times higher than first expected once the overlooked deployments are handled properly. The opportunity is real, and it closes the moment the term ends.
Production is the obvious part. The value sits in the environments often left out: test, development, and disaster recovery instances deployed within the term. Each is legitimate entitlement, and each is permanent once certified.
Cloud counting is contract specific. Many contracts require a deployment in AWS or Azure to run 365 continuous days to count, some exclude public cloud, and many are silent on Google Cloud, where silence is not inclusion. Where cloud will count, it is captured. Where it will not, workloads can be repatriated on premises or moved to OCI before exit so they do, provided there is time for any continuous run clock to complete.
Under Oracle's partitioning stance, soft partitioning does not limit scope, so an entire VMware cluster can be counted. In a defensive setting that is a risk, but in a maximization setting the same rule supports a larger count where deployment genuinely runs on a large cluster. The position has to be measured and documented either way.
For products that allow Named User Plus, the metric choice affects the entitlement, and the per processor minimum can lift the count. Modelling processor against Named User Plus for each eligible product is part of the maximization work.
A financial services firm first expected to certify around its production database footprint. Maximization added documented disaster recovery instances, a non production cluster, an OCI region, and an AWS deployment that met a 365 day continuous run clause. The certified count landed well above twice the initial estimate, and because support continues at the ULA level, the annual cost did not move. Every addition was evidenced, so the position held under later review. Figures are indicative and depend on the specific contract language.
Maximization is aggressive about claiming entitlement and disciplined about what counts. A counted deployment must be genuine, live within the term, inside the contract's customer definition and territory scope, and backed by evidence. Counting deployments that are not real, or that sit outside scope, does not create durable value. It creates audit exposure, because audit risk rises in the first two years after certification and an unsupported number is exactly what a review surfaces. The goal is the highest defensible count, not the highest count.
Every lever above depends on the evidence file. Server lists, deployment dates, tool output, cloud condition records, and virtualization measurements turn a high count into a durable one. The evidence file matters as much as the number, because it is what defends the maximized count after the letter is signed.
How cloud counts, how virtualization is read, which products allow Named User Plus, and what scope applies all come from the specific agreement. Two firms with similar estates can maximize to very different numbers because their contracts differ. In ULA work the answer almost always depends on the specific wording, so maximization is built against your own contract, not a general playbook.
If your ULA is approaching its end, the maximization window is open now and closes at the term. Start with the deployment maximization pillar guide, then read standing up capacity you will actually use and moving workloads on premises to count them.
Deployment maximization is the disciplined work of certifying every defensible deployment of your named products before a ULA ends, so the perpetual count is as high as the contract and the evidence allow. It is about capturing entitlement you have already paid for through the fixed fee, not inventing usage.
Yes, when every counted deployment is genuine, deployed within the term, inside the contract scope, and backed by evidence. Maximization claims entitlement you are due, including cloud, disaster recovery, and non production deployments that are routinely overlooked. It is not about counting deployments that are not real.
Certified counts often land 1.5 to 2.5 times higher than first expected once cloud, disaster recovery, and non production deployments are handled properly, and support stays flat regardless. The exact uplift is indicative and depends on the estate and the specific contract language.
Book a confidential assessment and we will find the defensible deployments your first estimate missed, and turn them into permanent licenses.