Oracle Java SE has been sold under multiple licensing metrics over the course of its commercial history — Named User Plus (NUP), per-device, per-processor, and most recently the Employee Metric introduced in January 2023. Understanding each metric, how Oracle transitioned between them, and what each costs in practice is essential for any enterprise managing legacy Java SE entitlements, reviewing prior agreements, or navigating Oracle's audit and subscription renewal process. Former Oracle insiders explain how each metric works, what it cost, and what the 2023 shift means for enterprises that previously had Java SE agreements based on NUP or other legacy metrics.
Oracle's Java SE commercial licensing history reflects a gradual shift from usage-based metrics (per-user, per-device) toward entity-wide metrics (per-employee) that maximize Oracle's revenue from large enterprise customers regardless of actual Java consumption. Understanding this history matters because enterprises may have prior Java SE commitments, purchase orders, and compliance declarations based on earlier metric versions — and those legacy positions can interact with Oracle's 2023 metric change in ways that affect current audit risk and renewal negotiations.
The evolution of Oracle Java SE commercial licensing metrics:
This timeline is not merely academic. Enterprise buyers who managed their Java SE exposure under NUP agreements signed before 2023 may believe they are compliant based on their NUP-based license counts. Oracle's position: the 2023 metric change applies to all commercial Java use from January 2023 — organizations on NUP agreements are not automatically grandfathered into the new metric at the NUP cost. They are expected to convert to the Employee Metric subscription. How this conversion is managed determines whether the legacy NUP agreement protects against audit exposure or leaves a gap.
Named User Plus was Oracle's primary per-user licensing metric for Java SE commercial licenses prior to 2023. Under NUP, a "Named User" was a specific, identified person authorized to use the licensed product — an employee, contractor, or customer who had been granted access to a system running Oracle JDK commercially. "Plus" referred to the requirement to license not only direct users but also any indirect users accessing the system through automated interfaces.
For Oracle Java SE under NUP, the metric required organizations to license Java SE for every Named User who could access a system where Oracle JDK was running commercially. This applied to production systems where security updates were required and where Oracle JDK's commercial features (Flight Recorder, Mission Control, Advanced Management Console) were in use. Development and testing environments had different rules under Oracle's developer license, but production access triggered the commercial NUP obligation.
The NUP metric had a minimum of 25 Named Users per processor for Oracle Java SE — a floor that prevented organizations from claiming a very low NUP count on a high-core-count server. An eight-core server running Oracle JDK required a minimum of 200 NUP licenses (8 × 25), regardless of how many actual users accessed it. For small deployments with few actual users, this minimum could make NUP more expensive than a processor-based metric.
Oracle's NUP pricing for Java SE under the pre-2023 commercial license was in the range of $40–100 per Named User per year, depending on the specific Java SE edition, support level, and whether it was licenced as a standalone product or as part of a broader Oracle agreement. The exact price varied significantly by negotiated enterprise agreement terms and Oracle's discretionary pricing in individual deals.
For a 10,000-person organization with 1,000 Java users, NUP pricing at $50/user/year produced an annual cost of approximately $50,000. The same organization under the 2023 Employee Metric at $9.50/employee/month faces an annual cost of approximately $1,140,000 — a 22× increase, with no change in Java usage. This is the economic core of Oracle's 2023 licensing change.
Before NUP became Oracle's primary Java SE metric, Oracle also offered per-device and per-processor licenses for Java SE deployments. Understanding these legacy metrics matters for organizations that have old Java SE purchase orders, CSI numbers, or compliance documentation from different metric periods.
Under per-device licensing, a Java SE commercial license was required for each device (physical machine, virtual machine, or terminal) on which Oracle JDK ran commercially. This metric was more tractable for environments with well-controlled server deployments — a data center with 100 servers running Oracle JDK required 100 device licenses. Per-device pricing for Oracle Java SE was in the range of $75–150 per device per year depending on the agreement vintage and negotiated rates.
Per-device licensing became problematic as virtualisation proliferated. When a physical server running 50 virtual machines all ran Oracle JDK, the per-device count could explode from 1 to 50 with a virtualisation deployment decision that had nothing to do with Java usage. This was an early precursor of the virtualisation licensing complexity that continues to affect Oracle Database and Middleware deployments today — see our guide to Oracle Database licensing on VMware for how this plays out in a different product context.
Per-processor (per-core) licensing was available for some Java SE deployments — particularly for server-side Java applications where the number of users was large or undefined. Under processor licensing, the cost was based on the number of processor cores on servers running Oracle JDK commercially, subject to Oracle's Core Factor Table adjustments for multi-core processors. Processor licensing for Java SE was less common than NUP and per-device, and was typically used for application server environments where user counts were impractical to track.
Oracle's January 2023 introduction of the Java SE Universal Subscription and its Employee Metric was the most significant change in Java SE commercial licensing history. The Employee Metric eliminated all prior per-user, per-device, and per-processor metrics for new Java SE commercial agreements, replacing them with a single metric: every employee of the organization and its controlled entities.
The Employee Metric's defining characteristic is its complete disconnection from actual Java usage. Under every prior metric — NUP, per-device, per-processor — there was at least a theoretical connection between the license count and actual Java deployment. Under the Employee Metric, an organization with 100,000 employees pays the same whether it runs Java on 10 servers or 10,000 servers. The metric is an organization-level tax, not a product usage fee.
Oracle's rationale for the change — "simplification" — is technically true but economically self-serving. The Employee Metric does eliminate the complexity of tracking individual users, devices, and processors. But the simplification dramatically favours Oracle: it converts Java SE from a product that many enterprises could manage within a modest budget into an enterprise-wide subscription that generates Oracle revenue at a scale disconnected from product value delivered. See our detailed Employee Metric guide for the full analysis of how the metric works and what it costs.
The 2023 change was not retroactive to existing agreements — but the gap matters. Organizations on NUP agreements signed before 2023 retained their NUP entitlements under those agreements until expiry or renewal. From January 2023, however, Oracle treats any new Oracle JDK use in production without a subscription as subject to the Employee Metric — regardless of existing NUP agreements. The compliance gap appears when an organization's NUP agreement covers 500 Named Users but Oracle JDK is actually running on systems accessed by more users, or the NUP agreement expires and the organization continues running Oracle JDK without converting to a subscription.
The cost difference between the NUP metric (as it was priced pre-2023) and the Employee Metric (as priced post-2023) is the starkest illustration of Oracle's commercial intent in making the change. The following comparison uses a representative enterprise profile and Oracle's published list prices at each metric's period.
| Scenario | NUP Metric (pre-2023) | Employee Metric (post-2023) | Cost Increase |
|---|---|---|---|
| 5,000 employees, 200 Java users | ~$10,000/yr (200 NUP) | ~$630,000/yr (Employee Metric) | 63× |
| 10,000 employees, 500 Java users | ~$25,000/yr (500 NUP) | ~$1,140,000/yr | 46× |
| 25,000 employees, 2,000 Java users | ~$100,000/yr (2,000 NUP) | ~$2,475,000/yr | 25× |
| 50,000 employees, 10,000 Java users | ~$500,000/yr (10,000 NUP) | ~$4,950,000/yr | 10× |
The cost increase ratio diminishes as the proportion of actual Java users increases relative to total employee headcount. An organization where nearly every employee uses Java-based systems (uncommon but not unheard of for certain technology companies) might see only a 2–3× increase under the Employee Metric compared to a comprehensive NUP license. But for the majority of enterprises — where Java users represent 5–20% of total headcount — the Employee Metric represents a 10–50× cost increase for the same deployment.
This cost differential is Oracle's deliberate leverage tool. Oracle's Java subscription team opens renewal conversations knowing that the cost comparison to prior NUP agreements is extremely unfavourable. Their leverage: "this is what Java SE costs now — do you want to subscribe, or face an audit for back payments?" The independent advice for buyers in this position: the conversation should not begin with Oracle's renewal proposal as the frame of reference. It should begin with a forensic assessment of your actual obligation — what Oracle JDK is actually deployed, whether alternative JVMs can replace it, and what the defensible scope of any subscription is under your corporate structure.
Whether you have a legacy NUP agreement, a new Employee Metric subscription, or no current agreement at all, our Java Licensing Advisory validates your current position, identifies compliance gaps, and gives you an independent view of your actual obligation before Oracle does.
Organizations that held Oracle Java SE agreements based on NUP or per-device metrics when Oracle introduced the Employee Metric in January 2023 faced a complex situation. Oracle's position was clear: the Employee Metric applies to all new Java SE commercial use from January 2023. But what happened to existing NUP agreements?
Existing NUP or per-device agreements signed before January 2023 remained valid under their original terms until their contractual expiry date. An organization on a multi-year NUP agreement through December 2024, for example, retained its NUP-based entitlements for the duration of that agreement. At renewal, however, Oracle's standard position is that the renewal must be on Employee Metric terms — NUP renewals are not available through Oracle's standard channels after January 2023.
The "expiry cliff" created by this policy means that many enterprises were effectively on a countdown from January 2023: once their NUP agreement expired, they would face either subscribing under the Employee Metric (at dramatically higher cost) or having no current agreement for their Oracle JDK deployments. Organizations that recognized this cliff early were able to either negotiate multi-year NUP renewals before the change (extending the runway) or begin Java migration planning with a clear end date in mind.
The most dangerous position for organizations with legacy NUP agreements is the gap period — the time between a NUP agreement's expiry and either an Employee Metric subscription or a completed OpenJDK migration. During this period, Oracle JDK deployments that continue to access Oracle's security patch channel or use commercial features without a current agreement create audit exposure. Oracle's Java compliance team actively prospects organizations in this gap period — they have data on agreement expiry dates and proactively reach out when agreements lapse.
For organizations in or approaching this gap period, our audit defense advisors provide immediate protective measures: a deployment inventory to understand actual Oracle JDK exposure, a negotiating strategy for the employee metric subscription that accounts for the gap period, and technical guidance on accelerating OpenJDK migration to reduce the subscription scope. See our Oracle Java Licensing Guide for the full framework.
In 2026, the relevant Java SE licensing metric for any new Oracle Java SE commercial agreement is the Employee Metric — Oracle does not offer NUP, per-device, or per-processor Java SE subscriptions through standard channels. The question of "which metric applies" is therefore primarily relevant in three contexts: organizations reviewing legacy NUP agreements for compliance purposes, organizations in Oracle Java audit processes where Oracle is claiming back payments, and organizations negotiating a Java SE subscription that includes retrospective elements covering a period before the subscription started.
If your organization holds legacy Oracle Java SE agreements based on NUP or per-device metrics, the compliance review question is: during the period covered by those agreements, did your actual Java deployment match the licenced quantity under the applicable metric? For NUP agreements, this means verifying that the number of Named Users who accessed Oracle JDK commercially did not exceed the licensed count plus the applicable processor minimum. For per-device agreements, it means verifying that the number of devices running Oracle JDK commercially did not exceed the licensed device count.
In an Oracle Java audit covering a period that spans both pre-2023 and post-2023 deployments, Oracle may attempt to apply the Employee Metric to the entire period retroactively — claiming that because the Employee Metric applies from January 2023, any pre-2023 NUP-era shortfall should be assessed at Employee Metric rates. This position is legally contestable: the applicable metric for a given period is the metric in force under the relevant agreement at that time. Expert Oracle audit defense challenges retroactive application of the Employee Metric to pre-2023 periods covered by NUP agreements.
The bottom line for organizations navigating the NUP-to-Employee transition: the metric change was unilateral and commercially aggressive, but it was not unlimited in its legal effect. Legacy agreements had terms. Those terms defined the applicable metric for their duration. The compliance gap that creates real audit risk is the period after NUP agreement expiry and before either a current Employee Metric subscription or a completed OpenJDK migration — and managing that gap is where independent advisory expertise delivers the most direct financial value.
A pan-European telecom with a lapsed NUP agreement received an Oracle Java claim covering both pre-2023 NUP-period gaps and post-2023 Employee Metric exposure, totalling $15M. Our team successfully challenged Oracle's retroactive application of the Employee Metric to the NUP period, negotiated a zero-payment resolution with an agreed OpenJDK migration timeline, and eliminated the forward Employee Metric obligation. Read the full case study →
The complete enterprise guide to Oracle Java SE licensing — metrics history, Employee Metric implications, audit defense methodology, and OpenJDK migration playbook. Written by former Oracle Java licensing specialists.
Download Free →Weekly briefings on Oracle Java SE developments, audit trends, and metric changes from former Oracle insiders. Free. Read by ITAM leads, CIOs, and legal teams at global enterprises.
No spam. Unsubscribe anytime. Not affiliated with Oracle Corporation.
We review your current and legacy Java SE agreements, identify compliance gaps between metric periods, and give you a clear picture of your actual obligation — before Oracle's Java compliance team presents theirs. Former Oracle insiders, working exclusively for the buyer.
✓ Confidential · ✓ Independent · ✓ Not affiliated with Oracle Corporation
Free Research
Download our Oracle SaaS Subscription Negotiation Guide — expert analysis from former Oracle insiders, 100% buyer-side.
Download the SaaS Negotiation Guide →