Oracle now prices Java SE per employee, which means the bill is driven by your headcount and not by how much Java you actually run. A disciplined OpenJDK migration shrinks the population that Oracle can charge for, removes the contract traps, and hands you the leverage at renewal. This playbook is the buyer side method we use to do it.
OpenJDK is the same Java platform that Oracle builds on, available from several free and supported distributions. Migrating the workloads that do not need Oracle Java is the single most effective way to cut the per employee bill, because it lets you negotiate the residual against a much smaller envelope.
In January 2023 Oracle moved Java SE to the Universal Subscription, priced on a per employee metric. List pricing runs from 5.25 to 15.00 dollars per employee per month, stepping down through volume bands, with small estates near the 15.00 ceiling and the largest estates near the 5.25 floor. The metric counts every full time and part time employee, every contractor, and every temporary worker, regardless of who actually touches Java. A company with twenty thousand people in the count can face a list figure near two million dollars a year for a deployment that may sit on a few hundred servers.
That structure changes the math. Under the old per processor or Named User Plus models, you controlled cost by controlling where Java ran. Under the employee metric, the only durable way to control cost is to remove the obligation to subscribe at all for most of the estate. Migration is no longer a tidy housekeeping project. It is the lever that decides what you pay.
OpenJDK runs the overwhelming majority of standard Java workloads without code changes, because Oracle Java SE and OpenJDK are built from the same source. The practical questions are about support and certification, not capability. The table below shows the pattern we see across estates. Treat the dispositions as indicative, since every estate differs.
| Workload | Typical disposition | What to check |
|---|---|---|
| Internal server side applications | Move now | Runtime version parity and test coverage |
| Containerized and cloud services | Move now | Base image swap and build pipeline |
| Standard desktop Java applications | Move now or soon | Packaging and update delivery |
| Third party software with vendor terms | Move later | Vendor certification for OpenJDK |
| Legacy apps tied to an Oracle only feature | May stay | Whether the feature is truly required |
The savings from a migration are easy to frame. Take your counted population, multiply by the indicative list rate per employee per month, and multiply by twelve. That is the figure Oracle would like to charge for the whole estate. Now picture the same calculation against only the residual you cannot move. The gap is the prize. For a deeper walk through, see our guide to estimating the savings from an OpenJDK migration.
A services firm with 12,000 in the employee count modeled an indicative list figure near 1.2 million dollars a year at a mid band rate. After migrating internal and containerized workloads and isolating a small Oracle Java residual, the defensible envelope fell sharply, and the renewal was negotiated against that smaller base. Figures are indicative and depend on deployment and contract.
There are several mature OpenJDK distributions. Some are free with community support, some add a paid support tier, and some certify against particular platforms. The right choice depends on your support appetite, your operating systems, and what your application vendors will certify. For the deeper comparison, read our overview of security updates on OpenJDK distributions and our guide to support options for OpenJDK in the enterprise.
The point of all this is not only the runtime cost. A credible migration in progress changes the conversation with Oracle. When you can show that most of the estate has already left, the opening number loses its grip, and the escalator and the true up become negotiable rather than fixed. The migration is the walk away that makes the negotiation honest.
Begin with discovery, because the estate inventory is the asset that drives every later decision. From there, triage, pick distributions, and phase the work. We can run the whole program, or sit beside your team and defend the residual at renewal. Both engagements carry our guarantee: Fixed Fee from 18,000 dollars, or Gainshare, a share of verified savings or avoided exposure, with zero retainer and no risk to the customer.
The Migration Field Guide walks through estate discovery, workload triage, distribution choice, and the residual negotiation, with a worked exposure model.
Download the field guide Book a Strategy CallFixed fee or gainshare, both backed by our guarantee. We sit between you and Oracle and we never take vendor money.
Get a QuoteWeekly intelligence on Oracle Java licensing moves and the buyer side defenses that work.