“Non-production is free” — the most expensive Java myth

“It’s only a test box — that doesn’t need a licence.” It is one of the most common assumptions in enterprise Java, and one of the most costly. The belief that development and test environments are automatically free of Oracle Java licensing has a kernel of truth buried in it, but the kernel is small and the belief is built far beyond it. Under Oracle’s legacy metrics, the distinction between production and non-production carried real licensing weight. Under the current employee-based Java SE Universal Subscription, it carries almost none. This guide separates what is genuinely free from what only feels like it should be — because the gap between the two is where audit claims are made.

Where the myth comes from

The “non-production is free” idea is not invented from nothing. It comes from two real sources, both of which are narrower than the myth they have grown into.

The first source is genuine: the Oracle Technology Network (OTN) License Agreement, which governs many Oracle JDK downloads, permits free use of Oracle Java for development, testing, prototyping, and demonstrating applications. That is a real, written allowance — and it is the seed of the myth. The second source is the legacy processor and Named User Plus metrics, under which you licensed specific machines or users; a dev server simply not licensed was, in a loose sense, “outside” the count. Both sources are real. Neither supports the blanket claim that dev and test Java is always free — and one of them, OTN development rights, is routinely misread.

OTN development rights, precisely

The OTN allowance is the strongest argument for free non-production Java, so it pays to read it precisely. The OTN agreement permits free use of Oracle JDK for “developing, testing, prototyping and demonstrating” applications. The key word is activity: OTN free use is defined by what the software is being used for, not by which environment label the server carries.

That distinction matters in both directions. A server tagged “TEST” in your CMDB is not free under OTN if what actually runs on it is, for example, internal business software being used in earnest, or a staging environment serving real users. Conversely, genuine development activity is free under OTN even on a machine without a tidy “dev” label. OTN also draws a hard line at production: it does not permit any use “for any data processing or any commercial, production, or internal business purpose.” So OTN gives you free development and testing — but the moment Java touches a production or internal-business workload, OTN stops applying and a paid subscription is required. The allowance is real; it is just much narrower than “all non-production is free.”

Why the employee metric breaks the rule

Here is the part that surprises almost everyone, and the reason the “non-production is free” myth is so dangerous today. Under the current Java SE Universal Subscription, the licence is sold on the employee metric: the subscription is sized on your total employee headcount, full stop. It is not sized per server, per environment, or per installation.

The consequence is stark. If any part of your estate requires a paid Java SE Subscription — one production server is enough — the subscription is sized on your whole organisation’s headcount. Once you are paying, your development and test environments add nothing further to the bill, because the bill was never counting environments in the first place. And the reverse is just as important: keeping Java off a few dev boxes saves nothing if production already triggers the subscription. The production/non-production distinction simply does not change the price under the employee metric. It changes nothing — unless you can keep every chargeable use out of your estate entirely. The myth assumes the metric still counts environments. It does not.

Environment by environment

Putting OTN and the employee metric together, here is how each environment type actually stands.

Two patterns stand out. First, the dangerous environments are the ones near production — staging, pre-production, and UAT — because they tend to run real data and serve real internal purposes, which takes them outside OTN’s development allowance. Second, once any chargeable use exists, the entire dev/test column becomes cost-neutral, because the employee metric already counts every employee regardless of environment.

The NFTC alternative

There is one route where the production/non-production question genuinely disappears: the Oracle No-Fee Terms and Conditions (NFTC), which govern Oracle JDK 17 and later within their free-use window. Under the NFTC, Oracle Java is free for all uses — development, test, and production, commercial included — for the defined period of that release.

An estate standardised entirely on an NFTC-covered release, within its free window, has no dev/test/production licensing distinction to manage, because none of it is chargeable. The catch is the window: NFTC free use is time-limited and per release, so an NFTC-based strategy needs the discipline to upgrade before each window closes. The fully clock-free alternative is a non-Oracle OpenJDK distribution — Temurin, Corretto, Zulu — which is free in every environment, production and non-production alike, with no window to track at all. For an estate that wants the dev/test question to simply not exist, OpenJDK is the cleanest answer.

How to license dev, test and production

A coherent approach to dev, test and production Java licensing comes down to a few principles:

1. Stop thinking in environment labels. Oracle does not license “environments” under the current model. License by the rule that applies — OTN by activity, NFTC by release and window, subscription by headcount.
2. Find every chargeable production use first. One unlicensed production Oracle JDK install determines whether you owe a subscription at all. That single fact dominates the whole calculation.
3. Scrutinise staging, pre-prod and UAT. These are where “non-production” quietly becomes “internal business purpose.” They are the highest-risk environments, not the lowest.
4. If you must pay, dev/test is free anyway. Once the employee subscription is in place, do not waste effort “saving” on non-production — it costs nothing extra.
5. If you want zero cost, go OpenJDK everywhere. The only way the dev/test/production distinction truly stops mattering is to remove chargeable Oracle Java from the estate entirely.

Common mistakes

• Believing all non-production is free. OTN covers development activity, not every server labelled non-production. Staging and UAT routinely fall outside it.
• Trusting the environment label. OTN follows what the software does, not what the CMDB calls the box. A “test” server running real workloads is chargeable.
• Thinking dev/test adds to the bill. Under the employee metric it does not. Once you pay, non-production is cost-neutral — effort spent trimming it is wasted.
• Treating UAT as safe. User acceptance testing with real users and real data can be an “internal business purpose” OTN excludes. It is one of the riskiest environments.
• Forgetting the production trigger. A single unlicensed production install can size a subscription for the entire organisation. Non-production housekeeping does not change that.

Getting independent help

The belief that development and test environments are automatically free is a relic of a licensing model Oracle has retired. OTN does grant free use — but for development activity, not for everything wearing a non-production label, and never for production or internal-business workloads. And under today’s employee metric, the production/non-production line barely affects the price at all: one chargeable production install sizes a subscription on your entire headcount, after which dev and test add nothing. The only ways to make the distinction genuinely irrelevant are to standardise on an in-window NFTC release or to move the estate to a free OpenJDK distribution.

Independent, buyer-side advisers establish exactly which environments are free, which are chargeable, and whether the employee metric makes the question moot for your estate. Our Java Compliance Assessment classifies every environment against the rule that actually applies; our Java Migration service removes the chargeable element entirely where that is the better path. Across 340+ Java engagements, that approach has contributed to a 68% average reduction in audit claims and more than $180M in client savings.

Frequently asked questions