A free-use window that many organisations have been quietly relying on for their Java estate closed at the end of last month, and the deadline was easy to miss precisely because it was never framed as urgent when it was originally announced. Oracle JDK 21 updates were made available under the No-Fee Terms and Conditions license until September of 2026, one year after the release of JDK 25 as the current long-term support version in September 2025, with further JDK 21 updates beginning with the upcoming October 2026 critical patch update moving to the paid Java SE OTN license instead.
Why This Catches Organisations Off Guard Every Time
Oracle’s free-use licensing model follows a consistent, predictable pattern once you understand it, but that predictability does not stop it from surprising organisations at each transition point. The current long-term support release is free to use under the No-Fee Terms and Conditions licence, and the previous long-term support release remains free for exactly one year after the new one ships, giving organisations a defined overlap window to migrate. Once that year elapses, continuing to receive updates for the now-previous release requires moving to the paid Oracle Technology Network licence, the same commercial terms that already apply to older versions like Java 8, 11, and 17.
The surprise is rarely about the rule itself, which Oracle has applied consistently since introducing this model. It is about organisations losing track of exactly which specific version their own estate is actually running, and therefore not realising a specific instance of Java 21 has quietly crossed from free to paid.
What the Upcoming October Update Actually Changes
Nothing changed retroactively for updates already applied before 1 October, and existing JDK 21 installations did not stop functioning the moment the calendar turned. What changes is forward-looking: any organisation wanting the upcoming October 2026 critical patch update, or any subsequent update, for JDK 21 needs a Java SE subscription to receive it under the new licensing terms. An organisation that simply stops updating JDK 21 at this point continues running without a subscription, but also stops receiving security patches for a JDK version that remains in active production use across a large share of the enterprise Java estate.
The Extended Support Detail Worth Knowing
For organisations planning to stay on Java 21 for the long term rather than migrating to a newer release immediately, it is worth understanding how far Oracle’s own commercial support actually extends once a subscription is in place. Organisations wishing to continue receiving Oracle JDK 21 updates starting in October 2026 should consider the Java SE Universal Subscription, under which commercial support for Java 21 remains available until at least September 2031, consistent with the broader long-term support lifecycle Oracle has committed to for this release.
That long support horizon is a genuinely useful planning input for any organisation weighing whether to subscribe and stay on Java 21, versus investing engineering effort in migrating to Java 25 specifically to avoid the subscription cost. A five-year support runway from a paid subscription is a meaningfully different proposition than a short-term stopgap, and it deserves to be weighed honestly against the migration cost rather than dismissed automatically as the more expensive option.
Why the Employee Metric Makes This Bigger Than It Looks
The financial exposure this deadline creates is considerably larger than a simple per-installation cost, because of how Oracle’s current Java subscription pricing actually works. Oracle’s Java subscription costs are driven by enterprise-wide employee counts rather than where Java is actually deployed, meaning organisations pay for scope rather than actual usage, and a subscription triggered by a single unmigrated JDK 21 instance is priced against the organisation’s full employee headcount, not against that one specific installation.
That employee-wide pricing structure is precisely why a single overlooked JDK 21 instance carries such disproportionate financial risk. The subscription decision is not really about one server or one application. It is about the organisation’s entire employee count, which makes the inventory step described below considerably more consequential than it might first appear.
The Inventory Step That Actually Matters Right Now
Given how the employee-based pricing model works, the single most valuable action available right now, ahead of the October critical patch update, is a direct, accurate inventory of exactly where Oracle JDK 21 is actually running across the organisation, including instances bundled inside third-party applications, developer tooling, and container images that may not have been rebuilt in years. That inventory is what determines whether this transition requires a genuine commercial decision at all, since an organisation that can confirm it holds no unmigrated JDK 21 instances, or that has already completed a migration to JDK 25 or an OpenJDK distribution, has no exposure to this specific transition regardless of how the broader Java licensing landscape continues to evolve.
A 2Data Perspective
If you would rather have an independent set of eyes on this specific decision, get in touch with 2Data directly. Gartner’s own Market Guide for Software Asset Management Tools frames this exact shift directly, noting that SAM has moved well past simple audit defense toward a central role in cost governance, cloud optimisation, and AI readiness is exactly the kind of broader industry context we bring to a conversation like this one.
Conclusion
The free-use window for Oracle JDK 21 has already closed, with the upcoming October 2026 critical patch update marking the point from which continuing to receive JDK 21 updates requires an employee-wide Java SE subscription, a pricing structure that makes even a single overlooked instance a genuinely significant financial exposure.
Running a direct, accurate inventory of every JDK 21 instance across the organisation, including those hidden inside third-party applications and container images, is the essential first step before deciding between subscribing for the long support runway available through 2031 or investing in migration to a still-current, no-fee release instead.
