Java 17 NFTC license terms.

When Oracle released JDK 17 it did something that surprised the market: it made Oracle Java free for commercial production use again — under a new licence called the No-Fee Terms and Conditions, the NFTC. After the restrictive OTN era, this looked like a return to the old free Java. It is not. The NFTC is free, but it is free with a timer attached, and the timer is exactly what catches enterprises out. This guide explains the NFTC terms as they apply to Java 17, what the free window really means, and what happens when it ends.

What the NFTC is

The Oracle No-Fee Terms and Conditions (NFTC) licence is the agreement Oracle introduced with the release of Oracle JDK 17 in September 2021. It is the licence under which Oracle has released its JDK builds from version 17 onward — 17, 21, and the releases between and after them.

The NFTC was Oracle's response to the backlash against the OTN licence, under which Oracle JDK 11 through 16 could not be used in production without a paid subscription. The NFTC restored a genuine free right: under it, Oracle JDK 17 can be used in commercial production at no licence cost. Like every Oracle Java licence, the NFTC governs Oracle's own binary build of Java; it sits as the third major licence in the sequence after BCL and OTN, and our BCL/OTN/NFTC comparison places all three together.

What the NFTC allows

The NFTC's headline grant is broad and real. Under the NFTC licence, an enterprise may use the Oracle JDK — including JDK 17 — at no licence cost for:

• Commercial use. Unlike the OTN licence, the NFTC explicitly permits commercial use, not just development and testing.
• Production environments. Running live, business-critical applications on Oracle JDK 17.
• Internal business operations. The internal applications that the OTN licence specifically excluded from its free rights.
• Redistribution. Subject to the conditions in the agreement, redistributing the JDK with applications.

This is a meaningful difference from the OTN era. Under OTN, putting Oracle JDK 11 on a production server was a breach. Under the NFTC, putting Oracle JDK 17 on a production server is permitted and free. For the duration of the free window, the NFTC genuinely is free commercial Java — which is precisely why it is easy to relax and miss the catch.

The free window

The catch is the time limit. The NFTC does not grant free use of a version forever. It grants free use for a defined window tied to the version's release — and then it stops.

Oracle's model works release by release. A given JDK version is free under the NFTC from its release, and remains free for that version through a window that, in Oracle's stated approach, extends roughly until a year after the next long-term-support release becomes available. After that point, continued use of that specific version is no longer covered by the NFTC's no-fee grant — Oracle moves the older version to its restrictive terms, and continued use requires a paid subscription.

The practical consequence is that the NFTC keeps you free only if you keep moving. An organisation that adopts an Oracle JDK version under the NFTC and then leaves it in place — as enterprises very often do with long-lived applications — will, when the window closes, find that the same unchanged installation now requires a subscription. Nothing about the software changed. The licence clock simply ran out.

What happens after the window

When a version's NFTC free window closes, an enterprise still running that Oracle JDK version faces a clear set of options — and it is far better to choose between them deliberately than to discover the situation in an audit.

• Upgrade to a newer Oracle JDK version that is still within its own NFTC free window. This keeps you free, but it commits you to a permanent upgrade treadmill — every version, on Oracle's schedule, indefinitely.
• Buy a Java SE subscription to keep running the old version legitimately. This is Oracle's preferred outcome, and it means the headcount-priced Java SE Universal Subscription on the employee metric.
• Migrate to a free OpenJDK build of the same version — Eclipse Temurin, Amazon Corretto, Azul Zulu and others — which carries no NFTC-style window and no subscription requirement at all.
• Do nothing — and unknowingly run an out-of-window Oracle JDK version that now requires a licence. This is the path that ends in audit exposure.

The fourth option is the real risk, because it is the default for any enterprise that does not actively track NFTC windows. An installation that was correctly free when deployed becomes unlicensed simply through the passage of time, with no event — no patch, no change — to flag it. Our guide on how Oracle detects Java covers how Oracle later identifies exactly these installations.

NFTC vs OTN

Because the NFTC and OTN licences both govern modern Oracle JDK versions, enterprises frequently confuse them. The distinction is sharp and worth holding clearly.

The summary: OTN restricts free use by activity — you may not run it in production for free, ever. The NFTC restricts free use by time — you may run it in production for free, but only until the window closes. Both end in the same place — a Java SE subscription — but they get there differently, and the NFTC's route is quieter and easier to miss.

Java 17 specifics

Java 17, as a long-term-support release and the first version under the NFTC, is the version most enterprises will be reasoning about. A few specifics matter.

JDK 17 was released in September 2021 and was free under the NFTC from that point. As later LTS releases have arrived, JDK 17's NFTC free window has moved toward its close on Oracle's model. The exact dates are Oracle's to set and have shifted with Oracle's release cadence, so the responsible approach is not to memorise a date but to verify the current NFTC status of every Oracle JDK 17 installation you run against Oracle's published terms, and to recheck it periodically.

The other Java 17 specific is scope. NFTC status applies to Oracle's JDK 17 build. If your JDK 17 came from Eclipse Adoptium (Temurin), Amazon (Corretto), Azul (Zulu) or another OpenJDK distributor, it is not under the NFTC at all — it is under the OpenJDK open-source licence, free with no window. So the first question for any “JDK 17” installation is not “is it in the NFTC window” but “is it an Oracle build at all.” Only Oracle's build raises the NFTC question.

Planning around the NFTC

The NFTC can be used safely — it just cannot be used passively. A sound approach has three elements.

Track the windows. Maintain an inventory of every Oracle JDK installation, its exact version, and the current NFTC free-window status of that version. Treat an approaching window close as a scheduled event with an owner and a deadline, not a surprise.

Decide before the window closes. For each Oracle JDK version approaching the end of its window, choose deliberately: upgrade to a still-free version, license it, or migrate it off Oracle. The worst outcome is the one that results from making no decision.

Question whether you need Oracle's build at all. The NFTC's whole structure — free, but only if you stay on Oracle's upgrade treadmill — exists to keep enterprises tethered to Oracle Java. A free OpenJDK build of the same version sidesteps the entire mechanism: no window, no treadmill, no subscription. For most estates, the cleanest plan around the NFTC is not to manage its windows but to remove the dependency. Our OpenJDK comparison and free Java versions list set out the alternatives.

Frequently asked questions

This article is general information on the NFTC licence, not legal advice. NFTC window dates are set by Oracle and change with its release cadence; consult a qualified independent Java licensing specialist and Oracle's current published terms for your specific estate.