Oracle Java SE is licensed per employee at $5.25 to $15.00 per employee per month, and the count includes every worker in the organization, not only those who use Java. Since the January 2023 move to the Java SE Universal Subscription, a Java footprint of a few dozen servers can generate a bill sized to the entire payroll. This guide sets out exactly how the model works in 2026, what each tier costs, how Oracle defines an employee, where the audit risk sits, and how most organizations remove the cost entirely by moving to a supported OpenJDK build.
Inside This Guide
- How Oracle Java licensing changed
- The per-employee subscription model
- 2026 price tiers in full
- How Oracle counts employees
- Legacy versus Universal Subscription
- What the subscription covers
- Java audit risk and how Oracle finds you
- OpenJDK: the free, production-grade path
- Choosing a distribution
- Migration sequence and timeline
- If you must keep Oracle Java
- The 2026 action plan
How Oracle Java licensing changed
For most of its life Java was free to use in production. Oracle began charging for Java SE support in 2019 with the per-named-user and per-processor Java SE Subscription, which priced against the Java deployment itself. That model was already a surprise to many buyers, but it was at least proportionate to use. Then in January 2023 Oracle replaced it with the Java SE Universal Subscription and changed the metric to employees. The price no longer tracks how much Java you run. It tracks how many people you employ.
The change matters because the two models can differ by an order of magnitude for the same deployment. An organization running Java on 50 servers under the old per-processor model might have paid in the low six figures. The same organization under the per-employee model pays against its full headcount, which routinely produces a five to fifteen times increase. Oracle did not grandfather existing customers onto the old metric at renewal, so the increase arrives the first time a legacy subscription comes up for renewal.
This page is the Java sub-pillar of our complete Oracle licensing guide. For the firm-side help, see our Oracle Java licensing and audit defense page, and for the full cost reference across Oracle products, our Oracle licensing costs guide.
The per-employee subscription model
The Java SE Universal Subscription is billed per employee per month, on an annual commitment. The defining feature is that the unit of count is the employee, defined broadly, rather than the Java user or the server. A company with 15,000 employees and Java on a single application pays the same as a company with 15,000 employees running Java across every desktop and server. Deployment size is irrelevant to the bill above the point where any commercial Java is used at all.
This is the single most important fact for any buyer to absorb. Optimizing the Java deployment, consolidating servers, or reducing the number of Java applications does nothing to reduce the subscription cost, because none of those things change the employee count. The only ways to reduce the bill are to remove the Oracle Java dependency entirely or, where a genuine dependency remains, to dispute the employee count down to a defensible figure.
The core trap: Buyers instinctively try to cut a Java bill by cutting Java usage. Under the per-employee model that effort is wasted. The bill is a function of headcount, so the remediation is removal of the Oracle dependency, not optimization of the deployment.
2026 price tiers in full
Oracle publishes the Java SE Universal Subscription on a tiered, volume-declining rate card. The more employees you have, the lower the per-employee rate, but the total still rises with headcount. The table below shows the 2026 list rates and the annual cost at the floor of each band.
| Total employees | 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 39,999 | $5.70 | $2,052,000 |
| 40,000 to 49,999 | $5.25 | $2,520,000 |
| 50,000 and above | Negotiated | Bespoke |
Read the table carefully. The headline rate falls as headcount rises, which Oracle presents as a volume discount, but the annual cost climbs steeply because it multiplies the rate by the full employee count. A 25,000-employee organization sits in the $6.75 band and pays roughly $2.0M a year for Java, whether it runs Java on five servers or five thousand. The cost data for this and every other Oracle line item is maintained in our Oracle licensing costs reference.
A worked example makes the scale concrete. Take a manufacturer with 18,000 employees that runs Java on 40 application servers supporting a single line-of-business system. Under the legacy per-processor model, with those 40 servers at a 0.5 core factor, the annual Java cost sat near $120,000. Under the Universal Subscription the same company falls in the 10,000 to 19,999 band at $8.25 per employee per month, which is 18,000 multiplied by $8.25 multiplied by 12, or $1,782,000 a year. Nothing about the Java deployment changed. The metric did, and the bill rose almost fifteen times. That is the calculation every legacy customer should run before their renewal date, not after Oracle presents the quote.
The NFTC and which Java is actually free
Oracle does provide a free use route for the current Java release through the Oracle No-Fee Terms and Conditions, known as the NFTC. Under the NFTC, the latest Oracle JDK is free for commercial production use, but only for the current release and only until one year after the next long-term-support version ships. After that grace period, continued use of that version requires the paid subscription. The NFTC is therefore a moving target, not a stable free license, and it rewards organizations that upgrade aggressively while penalizing the far larger group that runs older versions in production.
This is where many buyers create accidental liability. A team downloads the current Oracle JDK believing it is permanently free, the next long-term-support release arrives, the grace period lapses, and the installed version silently moves into paid territory. Oracle download telemetry records the original download, which becomes audit evidence. The safe position is to treat any Oracle JDK in production as a future liability and to standardize on an OpenJDK build whose support terms do not expire on Oracle release schedule.
NFTC is not a free license: Free under the NFTC means free for the current version, for a limited window. Older versions, which is what most enterprises actually run, require the per-employee subscription. Treat the NFTC as a time-limited grace period, not a permanent entitlement.
How Oracle counts employees
The definition of employee in the Universal Subscription is deliberately wide. It covers all full-time, part-time, temporary, and seasonal staff, and it extends to the workers of agents, contractors, and outsourcers who support the organization internal operations. In practice Oracle reads this to mean the total human resource supporting the business, regardless of whether any individual has ever touched Java.
| Worker category | Counted? | Note |
|---|---|---|
| Full-time employees | Yes | Includes non-technical staff |
| Part-time and temporary | Yes | Counted as employees |
| Contractors and consultants | Yes, where supporting internal ops | Common dispute area |
| Outsourcer staff | Yes, where supporting your operations | Common dispute area |
| Customers and external users | No | Outside the definition |
The contractor and outsourcer language is where the count, and therefore the bill, can swing the most. Oracle audits frequently apply the broadest reading, sweeping in every contractor and outsourced worker. Whether those workers genuinely fall inside the contract definition is contestable, and disputing the count is often the largest single reduction available to an organization that has a real Java dependency it cannot immediately remove. This is core to our Oracle audit defense work.
Legacy versus Universal Subscription
Some organizations still hold legacy Java SE Subscription contracts priced per named user or per processor. Oracle has confirmed it will renew certain legacy agreements, but it steers customers toward the Universal Subscription at every opportunity, and new purchases are Universal only. The comparison below shows why the metric change is so consequential for the same deployment.
| Model | Metric | Basis of count | Typical relative cost |
|---|---|---|---|
| Legacy Java SE Subscription | Per processor / per named user | The Java deployment | Baseline |
| Java SE Universal Subscription | Per employee | Total headcount | 5x to 15x baseline |
Renewal is the trigger: The per-employee increase does not arrive on a fixed date. It arrives the first time a legacy Java subscription renews. Organizations on legacy terms should model the Universal Subscription cost well before renewal and decide whether to migrate off Oracle Java before that conversation begins.
What the subscription covers
The Universal Subscription bundles the Oracle JDK with security updates, bug fixes, and Oracle support, across both desktop and server deployments, including older Java versions that no longer receive free public updates. For organizations that run on legacy Java versions and want a single vendor accountable for patching, that bundle has value. The question is whether it is worth a fee sized to the entire payroll when free distributions provide the same security updates.
For the overwhelming majority of server-side workloads, the answer is no, because production-grade OpenJDK builds deliver the same compiled bytecode behavior and the same quarterly security patches at zero license cost. The narrow exception is the organization that needs a contractual support guarantee on a specific legacy version, and even that need is met by third-party Java support at a fraction of Oracle pricing. See our Oracle third-party support analysis.
Java audit risk and how Oracle finds you
Oracle has built an active enforcement program around Java. It identifies likely users from Java download records tied to corporate domains, from support tickets, and from the telemetry that older Oracle JDK installations report. A common pattern is an unsolicited soft outreach, an email or call offering to help with Java compliance, which is the opening move of an audit rather than a courtesy.
| Audit signal | What Oracle infers | Buyer response |
|---|---|---|
| Oracle JDK downloads from your domain | Commercial Java use | Inventory actual deployment first |
| Support tickets referencing Java | Active Oracle Java estate | Do not confirm scope informally |
| Telemetry from installed JDK | Version and machine count | Independent measurement before any reply |
| Soft compliance outreach | Pre-audit qualification | Route to advisor, do not self-report |
The most expensive mistake is responding to that outreach with deployment data or an employee count. The figure you volunteer becomes the basis of the claim. The correct response is to inventory your own estate independently, separate Oracle JDK from already-free OpenJDK builds, and decide your position before any number reaches Oracle. The full process is in our Oracle audit defense guide.
Do not self-report: An informal employee number given to an Oracle representative during a friendly call has anchored more Java claims than any audit script. Treat the first contact as the start of a negotiation, not a help desk interaction, and let an independent measurement establish the facts.
OpenJDK: the free, production-grade path
OpenJDK is the open-source reference implementation of the Java platform, and it is the source from which Oracle JDK itself is built. Multiple vendors package OpenJDK into free, production-grade, long-term-support distributions that pass the Java compatibility tests and ship the same quarterly security updates. For the large majority of workloads, moving from Oracle JDK to one of these builds is a configuration change rather than a code change, and it removes the per-employee fee in full.
This is now standard practice rather than a fringe option. Major distributions are backed by Amazon, Microsoft, Eclipse Adoptium, and Azul, all of which commit to multi-year support windows for their long-term-support releases. The detailed head-to-head is in our Oracle Java subscription versus OpenJDK comparison.
Choosing a distribution
All major OpenJDK builds compile from the same source and behave identically at runtime. The choice comes down to the support model, the release cadence, and the ecosystem fit. The table below summarizes the leading free distributions used as Oracle Java replacements in 2026.
| Distribution | Backed by | Cost | Best fit |
|---|---|---|---|
| Eclipse Temurin | Eclipse Adoptium | Free | Vendor-neutral default for mixed estates |
| Amazon Corretto | Amazon | Free | AWS-centric workloads |
| Microsoft Build of OpenJDK | Microsoft | Free | Azure and Windows estates |
| Azul Zulu | Azul | Free, paid support optional | Teams wanting an optional support contract |
| Red Hat build of OpenJDK | Red Hat | Included with RHEL subscription | Red Hat Linux estates |
For most enterprises with a mixed technology base, Eclipse Temurin is the cleanest default because it is vendor-neutral and carries no platform tie. Cloud-aligned estates often standardize on the build from their primary cloud provider for operational simplicity. Where a contractual support guarantee is genuinely required, Azul and Red Hat offer paid support priced on the systems supported, not on headcount.
Migration sequence and timeline
A Java migration is a controlled, low-risk project when sequenced properly. The work is dominated by inventory and testing rather than code change. A typical enterprise migration runs 12 to 20 weeks, and the cost is usually a small fraction of a single year of the Universal Subscription.
| Phase | Activity | Typical duration |
|---|---|---|
| 1. Inventory | Find every JDK across servers and desktops | 2 to 4 weeks |
| 2. Separate | Split Oracle JDK from existing free OpenJDK | 1 to 2 weeks |
| 3. Pilot | Migrate and test a representative workload | 2 to 4 weeks |
| 4. Roll out | Replace Oracle JDK across eligible systems | 4 to 8 weeks |
| 5. Decommission | Remove Oracle JDK, document compliance | 1 to 2 weeks |
Risk is managed through staging and a rollback path. Because the bytecode behavior is identical, the practical risks are confined to edge cases: an application that calls a removed internal API, a build pipeline pinned to an Oracle-specific path, or a third-party product certified only on Oracle JDK. The pilot phase surfaces these before any production change, and a parallel-run period keeps the Oracle JDK installed but unused until the OpenJDK build has proven itself, so reverting is immediate if a problem appears. In practice the great majority of server workloads migrate with no code change at all.
The return is immediate and recurring. The illustrative figures below show typical year-one economics by organization size, with migration cost set against one year of subscription removed.
| Employees | Annual Oracle Java fee | Migration cost | Year-one net saving |
|---|---|---|---|
| 3,000 | $378,000 | $40,000 to $80,000 | $300,000+ |
| 15,000 | $990,000 | $90,000 to $160,000 | $830,000+ |
| 25,000 | $2,025,000 | $140,000 to $260,000 | $1.78M+ |
If you must keep Oracle Java
A minority of workloads genuinely cannot move in the short term, for example where a vendor application is certified only on Oracle JDK, or where a regulator requires a named support contract on a specific version. For those, the goal shifts from removal to reducing the count and the term. The two levers are the employee definition and the commitment structure.
On the definition, contractor and outsourcer inclusion is contestable and is the largest reduction available. On structure, a shorter term and a documented migration commitment can constrain Oracle pricing, because the credible threat of full migration is the strongest position a Java buyer holds. Our Oracle practice and software licensing advisory service handle both.
Five common Oracle Java mistakes
Across Java engagements the same avoidable errors recur. Each one either inflates the bill or hands Oracle an audit advantage that did not need to exist.
- Confusing the NFTC with a permanent free license. Teams download the current Oracle JDK, assume it is free forever, and drift into paid territory when the grace period lapses. Standardize on a distribution whose terms do not expire on Oracle release schedule.
- Trying to cut the bill by reducing Java usage. Under the per-employee metric, consolidating servers or retiring Java apps changes nothing, because the count is headcount. Only removal or count dispute reduces cost.
- Self-reporting an employee number. A figure volunteered during a friendly Oracle call anchors the entire claim. Establish the facts through an independent inventory before any number reaches Oracle.
- Accepting the broadest contractor count. Oracle audits sweep in every contractor and outsourced worker. Whether they fall inside the contract definition is contestable and is often the largest single reduction available.
- Waiting until the renewal quote arrives. The per-employee increase lands at the first legacy renewal. Modeling the Universal Subscription cost 12 months ahead is the difference between a planned migration and a forced purchase.
None of these requires deep technical work to avoid. They require treating Java as a commercial exposure to be managed proactively rather than a free utility to be assumed. The firm-side support for that work is our Oracle Java advisory and the broader Oracle practice.
The 2026 action plan
For any organization paying for, or being audited on, Oracle Java in 2026, the sequence is the same. Inventory the estate independently before Oracle frames it. Separate the Oracle JDK from the OpenJDK you already run. Scope a migration for everything that can move, which is almost everything on the server side. Dispute the employee count for any genuine residual dependency. And never volunteer a headcount to an Oracle representative before an independent measurement is done.
The economics are decisive. The migration cost is small, recurring, and one-time, while the subscription is large, recurring, and permanent. For firm-side help, start with our Oracle Java licensing and audit defense page, the subscription versus OpenJDK comparison, and the 2026 Java update. The wider Oracle context sits in the complete Oracle licensing guide.