Case Study: Java Licensing Optimization for an Australian Bank

Background

An Australian bank with heavy Java usage across both in-house and third-party developed systems faced a significant financial impact when Oracle introduced its new Java SE licensing metric. The bank relied on Java extensively throughout its technology stack — powering core banking applications, middleware, customer-facing digital services, and internal tooling — making Java licensing a material enterprise cost.

Under Oracle's employee-based Java SE Universal Subscription model, the bank was facing a $5 million annual subscription cost. This was a dramatic increase from what they had been paying under previous Java licensing arrangements, driven by Oracle's requirement to licence every employee in the organisation regardless of whether they personally use Java.

The bank enlisted Redress Compliance's expertise to conduct a comprehensive assessment and develop an optimisation strategy that would bring Java licensing costs under control without disrupting operations.

Why Java licensing costs have exploded: Oracle's 2023 shift to an employee-based Java SE Universal Subscription fundamentally changed the economics of Java licensing. Instead of paying per server processor or per named user, organisations must now licence every employee — full-time, part-time, contractors, and consultants — even if only a handful actually use Java. For a large bank, this can turn what was previously a modest infrastructure cost into a multi-million-dollar annual obligation. See Oracle Java JRE Licensing — What Enterprises Need to Know.

Challenge

The bank faced a potential Oracle Java licensing cost of $5 million annually under the new employee-based metric. They needed a comprehensive strategy to mitigate this cost and optimise their Java licensing position.

Challenge	Detail
$5M Annual Java Cost	Oracle's employee-based Java SE Universal Subscription would require the bank to licence every employee at Oracle's tiered pricing, resulting in a $5 million annual cost — regardless of how many employees actually use Java in their daily work.
Extensive Java Footprint	Java was deeply embedded across the bank's technology stack, powering in-house developed applications, third-party systems, middleware, and development environments. The breadth of Java usage made it impossible to simply "remove Java" as a quick fix.
Mixed Java Environments	The bank ran a mixture of Oracle JDK versions across different environments — production, development, testing, and disaster recovery — with varying licence obligations depending on version, use case, and which Oracle terms applied.
Limited Internal Java Licensing Knowledge	Until Oracle changed its pricing model, Java had been a low-cost or free technology. The bank's IT and procurement teams lacked the specialised knowledge of Oracle's Java licensing rules needed to identify optimisation opportunities and avoid compliance traps.

The employee metric trap: Oracle's Java SE Universal Subscription counts all employees — including full-time, part-time, temporary staff, and contractors — regardless of whether they use Java. A bank with 10,000 employees but only 200 Java users still pays for all 10,000. At Oracle's list price of $5.25–$15 per employee per month, this creates enormous cost exposure for large organisations with limited actual Java usage. For a detailed breakdown, see How to Calculate Oracle Java SE Licensing Costs.

Solution

Redress Compliance was engaged to deliver a comprehensive Java licensing optimisation engagement covering assessment, education, strategy development, and implementation guidance:

Phase 1: Java Licensing Assessment

Redress conducted a complete Java licensing assessment to map every Java deployment across the bank's infrastructure. This included identifying all Oracle JDK installations on servers, desktops, virtual machines, containers, and development environments — determining which versions were installed, which Oracle licence terms applied to each, and where the bank had genuine Oracle Java licence obligations versus deployments that could be migrated to alternatives.

Phase 2: Java Licensing Training

Redress delivered comprehensive Java licensing training to educate the bank's IT staff on Oracle's Java licensing rules. The training covered the differences between Oracle JDK and OpenJDK, which Java versions require commercial licences, how Oracle's employee metric works, what triggers a Java licence obligation, and how development and testing environments are treated. This knowledge transfer was critical to ensuring the bank's teams could make informed decisions about Java usage going forward.

Phase 3: Licensing Optimisation Strategy

Based on the assessment findings, Redress created a tailored licensing optimisation strategy specific to the bank's Java usage patterns, application dependencies, and roadmap. The strategy identified which Java deployments genuinely required Oracle's commercial JDK (and therefore a licence), which could safely migrate to OpenJDK or other open-source distributions, and which could be consolidated or removed entirely.

Phase 4: Optimisation Implementation

The bank implemented the optimisation strategy with Redress guidance. This involved upgrading to more cost-effective Java versions where possible, consolidating Java deployments to reduce the licensing footprint, migrating eligible workloads to OpenJDK distributions that carry no Oracle licence fee, and optimising the remaining Oracle Java usage to minimise the subscription count required.

OpenJDK migration is the primary cost lever: For most organisations, the single biggest Java licensing optimisation opportunity is migrating from Oracle JDK to an OpenJDK distribution (such as Eclipse Temurin, Amazon Corretto, or Azul Zulu). These are functionally equivalent to Oracle JDK for the vast majority of use cases and carry no Oracle licence fee. In our experience, 60–80% of enterprise Java deployments can safely migrate to OpenJDK — often reducing the Oracle Java licensing obligation to a fraction of the original cost. The key is conducting a thorough assessment first to identify which deployments have genuine Oracle JDK dependencies.

Outcome

$5M → $700K

Annual Java Cost Reduction

86% reduction in licensing spend

$4.3M

Annual Recurring Savings

Year-over-year cost avoidance

$12.9M

3-Year Total Savings

Cumulative cost reduction

The bank reduced its potential $5 million annual Java licensing cost to $700,000 annually — an 86% reduction that saved $4.3 million per year. Over three years, this resulted in total savings of $12.9 million.

Before Optimisation

$5M / year

Full employee-based Java SE Universal Subscription at Oracle's pricing for the bank's entire workforce

After Optimisation

$700K / year

Reduced Oracle Java subscription covering only genuine Oracle JDK dependencies after OpenJDK migration

Annual Savings

$4.3M / year

Recurring annual cost reduction through deployment optimisation, OpenJDK migration, and licence consolidation

3-Year Savings

$12.9M

Total cumulative savings over three-year period with no reduction in Java capability or operational impact

The optimisation delivered immediate and sustained financial impact while maintaining the bank's full Java capability. By understanding exactly where Oracle JDK was genuinely required — and migrating everything else to cost-free alternatives — the bank transformed Java from a $5 million annual cost burden into a manageable $700,000 operational expense.

The strategic insights and deep expertise of Redress Compliance have been instrumental in our Java licensing optimisation process. Their comprehensive approach, from the initial assessment to the final implementation, was key in navigating the complexities of Java licensing. They helped us understand our Java usage better and guided us in making an informed decision that resulted in significant cost savings.— IT Vendor Management, Australian Bank

Facing a Multi-Million Dollar Java Licensing Bill?

Oracle's employee-based Java metric has turned Java into one of the most expensive items in enterprise software portfolios — but it doesn't have to be. Our Java licensing specialists have helped banks, manufacturers, retailers, and Fortune 500 companies reduce their Java costs by 70–90% through strategic assessment, OpenJDK migration, and licence optimisation.

Java Compliance Assessment →Book a Consultation

Key Takeaways

For CIOs, ITAM professionals, and procurement leaders managing Oracle Java licensing:

1. Oracle's employee metric massively overcounts actual Java usage. Oracle's Java SE Universal Subscription requires licensing every employee regardless of Java usage. For most large organisations, fewer than 20% of employees actually use Java — meaning you're paying for enormous "shelfware." The first step to optimisation is understanding how many employees genuinely need Oracle Java versus the total headcount Oracle wants to charge for.

2. OpenJDK migration is the highest-impact optimisation lever. The vast majority of enterprise Java workloads can run on OpenJDK distributions (Temurin, Corretto, Zulu) at zero licence cost. This bank reduced its Oracle Java obligation by 86% primarily through strategic OpenJDK migration. See Oracle Java Licensing Changes — Updated Guide.

3. Java licensing training is a force multiplier. Java licensing was historically free, so most IT teams have no training in Oracle's Java rules. Educating your development, operations, and procurement teams on what triggers a Java licence obligation — and how to avoid unnecessary Oracle JDK installations — prevents compliance exposure from growing while you optimise.

4. Act before Oracle audits. Oracle is aggressively auditing Java usage, often starting with "friendly" usage reviews that escalate into formal audits. Organisations that proactively assess and optimise their Java position are far better positioned to defend against audit claims than those caught unprepared. See Oracle Java Audit Guide — How to Fight Back.

5. Savings compound as Oracle raises prices. Oracle's Java subscription is an annual commitment — and Oracle has a track record of increasing prices at renewal. The earlier you optimise your Java footprint, the more you save cumulatively. This bank's $4.3M annual saving translates to $12.9M over three years, and the gap widens with each renewal cycle.

☕ See how we've helped enterprises optimise Java licensing and defend against Oracle Java audits.

Java Licensing Case Studies →

📄

Oracle Java Audit & Licensing White Papers

Expert playbooks for defending against Oracle Java audits, understanding the employee-based metric, calculating your Java cost exposure, and developing an OpenJDK migration strategy.

Browse White Papers →

🔗 Official Oracle Resources

Oracle Java Technologies Overview
Oracle Java SE Downloads
Oracle Corporate Pricing
Oracle Java SE Support Roadmap

Java & Oracle Advisory Services

☕ Java Compliance Assessment 🛡️ Java Audit Defence 📋 Oracle Contract Negotiation 📊 Oracle Licence Management

Fredrik Filipsson

Co-Founder @ Redress Compliance

20+ years in enterprise software licensing. Former IBM, SAP, and Oracle. 11 years as an independent consultant advising hundreds of Fortune 500 companies on Oracle, Microsoft, SAP, IBM, Salesforce, and ServiceNow licensing, contract negotiations, and cost optimisation.

LinkedIn · View All Posts

Java Licensing Optimisation for an Australian Bank