Oracle Java, the most aggressive metric change of the decade
Oracle Java SE moved from per processor and per Named User Plus to the per employee Universal Subscription in January 2023: the metric counts every employee whether or not a single one opens a Java application, and deployment size does not appear in the formula at all. A company with one hundred Java servers and ten thousand employees now pays for ten thousand employees, and the two clocks that matter, the billing metric and the license printed on each binary, do not run together.
Prepared by Redress Compliance · August 8, 2026 · Oracle advisory. Based on 35 to 45 Oracle Java engagements closed 2024 to 2025.
Executive summary
The ladder prices payroll, and the arithmetic is merciless on small estates. List runs from $15.00 per employee per month at 1 to 999 employees down to $5.25 at 40,000 to 49,999, with no published rate above 50,000: a 5,000 employee company needing Oracle Java on 40 servers pays for 5,000 employees, $630,000 a year at list, or $15,750 per server. The count reaches every full time, part time, and temporary employee plus the staff of agents, contractors, outsourcers, and consultants supporting internal operations, and pre 2023 processor and Named User Plus contracts remain valid but cannot expand to anything new.
The band cliff inverts the arithmetic at every boundary. At 9,999 employees the annual list is $1,259,874; at 10,000 it is $990,000, because the whole count reprices at the band rate, so above 7,857 defended employees the rational order is 10,000: the boundaries are negotiation facts, not rounding details. The count itself is the first argument in every engagement, and Oracle's quoted employee number ran 18 to 28 percent above what buyers could defend once temporary staff and non supporting contractors were stripped out, with signed discounts landing 22 to 41 percent off the opening quote, tracking the band more than the effort.
Eight words decide the largest dispute. The Employee definition captures contractor staff that support your internal business operations, and a contractor building a product you sell to customers is not supporting internal operations: that narrower reading carried in roughly four of five engagements where contractor counts were contested, which makes the definition, not the census, the negotiation. The opening shot in most engagements was a download log entry tied to the corporate email domain, not a renewal calendar, and enforcement peaked in the three quarters after the metric change before settling into a steady rhythm.
The exits price better than the subscription, and hybrid prices worst of all. At 12,000 employees, the OpenJDK exit models at $1,728,000 over three years against $2,102,760 to $2,779,920 for a negotiated subscription, migrations completed in nine to fourteen months at large enterprises with tooling discipline rather than code as the blocker, and hybrid, keeping some Oracle Java while migrating the rest, is the worst of the three options on cost and the one that reaches the shortlist most often. The NFTC clock ticks alongside: Oracle JDK 21 leaves the free terms in September 2026 as JDK 17 did in October 2024 at 17.0.13, and patch pipelines convert estates silently.
The metric history, and the two clocks
| Period | Metric | List rate then in force | The implication |
|---|---|---|---|
| Before 2019 | Free for commercial use under the BCL | None | Estates ran without contracts, records, or owners |
| 2019 to 2023 | Per processor and Named User Plus | $25.00 per processor, $2.50 per user, monthly | Priced on usage; contracts from this window remain valid |
| 2023 onward | The per employee Universal Subscription | $15.00 down to $5.25 by band | Priced on payroll; replaces both metrics for anything new |
The count, the cliff, and the eight words
- The definition lives in the price list, not a marketing page: every full time, part time, and temporary employee, plus agent, contractor, outsourcer, and consultant staff supporting internal business operations.
- The eight words are the dispute: a contractor building the product you sell is not supporting your internal business operations, the narrower reading that carried in four of five contested engagements.
- The quoted count is an opening position: 18 to 28 percent above the defensible number once temporary staff and non supporting contractors were stripped.
- The cliff rewards crossing it: $1,259,874 at 9,999 employees against $990,000 at 10,000, so above 7,857 defended employees, order the band.
- Restricted use and ISV embedded Java only help if they take the chargeable footprint to zero, because one chargeable install prices the whole workforce.
The Java SE employee licensing brief
The ladder, the definition arguments, the band arithmetic, and the negotiation sequence worked on a representative workforce.
Get the white paper →The exits, costed over three years
At 12,000 employees the three options price cleanly: the OpenJDK exit models at $1,728,000 over three years, migration project included; the negotiated subscription runs $2,102,760 to $2,779,920 depending on the discount landed; and hybrid, keeping Oracle Java on part of the estate while migrating the rest, is the worst of the three on cost, because the retained Oracle footprint still prices the entire workforce while the migration costs are paid anyway, and it is the option that reaches the shortlist most often because it feels safe. Migrations completed in nine to fourteen months at large enterprises with the blocker in tooling discipline on developer workstations and CI CD pipelines rather than code. The build selection and compatibility record run in the Java alternatives guide, the tier arithmetic in the worked pricing example, and the audit defense for the exit window in the Java audit defense guide.
- Percentile standing for your exact deal size and industry, from real closed transactions
- Scenario simulation before the call: test alternative terms and see the financial impact of each
- A negotiation playbook, talking points, and a two page executive brief on day one
What we saw across Java engagements, 2024 to 2025
Roughly 35 to 45 Oracle Java engagements closed through 2024 and 2025 produced the same three arguments, in the same order, almost every time:
Oracle's quoted number above the defensible one, stripped of temps and non supporting contractors.
Engagements where the narrower internal operations interpretation carried.
The third argument was what started it: in most engagements the opening shot was a download log entry tied to the corporate email domain rather than a renewal calendar, which means the defense begins with download governance and the entitlement record, not with the negotiation. The NFTC cliff schedule turns the passive estate into a converting one, JDK 17 left the free terms in October 2024 at update 17.0.13 and JDK 21 leaves in September 2026, with patch pipelines pulling the post cliff updates silently, so the estate that does not manage its Java versions is buying subscriptions one automated update at a time.
Your first five moves
- Defend the count before discussing the rate: strip temps and non supporting contractors from the 18 to 28 percent overcount.
- Run the band arithmetic at every boundary, where 10,000 employees price below 9,999.
- Read any pre 2023 contract before Oracle calls it obsolete, because usage pricing survives in it.
- Diarize the NFTC cliffs and pin the patch pipelines, the silent conversion running through September 2026.
- Cost all three exits honestly, knowing hybrid prices worst and shortlists best. The Oracle practice runs the engagement with you.
Frequently asked questions
How does Oracle Java licensing work in 2026?
Through the Java SE Universal Subscription, priced per employee across the whole organization: every full time, part time, and temporary employee plus contractor and outsourcer staff supporting internal operations, with no deployment input to the calculation at all. List runs from $15.00 per employee per month at the smallest band down to $5.25 at 40,000 to 49,999, with no published rate above 50,000.
What does Oracle Java actually cost?
Payroll times the band rate, regardless of usage: a 5,000 employee company running Oracle Java on 40 servers pays $630,000 a year at list, $15,750 per server, and a 100 server estate at the same headcount pays exactly the same. Signed discounts landed 22 to 41 percent off opening quotes in our engagements, tracking the band tier more than negotiation effort.
Who counts as an employee for Oracle Java?
The definition in the price list captures your entire workforce plus the staff of agents, contractors, outsourcers, and consultants that support your internal business operations, and those eight words are the largest dispute: a contractor building a product you sell is not supporting internal operations, the narrower reading that carried in roughly four of five contested engagements. Oracle's quoted counts ran 18 to 28 percent above the defensible number.
What is the Oracle Java band cliff?
The band boundaries reprice the whole count: at 9,999 employees the annual list is $1,259,874, at 10,000 it is $990,000, because the larger band's lower rate applies to everyone. Above 7,857 defended employees the rational order is 10,000, and the same inversion exists at every boundary, which makes the band arithmetic part of the count negotiation rather than an afterthought.
Is Oracle JDK still free?
Under the No Fee Terms and Conditions, each LTS release is free until one year after the next one ships: JDK 17 left the free terms in October 2024 at update 17.0.13, and JDK 21 leaves in September 2026. Patch pipelines convert estates silently, pulling post cliff updates under paid terms, so the unmanaged estate buys subscriptions one automated update at a time.
Should we pay for Oracle Java or migrate to OpenJDK?
Cost all three options: at 12,000 employees the OpenJDK exit modeled at $1,728,000 over three years against $2,102,760 to $2,779,920 for a negotiated subscription, with migrations completing in nine to fourteen months and tooling discipline, not code, as the blocker. Hybrid is the worst option on cost, since any retained chargeable footprint prices the whole workforce while the migration is paid for anyway, and it is the option that reaches shortlists most often.
