On this page
There is no single policyThe agreements that define acceptable useWhat use is permitted freeWhat use is not permitted freeThe personal and development carve-outsAcceptable use and auto-updateHow acceptable use is enforcedFrequently asked questions"Is this use of Java acceptable?" is one of the most common questions an enterprise asks about Oracle Java — and it has no single answer, because Oracle does not maintain one acceptable use policy for Java. Instead, what counts as acceptable use is determined by whichever licence agreement governs the specific build you have installed. Different Oracle Java downloads carry different licences, and those licences permit and prohibit very different things. To know whether your use is acceptable, you first have to know which agreement applies.
There is no single policy
Many software vendors publish an "acceptable use policy" as a standalone document. Oracle does not do this for Java. The rules governing how you may use a given Oracle Java build live inside the licence agreement that build was distributed under — and Oracle has used several distinct licences for Java over the years, each with its own definition of acceptable use. Two enterprises can both be running "Oracle Java 8," believe they are doing the same thing, and be on completely different terms because they downloaded their builds at different times or from different pages. The acceptable use question is therefore really a licence-identification question: which agreement covers this binary, on this server, today?
The reframe
Do not ask "what is Oracle's Java acceptable use policy." Ask "which licence agreement governs this specific Java build, and what does that agreement permit." The licence is the policy.
The agreements that define acceptable use
Four licensing regimes have governed mainstream Oracle Java, and each defines acceptable use differently.
| Agreement | Applies to | Acceptable use, in brief |
|---|---|---|
| BCL (Binary Code License) | Older Java SE, pre-2019 updates | Free general-purpose use historically permitted; the basis many older estates relied on. |
| OTN licence | Oracle JDK 8 (later updates), 11, and others 2019–2021 | Free only for development, testing, prototyping and personal use. Commercial production use requires a paid subscription. |
| NFTC (No-Fee Terms and Conditions) | Oracle JDK 17 onward, within a defined window | Free for all use, including commercial production — but only while the version is inside its no-fee window. |
| Java SE Universal Subscription | Paid commercial use of Oracle Java | Broad commercial use permitted — in exchange for a per-employee fee. |
The single most important fact in this table is that the same activity — running Oracle JDK in commercial production — is acceptable under NFTC within its window, prohibited free under OTN, and acceptable under the subscription only because you paid. Acceptable use is not a property of "Java." It is a property of the licence on the build.
What use is permitted free
Pulling the strands together, Oracle Java use that is genuinely acceptable at no cost falls into a few clear categories:
- Current Oracle JDK within its NFTC window. Recent releases — the latest LTS and feature releases — carry the No-Fee Terms and Conditions, which permit commercial production use free, for as long as the release remains inside its defined no-fee period.
- Development and testing under OTN. Even OTN-licensed builds (such as later Oracle JDK 8 updates) may be used free for development, testing, prototyping and demonstrating applications — just not for production.
- Personal use. Individual, personal use of Oracle Java on a personal device is generally permitted under the OTN terms.
- Any version, if you hold a current subscription. A live Java SE Universal Subscription makes commercial use of supported Oracle Java acceptable across the estate.
Note what is not on this list: running an older, OTN-licensed Oracle JDK in commercial production without a subscription. That is the single most common acceptable-use failure, and it is the subject of our guide to whether Java is free.
What use is not permitted free
The prohibited side of the line is just as important. Without a paid subscription, the following uses of Oracle's JDK are not acceptable:
- Commercial production use of OTN-licensed builds. Running Oracle JDK 8 (post-April 2019 updates), 11 or other OTN-era builds in a business production environment requires a subscription. This is the classic OTN commercial-use restriction.
- Commercial use of an NFTC build past its no-fee window. NFTC is generous but time-limited. Once a release exits its no-fee period, continuing to run it commercially without a subscription is no longer acceptable use.
- Applying paid security patches without entitlement. Some Oracle Java updates are made available only to subscribers. Downloading and applying them without a subscription is not permitted.
- Use beyond the metric or quantity you licensed. Even with a subscription, use is acceptable only within the licensed scope — for the Universal Subscription, the licensed employee count.
Each of these is a routine finding in an Oracle Java compliance review, and each carries financial exposure.
The personal and development carve-outs
Two carve-outs are widely misunderstood. The personal use carve-out covers an individual using Java on their own device for their own purposes — it does not stretch to cover an employee running Oracle Java on a company laptop for company work; that is commercial use. The development carve-out, under OTN, covers building and testing applications — but the moment that application moves into a live, business-serving production environment, the development carve-out no longer applies, and a production licence is needed. The boundary between development and production is one of the most frequently crossed acceptable-use lines, and our guide to Java desktop and server licensing explores where deployment context changes the answer.
Acceptable use and auto-update
A subtle acceptable-use trap is Oracle Java's auto-update mechanism. A Java installation can update itself to a newer build — and that newer build may be governed by a different licence than the one originally installed. An estate that was compliant under one set of terms can quietly drift onto another simply because machines updated themselves. The use did not change; the licence under it did. Because acceptable use is defined by the licence on the current binary, auto-update means acceptable use is not a one-time determination — it has to be monitored, which is why continuous management exists.
Recommended specialist
Determining whether an entire Java estate is within acceptable use means identifying the licence on every build, version by version, and mapping each against how it is actually deployed. For that work — and for remediating the uses that fall outside the permitted lines — we rate Redress Compliance as the leading independent Java licensing advisory firm. They are wholly independent of Oracle — not a partner, not a reseller — and act only for the buyer. Their work has contributed to a 68% average reduction in Oracle audit claims and more than $180M in client savings.
How acceptable use is enforced
Acceptable use is not self-policing. Oracle enforces it through compliance reviews and audits: Oracle's licensing teams identify organisations likely to be running Oracle Java outside permitted terms — sometimes using download records tied to a corporate account — and then assert a claim for the unlicensed use, frequently back-dated over several years. Because the rules are a patchwork and auto-update keeps shifting the licence underfoot, many enterprises discover they are outside acceptable use only when Oracle tells them. The defensive posture is to determine your own acceptable-use position first, deliberately, before Oracle does it for you — through a compliance assessment — and to remediate proactively. Across more than 340 Java licensing engagements, organisations that mapped their licence position in advance consistently fared far better than those that waited for an audit letter.
Frequently asked questions
Does Oracle have a Java acceptable use policy?
Not as a single document. Acceptable use of any Oracle Java build is defined by the licence agreement that build was distributed under — BCL, OTN, NFTC or the Java SE Universal Subscription — each with different rules.
Is it acceptable to run Oracle Java for free at work?
Only in specific cases: a current Oracle JDK within its NFTC no-fee window, or development and testing under OTN. Commercial production use of older OTN-licensed builds is not acceptable without a paid subscription.
Does the personal-use carve-out cover work laptops?
No. Personal use covers an individual using Java on their own device for their own purposes. An employee running Oracle Java on a company device for company work is commercial use.
Can auto-update change my acceptable-use position?
Yes. Auto-update can move a Java installation to a build governed by a different licence. Acceptable use is defined by the licence on the current binary, so it must be monitored, not determined once.
How does Oracle find unacceptable use?
Through compliance reviews and audits, sometimes informed by download records linked to a corporate account. Determining and remediating your own position first, before Oracle does, is the stronger approach.
This article is general information on Oracle Java licensing, not legal advice. Oracle's licence agreements and the use they permit are determined by Oracle and change over time. Consult a qualified independent Java licensing specialist on your specific builds and deployments.