Updates to Java SE 17 are not free after September 2024

The licensing landscape for Oracle Java SE 17  is undergoing significant changes  after September 2024.  Understanding these changes is crucial for organizations that rely on Java for their applications and infrastructure. This article will explore the implications of these changes, how to manage licensing effectively, and alternatives to consider.

What are the changes to the Java SE 17 licensing after September 2024?

• All updates to Java SE 17 after September 2024 move out of the NFTC (No Fee Terms and Conditions) agreement.
• Updates prior to September 2024 continue to be available under the NFTC agreement.
• After September 2024, updates for Java SE 17 will be provided under the Oracle Technology Network (OTN) license.

What are the options for customers on Java SE 17?

• Customers can continue to be on updates to Oracle Java SE 17 that have been applied prior to September 2024. This will continue to be free under the NFTC agreement.
• Customers can move to Oracle Java SE 21. This version is available under NFTC.
• Customers can move to free Open JDK
• Customers will need to pay and purchase licenses if they want to apply the latest update patches to Oracle Java SE 17

What can customers expect from Oracle?

• Expect outreach from Oracle regarding the transition to the new licensing model.
• Oracle will discuss with you commercial proposals based on their “Employee for Java SE Universal Subscription”

What should customers do?

• Customers who want to pay Oracle license fees
  • As discussed Java SE 17 Not Free any longer, but this does not mean that customers who want to buy have nothing to do. You need to visualize your deployment and going forward usage.
  • Evaluate your usage. This will ensure you have the data to engage with Oracle.
  • Budget for costs based on their “Employee for Java SE Universal Subscription,” license metric.
• Customers who were using Java SE 17 and do not want to pay license fees
  • Evaluate your usage.
  • Consider the alternatives
    • Move to Open JDK
    • Move to non-Oracle Java distributions (like Azul, Bellsoft, Eclipse, Coretto etc)
    • Stop using Java

How we can help

Rythium, has developed  discovery and license normalization techniques to provide you with an enterprise-wide Java (from Oracle, Open source, IBM, RedHat, etc) deployment inventory as well as a Java ELP. Using our services, you will be able understand your exposure, if any, to Java license fees.

We will assess the deployments, estimate potential savings, analyse risks & license non-compliance exposures and recommend optimizations.

Rythium is the parent company of the Euladox division.

Oracle’s official policy on Java SE 17 can be seen here