The decision rule is a ratio: the legacy Java SE subscriptions priced what you used — named users and processors — while the Universal Subscription prices who you employ, counting every employee and qualifying contractor whether or not they ever touch Java. Hold a legacy metric for as long as Oracle will renew it when your Java footprint is small relative to headcount; accept the employee metric only when Java genuinely runs everywhere — and weigh the third route, removing Oracle JDK altogether, before signing either.
Published 10 February 2026 · Last reviewed 10 February 2026
Until January 2023, commercial Oracle Java was sold the way Oracle sells databases: a Java SE Subscription counted in Named User Plus for desktop populations and in Processors for servers, so the bill tracked the size of the Java estate. The Java SE Universal Subscription that replaced it abandoned usage as the metric entirely. It is priced per employee, per month, on the total headcount of the subscribing organisation — and Oracle's definition of employee reaches past payroll to part-timers, temporary staff, and the personnel of contractors, agents and outsourcers who support internal business operations.
Three years on, the practical state of play is settled. New commercial subscriptions are sold on the employee metric only. Organisations that held NUP or Processor subscriptions before the change have been able to renew on their legacy terms — but at Oracle's discretion, at existing quantities, and increasingly through a renewal process that asks for deployment evidence first. Meanwhile Oracle's Java sales motion has become one of the most active compliance campaigns in enterprise software, built on the company's own download logs rather than on contractual audit clauses alone.
That is why this comparison has three honest answers rather than two. Universal versus legacy is the question Oracle frames; for a large share of organisations the better-fitting answer is neither — current LTS releases are free under the No-Fee Terms and Conditions license for a defined window, and OpenJDK builds are free indefinitely. The comparison below covers all three.
This guide is general information about Oracle's Java licensing programs, not legal or licensing advice for your situation; subscription terms are set by your agreement and Oracle's current policy documents. It names no firms; the firm directory lists Oracle-capable advisors with balanced pros and cons, listed, not ranked.
| MECHANIC | LEGACY (NUP / PROCESSOR) | UNIVERSAL (EMPLOYEE) |
|---|---|---|
| What is counted | Named users on desktops; processors on servers, core-factor adjusted | Total employees plus qualifying contractor and outsourcer personnel |
| Relationship to usage | Direct — the bill tracks the Java estate | None — one server or ten thousand, the count is headcount |
| Availability | Withdrawn from new sale January 2023; renewal at Oracle's discretion for existing holders | The only commercial Java subscription Oracle now sells |
| Growth headroom | None beyond licensed counts; expansion requires migration to the employee metric | Unlimited deployment across desktop, server and third-party cloud |
| Compliance burden | Continuous counting: users, cores, virtualization boundaries | A headcount census — simpler, but the employee definition needs active management |
| Renewal dynamics | Usage validation before renewal; overage converts the renewal into a migration quote | Headcount trued up at renewal; tier pricing moves with employee count |
| Exit dynamics | Lapse and remove Oracle JDK, or migrate to the employee metric | Lapse and remove Oracle JDK; no perpetual rights survive a subscription |
The table's pivotal row is relationship to usage. Every other difference follows from Oracle's decision to decouple the Java bill from the Java estate. For an organisation of fifty thousand people running Java on two hundred servers, the employee metric multiplies the licensed population by orders of magnitude; for a software-saturated firm where every laptop carries a JDK, it can simplify a counting problem that the legacy metrics handled badly. Neither subscription leaves anything behind when it ends — both are rental, and lapsing either means removing or replacing Oracle JDK.
If you still hold a NUP or Processor Java subscription, you hold something Oracle no longer sells — usually at a fraction of what the employee metric would cost for the same estate. Treat it accordingly. Oracle's public position has been that legacy holders may renew on their existing metrics and quantities; its operational position is that a legacy renewal is approved after a usage validation in which the customer evidences that deployments still fit within the licensed counts. That validation is, functionally, a small audit run through the renewal desk: deployment data is requested, and an overage discovered there does not price as an incremental legacy purchase — it prices as a migration to the Universal Subscription for the whole organisation.
The legacy position therefore rewards discipline and punishes drift. It cannot grow: new projects, acquisitions and platform expansions have no legacy headroom to land in. Each renewal is discretionary, and the discretion belongs to the counterparty with a structural interest in migration. The defensible strategy is to treat every legacy renewal as a checkpoint — verify internally that usage sits inside entitlements before Oracle asks, document it, and decide deliberately each cycle whether the next term's needs still fit inside a frozen entitlement. An internal effective license position scoped to Java is the cheap version of that insurance.
No Oracle Java decision is complete without the licensing that costs nothing. Oracle's own current LTS releases ship under the No-Fee Terms and Conditions (NFTC) license, free for production use until one year after the following LTS releases: JDK 17's free window closed in September 2024, JDK 21's runs until September 2026 now that JDK 25 has shipped, and JDK 25's is expected to run to September 2028. After each window, later updates of that release revert to the OTN license, under which production use requires a subscription — the mechanism by which a free estate quietly becomes a licensable one if patching continues past the cliff.
Parallel to the NFTC sits OpenJDK: builds such as Eclipse Temurin and Amazon Corretto are compiled from the same codebase, pass the same compatibility kit, and are free for production indefinitely under the GPL with Classpath Exception. For organisations whose Java needs are ordinary — run supported LTS releases, apply patches — a managed migration to OpenJDK removes the Oracle licensing question entirely. The condition is absolute completeness: one surviving Oracle JDK installation, including one embedded in a vendor appliance or pulled in by a container base image, re-opens the question for the entire headcount under the employee metric. Both subscriptions in this comparison are therefore really being compared against a third option whose price is an inventory-and-migration project rather than a recurring fee. That trade is information for your modelling, not advice; commercial support needs, vendor certifications and patching obligations differ by estate.
Staying legacy suits organisations with a contained, stable Java estate and a verified compliance position: the frozen entitlement is cheap precisely because it cannot grow, and the renewal validation holds no terror for an estate that is actually inside its counts. It is a holding position, not a destination — worth keeping while the gap between legacy and employee pricing remains wide, and worth pairing with a quiet evaluation of the OpenJDK route for the day Oracle declines the renewal.
The Universal Subscription suits organisations where Java is pervasive relative to headcount — software houses, engineering-dense firms, estates where the legacy desktop NUP arithmetic was already approaching the size of the workforce — and organisations that positively want Oracle's JDK, Oracle's patch cadence and Oracle support on terms that remove deployment counting altogether. The unlimited-deployment grant is genuinely simple; what must be managed instead is the denominator, because the contractor and outsourcer language can swell the counted population well past payroll, and headcount growth reprices the whole subscription at renewal.
The exit suits more organisations than either subscription, on the numbers most advisors see: ordinary Java workloads on LTS releases, no hard dependency on Oracle-specific support, and the organisational capacity to run a real migration with a real inventory. The discriminator is honesty about that capacity — a nominal migration that leaves stragglers is the worst of all three positions, paying nothing while carrying the full exposure.
The download-log dynamic. Oracle's Java campaign characteristically begins not with an audit notice but with an email: its records show your organisation downloading JDK installers or patches, and it would like to discuss licensing. The inference from download to deployment is rebuttable, but only by an organisation that knows what is actually installed. Building that inventory before responding — and routing the response through people who handle such outreach routinely — is standard practice; this is the territory where Oracle audit defense firms now spend a substantial share of their time.
The employee definition is negotiable at the edges. The metric's reach into contractors, agents and outsourcers is contract language, and large deals have carved at its edges: which third-party populations count, how headcount is measured and dated, how acquisitions enter the count and on what timeline. Locking the measurement rules at signature matters more here than in most subscriptions, because the denominator is the entire price.
Renewal-time leverage differs by direction. A legacy holder approaching renewal holds little contractual leverage but one real alternative: the credible, evidenced ability to decline the renewal and leave for OpenJDK resets the conversation more effectively than any negotiation tactic. A Universal subscriber approaching renewal negotiates tier boundaries, headcount true-up mechanics and term length — ordinary subscription craft, with the same exit alternative in the background. In both cases the asymmetry is familiar: Oracle's Java desk runs this negotiation daily, and most buyers meet it once. Independent negotiation support exists to level exactly that.
Renewing legacy on autopilot. Submitting deployment data for the renewal validation without checking it internally first hands Oracle the overage discovery — and with it, the migration quote — in a process you initiated.
Patching past the NFTC cliff. Estates that adopted JDK 17 or 21 as free and kept applying updates after the window closed converted themselves into licensable deployments without a single procurement decision being taken. Date the cliffs — September 2026 for JDK 21 on current plans — and decide before them.
Counting employees the easy way. Self-declaring payroll headcount and ignoring the contractor and outsourcer language understates the metric Oracle will apply at true-up. The definition in the agreement, not the HR system's default report, is the count.
The phantom migration. Declaring an OpenJDK migration complete on the strength of a software push, without verifying removal — including bundled JDKs inside third-party applications and golden images — leaves the exposure intact and the vigilance gone.
Answering download outreach casually. A well-meant reply confirming “we only use Java a little” concedes deployment without establishing entitlement or scope. Treat the first email with the same preparation as a formal audit notice.
Deciding inside Oracle's frame. The renewal letter offers two options: legacy renewal on validation, or Universal migration. The third option never appears in the letter, and pricing the choice without it — and without someone independent doing the modelling — reliably overstates the case for whichever subscription Oracle prefers that quarter.
The legacy metrics' own internal fork →
The other recurring-stream decision →
Unlimited structures on the database side →
How to pick the firm for this work →
Firms that model decisions like this one →
Every field guide on the site →
Sometimes. Oracle withdrew the legacy Java SE subscriptions from new sale in January 2023 but has allowed existing subscribers to renew on their old metrics, at Oracle’s discretion and at unchanged quantities. In practice Oracle conditions a legacy renewal on a usage validation: you must evidence that deployments still fit within the licensed NUP or Processor counts. If usage has grown past the entitlement, the renewal conversation typically becomes a migration conversation onto the employee metric.
Far more people than use Java. The metric counts your full-time, part-time and temporary employees, plus the employees of agents, contractors, outsourcers and consultants who support your internal business operations. It is a headcount census, not a user count — an organisation where Java runs on a handful of servers licenses the same population as one where it runs everywhere.
No. OpenJDK distributions such as Eclipse Temurin and Amazon Corretto are licensed under the GPL with Classpath Exception and are free for production use. The compliance risk sits in the word only: a single overlooked Oracle JDK installation, or an Oracle JDK pulled in silently by an installer or container base image, recreates the licensing question for the whole organisation under the employee metric. Migrations off Oracle JDK succeed or fail on the completeness of the inventory.
Until September 2026. Oracle’s No-Fee Terms and Conditions license covers each LTS release until one year after the next LTS ships. JDK 25, released September 2025, started that clock for JDK 21; JDK 25 itself is expected to remain under the NFTC until September 2028. After the window closes, later updates of that release move to the OTN license, under which production use requires a subscription — the pattern JDK 17 followed when its free window ended in September 2024.
Mostly from its own records. Oracle logs downloads of its JDK installers and security patches by IP address and correlates them with organisations, then opens contact through sales-led outreach — the soft audit — before any formal audit clause is invoked. Download history is treated as an indicator of deployment, which is why responses to such outreach benefit from preparation: the inference is rebuttable, but only with an actual inventory.
Yes — that is its main structural simplification. One employee-based subscription covers Oracle Java on desktops, servers and third-party clouds without counting installations, where the legacy model required separate NUP arithmetic for desktops and Processor arithmetic for servers. The simplification is real; whether it is worth the price of licensing every employee is the question this guide compares.
Deciding between a frozen legacy entitlement, a headcount-priced subscription and a managed exit is exactly what an Oracle licensing advisor is for. The directory lists the firms that do this work, with balanced pros and cons, listed, not ranked.
Tell us the vendor, the service you need and where things stand, and we will route your brief to firms that genuinely cover that combination. The directory and matching are free for buyers, no vendor ever sees your brief, and we add no markup.
Our weekly dispatch on vendor audit programs, regional developments and one buyer move. Subscribe to The Licensing Radar.