Named User Plus vs the employee metric.

Oracle has sold Java SE subscriptions under two very different metrics. The legacy Named User Plus model tied cost to who used Java. The current employee metric ties cost to how many people you employ. If you hold an older agreement, the move from one to the other is the most consequential renewal decision you will face — so it pays to understand both.

Two metrics, two eras

When Oracle launched the Java SE Subscription in 2019, it priced it on metrics borrowed from the rest of its catalogue: Named User Plus (NUP) for desktop-style usage and Processor for server-style usage. Both are deployment-based: the bill follows the size of your actual Java footprint.

In January 2023 Oracle replaced that approach with the Java SE Universal Subscription, priced on the employee metric — an organisation-based measure where the bill follows your headcount, not your deployment. Understanding the difference between deployment-based and organisation-based pricing is the whole story.

The legacy model: Named User Plus and Processor

Under the original Java SE Subscription, Named User Plus counted individuals authorised to use Java on the licensed devices, at a list rate in the region of USD 2.50 per user per month. It carried minimum-quantity rules, so very small counts still attracted a floor charge. The Processor metric counted licensed processor cores — adjusted by Oracle's core factor table — at a list rate around USD 25 per processor per month, and suited servers where counting individual users was impractical.

The defining feature of both: if you ran a little Java, you paid a little. A company with 200 Java users and a dozen servers paid for 200 users and a dozen servers. Cost scaled with consumption, which made budgeting predictable and made eliminating Java a direct route to a lower bill.

The current model: the employee metric

The employee metric throws that proportionality away. The Universal Subscription licenses every employee in the organisation — full-time, part-time and temporary staff, plus the contractors, consultants and outsourcers who support internal operations — regardless of whether they ever use Java. Pricing runs on a tiered per-employee rate, from roughly USD 15.00 per employee per month at the entry band down to about USD 5.25 at the largest published tier.

The consequence is stark for any organisation with light Java usage. The cost is now set by HR headcount, a number that has nothing to do with the IT estate. Decommissioning Java servers no longer reduces the bill; only exiting the subscription entirely does.

Named User Plus vs employee metric: the key differences

Aspect	Named User Plus (legacy)	Employee metric (current)
What is counted	People who use Java	All employees and relevant third parties
Cost basis	Deployment / consumption	Organisation headcount
List rate	~USD 2.50 / user / month	USD 5.25–15.00 / employee / month
Light Java usage	Cheap	Expensive — usage is irrelevant
Effect of cutting Java	Lowers the bill	No effect unless you exit entirely
Available to buy new	No — retired Jan 2023	Yes — the only current model

For an organisation where Java is used by a minority of staff, the two models can differ by an order of magnitude. That gap is precisely why renewal conversations have become so charged.

Which metric applies to you

• You bought a Java SE Subscription before January 2023. You are most likely still on NUP or Processor — for now. The metric is contractual and stays in force until your agreement ends.
• You are buying Java SE for the first time today. Only the employee-metric Universal Subscription is available. NUP and Processor cannot be bought new.
• Your legacy agreement is approaching renewal. This is the pressure point. Oracle's standard position is to renew you onto the employee metric, often with a significant cost increase.

Can you still buy Named User Plus for Java?

For new Java SE purchases, no. Since 23 January 2023 the employee-metric Universal Subscription is the only Java SE subscription Oracle sells. Existing NUP and Processor subscriptions can generally be renewed for a period under their original metric — Oracle has allowed continuity rather than forcing an immediate switch — but this is not guaranteed indefinitely, and Oracle actively encourages migration to the new model. If you still hold a legacy metric, treat it as a valuable and finite asset: it is almost always cheaper than the employee-metric alternative, and keeping it for as long as possible is a legitimate negotiating goal.

What happens at renewal

When a legacy Java SE agreement comes up for renewal, expect Oracle to present the employee metric as the path forward. The quoted figure is frequently several times the legacy cost, because it reprices Java against total headcount. This is a negotiation, not a fixed outcome. Your options at the table include renewing on the legacy metric where Oracle will still allow it, negotiating the employee-metric rate and term, or declining the subscription altogether in favour of a migration to free OpenJDK. The worst outcome is to accept the first employee-metric quote without testing any of those alternatives.

How to decide your strategy

• Establish your real numbers. Compare your current NUP/Processor cost against a modelled employee-metric cost using an accurate headcount. You cannot negotiate what you have not quantified.
• Value your legacy metric. If NUP is materially cheaper for your profile, defending it — or extending it — may be worth more than any discount on the new model.
• Build the migration alternative. A credible plan to move to a free OpenJDK distribution is the strongest leverage you can bring, because it makes "no subscription at all" a genuine option.
• Start early. Leverage in a Java renewal decays as the deadline approaches. Begin 9–12 months out.

How the Processor metric and core factor worked

The Processor metric deserves a closer look, because organisations still holding it often misjudge its value. Under this metric, Oracle counted the processor cores on which Java SE ran and multiplied by a core factor from Oracle's published table — a multiplier that reduced the count for many common processor types. The result was a "licensable processor" number, charged at a list rate of around USD 25 per processor per month.

The key point is that this number tracked your infrastructure, not your organisation. A consolidated, well-virtualised Java estate could carry a surprisingly small processor count. For organisations with a contained Java footprint, a legacy Processor subscription can be dramatically cheaper than the employee-metric equivalent — which is exactly why Oracle is keen to move customers off it, and why defending it at renewal can be worth real money.

Frequently asked questions

Can I still buy a Named User Plus subscription for Java?

No. Since 23 January 2023 the employee-metric Universal Subscription is the only Java SE subscription Oracle sells to new customers.

Will Oracle force me off my legacy metric?

Not immediately. Existing Named User Plus and Processor subscriptions can generally be renewed for a period under their original metric, but Oracle actively steers customers toward the employee metric and continuity is not guaranteed indefinitely.

Why is the employee metric usually more expensive?

Because it prices Java against total headcount rather than actual Java deployment. For any organisation where Java is used by a minority of staff, headcount is far larger than the old metrics measured.

Is the legacy metric always cheaper?

For most organisations with contained Java usage, yes — often by a wide margin. But it depends on your specific deployment and headcount; the only reliable answer is to model both side by side.

When should I start planning my renewal?

Nine to twelve months before the renewal date. Leverage decays as the deadline approaches, and a credible migration alternative takes time to prepare.

Conclusion

Named User Plus and the employee metric are not two pricing options you choose between — they are two eras, and most organisations are being carried from the first into the second whether they like it or not. The legacy metric rewarded keeping Java usage small; the employee metric does not. If you still hold a NUP or Processor agreement, it is an asset worth defending, and your renewal strategy should be built around quantifying the gap, protecting the cheaper metric where you can, and keeping a real migration on the table as the alternative that gives you power.