White Paper · Oracle Java

Oracle Java Licensing Guide 2026

How the Java SE Universal Subscription's per-employee metric turns a free runtime into a seven-figure liability, and the field-tested moves enterprise buyers use to calculate, contain, and eliminate the exposure.

By Atonement Licensing Advisory Former Oracle LMS & Java practitioners Published Jan 2026 · Updated June 2026 ≈ 17 min read

Prepared by Atonement Licensing · buyer-side advisory · last reviewed June 2026. List prices are Oracle's published per-employee tiers; worked exposure and saving figures are clearly labelled indicative scenarios for illustration, not quotes for any specific organisation.

Executive summary

In January 2023 Oracle replaced its processor- and named-user-based Java SE pricing with a single Java SE Universal Subscription licensed by total employee headcount, converting a metric that scaled with usage into one that scales with the size of your organisation. For an enterprise running Java on a handful of servers, the per-employee model can multiply cost by an order of magnitude, and because almost every member of staff becomes billable, it is now one of Oracle's most active audit fronts.

The exposure is real but rarely fixed. As an indicative illustration, a 10,000-employee organisation falls in Oracle's published $8.25 per-employee-per-month tier, which lists at roughly $990,000 a year regardless of whether Java runs on three servers or three hundred. Yet eligible workloads usually move to a supported OpenJDK build at no licence cost, which is why most enterprises can remove a large share of the subscription through migration, estate right-sizing, and disciplined negotiation. Oracle's published price is an opening position, not a settled bill.

This guide explains how the metric is defined, how to calculate your true exposure, where the defensible savings sit, how to respond when an Oracle compliance review (formerly LMS, now often GLAS) letter arrives, and what 2026 negotiated outcomes actually look like. The central message for buyers is unambiguous: most organisations can remove 40 to 100 per cent of the Java subscription, and the work begins with an honest inventory, not a renewal quote.

$5.25–15Published Oracle list price per employee per month, by volume tier
100%Of headcount counted, staff, part-time, temps, and supporting contractors
40–100%Subscription cost typically removable via migration and right-sizing (indicative)
90 daysWindow to control the narrative once a review letter lands
1

What changed in 2023, and why it matters

For most of Java's commercial history, paid support was priced the way enterprise software usually is: by the resource that consumed it. Under the legacy Java SE Subscription, introduced in 2019, you paid per Named User Plus for desktops or per processor for servers. An organisation that ran Java on twenty servers paid for twenty servers' worth of cores, and the cost tracked the deployment.

The Universal Subscription broke that link. From 23 January 2023 the only Java SE metric Oracle sells to new customers is per employee, where "employee" is defined expansively to include full-time and part-time staff, temporary staff, and, critically, the agents, contractors, and consultants who support your internal operations. The count is your total organisational headcount, not the number of people who use Java, install Java, or have ever heard of Java. A 10,000-person company that runs Java on three servers is licensed for 10,000 employees.

The commercial logic is deliberate. Java is embedded in thousands of enterprise applications, middleware stacks, and build pipelines, and it is notoriously hard to inventory because it ships inside other products and is installed ad hoc by developers. By pricing on headcount, Oracle removes its own need to measure your deployment at all: the bill is a function of a number your HR system already publishes. That same property is what makes the metric so punishing, and why exposure calculation, not deployment counting, is now the first task for any buyer.

Insider note

Customers still holding legacy 2019-era Java SE Subscriptions, priced per processor or Named User Plus, are generally permitted to renew on those terms for now, but Oracle steers every renewal conversation toward the Universal metric. If you have a legacy agreement, protecting your right to renew it is often worth more than any single negotiated discount on the new model.

Action. Establish which metric governs you today, legacy or Universal, before any renewal conversation. The metric, not the discount, decides the size of the bill.

2

How the per-employee metric is counted

The single most expensive misunderstanding buyers carry into a Java negotiation is the belief that "employee" means "Java user." It does not. Oracle's definition sweeps in categories that inflate the billable number well beyond payroll headcount, and the gap between a naive count and Oracle's count is exactly where disputes, and settlements, happen.

Table 1, What counts toward the Java SE "employee" metric
CategoryCounted?Buyer note
Full-time employeesYesBase of the count; pull from the HR system of record
Part-time & temporary staffYesCounted as full heads, not FTE-adjusted
Agents, contractors, consultantsYes, if supporting internal operationsMost-disputed category; scope and evidence matter
Outsourced staff at third partiesOften contestedDepends on who they "support"; negotiate the definition
Customers and end-users of your productsNoExternal users are excluded; document the boundary
Employees of separate legal subsidiariesDependsHinges on the contracting entity and affiliate language

The contractor and outsourcing rows are where the count is fought. Oracle's definition reaches people who "support" your internal operations, but the boundary of that phrase is negotiable, and the burden of demonstrating who falls inside it is not one-sided. A documented view of which contractors support internal operations, versus those delivering services to your customers, is the difference between a headcount you can defend and one Oracle sets for you.

Action. Reconcile the billable population against the contract's actual definition before accepting any headcount figure, and document every category you exclude.

3

Calculating your true exposure

Exposure is a function of two numbers: the counted population and the tier price that population lands in. Oracle's published tiers fall as headcount rises, so the per-employee rate at 12,000 staff differs sharply from the rate at 900. Build the calculation from the published table, then layer your own right-sizing on top.

Table 2, Oracle Java SE Universal Subscription published list tiers (per employee, per month)
Employee bandList price / employee / monthIndicative annual list at band midpoint
1 to 999$15.00~$90,000 at 500 employees
1,000 to 2,999$12.00~$288,000 at 2,000 employees
3,000 to 9,999$10.50~$819,000 at 6,500 employees
10,000 to 19,999$8.25~$990,000 at 10,000 employees
20,000 to 29,999$6.75~$2.0M at 25,000 employees
40,000 to 49,999$5.25~$2.8M at 45,000 employees
50,000+Negotiated with OracleCustom; benchmark before signing

The worked example is sobering precisely because it is so detached from usage. A 10,000-employee organisation sits in the $8.25 tier: $8.25 multiplied by 10,000 employees, multiplied by twelve months, is roughly $990,000 a year at list. Whether that organisation runs Oracle Java on three servers or none of consequence makes no difference to the headline figure, which is why the saving comes from removing the requirement to subscribe at all, not from haggling the rate.

OpenJDK migration of server & build estate
up to 100%
Right-sizing the counted population
10 to 30%
Negotiating tier, term & ramp
10 to 25%
Removing shadow Oracle JDK installs
varies

Indicative ranges, shown to illustrate where reductions concentrate rather than to predict any single estate. The largest lever by far is eliminating the need for a paid Oracle runtime where a no-fee distribution does the same job.

Action. Calculate exposure from the published tier and your true counted population, then model the post-migration figure beside it. The comparison is the business case.

Unsure what your real Java exposure is? We size it against Oracle's count and model the migration path.

Oracle Licensing Experts
4

Where the defensible savings sit: OpenJDK migration and right-sizing

The single largest, most durable saving is migrating eligible workloads off the Oracle JDK and onto a supported OpenJDK build such as Eclipse Temurin, Amazon Corretto, Microsoft Build of OpenJDK, or Azul. These are the same Java language and the same class libraries, built from the same OpenJDK source, and for the great majority of server, container, and build-pipeline workloads they are a like-for-like replacement that carries no Oracle subscription. Where an enterprise needs commercial support, several vendors offer it on OpenJDK at a fraction of the per-employee cost.

Migration is an inventory exercise before it is an engineering one. Find every Oracle JDK install, separate it from the no-fee distributions already in the estate, and identify the small number of workloads with a genuine dependency on an Oracle-specific feature or a certified third-party application that mandates the Oracle runtime. Those genuine dependencies are usually a fraction of what the first scan suggests, and each one resolved removes a reason to subscribe.

Table 3, Oracle JDK versus supported OpenJDK for a typical enterprise estate
DimensionOracle JDK (Universal Subscription)Supported OpenJDK build
Licence costPer total employee, all staff billableNo Oracle licence; optional paid support per usage
Technical parityReference implementationBuilt from the same OpenJDK source
Security updatesOracle Critical Patch UpdatesQuarterly updates from the chosen vendor
Best fitWorkloads with a genuine Oracle-specific dependencyServer, container, and build-pipeline workloads
Takeaway. The metric is punishing, but the runtime is replaceable. Most Java workloads do not need Oracle's JDK, and every one you migrate removes a head from the count that never recovers.

Action. Run a full Oracle JDK inventory, migrate everything without a genuine dependency to a supported OpenJDK build, and reserve any paid subscription for the residue that truly requires it.

Oracle prices Java on the size of your company. The buyer's answer is to make the company's size irrelevant by removing the runtime that triggers the bill.
5

Responding when an Oracle Java review letter arrives

A Java review follows the same logic as any Oracle compliance exercise, and the same discipline applies. The letter, whether it cites the audit clause or arrives as a friendly "soft" review, is an invitation to share data on Oracle's terms, and the first 90 days decide whether you respond on yours instead. Acknowledge in writing, route every contact through one named owner, and do not run download-detection scripts or hand over install telemetry before scope is agreed.

Days 1 to 15

Contain

Acknowledge in writing, name a single owner, confirm exactly what is being asked and under what right, and pause all data sharing until scope is agreed.

Days 15 to 45

Measure

Inventory real Oracle JDK installs against no-fee builds, and reconcile the counted population against the contract's actual employee definition.

Days 45 to 90

Resolve

Migrate eligible workloads, scope the billable population down to the defensible number, and settle or negotiate the residual in writing.

The Java-specific trap is download history. Oracle can correlate downloads of the Oracle JDK from its own site against a company domain, and an old download by one developer becomes the opening for a review. A download is not proof of current commercial use, and a build replaced months ago by a no-fee distribution is not a licence liability. Meet the assertion with the inventory, not with an apology.

Action. Treat a Java review with full audit discipline from day one, measure your own estate before sharing anything, and answer download-based claims with current-state inventory evidence.

6

Negotiating the Universal Subscription, and 2026 outcomes

Where a genuine residual remains and a subscription is warranted, the deal is still negotiable on more than the rate. The levers that move a Java number are the counted population, the term, the ramp, and the right to true the count down as migration proceeds. A subscription signed at full workforce with no reduction mechanism locks in the worst case; one signed against a defined, evidenced population with a migration ramp tracks reality.

Indicative list exposure~$990k

Annual list cost for a 10,000-employee organisation in the $8.25 tier, irrespective of how little Java it actually runs (indicative, at published list).

OpenJDK migration cost$0

Oracle licence cost of moving eligible workloads to a supported OpenJDK build such as Eclipse Temurin or Amazon Corretto, the largest single saving available.

The 2026 pattern we see is consistent: buyers who arrive with an independent inventory, a migration plan, and a defensible population settle far below the opening per-employee number, and many remove the subscription entirely once the residual workloads are migrated. Buyers who negotiate only the headline rate, accepting the all-employee count, save least, because they are discounting a number that should not exist. Benchmark the offer, contest the population, and put any agreed reduction right and price hold in writing before signing.

Action. Negotiate the population and the reduction rights, not just the rate, and only subscribe for the workloads that genuinely require the Oracle runtime.

7

Legacy subscriptions and future-proofing the estate

A legacy 2019-era subscription, priced per processor or Named User Plus, is frequently the most valuable asset a Java buyer holds, because it prices on usage rather than headcount. Where one exists, protecting the right to renew it on its existing terms can be worth more than any concession on the Universal model, and it should be defended deliberately rather than allowed to lapse into a Universal renewal by default.

Future-proofing is mostly governance. Standardise on a supported OpenJDK distribution as the default runtime, block ad hoc Oracle JDK downloads through endpoint policy, and keep a current inventory so that a future review meets evidence rather than guesswork. The estates that avoid a recurring Java liability are the ones that removed the trigger and then kept it removed.

Our recommendation

Inventory the real Oracle JDK footprint, migrate every workload without a genuine dependency to a supported OpenJDK build, defend any legacy per-processor subscription, and subscribe to the Universal metric only for the residue that truly requires it, against a defined population with reduction rights in writing. The per-employee metric is designed to make your headcount the bill; the buyer's answer is to make the Oracle runtime, and therefore the metric, irrelevant to all but a handful of workloads.

Key takeaways

Frequently asked questions

Does every employee really get counted, even if they do not use Java?

Yes. Under the Java SE Universal Subscription the metric is total employee headcount, including part-time and temporary staff and the contractors who support internal operations, regardless of how many people actually use Java. The number of Java users is irrelevant to the bill, which is why the saving comes from removing the runtime, not from counting users.

We only run Java on a few servers, so why is the quoted bill so large?

Because the price is detached from deployment. A 10,000-employee organisation sits in the published $8.25 per-employee-per-month tier, listing at roughly $990,000 a year (indicative, at list), whether Java runs on three servers or three hundred. The fix is to migrate eligible workloads off the Oracle JDK so no subscription is required.

Can we keep our legacy 2019 Java subscription?

Often, yes. Customers on the legacy per-processor or Named User Plus subscription are generally permitted to renew on those terms for now, though Oracle steers renewals toward the Universal metric. Protecting that right is frequently worth more than any discount on the new model, so defend it deliberately.

Is OpenJDK a safe replacement for Oracle Java?

For most server, container, and build-pipeline workloads, yes. Supported builds such as Eclipse Temurin, Amazon Corretto, and the Microsoft Build of OpenJDK are built from the same OpenJDK source and provide quarterly security updates, with optional paid support at a fraction of the per-employee cost. Reserve the Oracle runtime for the few workloads with a genuine Oracle-specific dependency.

What should we do first if we receive an Oracle Java review letter?

Acknowledge it in writing, route every contact through one named owner, and confirm what is being asked and under what right before sharing any data. Inventory your own estate first, and answer download-based assertions with current-state evidence rather than assumptions.

Get this guide applied to your Java estate. Confidential assessment within one business day.

Book a 30 minute call

Related research: the Oracle Audit Defense Playbook 2026, the Oracle Licensing Playbook 2026, and the Oracle Negotiation Playbook 2026.