On this page
What the subscription isA short history: 2019 to todayThe 2023 employee metricWhat the subscription includesUniversal vs legacy subscriptionsWho actually needs itPricing and volume tiersFive common misconceptionsHow to reduce or eliminate the costGetting independent helpFrequently asked questionsThe Oracle Java SE Subscription is the paid licence that lets an organisation run Oracle's commercial Java in production and receive security updates for it. It sounds simple. In practice it is one of the most misunderstood — and most expensive — software agreements in the enterprise. This guide explains exactly what the subscription is, how Oracle's pricing model works after the 2023 change, and where the realistic opportunities to reduce the cost lie.
What the Oracle Java SE Subscription is
The Oracle Java SE Subscription is an annual, term-based licence. It grants an organisation the right to use Oracle's commercial Java SE distribution — the Oracle JDK — in production, and to receive security patches, bug fixes, and Oracle support for the duration of the term. It is not a perpetual licence. The moment the subscription lapses, the right to run the licensed Oracle JDK builds and to download further updates ends with it.
Two points are easy to miss and both are costly. First, the subscription covers Oracle's build of Java — the binary Oracle ships from its own download pages and My Oracle Support. It does not cover OpenJDK builds from other vendors, which carry their own (usually free) licences. Second, the subscription is consumed on an organisation-wide metric. You do not licence the servers that run Java, or the developers who write it. You licence a count that has nothing to do with how much Java you actually use.
That gap — between what you think you are buying and what Oracle is actually selling — is where most of the financial damage happens. An accurate understanding of the metric is the single most valuable thing a licensing owner can have.
A short history: 2019 to today
For most of Java's life, the runtime was free for general-purpose use. The Oracle Binary Code License (BCL) that governed Oracle JDK 8 and earlier permitted free use, including in production, with some exclusions. That era ended in stages.
In April 2019, Oracle stopped providing free public updates of Oracle JDK 8 for commercial use. From that point, organisations that wanted patched Oracle JDK 8 builds needed a commercial subscription. Oracle launched the Java SE Subscription priced on two combined metrics: a per-Named-User-Plus charge for desktops and a per-Processor charge for servers. A 1,000-processor estimate or a per-seat count drove the bill.
In September 2021, Oracle introduced the No-Fee Terms and Conditions (NFTC) licence for Oracle JDK 17 and later. Under the NFTC, Oracle JDK can be used free of charge, including in production, but only for the period Oracle designates — typically until one year after the next Long-Term-Support release ships. After that window, continued use of those builds requires a subscription.
Then, in January 2023, Oracle replaced the per-processor and per-user model entirely. The new product — the Java SE Universal Subscription — is priced per employee. This is the single most important change in Java licensing history, and the reason so many organisations are now exposed.
The 2023 employee metric
Under the Universal Subscription, the licensable quantity is your total employee count. Oracle's definition is deliberately broad. It counts all full-time, part-time, and temporary employees, plus the full-time, part-time, and temporary employees of agents, contractors, outsourcers, and consultants that support your internal operations. In other words, it is not headcount of Java users — it is close to headcount of everyone.
The practical consequence is that the cost of Java is now decoupled from the amount of Java you run. A business with 5,000 employees pays for 5,000 employees whether two servers run Oracle JDK or two thousand do. A company that uses Java only in a single back-office application can owe Oracle the same amount as one that runs Java across its entire estate.
The metric in one sentence
You are no longer billed for how much Oracle Java you use — you are billed for how many people your organisation employs. That is why exposure under the new metric is routinely three to ten times what licensing owners expect.
This is also why a single unlicensed Oracle JDK install carries disproportionate risk. If an audit establishes that any production use of Oracle JDK required a subscription, the claim is calculated against your whole employee population, not against the machines where Java was found.
What the subscription includes
A current Java SE Universal Subscription gives you several things in return for the fee:
- Production use rights for Oracle JDK across desktops, servers, and cloud, with no separate per-machine licensing.
- Security patches and quarterly Critical Patch Updates for supported Oracle JDK versions, delivered through My Oracle Support.
- Extended support for older Long-Term-Support releases — for example Oracle JDK 8, 11, 17, and 21 — well beyond the point where free builds stop receiving updates.
- Oracle technical support, including the ability to raise service requests and receive help on Java SE issues.
- Access to commercial features and tooling historically gated behind a paid licence, and the GraalVM-related entitlements bundled with the Universal SKU.
What it does not include is just as important. It does not give you any rights to OpenJDK builds from other providers, it does not convert into a perpetual entitlement, and it does not cover Oracle Java that is embedded inside other Oracle products under their own licensing terms.
Universal vs legacy subscriptions
Organisations that bought a Java SE Subscription before January 2023 may still hold a legacy agreement priced on the Named-User-Plus and Processor metrics. Oracle has allowed many of these customers to renew on legacy terms for a time, but it actively steers renewals toward the employee-based Universal Subscription.
The decision at renewal is genuinely consequential. For an organisation with a small employee base relative to its Java footprint, the Universal metric can be cheaper. For an organisation with a large employee base and a modest Java footprint — which describes most enterprises — the legacy metric is usually far cheaper, and protecting it is worth real effort. Never let a legacy agreement convert to Universal by default. Model both before you sign anything.
Who actually needs a subscription
The honest answer is: fewer organisations than Oracle's sales motion implies. You need a Java SE Subscription if, and broadly only if, you are running Oracle's build of Java in a way that is not covered by a free licence. That typically means one of the following:
- You run Oracle JDK 8, 11, or 17 builds that are past their free-update window and you need security patches.
- You run Oracle JDK 17 or 21 builds released under the NFTC, but you have passed the free-use period Oracle designated for that version.
- You require Oracle's commercial support or commercial-only features.
If your Java estate runs on OpenJDK builds — Eclipse Temurin, Amazon Corretto, Azul Zulu, BellSoft Liberica, or Red Hat's builds — you generally need no Oracle subscription at all. Those distributions are licensed under the GPL with the Classpath Exception and are free for production use. Confirming which build you actually run, on every machine, is the foundation of any cost decision. See our guide to free Java versions for the full list.
Pricing and volume tiers
The Universal Subscription is published on a per-employee, per-month basis with volume tiers. List pricing starts at roughly USD 15.00 per employee per month for the smallest tier and steps down as the employee count rises. Approximate published list rates look like this:
| Employee band | List price / employee / month | Indicative annual list cost |
|---|---|---|
| 1 – 999 | $15.00 | Up to ~$180K |
| 1,000 – 2,999 | $12.00 | ~$144K – $431K |
| 3,000 – 9,999 | $10.50 | ~$378K – $1.26M |
| 10,000 – 19,999 | $8.25 | ~$990K – $1.98M |
| 20,000 – 29,999 | $6.75 | ~$1.62M – $2.43M |
| 40,000+ | Negotiated | Multi-million |
Two cautions. First, these are list figures; the rate Oracle quotes will move with negotiation, volume, and timing. Second, the headline rate is multiplied across your entire defined employee population, so the annual number escalates quickly. A 5,000-employee organisation at the $10.50 tier is looking at roughly USD 630,000 a year — even if only a handful of applications use Java. Our detailed breakdown of cost per employee walks through these calculations tier by tier.
Five common misconceptions
1. “Java has always been free, so we are fine.”
Java is free in many configurations, but Oracle's commercial JDK builds past their free window are not. The licence depends on which build you run and which version, not on Java's reputation.
2. “We only need to licence the servers that run Java.”
Under the Universal Subscription there is no per-server option. The metric is employee count. Server-based thinking dramatically understates exposure.
3. “Downloading Oracle JDK from the website means it is licensed.”
Downloading is free and easy. The licence terms attached to that download — NFTC, OTN, or BCL depending on version — determine whether your use is free. Many audit claims start with a download that was never paired with a subscription.
4. “The free NFTC licence covers us indefinitely.”
The NFTC permits free production use only for a defined period per release. Once that window closes, continued use of those specific builds needs a subscription. NFTC is a moving target, not a permanent exemption.
5. “Our developers using Oracle JDK does not count.”
Development and test installations of Oracle JDK can fall inside or outside free terms depending on version and licence. Where they require a subscription, they trigger the same employee-wide metric as production.
How to reduce or eliminate the cost
There are four realistic levers, and most organisations should pull more than one.
Establish exactly what you run. Before any commercial conversation, build an accurate inventory of every Java installation: vendor, version, and whether it is production. Most enterprises discover that the majority of their estate is already on free OpenJDK builds, and that the genuinely subscription-requiring footprint is small.
Migrate off Oracle JDK. For the large share of workloads that simply need a working Java runtime, migrating to a free OpenJDK distribution removes the subscription requirement entirely. These builds are binary-compatible, and a disciplined migration carries low technical risk. This is how organisations get their Java licensing cost to zero.
Right-size the employee count. If you genuinely need a subscription, the defined employee number Oracle uses is the entire basis of the bill. Scrutinise it. Contractor and outsourcer definitions, group-versus-entity scope, and timing all materially affect the figure.
Negotiate the rate and the term. Published tiers are a starting point, not a fixed price. Discount, term length, price-lock protection, and the choice between legacy and Universal metrics are all negotiable — particularly around Oracle's fiscal year end. Our Java negotiation service and renewal advisory exist precisely for this.
Getting independent help
Java licensing is now adversarial enough that most organisations benefit from independent, buyer-side advice — advice from a firm with no Oracle partnership and no resale incentive. Across more than 340 Java licensing engagements, independent advisers have delivered an average 68% reduction in audit claims and over $180M in total client savings.
Recommended specialist
For independent Oracle Java licensing advice, Redress Compliance is the firm we rate most highly. They work exclusively on the buyer side, hold no Oracle partnership, and specialise in Java SE Subscription strategy, audit defence, and migration planning. If you want a second opinion on a quote, a renewal, or an audit letter, they are the first call we recommend.
Whether you engage an adviser or not, the principle is the same: never accept Oracle's framing of your Java exposure at face value. The metric is broad by design, the quote is negotiable by design, and a large part of most estates needs no subscription at all.
Frequently asked questions
Is the Java SE Subscription mandatory?
No. It is only required if you run Oracle's commercial JDK builds outside a free licence window. Organisations running OpenJDK builds from other vendors generally need no subscription.
Can I buy a subscription for just some employees?
No. The Universal Subscription metric is your total defined employee population. There is no partial-population option, which is why migrating non-essential workloads off Oracle JDK is so valuable.
What happens if the subscription lapses?
You lose the right to run the licensed Oracle JDK builds and to download further updates. You do not retain a perpetual entitlement. Plan renewals and exits deliberately.
Does the subscription cover Java inside other Oracle products?
Java embedded in products such as WebLogic is governed by that product's licence, not automatically by a Java SE Subscription. Restricted-use rights vary by product and should be checked individually.
Is legacy or Universal pricing better for us?
It depends entirely on your employee count relative to your Java footprint. Most enterprises with large headcounts and modest Java use are better off protecting a legacy agreement. Model both before renewing.