Java Licensing Decision Guide

Java licensing has moved from a technical footnote to a board-level cost conversation in many organizations. The reason is the metric: Oracle’s current Java SE Universal Subscription is priced on the number of employees in the organization, not on the number of servers, desktops or people who actually use Java.

This guide is designed to help CIOs, CFOs, procurement and legal teams understand the current rules and make a deliberate decision rather than a reactive one.

How does the Java SE Universal Subscription metric work?

According to Oracle’s Java SE Universal Subscription Global Price List, the subscription is licensed by “Employee for Java SE Universal Subscription,” defined as:

• all of your full-time, part-time and temporary employees; and
• all of the full-time, part-time and temporary employees of your agents, contractors, outsourcers and consultants that support your internal business operations.

Three consequences follow from that definition:

1. Usage does not drive the count. The price list states that the number of employees is determined without regard to how many of them use the programs.
2. The count is set at the start and must keep up. The licensed quantity must at least equal your employee count at the effective date of the order, and if your employee count exceeds the licensed quantity during the term, an additional license is required.
3. Third-party staff can count. The phrase “that support your internal business operations” is where much of the negotiation and interpretation happens.

The subscription has a minimum term of one year. Oracle’s price list also sets processor limits that depend on the licensed employee quantity, with desktops and laptops excluded from the processor calculation.

What does it cost?

Oracle publishes its price list, and it changes. The October 2026 version shows two structures: simplified pricing for organizations below 3,000 employees, with fixed band entitlements and a per-employee rate for employees above 500; and per-employee monthly rates for 3,000 employees and above that decline as the employee count rises, with organizations above 50,000 employees asked to contact Oracle.

Two practical points matter more than the headline rates:

• The rate applies to the entire count. For enterprise volumes, the per-employee price for your band is multiplied by your full employee count.
• Band boundaries matter. Because the rate changes at band thresholds, a modest change in the employee count can move the total materially. Confirm which band applies and how changes during the term are handled.

Always use the current price list and your own quote. Older figures circulating online may no longer reflect Oracle’s pricing.

Which Oracle JDK versions are free, and under which terms?

This is where most exposure is created, because the answer depends on the exact version and update installed. Based on Oracle’s Java SE Support Roadmap and Licensing FAQ:

• Oracle JDK 25 is offered under the Oracle No-Fee Terms and Conditions (NFTC), which permit use for internal business operations at no cost. Update releases after September 2028 are planned to move to the Java SE OTN license.
• Oracle JDK 21 was offered under NFTC. Update releases from the October 2026 Critical Patch Update onward are planned to be offered under the Java SE OTN license.
• Oracle JDK 17 updates released from October 15, 2024 are under the OTN license.
• Oracle JDK 8 and 11 updates are available under the OTN license; Oracle JDK 8 updates from 8u211 (April 2019) onward fall under these terms. Releases before April 16, 2019 were licensed under the older Binary Code License.

The OTN license permits personal use, development, testing, prototyping, demonstrating and some other limited uses at no cost. Production use under OTN terms generally requires a subscription. NFTC licensing applies to the specific builds released under it; it is the later update that changes terms.

Oracle also provides OpenJDK builds under an open source license (GPLv2 with the Classpath Exception) at jdk.java.net, and several other vendors distribute OpenJDK builds.

How does exposure typically arise?

Very rarely through a single deliberate decision. More often through:

• automated updates that move an installation from a free build to one under OTN terms;
• container images and build pipelines that pull Oracle JDK by default;
• desktop software catalogs and developer workstations;
• third-party applications that bundle Oracle Java, where entitlement depends on the vendor’s agreement with Oracle.

Note that a single installation requiring a subscription can, under an employee metric, lead to a subscription priced on the entire workforce. That is why inventory comes first.

What are the realistic options?

Subscribe. Appropriate when Oracle JDK is deeply embedded and the organization values Oracle’s support and tooling. Negotiate the count methodology, the treatment of contractors and changes during the term.

Migrate to OpenJDK. Many enterprises move to OpenJDK distributions. It can remove the subscription requirement, but it is a programme, not a switch: application testing, build pipelines, container images, desktop tooling and third-party software all need attention, and these often take longer than the application code itself.

Stay on free terms deliberately. Using Oracle JDK builds under NFTC is a legitimate path, provided update governance prevents installations from moving onto OTN-licensed updates without a decision, and security patching is planned.

Mixed paths need care. Keeping a small number of Oracle JDK installations that require a subscription while migrating everything else may not reduce cost under an employee metric. Be sure the end state actually removes the requirement.

How should we respond if Oracle raises Java with us?

Calmly and in order:

1. Evidence. Establish your own inventory of installations, versions and updates, and how they got there.
2. Classification. Map each installation to the license that applies: NFTC, OTN, BCL, OpenJDK or a bundled entitlement.
3. Count. Build the employee count with HR and legal entity data, and agree internally how contractors and outsourcers are treated.
4. Price. Only then discuss commercial terms.

Respond in writing, through a single channel, and avoid confirming numbers you have not verified.

Practical implications

• For the CIO: own the inventory and the update governance that keeps it accurate.
• For the CFO: model the subscription on the full employee count, including band effects, against the cost of migration.
• For procurement: negotiate the count date, methodology, contractor treatment and price protection for renewals.
• For legal: focus on the employee definition, entity scope and the treatment of acquisitions and divestitures.

For organizations with operations across Latin America, employee counts often span several legal entities, shared service centers and outsourced teams in different countries. Establish which entities and third parties are in scope before a number is shared, and budget for the subscription in US dollars against local-currency planning.

Practical checklist: five-step self-assessment

Common pitfalls

• Confirming an employee number too early. It becomes the basis for every later discussion.
• Leaving one Oracle JDK installation behind after a migration. Under an employee metric, it can matter far more than its size suggests.
• Letting Java be folded into another negotiation or review. Keep the topic separate and documented.
• Ignoring automatic updates. A free build today can be replaced by a non-free update tomorrow.
• Accepting retroactive periods without scrutiny. Ask for the basis of any claim covering past use.

Frequently asked questions