Oracle's current commercial licence for Java — priced per employee, not per user. An independent guide to how it works and what it really costs.
The Java SE Universal Subscription is the licence Oracle introduced on 23 January 2023 as the single commercial route to running Oracle Java in production. It replaced the previous Java SE Subscription, which was priced per named user and per processor. The word “Universal” signals the change: one subscription covers desktops, servers, and cloud, with no separate processor and user metrics to track.
The defining feature — and the reason it has reshaped Java budgets — is the metric. The Universal Subscription is licensed per employee, where “employee” is defined to include all full-time, part-time, and temporary staff, plus agents, contractors, and consultants who support your internal operations. It is not a count of who installs or uses Java. If your organisation has 5,000 employees and one server runs Oracle JDK, you license 5,000 employees.
Oracle publishes the Universal Subscription on a per-employee, per-month price list with volume tiers. The headline rate starts in the region of USD 15 per employee per month for smaller organisations and falls through published tiers as employee counts rise into the tens and hundreds of thousands. Because the count is the whole workforce, the annual figure scales fast: a 10,000-employee company sits well above USD 1 million per year at list price before any negotiation.
23 January 2023
Per employee (entire workforce)
Full-time, part-time, temporary, contractors, consultants
Per employee, per month
Legacy Java SE Subscription (user / processor)
Desktop, server, and cloud use
The hardest part of the Universal Subscription is not the price — it is the counting rule. Under the legacy subscription you paid for the processors and named users actually running Java. Under the Universal Subscription you pay for people who never touch Java at all. A warehouse worker, a retail cashier, and a board director all count if they fall inside Oracle's employee definition.
This makes the subscription extremely sensitive to how few machines actually need Oracle Java. If only a handful of legacy applications depend on the Oracle JDK, you are still licensing the entire company to keep them running. That asymmetry is precisely why migration to OpenJDK so often produces the largest savings: removing the last Oracle JDK install removes the entire subscription, not a slice of it.
Organisations that held the older Java SE Subscription before January 2023 have generally been allowed to renew on the legacy user and processor metric for a time. That grace is finite. At some renewal point Oracle will expect a move to the employee metric, and for many estates that transition is a step change in cost. Modelling it before the renewal conversation — not during it — is essential.
The price follows total employees. A budget built on the number of Java users will be wrong, and usually far too low.
Oracle's employee definition pulls in contractors, consultants, and temporary staff. Leaving them out understates both the count and the compliance position.
A single remaining Oracle JDK install can require licensing the whole workforce. One forgotten server is an enterprise-wide subscription.
We benchmark Oracle's employee-metric quote and negotiate it down — a 68% average reduction across engagements.
MigrateWe remove the last Oracle JDK from your estate so the subscription is not needed at all.
PlanFacing the move off a legacy subscription? We model the new cost and plan the renewal in advance.
If we take on your Oracle Java audit and cannot reduce the claim, we refund our fees. See how the guarantee works →
We benchmark the Universal Subscription, model your true cost, and show you whether to negotiate or migrate.
Weekly Oracle Java updates, audit alerts, and negotiation intel.