OTN license: the commercial-use restrictions.

The Oracle Technology Network (OTN) License Agreement for Oracle Java SE is the most misunderstood document in Java licensing — and the misunderstanding is precisely what Oracle audits exploit. The OTN licence is genuinely permissive in one respect: it lets you use Oracle Java for development and testing at no cost. It is genuinely restrictive in another: it charges for commercial production use. The gap between those two clauses is where enterprises fall, usually without noticing. This guide sets out exactly what the OTN licence allows, what it forbids, and where the commercial-use line is drawn.

What the OTN licence is

The OTN License Agreement for Oracle Java SE is the licence Oracle applied to its Java SE downloads from April 2019. It replaced the older, free-for-commercial-use Binary Code License (BCL) on new releases, and it governed Oracle JDK downloads through the Java 8 (update 211 onward), 11, and intermediate-version era, until the No-Fee Terms and Conditions (NFTC) arrived for Java 17.

Like every Oracle Java licence, the OTN agreement governs the use of Oracle's binary build of Java — not Java the platform, which is open source. When you download an Oracle JDK covered by OTN terms and accept the click-through agreement, the OTN licence is the contract that defines what you may do with that binary. Our BCL/OTN/NFTC comparison places it in the full sequence of Oracle Java licences.

What OTN permits

The OTN licence is not a paid-only licence. It grants real, free rights — and understanding them precisely is as important as understanding the restrictions, because the free rights are narrower than they first appear.

Under the OTN licence, an enterprise may use Oracle Java SE, at no licence cost, for:

• Development. Writing, compiling and building applications on Oracle Java.
• Testing. Running test suites and quality assurance against Oracle Java.
• Prototyping. Building proofs of concept and demonstrations.
• Personal use. Individual, non-commercial use on a personal device.

These are not trivial rights — they cover a great deal of what developers do day to day. A development team can legitimately build and test on Oracle Java under OTN at no cost. The restriction is not on touching Oracle Java; it is on what happens when the software those developers build goes live.

What OTN prohibits

The OTN licence's central restriction is the one Oracle's own description of the agreement makes explicit: the free rights do not extend to commercial use. Under the OTN licence, you may not use Oracle Java SE for:

• Production environments. Running live business applications on Oracle Java.
• Internal business operations. Using Oracle Java to support the running of the business, beyond development and testing.
• Commercial or revenue-generating use. Any use connected to delivering a product or service.

For any of those uses, the OTN licence requires a separate paid subscription — today, the Java SE Universal Subscription. The OTN licence does not let you “buy your way to compliance” within itself; it points you to a commercial agreement for anything beyond development and testing.

Defining 'commercial use'

The whole agreement turns on the phrase “commercial use,” and enterprises consistently read it too narrowly. The instinct is to think commercial use means “use that directly earns revenue” — a customer-facing application, a product you sell. That reading is wrong and it is dangerous.

Under the OTN licence, commercial use effectively means any use that is not development, testing, prototyping or genuine personal use. Crucially, it includes internal business operations. An Oracle Java installation running an internal HR system, a finance application, a logistics tool, a back-office batch job — none of which is sold to anyone, none of which directly generates revenue — is still commercial use. It is supporting the operation of a commercial enterprise, and that is enough.

This is the single most expensive misreading in Java licensing. Enterprises tell themselves “we don't sell anything built on Java, so our use isn't commercial” and conclude they are fine on the free OTN rights. They are not. If Oracle Java under OTN terms is running anything other than development and test workloads, the production restriction applies. The safe assumption is the strict one: outside of development and testing, treat all of your organisation's Oracle Java use as commercial.

Which versions are under OTN

OTN is not a universal licence — it applies to a specific band of Oracle Java versions and downloads, and identifying that band is essential to assessing your estate.

The pattern: OTN governs the “middle era” of Oracle Java — the Java 8 updates after April 2019 and the Oracle JDK 11–16 releases. If your estate contains Oracle JDK 11, or Oracle Java 8 patched with any update from 8u211 onward, those installations are under OTN terms and the commercial-use restriction is live. Note that this is about Oracle's builds specifically; an OpenJDK 11 build from Temurin, Corretto or Zulu is not under OTN at all.

The update trap

The most common way enterprises end up in breach of the OTN licence is not a deliberate decision — it is a security update. This is the trap, and it is worth spelling out.

An enterprise runs Oracle Java 8 in production. The installation originated in the BCL era and was genuinely free. Over time, the organisation does the responsible thing and keeps Java patched — through patch-management tooling, administrator action, or the JRE's own auto-update feature. Each Oracle Java 8 update applied after April 2019 is an OTN-licensed build. The moment that update lands on a production machine, that production installation is governed by the OTN licence — and OTN prohibits production use without a subscription.

So the enterprise is now non-compliant, and it got there by patching for security. The free, compliant alternative would have been to stay on an old, unpatched BCL build — a worse outcome for security. This is the genuine bind the OTN licence creates, and it is why so many estates are unknowingly exposed. Our guides on installer download compliance and auto-update risk cover how to detect and stop it. The clean resolution is to move production off Oracle's OTN-licensed builds entirely, onto a free OpenJDK build that has no such restriction.

OTN across your environments

Because the OTN licence draws its line at development and testing versus everything else, it is worth working through what that means for each tier of a typical enterprise environment — because the boundary is less obvious than it looks.

Development. Developer workstations and development environments running OTN-licensed Oracle Java are within the free rights. This is the one tier that is clearly safe.

Testing and QA. Test and quality-assurance environments are likewise covered by the free development-and-testing rights. A dedicated test environment running OTN Oracle Java is permitted.

Staging and pre-production. Here the line gets harder. A staging environment that exists purely to test releases before they go live can reasonably sit within the testing right. But staging environments are often used for more than testing — for demonstrations, for training, as a warm standby, or to run genuine business processes. The closer staging gets to doing real work, the more it looks like commercial use. Staging is not automatically safe.

Disaster recovery and standby. A disaster-recovery environment is a particular trap. It is not a test environment — it exists to run the business if production fails, which is unambiguously a commercial-use purpose. A DR environment running OTN Oracle Java should be treated as production for licensing, even though it is idle most of the time.

Production. Production is commercial use, plainly and without argument. OTN-licensed Oracle Java in production needs a subscription.

The safe rule when in doubt: if an environment does anything other than develop and test software, do not assume the free OTN rights cover it. Our note on test environment licensing covers the edges in more detail.

The audit exposure

Oracle's Java audits are, in large part, a search for OTN-licensed Oracle Java being used commercially. The OTN licence is, from Oracle's perspective, an audit instrument: it creates a free on-ramp that gets Oracle Java widely installed, and a commercial-use clause that turns much of that installed base into a paid liability.

When Oracle reviews an estate, every Oracle JDK 11 install and every post-8u211 Oracle Java 8 install running anything beyond development and testing is, on Oracle's reading, a breach requiring a subscription. And Oracle does not price the remedy as “license these specific servers.” It prices it through the Java SE Universal Subscription on the employee metric — your whole headcount — frequently with backdated fees from the date the OTN-licensed use began. A handful of OTN installs in production can become a claim to license every employee, for several years. Our guides on how Oracle detects Java and audit scope limitation cover the mechanics and the defence. The encouraging counterpoint: these claims are highly contestable — across more than 340 engagements, audit defence work has averaged a 68% reduction in the claim — because the development/production classification, the employee count, and the backdating period are all arguable.

Staying compliant

There are two coherent ways to be safe with the OTN licence, and a half-measure that is not.

The first coherent path is to keep Oracle's OTN-licensed Java strictly within its free rights — development and testing only — and to license every production and internal-business use through a paid Java SE subscription. This works, but it means accepting the headcount-priced subscription, and it requires genuine, ongoing control to ensure no OTN build ever drifts into production.

The second coherent path, and the one most enterprises ultimately choose, is to remove Oracle's OTN-licensed builds from the picture. Run free OpenJDK builds — Eclipse Temurin, Amazon Corretto, Azul Zulu, BellSoft Liberica and others — which carry no commercial-use restriction and no subscription requirement, in development and production alike. Once your estate runs no Oracle JDK build, the OTN commercial-use clause simply has nothing to attach to. Our OpenJDK comparison and migration guide set out how.

The half-measure that fails is assuming your internal-only applications are not “commercial” and therefore covered by the free OTN rights. They are not. That assumption is the most common reason an enterprise believes it is compliant when it is not.

Frequently asked questions

This article is general information on the OTN licence, not legal advice. Licence terms vary by version and download date; consult a qualified independent Java licensing specialist on your specific estate.