In January 2023, Oracle replaced Java SE per-user and per-processor pricing with a single "Employee" metric covering every employee, contractor, and "other person who supports your operations". The change turned what had been a $30,000-per-year contract into a $400,000-per-year contract for many mid-market customers. Three years on, the employee metric has expanded beyond Java SE — and its mechanics are now embedded across Oracle's commercial conversations. This is how it works, why it is a trap, and what the exits actually look like.
The Oracle Java SE Universal Subscription defines "Employee" as "all of Your full-time, part-time, temporary employees, and all of Your agents, contractors, outsourcers, and consultants that support Your internal business operations." That is more inclusive than any other vendor's licensing definition. It captures: full-time and part-time staff regardless of whether they have ever touched Java; offshore IT services teams supporting the customer; outsourced operational personnel; contingent workers in non-IT functions; staff at acquired entities for the duration of integration; and frequently, staff at vendors performing managed services for the customer.
The price is tiered: $15 per employee per month at the low end (sub-1,000 employees), tiering down to approximately $5.25 per employee at very high volume. For a 25,000-employee organisation, that is approximately $3M per year — irrespective of whether 25 or 25,000 of those employees ever use Java. Three years of escalation since 2023 have moved most enterprise renewals 12-18% above the original pricing.
The Java SE per-processor and per-NUP metric was difficult for Oracle to audit. Audit findings were uneven, customers contested the underlying compliance position, and the resulting commercial settlements varied widely. Employee-count metric eliminates that ambiguity. Oracle's audit position becomes a single number: "what is your total headcount?" — sourced from public filings or LinkedIn. The customer's room to contest narrowed dramatically.
The renewal letter usually arrives before the audit; both arrive eventually.
Oracle's Java audit process is fundamentally simpler than its database audits. The triggers are well documented and the evidence is straightforward to collect:
Once an audit is initiated, Oracle's position is typically that any download of Oracle JDK after April 2019 (the date the licence terms changed) creates a subscription requirement. The customer's defence rests on either demonstrating that no commercial Java SE features were used in production, or migrating to an alternative JDK in advance.
Migration roadmap, audit response template, and Oracle JDK alternatives compared.
Java itself remains open-source. Oracle's commercial subscription covers Oracle JDK specifically, with support, security updates, and certain commercial features. OpenJDK builds from other distributors are functionally equivalent for almost all enterprise workloads. The credible alternatives:
Migration from Oracle JDK to one of these distributions is typically straightforward for server-side workloads. Client-side Java migrations (Java Web Start, JavaFX applications) are more involved. The migration cost is almost always trivial compared to the Oracle subscription cost over three years.
When Java audit exposure is identified, the question is not whether to migrate — it is how to handle the contractual position. Customers typically have three choices: subscribe to the employee metric (the easy path, the expensive path), migrate to OpenJDK and risk a backwards-looking claim, or negotiate a transitional licensing arrangement covering the migration period. The third option is where independent advisory matters most.
The right move is rarely the renewal. The remediation maths is workload-by-workload.
Java SE was the proving ground for Oracle's employee metric. Since 2023, the metric has appeared in: Oracle Linux Premier subscriptions, Oracle Solaris subscriptions, and several variations of Oracle MySQL Enterprise commercial offerings. Anywhere Oracle owns a product with broad organisational distribution and difficult-to-measure deployment, the employee metric becomes the default pricing motion.
Customers with Oracle Linux deployments — particularly those that migrated from Red Hat under the assumption that Oracle Linux subscriptions would remain processor-priced — are seeing renewal proposals at the employee metric. The same dynamic applies to enterprise users of MySQL Enterprise Edition. Independent assessment of these positions is essential before any renewal commitment.
We have managed Java SE remediation and OpenJDK migration on estates from 1,000 to 100,000 employees. Our Java audit defense team holds the line when Oracle counts every head.
Weekly compliance intelligence for IT leaders.
