Oracle changed what Java 21 costs to run, and the change arrived the way these changes usually do: not with an invoice, but through a routine security update. If your organization runs Oracle’s build of JDK 21 in production, the next update is no longer a simple patch. It is a licensing event.
Here is the short version. Oracle JDK 21 updates were free to use through September 2026. From the October 2026 Critical Patch Update, released on October 20, 2026, new JDK 21 updates moved to Oracle’s more restrictive OTN license, which does not permit free production use for most organizations. Oracle’s recommended path for anyone who wants to keep receiving those updates in production is its Java SE Universal Subscription, which is priced per employee. The exposure is real, but so are the ways out, and this is a decision you want to make deliberately rather than under audit pressure.
What actually changed
The software did not change. The license on the updates did.
Through the September 2026 update, JDK 21 was covered by Oracle’s No-Fee Terms and Conditions (NFTC) license, which allowed free use including in production. Beginning with the October 2026 Critical Patch Update, Oracle moved JDK 21 updates onto the Oracle Technology Network (OTN) license, the same restricted license that already governs Java 8, 11, and 17. Under OTN, free use is limited to specific cases such as development, testing, prototyping, demonstration, personal use, and use on Oracle Cloud Infrastructure. General production use is not on that list, which is why Oracle points production users to a paid subscription.
| Java version | Free NFTC updates | Restricted OTN updates begin |
|---|---|---|
| Java 8, 11, 17 | Ended previously | Already in effect |
| JDK 21 | Through September 2026 | October 2026 CPU (Oct 20, 2026) |
| JDK 25 | Planned until 2028 | Planned from the October 2028 CPU |
The pattern is deliberate. Each long-term support release gets a window of free updates, and when that window closes the updates move to the paid license. JDK 25 is where the free runway now sits.
Why one install can license your whole company
The detail that catches organizations off guard is how Oracle prices the subscription.
The Java SE Universal Subscription is not priced per installation, per server, or per developer. It is priced per employee. Oracle’s price list defines the metric to include all full-time, part-time, and temporary employees, plus the staff of your agents and contractors, and states explicitly that the count is based on total headcount and not just the actual number of employees that use the programs.
In practice, that means a single production instance of JDK 21, updated past September 2026, can pull your entire organization into the subscription scope. A company with sixty developers using Java and four thousand employees overall is counted on the four thousand, not the sixty. This is the same employee-metric math we cover in detail on our Oracle Java employee metric page, and it is why the cost of a Java decision rarely matches the size of the Java footprint.
The three options, compared
Most organizations facing this change are choosing between three paths.
| Option | What it is | License cost | Best for |
|---|---|---|---|
| Subscribe | Take the Oracle Java SE Universal Subscription and keep patching Oracle JDK 21 | Per employee, tiered by headcount | Organizations with deep Oracle Java dependencies and no near-term migration capacity |
| Move to JDK 25 | Upgrade to Oracle JDK 25, which stays on the free NFTC license | Free, for now | Teams that can test and adopt a new major version and want to stay on Oracle binaries |
| Switch to OpenJDK | Replace Oracle’s build with Eclipse Temurin or Amazon Corretto | Free, including production | Most organizations that want to remove the per-employee exposure entirely |
OpenJDK vs Oracle JDK
For teams weighing the switch, the practical differences are narrow. Oracle JDK and OpenJDK distributions such as Temurin and Corretto are built from the same OpenJDK source and behave the same for the large majority of workloads. The split is license and support: Oracle JDK updates under OTN require a paid subscription for production, while Temurin and Corretto are free to run in production, including commercially, with support available from the distribution maintainer or a third party. For many organizations, moving to a free OpenJDK build removes the JDK 21 licensing question entirely, at the cost of a tested rollout.
What to do now
The first step is unglamorous, and it is the whole game: find out exactly where Oracle’s JDK 21 is running and which update level each instance is on, across servers, applications, containers, build pipelines, and developer machines. Because the bill is driven by headcount rather than installs, you cannot size your exposure, or rule it out, without that inventory.
The second step is to make the call before someone makes it for you. The most expensive version of this situation is the one where the security team does the responsible thing, applies the October update to stay patched, and only later does anyone realize it changed the licensing position. Deciding deliberately, with a current inventory in hand, is a very different outcome from explaining your deployment to Oracle during an audit.
UMS helps enterprises map their Oracle Java estate, size the real exposure, and choose between subscribing, upgrading, and migrating, with no upfront fee and paid only from what we save. If the October change has put Java on your radar, see our first 48 hours of an Oracle Java audit guide, or start with the inventory above.