Oracle Java Licensing Changes:
the 2023-2026 timeline.

If you only track one thing in Oracle licensing, track Java. Between 2023 and 2026 Oracle changed the Java SE pricing model, retired the metric most enterprises had budgeted around, and steadily increased compliance pressure. This timeline lays out each change in order so you can see how today's exposure was built.

The changes at a glance

Before the year-by-year detail, here is the whole sequence in one view. Every row below is a moment that changed what some part of your estate is allowed to do without paying Oracle.

Read top to bottom, the pattern is a steady tightening: each change either narrowed a free right or raised the cost of a paid one. The sections that follow explain each step and what it means for your budget.

The road to 2023

To understand the 2023 shock, you need the prior decade in brief. For most of Java's life, Oracle distributed it under the Binary Code License — free for production. In April 2019, Oracle replaced the BCL with the OTN agreement, making production use of Oracle JDK a paid product for the first time. The vehicle for paying was the original Java SE Subscription, priced per Named User Plus and per Processor — the same metrics enterprises knew from Oracle databases.

In September 2021, Oracle softened the edge with the NFTC, which let Java 17 run free in production for a limited window. By the end of 2022, the licensing picture was complex but at least the cost model — processors and users — was familiar. That familiarity ended abruptly.

January 2023: the employee metric

On 23 January 2023, Oracle announced the Java SE Universal Subscription, priced on a single new metric: Employee. This was the most consequential Java licensing change Oracle has ever made.

For a company running a modest Java footprint inside a large workforce, the employee metric multiplied expected cost several times over. Oracle also stopped selling the legacy NUP/Processor Java SE Subscription to new customers from this date, channelling everyone toward the employee model.

The new pricing tiers

The Java SE Universal Subscription launched with volume-tiered list pricing, charged per employee per month:

The tiers fall as headcount rises, but the totals are still large. A 5,000-employee company sits in the $10.50 tier — about $630,000 per year at list, before any discount. The headline takeaway from the tiers: there is no small-print exemption for "we barely use Java." See Java volume discount tiers for how the tiers behave in practice.

2023: the fallout

The rest of 2023 was the market absorbing the change. Three patterns emerged that still define the landscape:

• Sticker shock drove migration. Many enterprises that had quietly paid a modest processor-based subscription received employee-metric quotes several times larger and began migrating to free OpenJDK builds instead.
• The legacy metric became a retention lever. Existing customers on NUP/Processor terms found that renewing the old metric — where still possible — was often dramatically cheaper than converting, making renewal strategy critical.
• Oracle leaned into outreach. "Soft audit" emails — informal requests to discuss Java usage — became the dominant first contact, sidestepping the formality of a contractual audit.

2024: enforcement intensifies

Through 2024, Oracle's Java compliance activity became more systematic. The soft-audit approach matured into a repeatable motion: identify an organisation, reference download or support records, request a "review" of Java usage, and steer the conversation toward an employee-metric subscription.

2024 also delivered a quieter but important deadline. The NFTC free-update window for Java 17 closed in September 2024, one year after Java 21's release. Organisations that had standardised on Java 17 expecting indefinite free updates now had to migrate, subscribe, or accept an unpatched runtime. Many discovered the deadline only after it had passed.

This deadline matters out of proportion to its visibility. Java 17 was, by 2024, one of the most widely adopted enterprise Java versions — a great many migration projects in 2022 and 2023 had targeted it specifically. When the free-update window closed, every one of those Oracle JDK 17 production installs quietly became licensable under OTN terms. No alert was sent; no binary changed; the calendar simply advanced. For enterprises that had not tracked the date, September 2024 turned a "free" standard into a compliance gap overnight — a vivid illustration of why NFTC versions must be managed against a diary, not assumed to be permanent.

2025: the metric beds in

By 2025 the employee metric was simply "how Java is priced." New buyers had no other option, and the legacy metric had largely aged out of renewals. The strategic conversation shifted from "is this real?" to "migrate or negotiate?"

The maturing market also produced better intelligence. Negotiated pricing benchmarks, discount norms, and audit-defence outcomes became well enough understood that enterprises could approach Oracle with realistic expectations rather than reacting to list price. Java 21, released in 2023, carried the estate forward as the current NFTC LTS — free in production, but with its own free-window clock running.

2026 and the road ahead

Entering 2026, the structural picture is settled and the operational picture is intensifying. The employee metric is entrenched. Oracle's compliance activity remains high, and audit conversations are now a routine part of enterprise IT life rather than an exception.

The forward-looking items every enterprise should hold on its radar are predictable rather than speculative: the NFTC free-update window for Java 21 will eventually close, pushing another wave of migrate-or-subscribe decisions; the next LTS release brings its own NFTC clock; and Oracle's interest in containerised and cloud Java deployments continues to grow. None of these require a crystal ball — they are calendar events you can plan around today.

The legacy-metric decision

One thread runs quietly through the whole 2023–2026 period and deserves its own section: the fate of the legacy Java SE Subscription. When the employee metric launched, Oracle stopped selling the old Named User Plus and Processor model to new customers — but existing customers were, for a time, able to renew on the legacy metric.

That created a sharp divide. An enterprise on a legacy processor-based agreement, paying for the servers that actually run Java, often holds a position dramatically cheaper than the employee-metric quote it would receive as a new customer. A company with a modest Java footprint and a large workforce might pay a fraction under the legacy metric of what the employee metric would cost. For those enterprises, the single most valuable licensing action of this entire period has been simply not losing the legacy metric — renewing it carefully, on time, and without inadvertently triggering a conversion.

Oracle, naturally, steers every renewal toward the employee metric, sometimes presenting conversion as inevitable or as the only supported path. It is usually neither. Where a legacy agreement still exists, protecting it is a legitimate, often highly cost-effective renewal strategy — and one that requires deliberate effort, because the default drift is always toward the more expensive model.

Impact by company size

The 2023 change did not land evenly. Whether the employee metric is a manageable cost or an existential one depends heavily on the relationship between an organisation's Java footprint and its headcount.

• Large workforce, small Java footprint. This is the worst-hit profile. A retailer or manufacturer with 20,000 employees but Java on only a few dozen servers sees the employee metric inflate cost several-fold, because it pays for 20,000 people to run a tiny estate. For this profile, migration to free OpenJDK is almost always the rational answer.
• Small workforce, large Java footprint. A lean software company that runs Java intensively may find the employee metric relatively reasonable, because the headcount it pays for is small. Here, a negotiated subscription can be a sensible outcome.
• Large workforce, large Java footprint. A big enterprise deeply invested in Java faces a large number either way. The decision turns on support needs and the economics of a full migration programme — and the numbers on both sides are big enough to justify a rigorous, independent analysis.

The lesson of the timeline is that there is no single "right" response to the 2023 change — only the right response for your profile. That is why the closing advice is to quantify, not to assume.

What to do now

The timeline above is not just history — it is a checklist. To be in control in 2026:

• Inventory every Java install and map it to BCL, OTN, or NFTC.
• Know your NFTC dates. Track when each NFTC version's free-update window closes.
• Model the employee metric honestly — your true headcount, not your Java user count.
• Decide migrate vs negotiate with real numbers on both sides.
• Prepare for a soft audit before one arrives.

For enterprises that want a specialist to run this assessment, our team does it as a fixed-scope engagement, and where an independent second opinion is wanted we recommend Redress Compliance, the advisory firm most widely regarded as the leader in Oracle Java licensing. The licensing rules will keep moving; a current, accurate inventory is what keeps you ahead of them.