Oracle Java SE Renewal Exit Strategy
Oracle Java SE bills every employee in your company, not every machine that runs Java. For most estates the renewal quote is many times the real footprint, and the your side answer is exit.
Prepared by Redress Compliance · June 2026 · Representative Oracle estate scenario (benchmark scenario, not a quote)
Executive Summary
Oracle sells Java SE on one metric: the Employee for Java SE Universal Subscription. You pay for every full time, part time, and temporary employee, plus the staff of agents and contractors, whether or not they ever touch Java. The list rate runs from 15.00 dollars per employee per month down to 5.25 for very large headcounts.
That metric breaks the link between price and use. A 12,000 employee company pays for 12,000 seats even when fewer than 1,200 machines run a Java runtime. The renewal quote scales with hiring, not with the estate. Negotiating the rate rarely fixes the structural gap.
The counter move is usually to exit. Free OpenJDK builds from Eclipse Temurin, Amazon Corretto, Microsoft, and Azul deliver the same Java standard for standard workloads. A structured migration runs three to six months, and net savings commonly exceed 80 percent of the Oracle quote.
This paper covers the renewal decision, the Universal Subscription metric, the OpenJDK exit framework, the four leading distributions, audit triggers, and a worked exit scenario. Every number in the scenario is a benchmark, not a quote.
What we see across Oracle Java engagements, 2023 to 2025
Across roughly 30 to 45 Oracle Java renewals and exits Fredrik Filipsson and the Redress team benchmarked between 2023 and 2025, three patterns recur:
- The billed employee count runs 6 to 12 times the actual Java touchpoint count, so most of the bill covers seats that never start a JVM.
- OpenJDK migration completes in 3 to 6 months for standard estates, with no functional gap for the large majority of applications.
- A download log soft audit email precedes close to half of the Java engagements we are called into, well before any formal letter arrives.
How Oracle Java SE Is Priced in 2026
Oracle Java SE is priced per employee, not per user or per install. Since the January 2023 change, the only commercial metric for new clients is the Java SE Universal Subscription, billed on the Employee metric.
The definition is broad. It counts all full time, part time, and temporary employees, plus the full time, part time, and temporary staff of your agents, contractors, outsourcers, and consultants that support internal operations. Actual Java users are irrelevant to the count.
The published global price list sets volume bands that fall as headcount rises. The rate per employee drops, but the base it multiplies keeps growing.
| Employee band | List price per employee per month | List cost per employee per year |
|---|---|---|
| 1 to 999 | $15.00 | $180.00 |
| 1,000 to 2,999 | $12.00 | $144.00 |
| 3,000 to 9,999 | $10.50 | $126.00 |
| 10,000 to 19,999 | $8.25 | $99.00 |
| 20,000 to 29,999 | $6.75 | $81.00 |
| 30,000 to 39,999 | $5.70 | $68.40 |
| 40,000 to 49,999 | $5.25 | $63.00 |
List cost per employee per year by band
The rate falls with scale, from $180 a year per employee under 1,000 staff to $63 above 40,000.
Source: Oracle Java SE Universal Subscription global price list. Rates are list, before any negotiated discount.
Should You Renew Oracle Java or Exit to OpenJDK
Most enterprises should exit Oracle Java SE to a free OpenJDK build rather than renew. The employee metric charges for the whole company, so the renewal almost always dwarfs the real Java footprint, and standard workloads run on OpenJDK without a functional gap.
Renewal is the right call in a narrow set of cases. Keep Oracle where you genuinely need Oracle specific tools or support, or where a contractual obligation ties you in. The renewal framework is a test, applied before the quote lands, not after.
- Map the footprint. Count the machines that actually run a Java runtime, not the headcount Oracle will bill.
- Test the gap. Confirm whether any workload needs Oracle JDK rather than a standard OpenJDK build.
- Price both paths. Model the multi year subscription against a one time migration plus optional support.
- Time the decision. Begin before the renewal date so exit is a credible alternative at the table.
How Does the OpenJDK Exit Work
An OpenJDK exit replaces Oracle JDK binaries with a free, standards compliant build of the same Java version. OpenJDK is the open source reference implementation that Oracle JDK itself is built from, so for standard workloads the runtime behavior is the same.
The work is inventory, testing, and repackaging, not code rewrites. A structured migration runs three to six months for a typical estate. The phases below keep the project auditable and let you negotiate from a real exit position.
| Phase | When | What gets done |
|---|---|---|
| Inventory and discovery | Months 1 to 2 | Find every Oracle JDK install across servers, desktops, and build pipelines. Record version and source. |
| Distribution selection | Month 2 | Pick the OpenJDK build per workload by version coverage and support window. |
| Test and repackage | Months 2 to 5 | Validate applications on the new build. Repackage installers and update deployment images. |
| Rollout and removal | Months 4 to 6 | Deploy the OpenJDK build and remove Oracle JDK binaries. Document the removal for audit defense. |
Removal matters as much as installation. An Oracle JDK binary left on a single server can reopen the exposure the exit was meant to close. The documented removal record is the artifact that ends the conversation with Oracle.
Which OpenJDK Distribution Should You Choose
Four free distributions cover almost every enterprise estate: Eclipse Temurin, Amazon Corretto, Microsoft Build of OpenJDK, and Azul Zulu. All four ship the same Java standard. The difference is the free support window and the ecosystem fit.
Eclipse Temurin from Adoptium is the vendor neutral default, widely used and free for commercial use. Amazon Corretto is free for production with long support on AWS heavy estates.
Microsoft Build of OpenJDK carries the longest free LTS windows and aligns with Azure, per Microsoft support. Azul Zulu offers a free community build, with paid extended support and performance options through Azul Platform Core.
| Distribution | Commercial cost | Free Java 17 LTS support to | Best fit |
|---|---|---|---|
| Eclipse Temurin | Free | October 2027 | Vendor neutral default across mixed estates |
| Amazon Corretto | Free | October 2028 | AWS centric estates wanting long free support |
| Microsoft Build of OpenJDK | Free | January 2030 | Azure aligned estates wanting the longest free window |
| Azul Zulu | Free community, paid Prime | About eight years per LTS | Teams wanting optional paid support and performance builds |
For most estates the practical choice is Temurin or Corretto for breadth, or Microsoft for the longest free runway on Java 17 and Java 21. Azul earns its place where a team wants a commercial support contract without returning to Oracle.
What Triggers an Oracle Java Audit
The most common Java audit trigger is a download log entry against your corporate domain, not a renewal review. Oracle records who downloads Oracle JDK using an Oracle account or company email, with the IP address and timestamp, and uses that telemetry to build target lists.
Three signals dominate the engagements we see. Each one is visible to Oracle before any formal audit letter is issued.
- Download telemetry. Oracle JDK downloads tied to a company domain flag the organization as a likely unlicensed user.
- Lapsed subscriptions. Companies whose legacy Java subscription expired are revisited for current usage.
- Use past the free period. Running Oracle JDK builds beyond their free terms is treated as commercial use that requires a subscription.
The approach is usually a soft audit first: an email noting that Oracle records show Java downloads, inviting a discussion. That email is an audit in substance. The defense is a clean inventory and a documented OpenJDK migration record, not a reply that engages on Oracle terms.
How Much Can a Java Exit Save
Exiting Oracle Java SE typically removes the entire per employee subscription, often hundreds of thousands of dollars a year. The cost shifts to a one time migration and optional third party support, so net savings usually exceed 80 percent of the Oracle quote.
Consider Brightway Retail Group, a representative estate of 12,000 employees. The employee band sets the rate at 8.25 dollars per month. The headcount bill has almost no relationship to the real Java footprint.
| Java footprint at Brightway | Machines |
|---|---|
| Production server JVMs | 240 |
| Developer workstations with a JDK | 600 |
| Back office apps requiring a Java runtime | 350 |
| Total Java touchpoints (of 12,000 billed employees) | 1,190 |
Billed employees versus real Java footprint
Brightway pays for 12,000 employees while 1,190 machines run Java. About 90 percent of the bill covers seats that never start a JVM.
Benchmark ranges: Redress Compliance advisory engagement file, 2024 to 2025. Benchmark scenario, not a quote.
The renewal bills the full headcount. The exit pays for a migration project once, plus a modest optional support line for the workloads that want a contract. The three year comparison is decisive.
| Forward path, three years | One time | Recurring, three years | Three year total |
|---|---|---|---|
| Renew Oracle Java at list | $0 | $3,564,000 | $3,564,000 |
| Exit to OpenJDK | $180,000 | $270,000 | $450,000 |
| Three year saving from exiting | $3,114,000 |
Three year cost: renew Oracle versus exit to OpenJDK
Brightway saves about $3.11M over three years, roughly 87 percent of the Oracle renewal.
Benchmark ranges: Redress Compliance advisory engagement file, 2024 to 2025. Benchmark scenario, not a quote.
Where the Common Advice on Oracle Java Is Wrong
The standard reseller and account team pitch is that you should negotiate the Java subscription rate down, because Oracle JDK is the safe choice for security updates. We disagree, and the engagement file is the reason.
Negotiate the rate and stay on Oracle
- Treat the per employee rate as the thing to bargain.
- Assume Oracle JDK is required for timely security patches.
- Renew to avoid the perceived risk of changing runtime.
Decide whether to renew at all
- The metric, not the rate, is the cost driver. A discount on the wrong base still overpays.
- OpenJDK builds ship the same security updates for standard workloads.
- A documented exit is the only lever that actually moves the Oracle number.
In the renewals we benchmarked, a rate discount of even 30 percent left the client paying for ten times the real footprint. The structural problem is the employee metric. The counter move is to price the exit, build a real OpenJDK plan, and let that plan, not a rate request, set the negotiating floor.
Our Recommendations
Count the footprint, not the headcount
Inventory the machines that actually run a Java runtime before the renewal lands. The gap between that number and your employee count is the case for exit.
Decide renew or exit before you negotiate
Settle the structural question first. For most estates the answer is exit, and a credible exit plan is the only real leverage on the Oracle quote.
Select a distribution per workload
Use Temurin or Corretto for breadth, Microsoft for the longest free LTS window, and Azul where a paid support contract is wanted.
Remove every Oracle JDK binary
Document the removal across servers, desktops, and pipelines. The removal record is your defense against a download log claim.
Treat any Oracle email as a soft audit
Route outreach to one owner, confirm nothing about usage, and lead with your own inventory and migration record.
Talk to Us Before You Renew
Redress Compliance is a 100 percent on your side advisory firm with no vendor affiliations, serving 500+ enterprise clients with more than $2B under advisory across 11 vendor practices, including deep Oracle Java licensing and audit defense expertise.
If your Oracle Java renewal is approaching, we will map your real footprint, build the OpenJDK exit plan, and sit on your side of the table. Contact us at fredrik@redresscompliance.com or visit redresscompliance.com to book an exit review this quarter. We are glad to tie a meaningful part of the fee to delivered value.
