Java license cost calculator.

Most enterprises that want to know what Oracle Java costs them assume the answer depends on how much Java they run. It does not. Since January 2023, Oracle has priced the Java SE Universal Subscription on a single number — total employee count — and the calculator below turns that number into a price. The arithmetic is simple. The hard part, and the part the calculator cannot do for you, is knowing which number Oracle will actually use and whether you should be paying at all.

The employee metric in one sentence

The Oracle Java SE Universal Subscription is licensed per employee, where "employee" means every person in your organisation — not the people who use Java. That is the entire model. A company with 8,000 employees and 40 Java developers is licensed for 8,000, not 40. If you understand that one sentence, you understand 90% of Java licensing economics; the rest is the price table and the definitions.

This is a deliberate change from how Oracle used to charge. Before 2023, the Java SE Subscription was metered on Named User Plus and Processor counts — you paid in proportion to the machines and users actually running Oracle Java. The current Java SE Universal Subscription abandoned that proportionality entirely. The result is that for most organisations the bill went up sharply, because the denominator changed from "Java footprint" to "headcount." Our guide to how Oracle prices Java traces the full history; for the calculator, all you need is the headcount rule.

The Java cost calculator

Enter your total employee count below. The calculator applies Oracle's published per-employee monthly rate for the tier your headcount falls into and returns an annual estimate. It uses Oracle's public Java SE Universal Subscription price list and assumes list price with no discount.

Who counts as an employee

The number you typed into the calculator is the part Oracle scrutinises hardest, because Oracle's definition of "employee" for Java is far broader than the headcount your HR system reports. Under the Java SE Universal Subscription, the count Oracle expects includes:

• All full-time employees, regardless of role, location or whether they ever touch a computer.
• All part-time and temporary employees, counted as whole people, not pro-rated to hours worked.
• All agents, contractors and consultants who support your internal operations — even though they are not on your payroll.
• Staff of outsourcers working on your behalf in those internal operations.

In other words, the metric is designed to capture your effective workforce, not your legal employee roster. An organisation with 6,000 badged employees and 1,500 long-term contractors is, for Java pricing purposes, a 7,500-employee organisation. This is the single most common reason a do-it-yourself estimate comes in low: companies enter their HR headcount and Oracle later argues for a larger figure. When you use the calculator, use the broad number — it is closer to what Oracle will assert. The distinction between counting people and counting machines is also why the processor versus employee metric comparison matters so much to total cost.

The published price tiers

Oracle's Java SE Universal Subscription is volume-tiered: the more employees you have, the lower the per-employee rate, though the total still rises. The calculator uses the publicly listed rates below. These are list prices — the figure before any negotiated discount.

Two things about this table are easy to miss. First, the tier applies to your entire headcount, not just the employees above the threshold — cross from 999 to 1,000 employees and the whole organisation reprices at $12.00, not just employee number 1,000. Second, the lower per-employee rate at scale does not make large enterprises cheap; a 25,000-employee organisation at $6.75 still owes more than $2 million a year at list. The tiering softens the curve; it does not bend it down.

Three worked examples

To make the metric concrete, here are three organisations of different sizes, each priced at list with the calculator's logic.

Small enterprise — 600 employees

A 600-employee company sits in the 1–999 band at $15.00 per employee per month. The annual list cost is 600 × $15.00 × 12 = $108,000 a year. It does not matter whether 12 people or 120 people use Java; if any commercial Oracle JDK that requires a subscription is in the estate, this is the list exposure.

Mid-market — 5,000 employees

A 5,000-employee organisation falls in the 3,000–9,999 band at $10.50. The annual list cost is 5,000 × $10.50 × 12 = $630,000 a year. If this company also employs 800 contractors who support internal operations, the true count is 5,800, and the cost rises to roughly $730,000 — the same tier, but a six-figure swing driven entirely by who you count.

Large enterprise — 22,000 employees

A 22,000-employee enterprise lands in the 20,000–29,999 band at $6.75. The annual list cost is 22,000 × $6.75 × 12 = $1,782,000 a year. This is the figure that drives migration decisions: nearly $1.8 million a year, recurring, for a runtime that has a free and functionally equivalent alternative.

What the calculator cannot tell you

A calculator multiplies a headcount by a rate. It is useful for scale and budgeting, but it cannot answer the four questions that actually decide your Java cost.

Whether you owe anything at all. The employee metric only applies if you have a commercial requirement for Oracle Java — an Oracle JDK build, used commercially, in a version or under terms that require a paid subscription. An estate running entirely on free OpenJDK distributions — Eclipse Temurin, Amazon Corretto, Azul Zulu — owes Oracle nothing, and the calculator's number becomes irrelevant. The calculator tells you what a subscription would cost; it does not tell you that you need one.

The headcount Oracle will assert. As covered above, the definition of "employee" is contractual and broad. A calculator cannot know how many contractors and outsourced staff Oracle will fold into your count — that is a matter of evidence and negotiation.

The discount. The price list is a starting point. Real subscriptions are routinely negotiated below list, and the discount depends on volume, term length, timing in Oracle's quarter, and how credible your alternative is. The calculator shows list; your contract may not.

Legacy metric exposure. Organisations that bought the old Java SE Subscription before 2023 may still be on Named User Plus or Processor metrics. Those contracts price completely differently, and a calculator built for the employee metric does not model them. If you are on a legacy agreement, the renewal — when Oracle will push you onto the employee metric — is the moment that matters, and our 12-month renewal plan covers how to prepare for it.

How to make the number smaller

The calculator produces a list figure. There are exactly three levers that move it, and they are worth understanding in order of impact.

• Eliminate the requirement. The largest lever by far. If you migrate off Oracle's JDK to a free OpenJDK distribution, the employee metric stops applying and the calculator's number goes to zero. This is not a discount — it is removing the cost entirely. For most enterprises facing a six- or seven-figure figure, a planned migration is the rational response, and it is why so many calculator results end with a migration business case.
• Right-size the count. If you genuinely need an Oracle subscription, make sure the headcount is accurate and defensible. Do not let Oracle assert a contractor or outsourcer population larger than reality. Evidence-based headcount work routinely removes a meaningful slice of the bill.
• Negotiate the rate and term. List price is negotiable. A credible migration alternative, multi-year commitment, and good timing all move the discount. The single biggest factor in a strong Java negotiation is a real, demonstrated willingness to walk away — which only exists if you have done the migration analysis.

Across more than 340 Java licensing engagements, the pattern is consistent: the calculator's list number is the start of the conversation, not the end. Through migration, accurate counting and disciplined negotiation, that figure has been reduced by an average of 68% on audit claims, contributing to more than $180M in total client savings. The calculator tells you the size of the problem; the savings come from what you do next.

Frequently asked questions

This article is general information on Oracle Java licensing, not legal or financial advice. Oracle's price list, tier structure and the contractual definition of "employee" are determined by Oracle and change over time. Consult a qualified independent Java licensing specialist before relying on any estimate.