Summary

  • Oracle's 20 October JDK 21.0.13 release starts a different licensing regime inside the Java 21 family. Its current table continues to list 21.0.12 and earlier under NFTC; 21.0.13 and later use OTN or an applicable customer entitlement.
  • Commercial support for Java 21 extends beyond its broad no-fee update window. Buyers choosing continuity have to connect the precise runtime build, permitted use and contract with the cost of qualifying another release.

The patch number has a budget attached

The application owner sees Java 21 before the update and Java 21 afterwards. Procurement has to see the extra digits. Oracle's 21.0.13 release notes identify the 20 October update as the first JDK 21 release under the Oracle Technology Network licence for Java SE. It still conforms to Java SE 21. The technical family has stayed put while the terms for the new binary have moved.

That is an uncomfortable division of labour. A maintenance team wants a current runtime. An application team wants a familiar release. A purchasing team wants to know what the organisation is entitled to run. A ticket that says only “update Java 21” leaves the commercial decision hanging between them.

Oracle makes the dividing line unusually easy to locate. Its licensing FAQ, updated on 20 October, places 21.0.12 and earlier in the NFTC column and 21.0.13 and later under OTN or customer access. The older copies retain their place in that table. The new patch arrives with its own terms.

Same application, different permission

The NFTC licence permits internal business operations subject to its conditions. The OTN agreement grants specific categories of use: personal use, development, Oracle Approved Product Use and identified Oracle Cloud Infrastructure use. Development includes testing, prototyping and demonstrating applications. Uses beyond the agreement's grants require a separate valid licence.

This makes the destination of the binary financially relevant. The development permission has a defined scope. The production runtime needs the permission that covers its actual use. A download link cannot answer that question on behalf of the person approving the deployment.

Some organisations already have the answer. Oracle's customer routes include active Java subscriptions, qualifying legacy support, qualifying OCI entitlements and Java used solely with another entitled Oracle product. The applicable grant decides the scope. For a customer already covered, the October update can be an entitlement check within an existing purchase. For a deployment outside those routes, the choice reaches procurement and the application roadmap together.

LTS keeps running after the free window closes

Long-term support is a reassuring label with two clocks behind it. Oracle's support roadmap gives commercially supported Java 21 Premier Support through September 2028 and Extended Support through September 2031. Those are customer support timelines. The broad no-fee licensing window for new Oracle JDK 21 updates ended earlier.

Oracle's current LTS, JDK 25, supplies another route. The company plans NFTC updates for it through September 2028, a year after the planned September 2027 arrival of Java 29. Moving to 25 therefore changes the commercial window as well as the software. The application owner still has to qualify the move. A release available at no fee can carry an internal testing bill.

Staying on a previously obtained NFTC release keeps that older binary in Oracle's published licence category. It also leaves the organisation with that older set of fixes. Oracle recommends updating with each Critical Patch Update. The licence table cannot perform maintenance, and a maintenance ticket cannot create an entitlement. Each decision needs an owner.

Price the choice before the rollout

The useful unit for this decision is an actual deployment: runtime supplier, full build, application, use and entitlement. That lets a buyer distinguish a development machine from a business service and an already covered installation from one that needs a different route. Counting every entry labelled “Java 21” as a single commercial population loses the boundary Oracle has just drawn inside it.

Customer contracts and migration test costs are unavailable here; those would determine a named organisation's bill and preferred path. The public trade is clear enough. Paying for continuity can preserve the older family while work proceeds elsewhere. Moving to a newer no-fee family can bring qualification work forward. Another properly licensed runtime path has its own maintenance and testing decision. The vendor controls the update window; the customer funds the calendar that follows.

For the executive approving the work, the first question is now very small: which Java 21 build? An inventory that stops at “21” has dropped the digits where October's purchasing decision begins.

Sources