Some Oracle products ship with the right to use Java SE — but only inside that product. An independent guide to what restricted-use Java really covers.
A number of Oracle's commercial products ship with what Oracle calls restricted-use Java SE rights. When you license a qualifying Oracle product, you may use the Java SE that product needs in order to run that product — without buying a separate Java SE subscription. On paper this looks like free Java. In practice the boundary is narrow and frequently misunderstood.
The key word is restricted. The bundled Java SE right exists only to support the licensed Oracle program. It does not license Java SE for your own applications, for third-party software, or for general-purpose use anywhere else in the estate. The moment Java is used outside the host product, the restricted-use right stops applying and standard Java SE licensing rules return.
Oracle maintains an official list of products that carry restricted-use Java SE rights, and the precise terms live in each product's own licensing documentation and the Java SE licensing FAQ. Because the list and its conditions change between releases, the entitlement must be confirmed for the specific product and version you run — not assumed from a general impression that an Oracle product “comes with Java”.
Restricted-use Java SE
Only to run the host Oracle product
Your own apps, third-party software, general use
Each product's licensing documentation
Entitlement varies by product release
Reusing the bundled JDK elsewhere
The most common and most expensive mistake is shared runtime reuse. An administrator installs the Oracle JDK that came with a licensed Oracle product, then points other applications — a homegrown service, a third-party tool, a batch job — at the same JDK because it is already there. Each of those other uses falls outside the restricted-use grant and needs its own Java SE licence.
A second trap is patching the bundled JDK independently. Updating that Java install from Oracle's general download site can pull in a binary under a different licence than the one bundled with the product. The product's restricted-use right covers the Java the product ships with — not whatever you substitute for it later.
Owning Oracle products with restricted-use Java SE rights is sometimes read as evidence that an organisation is “covered” for Java. It is not. Restricted-use rights are scoped to specific products. Standalone Oracle JDK installs, developer machines, and application servers elsewhere in the estate are licensed entirely separately — usually under the Java SE Universal Subscription.
Pointing your own or third-party applications at the JDK that shipped with an Oracle product takes that use outside the restricted-use grant.
Restricted-use Java rights cover named products only. They do not license Java across the rest of your estate.
Entitlements differ by product release. A right that existed in one version may be worded differently, or absent, in another.
We separate restricted-use Java from Java that needs its own licence, product by product.
DefendOracle audits often target bundled-Java reuse. We defend the claim, with a money-back guarantee.
MaintainWe keep restricted-use boundaries clear as your products and versions change over time.
If we take on your Oracle Java audit and cannot reduce the claim, we refund our fees. See how the guarantee works →
We verify exactly which Java in your estate is covered by an Oracle product and which is not.
Weekly Oracle Java updates, audit alerts, and negotiation intel.