How Redress Compliance helped a multinational Swiss company with heavy in-house and third-party Java systems reduce a $3 million annual licensing cost to $400K per year—delivering $7.8 million in savings over three years through strategic assessment, IT training, and deployment optimisation.
A multinational Swiss company with heavy Java usage across both in-house developed and third-party systems faced a significant cost impact from Oracle's new Java licensing Employee metric. Under the new pricing model introduced in 2023, the company faced an annual Java SE subscription cost of $3 million—a dramatic increase driven entirely by the shift to per-employee pricing.
What made this engagement particularly complex was the dual nature of the company's Java estate. In-house developed applications could potentially be refactored or migrated to free Java alternatives, but third-party systems that shipped with embedded Oracle Java presented a different challenge—the company often had limited control over which Java distribution these vendor applications required.
The company enlisted Redress Compliance to navigate this complexity and find an optimisation path that addressed both in-house and third-party Java dependencies. For a comprehensive overview of the licensing changes, see Decoding Oracle Java Licensing Changes.
Under Oracle's new Java SE Universal Subscription Employee metric, the multinational company faced an annual licensing cost of $3 million. With operations spanning multiple countries and a large global workforce, the per-employee pricing model amplified the cost impact far beyond what usage-based licensing would have produced.
| Challenge | Description | Risk Level |
|---|---|---|
| New Employee Metric | Oracle's 2023 Java SE metric prices licences based on total global employee count. For a multinational with thousands of employees across multiple countries, this created a disproportionate cost burden. | Critical |
| In-House Java Applications | Custom-developed applications relied on Oracle Java across development, testing, and production environments. These systems required careful analysis to determine migration feasibility. | High |
| Third-Party Java Dependencies | Vendor-supplied applications shipped with embedded Oracle Java, creating licensing obligations the company could not easily eliminate without engaging each software vendor individually. | Critical |
| Multi-Country Complexity | Java deployments spanned multiple countries with different IT teams, varying infrastructure standards, and fragmented visibility into the full Java estate. | High |
| Internal Knowledge Gap | IT staff understood their applications well but lacked expertise in Oracle's Java licensing rules, particularly regarding the distinction between free and commercial Java and the implications of third-party bundling. | Medium |
Many enterprise software vendors bundle Oracle Java with their products. When Oracle shifted to the Employee metric, organisations discovered they were liable for Java licensing costs driven by third-party applications they did not develop and could not easily modify. Addressing this requires a systematic approach: identifying which vendors bundle Oracle Java, determining whether those vendors can provide alternative Java distributions, and negotiating with vendors to remove the Oracle Java dependency where possible.
For more on Java licensing cost implications, see our Java Licensing Cost Calculator.
Essential strategies for defending against Oracle Java compliance claims and audit notices. Protect your organisation before Oracle comes knocking.
Redress Compliance delivered a structured, four-phase engagement specifically designed to address both the in-house and third-party dimensions of the company's Java licensing challenge.
Redress conducted a complete Java licensing assessment across the company's global operations. This mapped every Java deployment—in-house applications, third-party systems, development environments, and end-user devices—across all countries of operation. Critically, the assessment distinguished between Java installations the company controlled directly (in-house) and those embedded in third-party vendor products, as the optimisation approach for each category was fundamentally different.
Redress delivered comprehensive Java licensing training to the company's IT staff across multiple regions. The programme covered Oracle's Java licensing rules, the distinction between free and commercial Java distributions, the specific implications of the new Employee metric for multinational organisations, and the critical topic of third-party Java bundling—helping IT teams understand when a vendor application creates an Oracle licensing obligation and when it does not.
Redress designed a dual-track optimisation strategy. For in-house applications, the strategy identified systems that could be migrated to free Java distributions (such as Eclipse Temurin or Amazon Corretto), consolidated redundant deployments, and optimised development and test environments. For third-party systems, the strategy mapped which vendor applications bundled Oracle Java, identified vendors offering alternative Java distributions, and created an engagement plan for vendors who could eliminate the Oracle Java dependency from their products.
The company executed the optimisation plan with Redress's guidance. In-house applications were migrated to free Java alternatives where feasible. Third-party vendors were engaged to provide non-Oracle Java versions of their products or confirm that their applications could run on free distributions. Redundant deployments were consolidated, unnecessary installations were removed, and governance processes were established to prevent Java licensing sprawl from recurring across the global estate.
The dual nature of this company's Java estate—combining in-house and third-party systems—is typical of large multinationals. The critical insight was treating these as two separate optimisation tracks. In-house applications are within the company's direct control and can be migrated relatively quickly. Third-party Java dependencies require a vendor engagement strategy, which takes longer but can eliminate significant licensing obligations. By running both tracks in parallel, the company achieved an 87% cost reduction without disrupting any business-critical systems.
For more on navigating Java in complex environments, see Java Licensing for Virtual Environments.
| Metric | Before Engagement | After Engagement | Impact |
|---|---|---|---|
| Annual Java Licensing Cost | $3 million | $400,000 | 87% reduction |
| Annual Savings | — | $2.6 million | Per year, recurring |
| 3-Year Total Savings | $9 million (projected cost) | $1.2 million (actual cost) | $7.8M saved |
| In-House Applications | Primarily Oracle Java | Migrated to free alternatives | Eliminated licensing obligation |
| Third-Party Systems | Vendor-bundled Oracle Java | Vendors engaged to provide alternatives | Reduced third-party Java exposure |
| Internal Capability | Limited Java licensing knowledge | Trained global IT teams | Self-sufficient compliance management |
The multinational Swiss company reduced its annual Java licensing cost from $3 million to $400,000—an 87% reduction—saving $7.8 million over three years. Both in-house and third-party Java dependencies were systematically addressed, and global IT teams now have the expertise to manage Java compliance independently across all regions.
"Working with Redress Compliance was a game-changer for us. Their team knows their stuff when it comes to Java licensing. They took the time to understand our needs, educated our team, and came up with a strategy that was spot on. The savings we made were beyond our expectations. It's clear that Redress Compliance is not just a vendor but a partner committed to our success."
Proven strategies for Oracle contract negotiations including Java licensing, audit defence, and cost optimisation tactics.
For more on Java licensing strategies, see our Oracle Java Licensing Guide and Oracle Java SE Licensing overview.
This case study demonstrates that even multinational organisations with complex, dual-track Java estates—combining in-house developed systems with third-party vendor applications—can achieve transformational cost reductions. The 87% reduction, from $3 million to $400,000 annually, was delivered through a systematic approach that addressed both categories of Java usage simultaneously.
The lesson for multinationals facing similar Java licensing pressure is clear: the complexity of a global, mixed Java estate is not a barrier to optimisation—it simply requires a more structured approach. With expert guidance, comprehensive assessment, and parallel optimisation tracks for in-house and third-party systems, the savings potential is substantial.
For more Java licensing success stories, visit our Java Licensing & Audit Defence Case Studies hub, or read about similar engagements: $19.2M Saved for a US Pharmaceutical Company, $5.64M Saved for a Swedish Manufacturer, and Java Optimisation for an Australian Bank.
Expert strategies for Oracle contract renewals, Java licensing optimisation, and cost reduction approaches.
Download our expert research on Oracle Java licensing, audit defence, and negotiation strategy.
Redress Compliance provides independent, vendor-neutral Java and Oracle advisory services to enterprises worldwide.