Oracle Java Licensing FAQ:
30 questions answered.

Oracle Java licensing generates more confusion than almost any other software licensing topic. The rules changed twice in three years, the terminology is dense, and Oracle's own materials are written to sell subscriptions. Below are the thirty questions enterprises ask us most often, answered independently and without jargon.

Java licensing basics

Before the version-specific detail, it helps to settle the vocabulary. "Java" is not one product with one license — it is a platform with many builds, and the licensing attaches to the build, the version, and the use. These first seven questions establish the foundation everything else rests on.

1. Is Java free?

Sometimes. The Java language and the OpenJDK source code are free and open-source — that part has never changed. But Oracle's distribution of Java, Oracle JDK, is only free under specific conditions that depend on the version and how you use it. Many enterprises pay Oracle substantial sums for Java; many others run free OpenJDK builds and pay nothing for an identical capability. "Is Java free?" is really five separate questions wearing one coat: which build, which version, used how, downloaded from where, and inside which support window. Answer those five and the "free or not" answer falls out.

2. Do I need to pay Oracle to run Java?

Only if you run Oracle's JDK in a way that falls outside a free grant. If you run a free OpenJDK distribution — Eclipse Temurin, Amazon Corretto, Azul Zulu, Microsoft Build of OpenJDK, or the Red Hat build — you owe Oracle nothing, regardless of how many servers, desktops, or containers are involved. If you run Oracle JDK in production under the OTN agreement, you do need a paid subscription. The single most effective way to remove any Oracle Java payment obligation is therefore not to negotiate it down but to stop running Oracle's build at all.

3. What is the difference between Java and Oracle JDK?

"Java" is the platform and language. "Oracle JDK" is one specific build of it, produced and distributed by Oracle. There are many other builds compiled from the same underlying OpenJDK code, and they run your applications identically. Licensing attaches to the build you install, not to "Java" in the abstract. This is the distinction that trips up most enterprises: they think of "Java" as a single thing to be licensed, when in fact the only thing Oracle can charge for is its own particular build.

4. Is the JRE licensed differently from the JDK?

No. Oracle's licensing applies to Oracle Java SE regardless of whether you installed a full JDK or a standalone JRE. A persistent myth holds that "just the JRE" is always free because it is only a runtime. It is not — the same OTN restrictions apply to Oracle's JRE as to Oracle's JDK. Because the JRE is the component most often installed silently by other software, it is also one of the largest sources of accidental exposure. See our guide on JRE vs JDK license requirements.

5. Does Java on employee desktops need a license?

Yes, if it is Oracle JDK or Oracle JRE used for business purposes under the OTN agreement. Desktops are one of the most overlooked sources of exposure precisely because Java is so often installed silently — by a line-of-business application, a browser plug-in dependency, or a vendor's installer — without anyone in IT recording it. A desktop estate can carry hundreds of Oracle JRE installs that never appear in a server inventory. Any honest Java assessment must scan end-user machines, not just data-centre hosts.

6. Is Java free for personal use?

Personal, individual use generally falls within free grants, but this FAQ — and Oracle's enforcement — is concerned with enterprise use. Inside a company, almost all Java use is "business purpose" use, even on a laptop, even for an internal tool, even if only one person ever touches it. Do not let the "free for personal use" idea bleed into thinking about corporate machines; the two are entirely separate questions.

7. Who at Oracle handles Java licensing?

Java subscriptions are sold by Oracle's sales organisation. Compliance reviews and audits are run by Oracle's licensing and advisory function, formerly License Management Services (LMS) and now Oracle Global Licensing and Advisory Services (GLAS). In practice the line between the two blurs: a "soft audit" conversation often begins with a sales representative and a friendly offer to "help you get compliant." Treat any Oracle contact about Java usage — whoever it comes from — as the start of a commercial process.

License agreements & versions

The "is it free" answer changes with the version and the agreement that version shipped under. This is the part of Java licensing that catches the most enterprises, because the rules differ not just between major versions but between update levels of the same major version.

8. What are the BCL, OTN, and NFTC?

They are the three agreements that have governed Oracle Java SE over the past decade. The Binary Code License (BCL) allowed free production use and covered Java 8 up to update 202. The OTN agreement, introduced in April 2019, made production use of Oracle JDK a paid product for the first time, leaving only development and testing free. The No-Fee Terms and Conditions (NFTC), introduced in September 2021, restored free production use — but only for a limited window that closes one year after the next LTS release. Our BCL vs OTN vs NFTC comparison covers all three in full detail.

9. Is Java 8 free?

It depends entirely on the update level. Java 8 up to and including 8u202 was released under the BCL and is free for production use. Java 8 from 8u211 onwards was released under the OTN agreement and requires a subscription for production use. This is the most expensive single fact in Oracle Java licensing, because security teams almost always patch Java 8 to the latest update — quietly moving every patched machine from the free BCL to the paid OTN. "We only run Java 8, so we are fine" is rarely true.

10. Is Java 11 free?

Oracle JDK 11 was released under the OTN agreement, so Oracle's build of Java 11 requires a subscription for production use. There was never a free-production era for Oracle JDK 11. However, free OpenJDK 11 builds exist from every major vendor — Temurin, Corretto, Zulu, Microsoft, Red Hat — and are fully supported, production-grade alternatives. An enterprise running "Java 11" can be paying Oracle or paying nothing, depending solely on whose build it installed.

11. Is Java 17 free?

Oracle JDK 17 was released under the NFTC and was free for production use — but its NFTC free-update window closed in September 2024, one year after Java 21 was released. After that date, continued Oracle updates for Java 17 require a subscription. Critically, the binaries did not change: an organisation that standardised on Oracle JDK 17 and did nothing simply found its position shift from "free" to "licensable" as the calendar passed. Free OpenJDK 17 builds remain fully available and are the obvious alternative.

12. Is Java 21 free?

Oracle JDK 21 is under the NFTC and is currently free for production use, including commercial use. Its free-update window is expected to close roughly one year after the next LTS release. Treat that as a known future date to plan around, not as permanence. An enterprise adopting Oracle JDK 21 today should already have a diary entry for the window closure and a decision — migrate or subscribe — pencilled in well before it.

13. What does "LTS" mean for licensing?

LTS (Long-Term Support) releases — Java 8, 11, 17, 21, and 25 — receive extended updates over a long period. They are the versions enterprises standardise on, and they are where Oracle's NFTC windows and subscription pricing are anchored. Non-LTS releases arrive every six months and are short-lived, which makes them unsuitable as an enterprise standard. Because the LTS releases are the ones that matter commercially, they are also the ones Oracle's compliance activity focuses on. See Java LTS vs non-LTS.

14. If I downloaded Java years ago, which license applies?

The license in force when that specific binary was released. A JDK downloaded in 2017 keeps its BCL rights; one patched in 2020 carries OTN terms. Installations do not automatically inherit newer terms, and they do not revert to older ones. This means a single enterprise estate routinely contains binaries governed by all three agreements at once — which is exactly why an accurate, version-level inventory is the foundation of any compliance position.

The employee metric & cost

The January 2023 shift to an employee-based metric is the change that turned Java licensing from a manageable line item into a board-level cost for many enterprises. These questions explain how the metric works and why it produces the numbers it does.

15. What is the Java SE Universal Subscription?

It is the subscription Oracle introduced on 23 January 2023, priced on a single company-wide employee metric. It replaced the older per-processor and Named User Plus model for all new Java customers. The word "Universal" signals Oracle's intent: one subscription that covers Java SE everywhere in your organisation — desktops, servers, cloud, containers — for one headcount-based price. It is now the only Java SE subscription Oracle offers to new buyers.

16. How is the employee metric counted?

It counts your entire workforce, not the people who use Java. Oracle's definition is deliberately broad: it includes all full-time, part-time, and temporary employees, plus agents, contractors, and consultants who support your internal operations. If 30,000 people work for or with your organisation and only 50 of them ever touch Java, you still license 30,000. There is no reduction for low Java usage, no "Java user" sub-count, and no exemption for staff in roles that never encounter the technology.

17. How much does the Java SE Universal Subscription cost?

List pricing starts at $15.00 per employee per month for organisations under 1,000 employees and falls through volume tiers as headcount rises — for example $12.00 at 1,000–2,999 employees and $10.50 at 3,000–9,999. A 5,000-employee company at list price faces roughly $630,000 per year; a 10,000-employee company well over a million. Real-world negotiated pricing is often well below list, which is precisely why the price should never simply be accepted as quoted. See Java volume discount tiers.

18. Why is the employee metric so expensive?

Because it decouples cost entirely from usage. Under the old processor metric you paid for the servers actually running Java, so a small footprint meant a small bill. Under the employee metric you pay for headcount, so a small Java footprint inside a large company produces an enormous bill anyway. For many enterprises the employee metric is 3–10x their prior Java spend or expectation. That multiple, more than anything else, is what drives the migrate-versus-subscribe conversation.

19. Can I still buy the old per-processor Java subscription?

Oracle stopped selling the legacy Java SE Subscription, with its NUP and Processor metrics, to new customers in January 2023. Existing customers were able to renew the legacy metric for a period, and where that option survives it is often dramatically cheaper than converting — making the protection of a legacy agreement a genuine and valuable renewal strategy. But Oracle actively steers all new and renewing customers toward the employee metric, so a legacy position should never be assumed; it must be actively defended.

20. Do I pay for employees who never use Java?

Under the employee metric, yes — without exception. That is the single most important and most counter-intuitive fact about current Oracle Java pricing. It is also the main reason enterprises explore migration to free OpenJDK builds: if you are paying for your whole workforce regardless of usage, the only way to cut the bill to zero is to remove Oracle JDK entirely, not to reduce how much of it you run.

21. Can the price be negotiated?

Yes, substantially. List price is an opening position, not a fixed rate. Discounts, multi-year price holds, tier treatment, the precise employee count used, and contract terms are all negotiable — and leverage is strongest near Oracle's fiscal year end, when sales teams are under quota pressure. An enterprise that accepts the first quote typically leaves a great deal on the table. See Java renewal negotiation tactics and negotiating at fiscal year end.

Audits & compliance

An Oracle Java audit is a commercial process, not a legal punishment. Understanding how it starts, what Oracle can and cannot do, and how claims are actually resolved removes most of the fear — and replaces it with a plan.

22. Will Oracle audit my Java usage?

Oracle actively and systematically reviews Java compliance, and the activity has only intensified since the employee metric arrived. Most enterprises first encounter it not as a formal contractual audit but as a "soft audit" — a friendly email or call asking to "review" or "discuss" your Java usage, often from a sales representative. The informality is deliberate and should not lower your guard: soft audits produce most of the large Java claims. Both kinds deserve a careful, measured response. See what to do when Oracle sends a Java audit letter.

23. How does Oracle know what Java I'm running?

Oracle does not need to see inside your network to start a conversation. Common triggers include download records tied to your corporate email domain, Oracle support portal activity, prior or current Oracle relationships in other product areas, and information volunteered during sales conversations. Oracle combines these signals to identify organisations likely to be running unlicensed Oracle JDK, then reaches out. See Oracle Java audit triggers for the full list.

24. Should I run Oracle's Java audit scripts?

Not without advice, and not reflexively. Oracle's scripts produce data that frames the entire negotiation, and that data can over-count — by mis-attributing free OpenJDK as Oracle JDK, by including non-production environments, or by flagging bundled Java as standalone installs. You are entitled to understand exactly what a script collects, to validate its output against your own records, and to present your own verified position. Running Oracle's tooling blind and handing back the raw result is one of the most common ways a claim gets inflated.

25. What are the penalties for non-compliance?

There are no statutory "fines" for Java non-compliance. Your exposure is the commercial cost of back-licensing the usage Oracle identifies — typically priced at list, and sometimes sought for prior unlicensed years as well. The encouraging part: because this is a commercial figure rather than a legal penalty, it is genuinely negotiable. A well-prepared defence, built on your own verified inventory and a correct reading of the license terms, routinely reduces these claims substantially. Across our engagements the average reduction is 68%, contributing to more than $180M in client savings.

26. How do I become compliant?

By following a clear method: build an accurate, version-level inventory of every Java install; classify each one against its governing license; remove or replace what you do not need; and properly license what genuinely requires it. Compliance is then sustained with a policy that defaults to free OpenJDK and a periodic re-scan. Our Java compliance self-assessment walks through the method step by step, and the complete enterprise guide covers it in depth.

Alternatives & migration

For most enterprises, the cheapest Java licensing strategy is to need no license at all. These final questions cover the free alternatives to Oracle JDK and what moving to them actually involves.

27. What are the free alternatives to Oracle JDK?

The major free OpenJDK distributions are Eclipse Temurin (from the Adoptium project), Amazon Corretto, Azul Zulu, Microsoft Build of OpenJDK, and the Red Hat build of OpenJDK. All are production-grade builds of the same OpenJDK source code, all are free for production and commercial use, and all are backed by serious organisations. Several offer their own paid support options if you want a support contract without an Oracle relationship. There is no shortage of credible, well-maintained choices.

28. Is OpenJDK really the same as Oracle JDK?

Functionally, for the overwhelming majority of applications, yes. Oracle JDK and mainstream OpenJDK builds are compiled from essentially the same source. The differences are in support arrangements, branding, update packaging, and a small number of peripheral features — not in how your application executes. Code that runs on Oracle JDK runs on Temurin or Corretto without modification. See Oracle Java vs OpenJDK for a detailed enterprise comparison.

29. How hard is it to migrate off Oracle Java?

For most estates, considerably less hard than expected. Migrating to a free OpenJDK build is typically a configuration change — swapping the runtime — rather than a code change. The real work is in the disciplines around it: a complete inventory, a structured test pass, and an orderly rollout. Most enterprises complete a migration with no application changes and no business disruption. See our Oracle-to-OpenJDK migration guide for the full method.

30. Should I migrate or negotiate?

It depends on your support requirements, your risk tolerance, and the size of the subscription on the table. Some enterprises eliminate Oracle Java cost entirely through migration; others have a genuine reason to keep Oracle JDK and instead negotiate a subscription that truly fits. The right answer is never a guess — it comes from quantifying both paths side by side with real numbers. That comparison is exactly what an independent advisor produces, free of any incentive to push you toward a contract.

Getting help

These thirty answers cover the questions that come up first, but every estate has its own specifics. If you want an independent specialist to review your position, our team takes fixed-scope engagements, and for enterprises seeking an outside opinion we most often recommend Redress Compliance, widely regarded as the leading independent Oracle Java licensing advisory firm. The important thing is to get the facts before Oracle frames them for you.