Oracle Java licensing in 2026: the Java SE Universal Subscription. Every employee counts, and the band sets the bill.

Oracle Java is priced on your whole workforce at $15.00 down to $5.25 per employee a month, however little Java you run. What you owe depends on the count, the band it lands in, and which JDK builds sit under paid terms.

How does the Java SE Universal Subscription work in 2026?

You pay a monthly rate for every employee in your organization, whether or not anyone runs Java. Oracle replaced its processor and Named User Plus metrics with the per employee Java SE Universal Subscription on January 23, 2023. Servers, desktops and installs do not appear anywhere in the calculation.

List runs from $15.00 per employee per month in the 1 to 999 band down to $5.25 at 40,000 to 49,999. Oracle publishes no rate above 50,000 employees and quotes those companies directly. The standard term is one year.

• What the fee covers. Java SE on desktops, servers and cloud, plus support, Java Management Service and the Enterprise Performance Pack.
• The processor ceiling. The employee license covers Java on up to 50,000 processors, not counting desktops and laptops. Beyond that Oracle requires an additional license, as our note on the 50,000 processor cap explains.
• What it replaced. The legacy Java SE Subscription and Java SE Desktop Subscription, which are closed to new purchases.

How did Oracle Java pricing change between 2019 and 2023?

Java was free for commercial use under the Binary Code License until 2019. Oracle then charged per processor and per Named User Plus, and from 2023 on the employee count.

The missing paperwork from before 2019 still matters. Companies kept few records of the Java they installed for free, which is why Oracle's download logs carry so much weight in a dispute.

Why do the billing metric and the binary license run on separate clocks?

The metric decides what you pay. The license printed on each Oracle JDK build decides whether you owe anything at all. Oracle has changed the billing metric twice and the binary license terms three times, and buyers who mix the two up either pay for builds that were free or run paid builds without a license.

Is a pre 2023 processor or Named User Plus contract worth keeping?

Yes, and read it before anyone at Oracle calls it obsolete. Contracts signed between 2019 and 2023 remain valid and price on servers and users rather than payroll. They cannot be expanded to cover anything new, but for the footprint they already cover they can cost far less than the employee metric.

Oracle's own FAQ says legacy customers may renew where the existing order permits, subject to confirming that current usage matches the licensed counts. Run your own inventory before you ask. Our guides to legacy Java licenses and renewing on the legacy metric cover the steps.

Who counts as an employee under the Java SE Universal Subscription?

Every full time, part time and temporary employee counts. So do the full time, part time and temporary staff of your agents, contractors, outsourcers and consultants who support your internal business operations.

The definition sits in Oracle's Java SE Universal Subscription price list, and Oracle states that the quantity follows the number of employees, including those who never use Java. The phrase about internal business operations causes more disputes than any other term in the order.

Which contractors fall outside the Oracle Java employee count?

• Usually counted. Staff of an outsourced service desk, payroll bureau, finance shared service center or infrastructure operator. Their work runs your internal operations.
• Arguable. Consultants on a fixed scope project such as an ERP rollout. If the statement of work has them building internal systems, expect Oracle to count them.
• Strong case to exclude. A contractor team building a product you sell to customers. That work serves your customers, and the narrower reading excluding it carried in roughly four of five engagements where we contested contractor counts.
• Outside the definition. Your customers and their users, who are neither your employees nor staff supporting your operations.

Build your own count from HR and supplier records, with the date it applies to, before you discuss any rate. Oracle's opening number is a starting position, and our note on counting contractors and consultants shows how to test each supplier contract against the wording.

Do restricted use rights or ISV embedded Java lower the count?

Only if they take your chargeable footprint to zero. Both routes can take individual installs out of scope:

• Restricted use. Java that ships inside a licensed Oracle product, such as WebLogic Server, carries restricted use rights for running that product.
• ISV embedded Java. Java bundled by an independent software vendor is covered only if that vendor holds its own redistribution agreement with Oracle, so ask the vendor to confirm it in writing. Our guide to embedded Java licensing covers what to request.

Neither reduces the price while even one chargeable Oracle JDK install remains, because that single install prices the whole workforce.

Why can 10,000 employees cost less than 9,999 on Oracle Java?

The band rate applies to your whole count, so crossing a boundary reprices every employee. At 9,999 employees you pay $10.50 a month on everyone, $1,259,874 a year at list. At 10,000 the whole count drops to $8.25, which comes to $990,000.

Work backward from that figure and the break even point is 7,857 employees. Any company above that pays less by ordering 10,000 than by ordering its real count. Near the top of the band the gap is large: at 9,999, ordering 10,000 saves $269,874, about 21 percent of list.

Raise an order for more employees than you have early, as part of the count discussion. The worked pricing example runs the tiers for more headcounts.

What does a 5,000 employee company pay per Java server?

A 5,000 employee company sits in the $10.50 band and pays $630,000 a year at list, however much Java it runs. Across 40 servers, that is $15,750 per server.

Compare the legacy metric on the same 40 servers. Say each counts as 2 Oracle processors after the core factor: 80 processors at $25.00 a month is $24,000 a year. That gap is why an old processor contract deserves a careful read before renewal.

A company with 100 Java servers and 10,000 employees now pays for 10,000 employees.

Which Oracle JDK versions are still free, and when does that end?

Oracle JDK 25 is free under the No Fee Terms and Conditions (NFTC) until September 2028. JDK 21 updates were free through September 2026, and from the October 2026 Critical Patch Update they ship under the Java SE OTN license, which requires a paid license for production use.

Each LTS release keeps NFTC terms until a year after the next LTS ships. JDK 17 left the free terms in October 2024, when update 17.0.13 became its first release under OTN. OTN still permits personal use and use for development, testing, prototyping and demonstrating applications without a fee.

How do patch pipelines turn free Java into paid Java?

An NFTC build you already installed stays under NFTC. The exposure comes when an automated process replaces it with a newer build under OTN terms and the license change goes unreviewed.

• Container images. Dockerfiles that fetch the newest Oracle JDK pick up an OTN build at the next rebuild, as our note on Java in Docker base images describes.
• Endpoint management. Configuration Manager or Intune catalogs that approve Java updates automatically.
• Developer workstations and CI CD pipelines. Build agents and setup scripts that download the current Oracle JDK on each run.

Before the October 2026 update lands, choose a route for each pipeline: upgrade to JDK 25 under NFTC, switch to an OpenJDK build, or pin the last free JDK 21 build and accept that it gets no further security fixes. Leave versions unmanaged and you end up buying the subscription one automated update at a time.

Should you renew Oracle Java, migrate to OpenJDK, or do both?

Cost all three options over three years before you choose. In our modeling for a 12,000 employee company, the OpenJDK exit came to $1,728,000 over three years with the migration project included. A negotiated subscription came to $2,102,760 to $2,779,920, depending on the discount.

Signed discounts landed 22 to 41 percent off Oracle's opening quote on three year orders, and where a buyer landed tracked the band tier more than the effort spent negotiating. Even the best result left the subscription $374,760 above the exit. At the weaker end the gap was $1,051,920.

Why keeping Oracle Java for a few systems costs the most

The usual advice is to migrate what is easy and keep Oracle Java for the handful of systems that feel risky. We advise against it. The retained footprint still prices your whole workforce, so you pay the full subscription and the migration project, which makes hybrid the most expensive of the three options.

It also reaches the shortlist most often, because it feels safe. If a few systems cannot move, check whether they qualify for restricted use under another Oracle license or can run on a supported third party build. Then plan a full exit around them, or keep the subscription and stop paying for a migration.

How long does an Oracle Java to OpenJDK migration take?

Large enterprises we advised finished in 9 to 14 months. Application code was rarely what held them up. The delays came from tooling discipline on developer workstations and in CI CD pipelines, where installers and scripts kept pulling Oracle JDK back in.

The Java alternatives guide covers build selection and compatibility, our distribution comparison weighs Corretto, Temurin and Zulu, and the Java audit defense guide covers how to protect the exit window if Oracle opens a review mid migration.

What have we seen in Oracle Java negotiations in 2024 and 2025?

Across roughly 35 to 45 Oracle Java engagements closed in 2024 and 2025, the same three arguments came up, usually in the same order. Enforcement peaked in the three quarters after the January 2023 metric change, then settled into a steady rhythm.

1. The opening. In most engagements Oracle's first contact cited a download log entry tied to the corporate email domain. A renewal date was rarely the trigger. The response started with download governance and the entitlement record, before any talk of price.
2. The count. Oracle's quoted employee number ran 18 to 28 percent above what the buyer could support once non supporting contractors, and temporary staff not on the payroll at the count date, were taken out.
3. The contractor reading. Whether contractor staff support internal business operations. The narrower reading won in most contested cases.

For your own renewal, the order matters. Settle the evidence, then the count, then the definition, and only then the rate, or you end up negotiating a discount on a number that is too high.

What will Oracle's Java sales team say, and how should you answer?

Expect these lines, and prepare a written reply to each before the first call.

• "Our records show this employee count for your company." Ask for the source and date of the figure. Reply with your own count, split into direct employees, temporary staff and each contractor group, with the definition applied line by line.
• "We see Oracle JDK downloads from your domain." Ask for the dates, versions and accounts behind each entry. A download is not an installation, and NFTC builds and OTN development use carry no fee.
• "Your legacy Java SE Subscription is being retired, so this renewal switches to the employee metric." Point to Oracle's own FAQ, which allows legacy customers to renew where the existing order permits, subject to confirming that usage matches the licensed counts. Bring your inventory showing it does.
• "This discount is only available if you sign before quarter end." Oracle's fiscal quarters close at the end of August, November, February and May, and that deadline serves the sales team's target. Settle the count and the order terms first, then decide whether the timing suits you.
• "Moving to OpenJDK is riskier and costlier than it looks." Show that you hold a costed three year model and a migration timeline, and ask Oracle to price against it. Our note on making the migration option credible explains what that model needs.

What should an Oracle Java order say before you sign?

It should fix the employee count and its date, how band changes apply during the term, the renewal price and the entities covered. Ask for each of these in writing, because anything left to the standard terms defaults to Oracle's reading.

• The count and its date. The employee number, how it was built and the date it applies to, with named exclusions for contractor groups that do not support internal operations. Otherwise the next renewal starts from Oracle's number again.
• Band treatment during the term. What happens when headcount crosses a boundary, so growth into a cheaper band lowers the rate. Our note on headcount cap wording has examples.
• A renewal price hold. A cap on the per employee rate at renewal, since the standard term is one year.
• No minimum annual fee. Strike any subscription floor that survives a fall in headcount.
• Entity scope. Which legal entities the order covers, and how an acquisition or divestiture changes the count.

How do you check your own Oracle Java position before Oracle does?

Inventory every Oracle JDK install, reconstruct your download history and build your own employee count. Run the install work and the headcount work in parallel, since Oracle tests both.

1. Find every Oracle JDK and JRE. Running java -version shows the build: Oracle JDK reports "Java(TM) SE Runtime Environment", while OpenJDK builds report "OpenJDK Runtime Environment". Collect it at scale with your inventory tools, as our guide to telling Oracle JDK from OpenJDK describes.
2. Record the version and update of each Oracle install. That tells you whether it sits under the BCL, NFTC or OTN terms.
3. Reconstruct your download history. Which Oracle accounts on your email domain downloaded which builds, and when. Our note on download history lists what to gather.
4. Build the employee count. HR headcount by legal entity, plus each supplier contract tested against the internal operations wording.

What to do next

1. This month. Move every JDK 21 pipeline to JDK 25 or an OpenJDK build before the October 2026 Critical Patch Update arrives under OTN terms.
2. 12 months before renewal. Pull every Java order since 2019 and check whether any processor or Named User Plus order allows renewal on its existing metric.
3. 9 months before. Build your employee count by entity, test each contractor group against the internal operations wording, and check where you sit against the band boundaries.
4. 6 months before. Cost renewal, full migration and hybrid over three years on your own count, and decide which one you would actually choose.
5. 3 months before. Send Oracle your count and the order terms you need, and answer any download log questions with dated records.
6. At signature. Sign only with the count, band treatment and renewal price hold in writing. The Oracle practice can run the engagement with you.

Frequently asked questions