Client Overview
Organisation
A prominent bank in the United Arab Emirates with Java deployed across virtual environments — powering core banking applications, middleware integrations, and internal business systems. Java was deeply embedded in the bank's technology stack across both server and end-user environments.
Java Estate
Widespread Oracle Java SE deployments across virtualised server infrastructure and end-user desktop devices. Java was used for both in-house developed applications and third-party software dependencies — creating significant licensing complexity under Oracle's new employee-based metric.
Compliance Exposure
Oracle's 2023 Java licensing changes moved from a per-user/per-processor model to a per-employee metric, exposing the bank to a $3.2 million annual compliance risk — regardless of how many employees actually used Java.
Objective
Engage Redress Compliance to conduct a comprehensive Java licensing assessment, train internal IT staff on Java licensing rules, develop an optimisation strategy, and negotiate with Oracle to achieve the lowest possible annual cost on favourable terms.
In January 2023, Oracle replaced the per-Named User Plus / per-Processor metric for Java SE with a per-employee metric — meaning organisations must license every employee, contractor, and casual worker, even if only a handful actually use Java. For a large bank, this change can multiply Java costs by 10–50× overnight. For the full picture, read our guide to Oracle Java licensing changes and strategies.
The Challenge
The bank's Java usage was widespread and deeply integrated into its technology infrastructure. When Oracle introduced the new per-employee licensing metric, the bank's compliance exposure jumped from a manageable annual cost to a $3.2 million annual liability — a figure that would recur every year without intervention.
| Challenge | Detail |
|---|---|
| New employee-based metric | Oracle's 2023 Java SE licensing change meant the bank had to license every employee — not just those running Java. This inflated the compliance exposure dramatically. |
| Virtual environment complexity | Java was deployed across virtualised server infrastructure where Oracle's licensing rules for virtual environments are notoriously complex and aggressive. |
| Widespread desktop installations | Java was installed on end-user devices across the organisation, including machines where Java was a dependency for third-party applications. |
| $3.2 million annual risk | Under the new metric, Oracle would demand $3.2 million per year — a cost that was not budgeted and represented a significant unplanned expense. |
| Limited internal licensing knowledge | The bank's IT and procurement teams did not have deep expertise in Oracle Java licensing mechanics — making it difficult to evaluate Oracle's claims or negotiate effectively. |
How Redress Compliance Helped
Redress Compliance was engaged to take complete ownership of the Java licensing strategy — from initial assessment through to final negotiation with Oracle. The approach was structured in six phases.
Java Licensing Assessment
Redress conducted a comprehensive Java licensing assessment across the bank's entire environment — servers, virtual machines, and end-user devices. The assessment mapped every Oracle Java installation, identified which Java versions were in use, determined which installations were genuinely required vs. legacy or unnecessary, and quantified the exact compliance position under both the new and legacy licensing metrics.
Java Licensing Training
Redress delivered targeted Java licensing training to the bank's IT staff, covering Oracle's Java licensing rules, the differences between Java SE versions, the implications of the new per-employee metric, and common compliance traps. This training built internal capability so the bank's team could maintain compliance independently going forward.
Licensing Optimisation Strategy
Based on the assessment, Redress developed a licensing optimisation strategy built around the legacy licence metric. Three key optimisation levers were identified:
Upgrade to free Java versions: Migrating eligible deployments to free, non-Oracle Java distributions (such as OpenJDK) where Oracle's commercial Java SE was not technically required.
Consolidate virtual deployments: Restructuring virtualised Java workloads to reduce the licensing footprint — consolidating Oracle Java onto fewer hosts.
Network and storage isolation: Implementing isolation for Java deployments to reduce the number of hosts Oracle could claim required licensing under its virtualisation counting rules.
Optimisation Implementation
The bank's IT team, guided by Redress, executed the optimisation plan: upgrading to free Java alternatives where possible, consolidating virtual environments, and implementing the network and storage isolation architecture. This work was completed before approaching Oracle — ensuring the bank negotiated from an optimised position rather than an exposed one.
Never negotiate with Oracle before optimising. Every unnecessary installation, every unmanaged virtual environment, and every legacy deployment that could be replaced with a free alternative — these all become leverage for Oracle to push you toward the maximum-cost scenario. Optimise first, then negotiate from a position of demonstrable, documented low usage.
Negotiation with Oracle
After the isolation agreement was signed and the optimisation was complete, Redress and the bank approached Oracle to negotiate on legacy metrics. With the optimised environment, the bank's actual licensable usage translated to $300K annually on legacy metrics — compared to $3.2 million on the new per-employee model. Oracle was presented with a clear, evidence-based case for why the legacy metric applied.
Final Decision and Metric Selection
Oracle agreed to allow the bank to purchase on either legacy metrics or employee metrics with a discount. The bank chose the legacy metric — a deliberate strategic decision. The legacy metric gave the bank the option to further reduce its Java licences in the future as it continued migrating to free Java alternatives. Under the employee metric, the cost would be tied to headcount regardless of actual Java usage.
Outcomes
Three-Year Financial Impact
| Metric | Before Engagement | After Engagement |
|---|---|---|
| Annual Java cost | $3.2 million (employee metric) | $300K (legacy metric) |
| Licensing metric | Per-employee (all employees counted) | Legacy per-NUP (actual usage counted) |
| Java footprint | Widespread, unmanaged across servers and desktops | Optimised, consolidated, free alternatives deployed |
| Virtual environment | No isolation; Oracle could claim entire estate | Network and storage isolation implemented |
| Internal capability | Limited Java licensing knowledge | Staff trained; ongoing compliance maintained internally |
| Future flexibility | Locked into escalating per-employee costs | Can further reduce licences as migration continues |
"The strategic insights and deep expertise of Redress Compliance have been instrumental in our Java licensing optimisation process. Their comprehensive approach, effective training, and unwavering support were key in navigating the complexities of the new Java licensing metric. They identified and helped us mitigate substantial compliance risk and guided us in making an informed decision that resulted in significant cost savings. Their contribution has been pivotal in our IT sourcing strategy."— Head of IT Sourcing, UAE Bank
Facing Oracle Java licensing pressure? Get an independent assessment before you sign.
Java Compliance Assessment →Key Takeaways for CIOs and IT Leaders
- Oracle's per-employee Java metric is not your only option. The legacy per-NUP and per-processor metrics may still be available through negotiation — and they can deliver dramatically lower costs for organisations that optimise their Java footprint first.
- Optimise before you negotiate. The bank's decision to migrate to free Java alternatives, consolidate virtual deployments, and implement isolation before approaching Oracle was the single most important factor in achieving a 91% cost reduction.
- Virtual environments are a Java licensing landmine. Oracle's rules for counting Java licences in virtualised environments can inflate costs by multiples. Network and storage isolation is a proven technique to contain the licensable footprint.
- Invest in internal Java licensing knowledge. The training Redress delivered gave the bank's team the ability to maintain compliance independently. See our Java Advisory Services for ongoing support.
- Choose metrics that preserve future flexibility. The bank deliberately chose legacy metrics over employee metrics because legacy metrics allow further cost reduction as free Java migration continues.
- Free Java alternatives are real and production-ready. OpenJDK and vendor-supported distributions provide identical functionality to Oracle Java SE for many workloads. Migrating eligible deployments off Oracle Java is the most effective way to reduce licensing exposure permanently.
Oracle Java Licensing Exposure? Don't Sign Without an Assessment.
Oracle's Java licensing changes have created multi-million dollar compliance risks for organisations worldwide. Our independent Java licensing team has helped banks, manufacturers, retailers, and Fortune 500 companies reduce Java costs by 80–95%. We work exclusively in your interest — never Oracle's.
Need audit defence against Oracle's Java compliance team?
Java Audit Defence →