11 November, 2026 | 3 min read

Oracle cuts Java SE prices and the fine print matters

Johnny Cree

Oracle SAM Licencing Consultant

Oracle cuts Java SE prices and the fine print matters

On 8th of October 2026, Oracle published a new Java Standard Edition (SE) Universal Subscription price list. For the first time since the employee-based metric arrived in 2023, organisations with fewer than 3,000 employees can get pricing built to match their size. A company with 100 employees that would have paid $18,000 a year under the March 2023 list now pays $1,000.

The old model charged $15 per employee per month for companies with 1 to 999 staff and $12 for those with 1,000 to 2,999. A ten-person firm paid the same per-head rate as a 900-person company which put undue pressure on the smaller company.

The new model replaces that with flat annual bands: $100 for up to 10 employees, $1,000 for up to 100, and $10,000 for up to 500.

Each employee from 501 to 2,999 then adds $147.20 per employee a year. Pricing for 3,000 employees and above stays as it was.

Table comparing annual Oracle Java SE costs in 2023 versus 2026 across different organisation sizes. For 10 employees, annual costs decrease from $1,800 to $100 (-94%). For 100 employees, costs decrease from $18,000 to $1,000 (-94%). For 500 employees, costs decrease from $90,000 to $10,000 (-89%). For 1,000 employees, costs decrease from $144,000 to $83,600 (-42%). For 2,000 employees, costs decrease from $288,000 to $230,800 (-20%). For 3,000 employees, costs remain unchanged at $378,000 (0%). The data shows the largest savings for smaller organisations, with savings reducing as employee count increases.

Pricing impact by organisation size

The savings are largest for the smallest firms and shrink as headcount grows. Above roughly 1,000 employees, the saving settles at about $55,000 to $60,000 a year.

Three conditions come with the new prices.

Banding

The bands cannot be stacked, so a company with 200 staff must buy the 500-employee band, not two 100-employee bands

Processor limits

The processor allowance now depends on headcount, from 1,000 processors at 10 employees to 50,000 above 500

True-up requirement

If headcount exceeds the licensed number at any point during the term, the customer must buy more licences immediately rather than at renewal

Companies on the edge of a band need to watch their numbers closely. Moving from 100 to 101 employees raises the bill from $1,000 to $10,000.

Summary

Oracle has cut Oracle Java SE costs for organisations under 3,000 employees, with the largest reductions for firms under 100 staff. The savings come with three new constraints: non-stackable bands, headcount-linked processor limits, and an obligation to license mid-term growth.

What this means for customers

  • Budget for the savings but check your headcount first. Small firms will see large reductions at their next renewal but the band cliffs mean a few extra hires can add several thousand dollars. Confirm your exact headcount against the band boundaries before you order.
  • Count everyone the definition covers. The definition still includes contractors, outsourcers and consultants who support internal operations, not only staff who use Oracle Java. Include them in your count.
  • Plan for mid-term growth. Talent hires, a contract win or an acquisition can trigger an immediate purchase. Build a contingency into the budget or align order timing with expected growth.
  • Measure processors, not only people. A 10-person company is capped at 1,000 processors. Managed service providers and hosting firms with large server estates may exceed these limits and face higher costs.
  • Compare the alternatives. OpenJDK distributions with commercial support may cost less over time for some estates. Weigh the support, patching and compliance implications against the subscription price.
  • Identify what versions of Oracle Java you have deployed. Identifying which installations of Oracle Java are commercial or not should be a priority before renewal or purchase. You may find that some impending upgrades could impact licensing during a financial year. Know before you upgrade.
  • Be Audit Ready. Organisations must be aware of the new rules and price changes and be ready for an audit. It is Oracle’s right to audit customers’ use of Oracle Java. If organisations know what they are using and what licenses they are applying before an audit commences, then they are ahead of the game and ready– although navigating an audit and knowing your position is critical; so ensure you engage specialist advice from us.

With over 200 years’ combined experience in Oracle licensing and in-depth knowledge of Oracle Java pricing changes, our team can help you navigate the changes and optimise your commercial outcome.

Our dedicated Java licensing website page hosts blogs, videos and links to further content, including our comprehensive overview of Oracle Java and its alternatives, Oracle Java discovery techniques and the steps involved if you wish to migrate to OpenJDK and an overview of Oracle Java audits and what this could mean for your business.

For help, contact the software asset management team.

Related insights

Insights