This is the complete Oracle Java SE Universal Subscription tier ladder, from $15.00 per employee per month down to $5.25, with Oracle's own 28,000-employee example that lands at $2,268,000 per year. We show the math for six headcount bands and name where the meter, the escalator, and the floor cost you money.
This is the complete Oracle Java SE Universal Subscription tier ladder, from $15.00 per employee per month down to $5.25, with Oracle's own 28,000-employee example that lands at $2,268,000 per year. We show the math for six headcount bands and name where the meter, the escalator, and the floor cost you money.
Oracle Java SE Universal Subscription prices on one metric only: the employee count. There is no per-install, per-core, or per-user option for new subscriptions. Oracle retired Named User Plus and Processor metrics for Java on 23 January 2023, so the table below is the only pricing structure you will be quoted from in 2026. The rate is published monthly, but contracts bill annually. To get your yearly list cost you multiply the monthly per-employee rate by twelve, then by your total employee count as Oracle defines it.
| Tier | Employee band | List price (USD per employee/month) | Annual list per employee (x12) |
|---|---|---|---|
| 1 | 1 to 999 | $15.00 | $180.00 |
| 2 | 1,000 to 2,999 | $12.00 | $144.00 |
| 3 | 3,000 to 9,999 | $10.50 | $126.00 |
| 4 | 10,000 to 19,999 | $8.25 | $99.00 |
| 5 | 20,000 to 49,999 | $6.75 | $81.00 |
| 6 | 50,000 and above | $5.25 (negotiable) | $63.00 |
Two clarifications on the bottom of the ladder. Oracle's own FAQ states that published tier pricing goes "as low as $5.25 per month and can be even lower for customers with more than 50k employees." Some third-party sources place the $5.25 floor beginning around 40,000 to 50,000 employees rather than strictly at 50,000. In our negotiating experience the difference is academic for buyers under 40,000, because those bands almost never reach $5.25 at list. Confirm the exact band breakpoints against the order document Oracle sends you, because the tier boundary is where a single extra headcount can move you up or down a whole rate.
The bill is driven by the number of employees you have, not the number of employees who touch Java. That is the entire pricing story.
Oracle publishes this exact calculation in its Global Price List, so it is not a Redress estimate. A company with a total employee count of 28,000 (23,000 full-time, part-time, and temporary staff, plus 5,000 agents, contractors, and consultants) falls in the 20,000 to 49,999 band at $6.75 per employee per month. The arithmetic Oracle prints is: 28,000 x $6.75 x 12 = $2,268,000 per year.
Read that example carefully, because it embeds two rules buyers routinely miss. First, the 5,000 contractors and consultants are counted as employees. If they support your internal business operations, they are in the number whether or not any of them run Java. Second, the 28,000 is a total, not a Java-user total. Oracle's contract language is explicit: the licensed quantity "must, at a minimum, be equal to the number of Employees as of the effective date of Your order." Usage is irrelevant to the count. For the full treatment of who lands in that number, see whether contractors and consultants count toward your Java employee total.
Below are list-price calculations at representative headcounts so you can locate your own organization on the ladder. These are annual figures before any discount and before the 8% escalator (covered later).
| Employees | Tier rate | Calculation | Annual list cost |
|---|---|---|---|
| 1,500 | $12.00 | 1,500 x $12 x 12 | $216,000 |
| 5,000 | $10.50 | 5,000 x $10.50 x 12 | $630,000 |
| 8,000 | $10.50 | 8,000 x $10.50 x 12 | $1,008,000 |
| 20,000 | $6.75 | 20,000 x $6.75 x 12 | $1,620,000 |
| 28,000 | $6.75 | 28,000 x $6.75 x 12 | $2,268,000 |
| 45,000 | $5.25 | 45,000 x $5.25 x 12 | $2,835,000 |
The 8,000-employee row is the trap illustrated most starkly. If only 500 of those 8,000 people actually use Java, you are still paying roughly $1,008,000 per year for the lawful right for 500 people to run it. That is an overspend factor of about twenty times relative to real usage. This is not a defect in your negotiation; it is the design of the metric. The only ways to bend it are to reduce the counted headcount, to discount the rate, or to leave the fee entirely. We cover the first two below, and the exit in which Java versions are free and which trigger a bill.
If your organization sits at the low-user, high-headcount end of this spectrum, the dedicated analysis in only 50 developers use Java, why are you licensing 10,000 employees quantifies the gap in more detail.
Oracle's definition of "Employee for Java SE Universal Subscription" is broad by construction. It includes: (i) all of your full-time, part-time, and temporary employees; and (ii) all of the full-time, part-time, and temporary employees of your agents, contractors, outsourcers, and consultants that support your internal business operations. There is no carve-out for staff who never run Java. There is no carve-out for retail, warehouse, or field workers who have never opened a JDK.
Every full-time-equivalent that supports your internal operations is a line in Oracle's total, whether they have ever run a Java program or not.
Because the count drives everything, the single highest-leverage negotiation move is scoping the count accurately and defensibly. Over-broad self-reporting is the most common way buyers overpay at signing. The full mechanics live in the pillar page, the Oracle Java Universal Subscription employee metric, fully decoded.
The tier table is only the starting number. Three contract mechanisms raise the real cost over a term, and each is negotiable if you catch it before signature.
Oracle applies an 8% annual increase to Java subscription and support fees, compounding year over year. That is not the 3% to 4% many procurement teams assume. On a $2,268,000 starting cost, an uncapped 8% escalator produces roughly $2,449,000 in year two, $2,645,000 in year three, and about $3,086,000 by year five. Over a five-year horizon the escalator alone adds well over a million dollars to the 28,000-employee example. Insist on a fixed rate for the full term or a cap materially below 8%.
Some Oracle order documents carry a minimum annual subscription of $50,000 or $100,000 regardless of headcount. A customer that reduces headcount below the floor still pays the floor. If you expect to shrink, or if you are a small organization near the bottom of Tier 1, read the order document for a stated minimum before you sign.
Oracle requires a headcount true-up at each anniversary. Grow the count and you pay the higher total, potentially at a higher tier. Shrink the count and you capture no refund within the term. The mechanism is asymmetric by design. Model your growth honestly, because a headcount projection that crosses a tier boundary can change your rate for the whole population, not just the incremental heads. The forecasting exercise is worked through in how much your Java bill will increase under the Universal Subscription.
The table is list price. Discounts are routinely available, and the size scales with your headcount and your willingness to walk. In our negotiating experience, discount bands of 15% to 30% are routine on mid-sized deals, and at large scale (20,000-plus employees) structured negotiation reaches 50% to 60%. On the 28,000-employee example, a 50% to 60% discount would bring the annual cost from $2,268,000 down to roughly $907,000 to $1,134,000. The largest single lever is the counted headcount; the second is a credible alternative to signing at all. Both are detailed in negotiating down the Java employee count, tier, and term.
The reason Oracle can hold list on unprepared buyers is the audit backdrop. In 2026 the soft outreach has given way to formal audit notices issued under Global Licensing and Advisory Services (GLAS), the function formerly branded LMS. Where non-compliance is found, back-fee exposure typically extends three years into the past, and Oracle prices the settlement on your full current headcount, not on the handful of machines it detected. This is why an unmanaged Java estate is dangerous even if you believe your paid users are few. The defensive playbook is in our Oracle Java audit defence guidance.
Oracle prices the audit settlement on your entire headcount today, not on the machines its telemetry happened to see.
For a large share of organizations, the correct outcome is not a better tier or a bigger discount. It is a migration to a free, production-grade OpenJDK distribution (for example Eclipse Temurin, Amazon Corretto, or Microsoft Build of OpenJDK), which eliminates the per-employee fee entirely. The subscription buys you Oracle's specific binaries and support, not the Java language. If you can move your runtime estate off Oracle's JDK and prove it, the whole tier table stops applying to you. Before you renew, benchmark the fully loaded five-year subscription cost (rate x headcount x 12, compounded at the escalator) against a one-time migration project. In most estates we review, the migration pays back inside the first year. If any pre-2023 entitlements exist, check whether your legacy perpetual and NUP Java licenses are still valid before you assume you owe anything at all.
The tier table is fixed and public. Your leverage sits in three places you control: the number you report, the discount you extract, and your credible ability to walk to OpenJDK. Treat the $15 to $5.25 ladder as the opening position, never the settlement.
List pricing runs in six bands: $15.00 per employee/month for 1 to 999 employees, $12.00 for 1,000 to 2,999, $10.50 for 3,000 to 9,999, $8.25 for 10,000 to 19,999, $6.75 for 20,000 to 49,999, and $5.25 (negotiable) for 50,000 and above. All rates are list price and bill annually at twelve times the monthly rate.
Oracle's own price list gives a company with 28,000 total employees (23,000 staff plus 5,000 contractors and consultants) the 20,000 to 49,999 band rate of $6.75. The math is 28,000 x $6.75 x 12 = $2,268,000 per year. Note that the 5,000 contractors are counted and that usage is irrelevant to the total.
Yes. Oracle counts all full-time, part-time, and temporary employees plus the equivalent staff of your agents, contractors, outsourcers, and consultants who support your internal operations. There is no discount for staff who never run Java, which is why buyers with few actual users still pay for their entire headcount.
In our experience, discount bands of 15% to 30% are routine on mid-sized deals, and structured negotiation at large scale (20,000-plus employees) reaches 50% to 60%. On the 28,000-employee example that would bring the cost from $2,268,000 down to roughly $907,000 to $1,134,000 per year.
Yes. Oracle applies an 8% annual escalator to Java subscription and support fees, compounding year over year, not the 3% to 4% many teams assume. Over five years this adds well over a million dollars to a large deal. Negotiate a fixed rate for the term or a cap materially below 8%.
Often, yes. Migrating to a free OpenJDK distribution such as Eclipse Temurin, Amazon Corretto, or Microsoft Build of OpenJDK eliminates the per-employee fee, because the subscription buys Oracle's binaries and support, not the Java language. In most estates we review, a migration pays back inside the first year against the subscription cost.
Oracle now audits Java SE on employee count, not installs, which can multiply the bill several times over. How to defend the notice and exit to OpenJDK.
Gated with a work email on the download page. No sales follow up you did not ask for.
Get the White Paper →
500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay for the next three years.
One buyer side briefing a week. Renewal signals, audit moves, and the levers that work. No vendor spin.
