Oracle Java licensing worries are percolating through the userbase
Summary
A survey by Dimensional Research, commissioned by Azul Systems, finds worry about Oracle’s Java pricing continues to climb. Ninety-two per cent of 2,000 respondents reported concern about Oracle Java pricing (up from 82 per cent last year), with those ‘very concerned’ rising from 19 per cent in 2025 to 29 per cent in 2026. The 2023 switch by Oracle from volume-based to per-employee Java SE subscriptions remains the key irritant, and many organisations are exploring or moving to OpenJDK alternatives.
Key Points
- 92 per cent of respondents are concerned about Oracle Java pricing, up from 82 per cent the previous year.
- 29 per cent are ‘very concerned’ about the licensing changes (up from 19 per cent in 2025).
- Oracle’s 2023 move to per-employee pricing (from per-user / per-processor) can significantly increase costs for organisations with many employees.
- Gartner research previously indicated costs under the new model could be two to five times higher for the same software use.
- 81 per cent have migrated, are migrating, or plan to migrate all or some Oracle Java to open source alternatives (examples: BellSoft Liberica, IBM Semeru, Azul Platform Core).
- A separate Dimensional Research study found 73 per cent of Oracle Java users had been audited in the past three years.
- Cloud-cost pressure compounds the issue: 97 per cent have taken actions to reduce public cloud costs, yet 74 per cent report more than 20 per cent unused compute capacity in their cloud environments.
Context and relevance
The licensing change remains a major commercial and operational headache for organisations that rely on Java. For procurement, finance and platform teams it alters budgeting and vendor risk calculations — especially where a single employee’s use of Oracle Java can trigger per-employee charges across the whole firm. The trend toward OpenJDK builds and other vendors offering supported distributions is accelerating as businesses seek predictable costs and to avoid audits or surprise bills. The interaction with cloud cost optimisation makes the issue broader than just Java licensing — it affects cloud strategy, rightsizing and supplier choices.
Why should I read this?
Short version: if you run Java in any part of your stack, this directly hits your invoices and audit risk. Read it to spot whether your organisation might be paying more than it should, whether you should prioritise a migration to OpenJDK builds, and to figure out who in the business needs to be looped into the conversation (hint: not just Devs). We’ve done the digging — savings and surprises could be on the line.
Source
Source: https://go.theregister.com/feed/www.theregister.com/2026/02/10/oracle_java_licensing/
