Executive takeaways
- Java presence is not the same as paid-license exposure. Version, update level, licensing terms, usage context and existing entitlements all matter.
- JDK 21 is at a time-sensitive transition point. Oracle says updates after September 2026 are planned to move from NFTC to the Java SE OTN license.
- The Employee metric can make subscription economics material at enterprise scale. But the metric should be applied after establishing that commercial subscription rights are actually required.
- A defensible Effective License Position starts with evidence. Estate discovery alone is not enough; installations need to be classified against their governing rights and use.
JDK 21 changes after September 2026
Oracle JDK 21 was released in September 2023 and has been available under Oracle's No-Fee Terms and Conditions (NFTC), which permits commercial and production use subject to the licence terms. Oracle designated JDK 25 as the next Long-Term Support release in September 2025, starting the one-year overlap period for JDK 21 users.
Oracle now states that JDK 21 updates through September 2026 remain available under NFTC, while subsequent updates beginning with the October 2026 Critical Patch Update are planned to be offered under the Java SE OTN license. Oracle recommends users who want to continue receiving Oracle JDK updates under the permissive NFTC model move to JDK 25.
The licensing question is version-specific.
An enterprise running Java should not treat every installation as one homogeneous population. JDK release, update level, licensing terms and the way Java is used can materially change the position.
When the Employee metric matters
Oracle Java SE Universal Subscription is sold using an Employee for Java SE Universal Subscription metric. Oracle's published definition includes the customer's full-time, part-time and temporary employees, plus specified employees of agents, contractors, outsourcers and consultants who support the customer's internal business operations.
Oracle's price list also states that the required subscription quantity is based on the number of Employees under that definition, not simply the number of people who actively use Java.
That does not mean that the discovery of any Java binary automatically makes an entire workforce chargeable. The first question is whether the specific Java deployment requires commercial Java SE rights at all. Only then does the applicable licensing metric become relevant to the commercial calculation.
Five factors that determine the real position
Rizen's Java assessments separate estate discovery from licensing qualification. A large inventory count may be the starting point, but the real exposure depends on what is running, how it is used and what rights already exist.
Version & Licensing Terms
Identify the exact JDK/JRE version and update level, then map it to the licence terms governing that release.
Development vs. Production Use
Understand how Java is being used and whether a free-use grant or a commercial-use requirement applies to that context.
Commercial Feature Usage
Review use of separately licensed or historically commercial features where relevant to the release and entitlement position.
Rights Through Oracle Programs
Check whether the Java deployment is covered through licensed Oracle products or other applicable Oracle entitlements.
COTS, OEM & ISV Bundling
Determine whether Java is bundled with third-party software and what distribution or embedded-use rights apply to that deployment.
The objective is to move from “Java exists in our estate” to a traceable, evidence-backed statement of which installations require remediation, commercial rights or further contractual analysis.
What Oracle's published list pricing looks like at enterprise scale
Oracle's published Java SE Universal Subscription Global Price List uses a sliding monthly price per Employee. The table below shows the enterprise bands from 10,000 Employees upward and the corresponding annual list-price illustration.
| Employee band | List price / Employee / month | List price / Employee / year | Illustrative annual list cost |
|---|---|---|---|
| 10,000–19,999 | $8.25 | $99.00 | $990,000–~$1.98M |
| 20,000–29,999 | $6.75 | $81.00 | $1.62M–~$2.43M |
| 30,000–39,999 | $5.70 | $68.40 | $2.05M–~$2.74M |
| 40,000–49,999 | $5.25 | $63.00 | $2.52M–~$3.15M |
| 50,000+ | Contact Oracle for pricing | ||
Source: Oracle Java SE Universal Subscription Global Price List currently published on Oracle's website. The document is dated 1 March 2023 and states that pricing is subject to change. Enterprises should verify current Oracle pricing and their contractual terms before making a commercial decision.
At these workforce sizes, applying an enterprise-wide metric before qualifying the underlying Java estate can produce a materially different commercial picture from an assessment that starts with versions, rights and actual usage.
What qualification can change in practice
Selected Rizen engagements illustrate why estate-wide discovery needs to be followed by licensing analysis rather than treated as the final exposure number.
These are individual engagement outcomes and are not guarantees of results for other organizations. Licensing and commercial outcomes depend on each client's estate, contracts, rights, use and negotiation context.
Rizen's four-phase Java assessment approach
A useful Java assessment should produce more than an inventory. It should establish a documented license position, identify remediation options and give management a clear basis for any subsequent Oracle conversation.
Planning & Governance
Define scope, stakeholders, data sources, timelines and evidence requirements before discovery begins.
Estate Discovery
Collect endpoint, server, version, update and application context across the relevant Java estate.
Qualification & ELP
Map deployments to licensing terms, usage, entitlements and bundling to establish the Effective License Position.
Remediation & Strategy
Prioritize remediation, commercial options, governance controls and negotiation support where required.
What enterprise teams should review now
- Identify where Oracle JDK 21 is deployed and whether those systems are expected to receive updates after September 2026.
- Build an inventory of Java versions and update levels across endpoints, servers and bundled applications.
- Document the licence basis for each material deployment instead of assuming all discovered Java has the same rights.
- Validate existing subscription, legacy, Oracle-product, OEM/ISV and other contractual rights before applying an Employee metric calculation.
- Quantify the Employee population only for scenarios where Java SE Universal Subscription is actually required.
- Evaluate available remediation paths, which may include removing unneeded installations, changing versions, moving to JDK 25 where appropriate, or considering alternative supported JDK distributions.
- Establish an Effective License Position before a major renewal, subscription proposal or compliance discussion.
- Put preventive controls around software distribution so remediated Java deployments do not quietly reappear.
Frequently asked questions
Does every Oracle Java installation require a paid licence?
No. The applicable position depends on the Java release and update, governing licence terms, how it is used and any existing contractual or product rights. Estate discovery should therefore be followed by licence qualification.
What changes for Oracle JDK 21 after September 2026?
Oracle states that JDK 21 updates through September 2026 are available under NFTC. Updates beginning with the October 2026 CPU are planned to be offered under the Java SE OTN license. Oracle recommends JDK 25 for users wishing to continue with the permissive NFTC model.
How does Oracle calculate the Employee metric?
Oracle's published definition includes the customer's full-time, part-time and temporary employees and specified employees of agents, contractors, outsourcers and consultants supporting internal business operations. Oracle states that the subscription quantity is based on Employees under this definition rather than actual Java users.
Is the number of discovered Java installations the same as licensing exposure?
Not necessarily. An inventory tells you where Java exists. A licensing assessment determines which installations are governed by which terms and which require remediation, commercial rights or further evidence.
What should an enterprise establish before discussing Java commercials?
A documented estate inventory, entitlement and contract position, licensing classification, Employee population where relevant, remediation options and an Effective License Position provide a stronger basis for decision-making.
Sources & further reading
- Oracle — JDK 21 approaches end-of-permissive license, 14 August 2026.
- Oracle — JDK License General FAQs.
- Oracle — Java SE Universal Subscription Global Price List.
- Oracle — Java SE Universal Subscription FAQ.
Oracle licensing terms, product availability and pricing can change. Organizations should review the current Oracle documentation together with their own contracts and deployment facts before making licensing or commercial decisions.