Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Oracle’s January 2023 move to an employee-based Java subscription gave many businesses a reason to reassess Oracle Java and consider OpenJDK distributions. The shift appears to have accelerated migration, but claims of “mass migration” rely largely on surveys from a commercial competitor—not a census of Java installations. And Java itself did not become proprietary: the cost and licensing change concerns Oracle’s commercial offering, while open-source Java builds remain available.
What Oracle changed in 2023
On January 23, 2023, Oracle introduced Java SE Universal Subscription, replacing its previous Java SE and Java SE Desktop Subscription models. Earlier licensing could involve processor, named-user, or desktop metrics and separate server and desktop entitlements. The new subscription uses an employee-based metric and is designed to cover Java use across desktops, servers, virtualized and containerized environments, and cloud deployments. Oracle presents the model as simpler because customers need not count each Java installation, processor, or container. The trade-off is that the charge can reflect workforce size rather than actual Java use. Oracle’s subscription FAQ and product page describe the change.
The employee count can be broader than an organization’s payroll headcount. Oracle’s published price-list definition includes full-time, part-time, and temporary employees, as well as employees of agents, contractors, outsourcers, and consultants supporting the customer’s internal business operations. The applicable contract and price-list terms matter; organizations should confirm their own metric with Oracle rather than assume that only direct employees count. Oracle’s price list provides the definition and tier details.
Why the price can feel disconnected from usage
Oracle’s FAQ lists a U.S. starting price of $15 per employee per month. Its published price list gives volume tiers, including $6.75 per employee per month for organizations in the 20,000–29,999 employee tier and $5.25 for the 30,000–39,999 tier. These are listed rates, not a promise of a particular customer’s contract price; geography, customer status, contract terms, and the relevant price-list edition can affect what applies.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Oracle’s price-list example for a 28,000-employee organization calculates $2,268,000 annually: 28,000 employees multiplied by $6.75 per month, then by 12. That is Oracle’s illustrative calculation, not an average bill or a prediction for every customer. It shows why the model can be difficult for an enterprise with a large workforce but relatively few Oracle Java installations. The price-list PDF contains the example.
Some migration material from Azul, a company that sells competing Java products and support, reports Oracle Java price increases of 300%–400%. Treat those as vendor-reported estimates, not independently established industry averages. A company’s actual comparison depends on its prior entitlements, workforce metric, contract, support needs, and migration costs. Azul’s migration material makes the estimates.
Rank #2
How strong is the evidence of migration?
The evidence supports a substantial migration trend, not a precise count of how many organizations—or Java installations—have left Oracle. Oracle’s licensing documents establish the change, and the presence of multiple OpenJDK distributions shows that alternatives are available. But the headline migration percentages come from surveys by Azul, a commercial competitor, and should not be treated as global market-share measurements.
- Azul’s 2024 survey announcement says 86% of respondents were migrating away from Oracle Java in whole or in part; it also reports that 47% preferred an open-source distribution such as OpenJDK. Those figures describe survey responses, not the share of all Java users or completed enterprise migrations. Azul’s announcement is the source.
- Azul’s 2026 migration material says 81% had migrated, were migrating, or planned to migrate to an open-source alternative. The wording combines completed moves with current work and future intent, so it does not mean 81% had finished. Azul’s migration material is the source.
These results are evidence of pressure and interest, particularly around cost predictability and audit concerns. They do not establish that Oracle lost 86% of its customers, that 86% of Java installations switched, or that every respondent completed a move. The survey figures should be read as vendor-sponsored indications of direction, not a census.
Java did not simply become paid
“Oracle made Java paid” is too broad. OpenJDK is open-source software, primarily licensed under GPLv2 with the Classpath Exception. Oracle publishes OpenJDK builds under GPL terms, while Oracle JDK is a branded binary distribution whose terms vary by release. Java SE Universal Subscription is Oracle’s commercial licensing and support offering, including enterprise services and long-term update options. Oracle says the subscription does not change use permitted under the applicable gratis terms for OpenJDK or Oracle JDK; users still need to check the license for the specific version and use. Oracle’s FAQ explains its position.
A free-to-download runtime is not the same as free enterprise support. A business may still pay for security maintenance over a required lifecycle, contractual support, older-version coverage, certified binaries, indemnification, compliance assistance, or performance engineering. The practical comparison is often Oracle’s commercial service against a self-supported OpenJDK build—or a paid OpenJDK provider—not simply a paid download against a free one.
OpenJDK alternatives: compare the operating model
These options are not interchangeable support contracts. Free binary availability does not establish a particular update window, platform matrix, service commitment, or legacy-version policy. Check each provider’s current terms and application-vendor certifications before standardizing.
Rank #4
| Distribution | What it may suit | What to verify |
|---|---|---|
| Eclipse Temurin | Organizations seeking a widely used, community-oriented OpenJDK build. Governance is through the Eclipse Adoptium project. | The free distribution is not itself a bundled enterprise support contract. If the business needs escalation or legacy coverage, identify the support provider and its terms. See also this governance and licensing overview. |
| Amazon Corretto | A potential fit for AWS-centered environments seeking an OpenJDK distribution aligned with that ecosystem. | Confirm supported operating systems, architectures, lifecycle, and application certification for workloads outside AWS as well as within it. |
| Microsoft Build of OpenJDK | A potential fit for Microsoft-oriented development and Azure environments. | Check platform coverage, lifecycle policy, update cadence, and whether existing support agreements apply to the intended use. |
| Red Hat build of OpenJDK | Organizations already using Red Hat Enterprise Linux or middleware that value integrated support and lifecycle governance. | Verify the current version matrix and subscription terms; the fit may be weaker without Red Hat infrastructure or support. |
| Azul Platform Core / Zulu | Businesses seeking commercial OpenJDK support, migration help, older-version coverage, or performance expertise. | This is a commercial alternative, not equivalent to adopting a community build without a support contract. Compare its terms and costs with Oracle’s and other providers’ offerings. |
BellSoft Liberica, IBM Semeru, and SAPMachine are other distributions an organization may assess. A useful comparison includes governance, supported Java versions, update cadence, operating-system and CPU coverage, contractual support, security response, indemnification, and total cost—not only the download price.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteWhat a responsible migration involves
A runtime swap can be small for an application that relies on standard Java SE APIs and is supported on the target distribution. It is not safe to assume that matching major-version numbers guarantee identical behavior. Oracle’s migration documentation warns that Java releases can introduce binary, source, and behavioral incompatibilities. Reliance on internal APIs, unsupported reflection, removed modules, vendor-specific behavior, or proprietary commercial features raises the risk. See the Oracle JDK 24 Migration Guide and Oracle’s guidance for moving from JDK 8 to later releases.
Best Value
- Inventory the estate. Find Java installations on employee devices, servers, build agents, containers, and appliances. Record vendor, version, architecture, install path, and update channel. Inspect application installers, container images, artifact repositories, CI runners, and Helm charts; package inventories alone can miss bundled runtimes.
- Map dependencies and ownership. Identify application-vendor certification requirements and determine who is responsible for the runtime in appliances or bundled products. Check for JavaFX, Web Start remnants, JNI libraries, JVMCI, JFR/JMC workflows, proprietary security providers, and commercial Java 8 features.
- Select a distribution and support model. Match the choice to required versions, lifecycle, platforms, patch responsibility, response commitments, and procurement requirements. Decide whether the team can self-support or needs a vendor contract.
- Build and test representative environments. Replace the runtime in developer, CI, test, staging, and production images. Run unit, integration, regression, load, security, and startup tests. Specifically review TLS and cryptographic providers, fonts, time-zone data, garbage-collector behavior, native libraries, container memory detection, and monitoring integrations.
- Roll out with a rollback path. Pin the vendor and major version, manage updates centrally, and retain prior runtime images until production validation is complete. Check that installers and third-party software do not silently reinstall Oracle JDK.
- Close the compliance loop. Preserve license notices and distribution records, document patch ownership, confirm unclear vendor support requirements in writing, and remove unmanaged Oracle binaries from software repositories where appropriate.
Where migrations are most likely to go wrong
Older Java 8 applications
Java 8 estates may rely on internal sun.* APIs, illegal reflective access, removed modules, Web Start, applets, legacy browser integration, proprietary deployment tools, commercial Java 8 features, or abandoned libraries. Oracle says Java 8 was the last major release targeting browser deployment through Web Start and recommends modern packaging that bundles the runtime with the application. That makes Java 8 a dependency and lifecycle assessment, not just a binary replacement. Oracle’s FAQ discusses the Web Start boundary.
Vendor certification and bundled runtimes
A successful test in a staging environment does not override a software vendor’s support matrix. An appliance may embed a runtime, and the appliance vendor—not the customer—may control its update or entitlement. Confirm responsibility and certification before changing that runtime.
Containers and unmanaged environments
Container images can preserve Oracle binaries even after virtual machines have been cleaned up. Include development-only images, disaster-recovery environments, build runners, and third-party images in the inventory. Also check whether a runtime is installed by an upstream base image rather than by an obvious package install.
Free tools Windows power users keep installed
One-click scans. No signup required.
Patch ownership and lifecycle
A community build can meet a workload’s needs while it is actively maintained, but a download being free does not promise indefinite security updates, contractual escalation, or coverage for a legacy version. Assign an owner for monitoring releases and deploying fixes, or purchase a support arrangement that provides the required coverage.
Stay with Oracle, switch, or use both?
| Approach | When it can make sense | Key condition |
|---|---|---|
| Stay with Oracle | The estate depends on Oracle-only commercial features or Oracle products; Oracle support is valuable; migration or recertification risk is high; or the subscription cost is acceptable for the organization. | Confirm the applicable contract and entitlements. Oracle says Java used with an Oracle product may continue to receive support and updates under the relevant arrangement; that does not establish a blanket exception for every customer or deployment. See Oracle’s subscription documentation. |
| Use a community OpenJDK build | Applications use standard Java APIs, the target version is maintained, application vendors support the runtime, and the organization can manage patching and incidents internally. | Make sure internal expertise and security-response capacity are sufficient. |
| Buy commercial OpenJDK support | Workloads require contractual support, older-version maintenance, migration assistance, performance help, or stronger procurement assurances. | Compare lifecycle, support response, platform coverage, certification, indemnification, and total cost—not just binary fees. |
| Use a hybrid estate | Some applications have Oracle dependencies while others are suitable for an OpenJDK distribution. | Maintain a clear inventory, runtime standard, exception process, and patch owner for each workload. |
The best financial comparison includes more than subscription rates: migration labor, application testing, vendor recertification, support contracts, internal patching, fleet management, training, and compliance work all affect total cost. For a large workforce with limited Java use, the employee metric can make Oracle’s model less attractive. For a critical Oracle-dependent workload, keeping Oracle may cost less than absorbing the risk and expense of moving it.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
