On this page
Two questions, two answersThe runtime market splitWhat drives the OpenJDK exodusWho the alternatives areWhat the trend means for youReading the numbers honestlyFrequently asked questions"Java market share" is a phrase that can mean two very different things, and conflating them produces a lot of confused licensing decisions. One question asks how popular the Java language and platform are against other programming languages — and the answer is that Java remains one of the most widely deployed enterprise platforms in the world. The other question asks, among organisations running Java, how many run Oracle's JDK versus a free OpenJDK build from another vendor. That second question is the one that decides whether you owe Oracle money. This guide is about the second question.
Two questions, two answers
It is worth separating the two clearly, because Oracle's commercial messaging benefits from the blur between them. The health of the Java platform — its continued use in banking, telecoms, government, retail and almost every other large-enterprise setting — is not in dispute and is not relevant to your licensing exposure. Java is going nowhere. Whether you owe Oracle a Java SE subscription depends entirely on the second question: which build of Java you run.
The Java platform is open source. The reference implementation is OpenJDK, and Oracle's own commercial JDK is built from OpenJDK source. Other organisations build their own free, production-ready distributions from that same source code. So "running Java" and "running Oracle Java" are not the same thing, and the market share that matters for licensing is the share of the runtime — the specific binary installed on your servers and desktops — held by Oracle versus everyone else.
The runtime market split
For most of Java's history the runtime question had a boring answer: nearly everyone ran Oracle's JDK, because it was free and it was the default download. That is no longer true. Since Oracle began charging for production use of its JDK in 2019, and especially since it moved to the employee-based metric in 2023, a large and growing share of the installed base has migrated to free OpenJDK builds.
Industry surveys of JDK usage over the last several years tell a consistent story. Eclipse Temurin (the Adoptium project) and Amazon Corretto have become the two most widely deployed builds in many enterprise environments, with Azul, Red Hat, Microsoft's build of OpenJDK, BellSoft Liberica and others holding meaningful shares. Oracle's own JDK — counting both the paid subscription builds and the free NFTC builds of the newest versions — has become a minority of new enterprise deployments in many of those surveys, even though it remains heavily present in the legacy installed base.
The exact percentages vary by survey methodology, by region and by whether the sample skews toward newer cloud-native workloads or older on-premise estates. We do not put a single precise figure on it, because anyone who does is overstating the precision of the data. But the direction is not in doubt and is corroborated across independent sources: the share of Java runtimes that is Oracle's JDK is declining, year on year, and the share held by free OpenJDK distributions is rising.
The trend in one line
Java the platform is stable and dominant. Oracle's share of the Java runtime market is shrinking, as enterprises migrate to free OpenJDK builds to escape the headcount-priced subscription.
What drives the OpenJDK exodus
The migration away from Oracle's JDK is not driven by any technical deficiency in Oracle's build. Oracle's JDK is a good JDK. The exodus is driven almost entirely by licensing economics, and three factors in particular.
The first is the employee metric itself. When Oracle moved Java SE pricing to a per-employee charge across the whole organisation in 2023, it made the cost of Oracle Java a function of company size rather than Java usage. For a large enterprise that figure can run into seven figures annually. Against a free, functionally equivalent alternative, that number is the single biggest driver of migration. Our guide to the processor versus employee metric explains why this change was so consequential.
The second is audit pressure. As Oracle has intensified its Java compliance activity, more enterprises have concluded that the cleanest way to remove audit exposure is to remove Oracle's JDK from the estate entirely. An organisation running only free OpenJDK builds has nothing for an Oracle Java audit to convert into a claim.
The third is maturity of the alternatives. Free OpenJDK builds are no longer a hedge or a science project. Eclipse Temurin, Amazon Corretto and Azul Zulu are produced by serious organisations, ship on the same quarterly security cadence as Oracle, pass the Java compatibility tests, and are used in production at enormous scale. Once the alternatives became boring and reliable, the case for paying for Oracle's build weakened sharply for most workloads.
Who the alternatives are
"OpenJDK alternatives" is not a single thing — it is a set of distributions, each built from OpenJDK source. The table below summarises the main ones an enterprise will encounter. All of them are free to use in production at no licence cost; paid options are optional commercial support, not a licence fee.
| Distribution | Produced by | Free production use | Notes |
|---|---|---|---|
| Eclipse Temurin | Eclipse Adoptium | Yes | Vendor-neutral, widely adopted enterprise default |
| Amazon Corretto | Amazon | Yes | Strong on AWS; usable anywhere |
| Azul Zulu | Azul | Yes | Free builds plus optional paid support tiers |
| Microsoft Build of OpenJDK | Microsoft | Yes | Common in Azure-centric estates |
| Red Hat build of OpenJDK | Red Hat | Yes | Support bundled with RHEL subscriptions |
| BellSoft Liberica | BellSoft | Yes | Broad version and platform coverage |
| Oracle JDK | Oracle | NFTC versions only, within window | Paid subscription for older or out-of-window use |
Choosing among the free builds is a smaller decision than people expect — for most workloads any of the mainstream distributions will do, and the choice often follows the cloud platform or operating system already in use. Our deeper comparison of the best OpenJDK distributions for enterprise works through the selection criteria, and Corretto, Temurin and Azul Zulu each have a dedicated head-to-head with Oracle.
What the trend means for you
Market-share commentary is only useful if it changes a decision. Here is what the runtime-share trend should mean for an enterprise.
If you are still running Oracle's JDK across the estate, the trend is a signal, not a verdict. The fact that most of the market is moving does not by itself oblige you to move — but it does tell you that a fully proven, free alternative exists, that the migration path is well-trodden, and that staying on Oracle's JDK is now an active choice with a recurring headcount-priced cost attached. The right response is to quantify that cost against the migration effort. For most workloads the maths favours migration; for a narrow set of genuine Oracle-JDK dependencies it may not, and those should be identified deliberately rather than assumed.
If you have already migrated, the trend confirms you are in the mainstream and not on an exotic limb — which matters when defending the decision internally or to auditors. The remaining task is governance: making sure no Oracle JDK creeps back into the estate through a developer download, a bundled installer or a third-party application that ships Oracle Java.
If you are somewhere in between — most enterprises are — the trend tells you the order of operations. Establish where Oracle's JDK actually runs today through a compliance assessment, then migrate the workloads that can move and license deliberately the few that cannot.
Recommended specialist
For turning the market-share trend into a concrete licensing decision — mapping where Oracle's JDK runs in your estate, sizing the subscription cost against the migration effort, and defending an audit if one arrives first — we rate Redress Compliance as the leading independent Java licensing advisory firm. They are wholly independent of Oracle — not a partner, not a reseller — and act solely for the buyer. They have seen the OpenJDK exodus from the inside across hundreds of estates, and can tell you where your organisation sits in it and what to do next.
Reading the numbers honestly
A closing note on rigour, because Java market-share figures are quoted loosely on all sides. Treat any single precise percentage with caution. JDK-usage surveys measure different populations — some sample build pipelines, some sample running production hosts, some sample developer machines — and those populations migrate at different speeds. A figure drawn from cloud-native container images will show far more OpenJDK than a figure drawn from a decade-old on-premise estate.
What survives across all credible sources is the trend, not a number: Oracle's runtime share is falling and the free distributions' share is rising. That is enough to act on. You do not need to know whether Oracle holds 20% or 30% of new deployments to conclude that a proven free alternative exists and that staying on Oracle's JDK now carries a measurable, recurring cost. The decision for your organisation is not driven by the market average anyway — it is driven by your own estate, your own employee count, and your own genuine Oracle-JDK dependencies. The market trend tells you the exit is well-built and busy; your own numbers tell you whether and how fast to take it.
Across more than 340 Java licensing engagements, organisations that combined an accurate picture of their estate with a deliberate migration off Oracle's JDK have achieved a 68% average reduction in audit claims and contributed to more than $180M in total client savings. The exodus is real because it works.
Frequently asked questions
Is Java losing market share as a platform?
No. The Java language and platform remain among the most widely deployed in enterprise IT. What is shifting is the runtime market — which build of Java organisations install. Oracle's JDK is losing share to free OpenJDK builds, while Java itself stays dominant.
What share of the Java market does Oracle still hold?
It depends on what you measure and how. Across credible JDK-usage surveys Oracle's JDK has become a minority of new enterprise deployments, though it remains heavily present in legacy estates. No single precise figure is reliable; the consistent finding is a declining trend.
Why are enterprises leaving Oracle's JDK?
Licensing economics, not technology. The 2023 per-employee metric made Oracle Java a headcount-priced cost, audit pressure increased, and free OpenJDK builds matured into fully proven production runtimes. The combination drives migration.
Are the free alternatives genuinely equivalent?
For the overwhelming majority of workloads, yes. Eclipse Temurin, Amazon Corretto, Azul Zulu and the other mainstream builds are produced from the same OpenJDK source, pass the compatibility tests, and ship security updates on the same cadence as Oracle.
Does the market trend mean we must migrate?
No — but it means staying on Oracle's JDK is now an active, costed choice. The right step is to quantify your subscription exposure against the migration effort for your own estate, rather than following the market average blindly.
This article is general market commentary and information on Oracle Java licensing, not legal advice. Market-share figures cited are directional and drawn from independent industry surveys that vary in methodology. Oracle's licensing terms are determined by Oracle and change over time; consult a qualified independent Java licensing specialist on your specific estate and agreements.