Oracle has no free non production licence
A common and costly misconception is that development and test environments are free or lightly licensed. For Oracle Database and most technology products this is not the case. Oracle licenses installed and running software regardless of whether the environment is labelled production, and there is no general free use right for non production database instances comparable to the limited developer allowances some other vendors offer. A test database running Enterprise Edition consumes a licence on the same metric as production. This rule does not change under a ULA; the unlimited right simply means the customer is not billed incrementally for that consumption during the term, as set out in the Oracle ULA pillar guide.
Understanding this is essential because it frames non production correctly: not as a free zone but as licensable deployment that the ULA happens to cover for the duration. The implication is twofold. During the term, non production is genuinely free to expand, which is an opportunity. After the term, every non production instance is a licensed object that must fit within the certified entitlement, which is a risk if it was never counted or controlled.
Non production during the term
While the ULA is live, teams can stand up development, test, staging, training, and sandbox environments running in scope products without paying for them, provided they use scheduled products on licensed entities. This is one of the practical pleasures of a ULA: engineering teams can provision freely, spin up short lived test estates, and refresh staging environments without raising a licensing request for each one. The freedom genuinely accelerates delivery and should be used.
During the term, non production is a free playground. The discipline is to recognise that everything in the playground is licensable software, and to decide which of it you intend to keep.
Because non production instances are installed and running software, they form part of the deployment that can be counted at certification. This connects non production directly to the deployment maximization opportunity: a substantial, stable non production estate that the organisation intends to keep is countable entitlement, not just overhead. The judgement is which non production capacity is permanent and worth counting, and which is transient and should not inflate a figure the organisation will have to sustain afterward.
Does non production count at ULA certification?
At certification the customer declares the quantity of in scope products deployed, and non production instances that are installed and running on the cut off date generally count on the same metric as production, applying the appropriate core factor where processor based. There is no automatic discount for a test or development environment; a running Enterprise Edition instance counts whether it serves customers or developers.
| Environment | During term | At certification |
|---|---|---|
| Development | Free under unlimited right | Counts if running and in scope |
| Test and QA | Free under unlimited right | Counts if running and in scope |
| Staging and pre production | Free under unlimited right | Counts if running and in scope |
| Training and demo | Free under unlimited right | Counts if running and in scope |
| Decommissioned or offline | No consumption | Does not count |
The practical decision is therefore to ensure that the non production capacity the business will keep is running and evidenced at the cut off, so it converts to entitlement, while transient environments that will be torn down are not relied upon to inflate the count. The same scope discipline that governs production applies: a non production instance running an out of scope product or sitting in an unnamed entity does not count and creates exposure, exactly as described in the ULA true-up guide.
Why non production sprawl matters
Non production sprawl is the tendency of dev and test estates to grow without governance because no one is paying per instance. Under a ULA this sprawl is harmless to the budget during the term, which is precisely why it goes unchecked. The danger is that the organisation loses visibility of how much non production it is actually running, so it arrives at certification unable to count it accurately and arrives after certification unable to control it.
The organisations that manage this well keep a live inventory of non production throughout the term, tagging each environment with its product, host, entity, and purpose. This inventory turns sprawl into a counted asset at certification and into a managed estate afterward. Without it, the certification figure is a guess and the post ULA compliance position is unknown, which is the worst possible footing for the audit that often follows the end of a ULA.
The post certification non production trap
The trap springs after certification, when the unlimited right is gone and the organisation holds a fixed perpetual quantity. Non production that was free to proliferate for three years is now licensed deployment competing for the same finite entitlement as production. If the certified quantity does not cover the non production estate plus production, the organisation is out of compliance, and Oracle audit practice specifically looks for non production environments that expanded under a ULA and were never accounted for afterward.
Avoiding the trap means deciding, before certification, how much non production the organisation will keep and ensuring the certified quantity covers it, then governing non production tightly afterward so it does not grow beyond the entitlement. This is a core reason the certification and the post ULA operating model should be planned together, as they are in the audit defence and ULA negotiation disciplines, rather than treated as separate events.
Governing non production environments
Good governance of non production under a ULA has three elements. First, a provisioning standard that ensures every non production instance uses in scope products on licensed entities, so sprawl never becomes scope leakage. Second, a live inventory that records every environment and its configuration, so the estate is always known. Third, a lifecycle discipline that decommissions environments when they are no longer needed, so the count reflects genuinely retained capacity rather than abandoned instances.
These practices let the organisation enjoy the freedom of unlimited non production during the term while keeping the certification honest and the post ULA position defensible. They convert non production from a hidden liability into either counted entitlement or cleanly decommissioned overhead, with nothing left ambiguous when the unlimited right expires.
The buyer side view
The buyer side view is that non production is licensable software that the ULA happens to make free for a while, not a permanent free zone. Use the freedom to provision and test without friction during the term, but inventory every environment, decide which non production capacity is permanent and should be counted, and ensure the certified entitlement covers what you keep. The organisations that get hurt let non production sprawl unmonitored, then meet it again as an audit finding after the unlimited right has lapsed.
Inventory your non production estate now, decide what is permanent before certification, and read the certification guide so the dev and test capacity you intend to keep is counted and the rest is cleanly retired before the term ends.
Oracle ULA non production environments: frequently asked questions
Are development and test environments free under an Oracle ULA?
They are free to deploy during the term because the unlimited right covers them, but Oracle has no general free non production licence, so each running instance is licensable software. See the ULA pillar guide.
Do non production environments count at certification?
Yes. Installed and running non production instances of in scope products generally count on the same metric as production, applying the core factor where processor based. There is no automatic discount for dev or test.
What is the post certification non production trap?
It is the exposure that appears when non production that proliferated freely under the ULA must fit within the fixed certified entitlement afterward. If it does not, the organisation is out of compliance. See the audit defence service.
How should we govern non production under a ULA?
Provision only in scope products on licensed entities, keep a live inventory of every environment, and decommission environments when no longer needed, so the certified count reflects retained capacity and the post ULA position stays defensible.