Oracle Java SE now prices per employee, not per user, which turns a modest Java footprint into a seven-figure bill. We assess your real exposure, defend the audit, and move you to a supported OpenJDK build that costs nothing in license fees.
Replacing Oracle Java SE Universal Subscription with a supported OpenJDK build removes 100 percent of the per-employee fee, an average of $1.3M a year for a 15,000-person organization. Oracle changed the Java metric in January 2023 from per user and per processor to per employee, where every worker in the company counts whether or not they touch Java. A few dozen servers running Java can produce a bill sized to your entire headcount.
Two problems usually arrive together: an audit claim built on the broadest reading of employee, and a renewal quote that assumes you have no alternative. We treat both as the same engagement. We measure where Java actually runs, separate Oracle JDK from already-free OpenJDK builds, and scope a migration for the workloads that can move. For the workloads that genuinely need Oracle Java, we negotiate the count down to a defensible number rather than your full payroll.
This advisory pairs with our Oracle audit defense when LMS has made contact, and draws on the analysis in our Oracle Java licensing pillar and the cost data in the complete Oracle licensing guide.
Oracle Java SE Universal Subscription is tiered by total employee count and billed per employee per month. The annual figures below assume the organization sits at the lower edge of each band.
| Employee band | Per employee, per month | Annual cost at band floor |
|---|---|---|
| 1 to 999 | $15.00 | up to $179,820 |
| 1,000 to 2,999 | $12.00 | $144,000 |
| 3,000 to 9,999 | $10.50 | $378,000 |
| 10,000 to 19,999 | $8.25 | $990,000 |
| 20,000 to 29,999 | $6.75 | $1,620,000 |
| 30,000 to 49,999 | $5.25 to $5.70 | $1,890,000+ |
| 50,000+ | Negotiated | Bespoke |
The definition is the whole game: Oracle counts every employee and many contractors, not Java users. A 15,000-person firm with Java on 60 servers pays the same $990,000 a year as one running Java everywhere. Reducing that bill is rarely about deployment, it is about removing the dependency or disputing the count.
| Organization size | Oracle Java annual fee | Typical migration cost | Year-one net saving |
|---|---|---|---|
| 3,000 employees | $378,000 | $40,000 to $80,000 | $300,000+ |
| 15,000 employees | $990,000 | $90,000 to $160,000 | $830,000+ |
| 25,000 employees | $2,025,000 | $140,000 to $260,000 | $1.78M+ |
We inventory every JDK in the estate, separate Oracle builds from free OpenJDK already in use, and size true exposure before Oracle frames it for you.
Java Licensing Pillar →We scope a move to a supported OpenJDK distribution for eligible workloads, with a rollout and support plan that removes the per-employee fee entirely.
Java 2026 Update →When an audit is live, we control the data, dispute the employee count, and settle the back-bill at actual use rather than headcount.
Audit Defense →Oracle issued a Java audit claim to a 22,000-employee insurer based on the full per-employee count, opening at roughly $2.0M a year. We inventoried the estate and found Oracle JDK on 90 servers, most of which already had free OpenJDK candidates. We disputed the employee definition, paused data sharing, and scoped a 16-week migration to Eclipse Temurin for the eligible systems.
The settlement closed the historical claim with no go-forward subscription, replaced by OpenJDK at zero license cost and a third-party support contract for the two systems that needed assurance. Net annual saving was $2.0M against a migration cost under $200,000.
No. Since January 2023 most commercial use of Oracle Java SE requires the Java SE Universal Subscription, which prices per employee across the whole organization rather than per Java user. Free production-grade alternatives exist, including Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, and Azul Zulu.
Oracle defines employee to include full-time, part-time, temporary, and contract staff, plus the workers of contractors and outsourcers who support internal operations, whether or not any of them use Java. This is why the per-employee bill so often dwarfs actual Java deployment.
Yes. Oracle uses download records, support tickets, and telemetry to identify Java usage and routinely issues per-employee back-bills. We assess true deployment, dispute the count, and reduce the claim to actual use before negotiating a settlement or a migration.
Replacing Oracle Java SE Universal Subscription with a supported OpenJDK build removes 100 percent of the per-employee fee, an average of $1.3M a year for a 15,000-person organization. Migration cost is usually a small fraction of one year of subscription.
Once the decision to leave Oracle Java is made, the next question is which free distribution to standardize on. All of the major builds compile from the same OpenJDK source and pass the same Java compatibility tests, so application behavior is consistent. The difference is the support model, the release cadence, and the long-term-support window each vendor commits to. The choice should follow your operational needs, not marketing.
Amazon Corretto is a strong default for AWS-centric estates and ships long-term-support builds with quarterly security updates at no cost. Eclipse Temurin, from the Adoptium project, is the vendor-neutral choice and the one we most often recommend for mixed environments. Microsoft Build of OpenJDK suits Azure and Windows-heavy estates. Azul Zulu and Zulu with commercial support fit organizations that want a paid support contract without Oracle's per-employee metric.
For the small set of workloads that genuinely require a commercial assurance, paid third-party Java support costs a fraction of Oracle's per-employee subscription and is priced on the systems supported rather than your headcount. The full distribution comparison and migration sequence are in our Java licensing pillar and the Oracle Java versus OpenJDK comparison.
Migration is faster than buyers expect: For most server-side workloads, moving from Oracle JDK to a supported OpenJDK build is a configuration change, not a code change. The typical enterprise migration runs 12 to 20 weeks including testing, against a subscription that bills every month it is delayed.
Weekly vendor licensing intelligence from former Oracle, Snowflake, and Databricks executives. Trusted by 3,000+ IT leaders.
Schedule a confidential Java assessment. We size your exposure and your migration path within 48 hours.