Client Profile
The client is a European precision engineering company headquartered in Germany, with manufacturing operations across six countries and a total workforce of approximately 6,500 employees, including production staff, engineers, and contractors. Oracle Java had been deployed across the client's manufacturing execution systems, enterprise resource planning integrations, and several bespoke manufacturing quality management applications developed by an external IT services provider. Java had also propagated onto endpoint devices via application dependencies and was present in several server environments where the original installation rationale had been lost over time.
The client had not considered Oracle Java to be a licensing risk prior to receiving Oracle's review letter. Java had historically been treated as a runtime environment — a commodity technology — rather than a commercially significant software product requiring active licence management. This is the situation in which the majority of manufacturing companies found themselves following Oracle's January 2023 licensing change.
The Challenge
Oracle's January 2023 licensing change replaced the previous processor- and Named User Plus-based metrics for Java SE with the Java SE Universal Subscription, priced by employee count. Under this model, any organisation that uses Oracle Java in any production system must licence its entire employee population — including part-time employees and contractors — regardless of how many employees actually interact with Java-dependent systems.
For the client, with 6,500 employees, Oracle's Universal Subscription pricing at the applicable tier implied an annual obligation of approximately £3.2M. This was an entirely new cost category: the client had previously been using Java SE under the legacy per-processor licensing model, which had been significantly cheaper. The 2023 change had made no distinction between organisations with deep, mission-critical Java deployments and those where Java was present in a small number of systems as a supporting runtime. The metric applied universally.
Oracle's "licence review" letter — the standard format used for Java compliance enquiries — requested information about the client's Oracle Java deployments and implied that non-compliance with the Universal Subscription would result in a formal audit. The client's legal team assessed the letter as commercially coercive and sought specialist advisory support before responding.
The Approach
Redress Compliance's initial engagement focused on two parallel workstreams: a technical assessment of Oracle Java deployment across the client's estate, and a legal and commercial analysis of Oracle's contractual position under the Universal Subscription model.
The technical assessment identified four categories of Oracle Java installation. First, production systems where Oracle Java was actively in use as the primary runtime and could not be immediately migrated: the manufacturing execution system integration layer and two bespoke quality management applications. These represented approximately 15% of the Java installation count by server, but the critical business systems on which they ran. Second, server-based installations where Oracle Java was present but had been superseded by application updates that no longer required Oracle's JDK specifically — OpenJDK was a viable and technically equivalent replacement. Third, endpoint device installations where Oracle Java had been deployed as a dependency of legacy desktop applications, many of which were no longer in active use. Fourth, development environment installations where Java was present for build and test purposes, a context where Oracle's free developer licence applies and no subscription is required.
The migration programme targeted Category 2 and 3 installations immediately. Category 2 server migrations to OpenJDK were executed over a six-week period, with minimal operational impact — OpenJDK is functionally equivalent to Oracle JDK for the vast majority of enterprise applications. Category 3 endpoint installations were removed as part of a broader endpoint management refresh. Category 4 development installations were documented as non-commercial use, exempt from the Universal Subscription. By the end of the migration programme, approximately 85% of Oracle Java installations had been either migrated or removed.
The remaining Category 1 installations — the manufacturing and quality management systems — required Oracle Java to remain in place, at least until the systems could be updated or replaced. For these systems, a targeted Universal Subscription was commercially necessary. However, the scope of the subscription could be limited to the employee count directly relevant to the Java-dependent systems, rather than the enterprise-wide count Oracle's initial letter demanded.
Redress Compliance's commercial engagement with Oracle presented the post-migration deployment evidence and proposed a subscription sized to the Category 1 deployment footprint. Oracle's commercial team, faced with deployment evidence that demonstrated an 85% reduction in Java installations, accepted a subscription scoped to 850 employees — the production and quality management workforce directly interacting with the Java-dependent systems — rather than the full 6,500-employee enterprise scope.
The Outcome
The settled annual Oracle Java obligation was £640,000, based on the 850-employee subscription scope at the applicable pricing tier. This represented an 80% reduction against Oracle's initial £3.2M demand. The three-year commercial commitment secured a fixed price for the subscription period, protecting against Oracle's ability to impose further pricing increases during the term.
The migration programme also produced ongoing benefits beyond the Java subscription saving. The removal of Oracle Java from 85% of the estate eliminated future Java licensing exposure as those systems evolve. OpenJDK — maintained by the Eclipse Adoptium project and other vendors — provides long-term support versions that remove the dependency on Oracle's commercial release cycle. The client's IT team described the migration as having "permanently solved the Java problem" for the majority of systems.
Oracle did not conduct a formal audit as part of this process. The proactive engagement — presenting deployment evidence, proposing a commercial resolution, and completing the migration before Oracle's review process had advanced — removed Oracle's rationale for escalation. The documented settlement provides the client with audit protection for the agreed scope.
Key Takeaways
The Oracle Java Universal Subscription has created genuine compliance exposure for a large proportion of manufacturing companies, many of which had not previously considered Java to be a commercially managed software product. The employee-based metric — applied to the entire workforce regardless of actual Java usage — creates disproportionate cost for manufacturing organisations with large production workforces who have minimal interaction with Java-dependent systems.
The most effective response to a Java licence review letter is not to respond immediately to Oracle's commercial demands, but to first conduct a technical assessment that establishes what is actually deployed, what can be migrated, and what genuinely requires Oracle's commercial Java. This assessment directly defines the commercially relevant licence scope and is the foundation of any negotiation.
OpenJDK migration is technically viable for the majority of Java-dependent applications in enterprise manufacturing environments. Oracle's JDK and OpenJDK are functionally equivalent for standard enterprise applications; the differences relate to specific Oracle commercial features that most enterprises do not use. The migration cost is a one-time investment that typically recovers itself within the first year of subscription saving.
Independent Java deployment analysis, remediation planning, and commercial negotiation. Buyer-side only. We resolve Java exposure without overpaying Oracle.