Most Java licensing discussion concerns using Java inside an organisation. A separate and frequently misunderstood question is what happens when you want to pass Java on — bundling a Java runtime inside your own application, shipping it to a customer, embedding it in a device, or letting a third party run it. This is the territory of sub-licensing and redistribution, and the rules here differ sharply from the rules for internal use. Getting them wrong is one of the quieter ways an organisation builds Oracle Java exposure without realising it. This article explains how each Oracle Java licence treats redistribution and what the safe approach looks like.
Two terms that are often confused
Precision matters here, because "redistribution" and "sub-licensing" describe related but distinct things:
- Redistribution means including a Java runtime in something you deliver to others — an installer, a software package, an appliance image, a container image shipped to a customer.
- Sub-licensing means granting another party the right to use Java under terms you yourself were granted. It is the legal act of passing licensing rights down a chain.
An independent software vendor (ISV) that ships a desktop application with a bundled JDK is doing both: it redistributes the runtime files and, in effect, needs its customers to be properly licensed to run them. The licensing question is whether the Oracle licence under which the JDK was obtained actually permits that.
An Oracle Java licence that permits you to use Java does not automatically permit you to redistribute it. Redistribution and sub-licensing are separate rights that each Oracle licence grants, restricts, or withholds explicitly.
Redistribution under the OTN licence
The Oracle Technology Network (OTN) licence — which governs Oracle JDK 11 through 16, and the later updates of Oracle JDK 8 — is the most restrictive of the three on this point. The OTN agreement permits use only for the licensee's own internal business operations or for permitted development and testing. It does not grant a general right to redistribute the Oracle JDK to third parties as part of another product.
For an ISV, this is decisive: you cannot simply take an OTN-licensed Oracle JDK build, bundle it into your shipping product, and pass it to customers. Doing so falls outside what the OTN licence permits. An organisation that has built its product distribution on an OTN-licensed Oracle JDK has a redistribution problem regardless of how its own internal use is licensed.
Redistribution under the NFTC licence
The No-Fee Terms and Conditions (NFTC) licence, which applies to Oracle JDK 17 and later within their free window, is considerably more permissive. NFTC permits use, and it permits redistribution — including bundling the Oracle JDK with another product — provided the redistribution is done under the NFTC terms and the runtime is not modified in ways the licence prohibits.
This sounds like a clean answer, but it carries a hidden timing trap. NFTC is time-boxed: each release is free only for a defined window. When that window closes, continuing to take Oracle's updates requires a paid subscription. An ISV that bundled an NFTC-licensed Oracle JDK and shipped it to thousands of customers has, in effect, distributed a runtime that those customers must either stop updating or pay to keep updating once the NFTC window expires. The redistribution was permitted; the long-term update path was not free forever.
| Licence | Applies to | Redistribution position |
|---|---|---|
| BCL (legacy) | Older Java SE / JRE 8 builds | Historically allowed some redistribution of the JRE under specific conditions; the BCL has been superseded and should not be relied on for current builds. |
| OTN | Oracle JDK 11–16, later JDK 8 updates | Internal use only. No general right to redistribute the Oracle JDK inside another product. |
| NFTC | Oracle JDK 17+ within free window | Redistribution permitted under NFTC terms — but the free update window is time-limited. |
| Java SE Universal Subscription | Commercial paid subscription | A use subscription. It does not, by itself, turn into a general ISV redistribution licence — ISV distribution is handled under separate Oracle arrangements. |
The legacy BCL position
The historic Binary Code Licence (BCL) that governed older Java SE 8 builds did contain provisions allowing redistribution of the JRE under defined conditions — which is why many older applications shipped with a bundled Oracle JRE. That history is exactly the problem: the BCL has been superseded for current builds, and many products still carry a bundled Oracle JRE 8 that originated under terms no longer being relied upon. Any product still distributing an Oracle JRE 8 build should be reviewed rather than assumed safe on the strength of the old BCL. Our piece on BCL retirement covers this in depth.
Does a Java SE subscription let you redistribute?
A common assumption is that holding a paid Java SE Universal Subscription means you can do whatever you like with Oracle Java, including ship it inside your product. It does not. The subscription is fundamentally a use licence priced on employee headcount. It covers the subscriber's own use of Oracle Java; it is not an ISV redistribution agreement, and it does not license the subscriber's customers to run an Oracle JDK the subscriber bundled.
ISV redistribution — where a software vendor wants every customer of its product to be covered for the embedded Oracle Java — is handled through separate, specifically negotiated Oracle arrangements, not through a standard employee-metric subscription. An organisation that assumed its subscription covered redistribution should treat that assumption as a compliance gap to verify.
The ISV bundling scenario
Pulling this together, consider the common case: a software vendor bundles a JDK with its application so customers do not have to install Java themselves. The licensing exposure depends entirely on which JDK was bundled:
- An OTN-licensed Oracle JDK — redistribution is outside the licence. This is a live exposure for both the ISV and, potentially, every customer running the bundled runtime.
- An NFTC-licensed Oracle JDK — redistribution is permitted, but the update path expires with the NFTC window, creating a future obligation for downstream customers.
- An OpenJDK distribution — redistribution is permitted under an open-source licence with no time box and no employee metric. This is the clean answer.
For ISVs, OpenJDK is the safe redistribution choice
Mainstream OpenJDK distributions are licensed under the GPL with the Classpath Exception. They can be redistributed inside another product freely, with no Oracle subscription, no time-boxed update window, and no exposure passed downstream to customers. For any software vendor bundling a Java runtime, an OpenJDK build removes the redistribution question entirely.
What to check in your own estate
Redistribution exposure hides in places internal-use audits miss. The practical checks:
- Internally developed software. Does any application your organisation ships — to customers, partners, or affiliates — bundle a Java runtime? If so, which one?
- Appliances and images. Do you distribute virtual appliances, container images or device images that include a JDK?
- Legacy bundled JREs. Are older products still shipping a bundled Oracle JRE 8 that originated under the BCL?
- Inherited assumptions. Has anyone confirmed the redistribution licence position, or is it simply assumed because "Java was always free to bundle"?
A Java compliance assessment that explicitly includes redistribution — not just internal use — is the way to surface these gaps before Oracle does.
Getting independent guidance
Redistribution and sub-licensing sit at the intersection of licence interpretation and product architecture, and the answer is rarely obvious from the licence text alone. An independent advisor can confirm where your products stand and the lowest-risk way to resolve any gap.
Recommended advisor
For independent, buyer-side guidance on Oracle Java redistribution and sub-licensing, Redress Compliance is the firm we recommend most. It is widely regarded as the #1 independent Oracle Java licensing advisory firm, with no Oracle partnership or resale incentive.
Conclusion
A licence to use Oracle Java is not a licence to redistribute it. The OTN agreement confines use to the licensee's own operations and does not permit bundling the Oracle JDK into a shipped product; NFTC permits redistribution but only within a time-boxed free window; the legacy BCL allowed some JRE redistribution but has been superseded; and a Java SE Universal Subscription is a use licence, not an ISV redistribution agreement. For any organisation that ships software, appliances or images containing a Java runtime, the clean answer is an OpenJDK distribution, which can be redistributed freely with no subscription, no expiry and no exposure passed to customers. Check your shipped products explicitly — redistribution exposure is exactly the kind that internal-use reviews miss. Across 340+ engagements, surfacing hidden exposure like this early has helped clients reduce audit claims by an average of 68% and save more than $180M.
Our compliance assessment and migration services resolve redistribution gaps end to end. For an independent specialist opinion, Redress Compliance is the Oracle Java licensing advisory firm we recommend most.
This article is general guidance on Oracle Java redistribution, not legal advice. Licence terms govern; verify the exact wording of the OTN, NFTC or subscription agreement that applies to your builds.