Exit Strategy for Java in Third Party Apps.

The Java buried inside third party applications is the hardest part of an estate to see and the easiest to overpay for. A buyer side exit separates the Java you are actually responsible for licensing from the Java the vendor already covers.

The Java you cannot easily see

Most Java exits handle the visible estate well: the runtimes IT installed and the applications the business wrote. The hard part is the Java bundled inside third party applications, where a vendor ships its own copy of a Java runtime as part of its product. Since January 2023 the Universal Subscription has priced Java SE at 5.25 to 15.00 dollars per employee per month, counting every full time and part time employee, every contractor, and every temporary worker, regardless of who uses the application. The risk with bundled Java is twofold. You may pay Oracle for runtimes a vendor already licenses, or you may carry exposure for an Oracle build a vendor quietly installed. An exit has to resolve both.

Who is responsible for the bundled runtime

Indicative. The single most valuable document in this work is a written statement from each vendor about what Java its product ships and who licenses it.

Separate real dependence from assumed dependence

The core buyer side move with third party applications is to separate real Oracle dependence from assumed dependence. A vendor that bundles its own free runtime, or that licenses an Oracle runtime under its own agreement, removes that application from your licensing problem entirely. A vendor that merely certified against Oracle but relies on a runtime you install has not created a real dependency, only a tested one. Pressing each vendor for a written statement of what its product ships, and who licenses it, is what turns a fog of assumed exposure into a short list of genuine ones. The technique for pressing those claims is in vendor support requirements during exit.

The discovery problem

Bundled Java is also a discovery problem, because LMS audits intensified in 2026 with a three year lookback, and Oracle's tooling can detect an Oracle runtime wherever it sits, including inside a third party install directory. A buyer needs the same visibility Oracle has. That means scanning for every Java runtime in the estate, recording where it came from, and matching each one to a responsible party. A runtime you cannot account for is exposure you cannot defend, so discovery is the foundation of the whole exercise.

Resolving each application

Once each third party application is mapped, the resolution is one of three. Where the vendor licenses the Java, you document it and exclude it. Where the application relies on a runtime you install, you move it to a free OpenJDK build, exactly as you would any other workload. Where a genuine Oracle dependency remains, you keep it as part of a scoped residual contracted to its true size, never against your full headcount. The discipline of containing that residual is in the residual subscription after an exit.

Exiting third party Java in five moves

1. Discover every runtime. Scan the estate, including inside third party install directories.
2. Trace each to a source. Record which product shipped it and who licenses it.
3. Get vendor statements in writing. Confirm coverage for vendor licensed runtimes.
4. Move the runtimes you own. Replace ones you install with a free build.
5. Scope the genuine residual. Keep only real Oracle dependencies, at true size.

What resolving third party Java is worth

Bundled Java is where exposure hides and where overpayment hides too. Resolving it both removes runtimes you should never have counted and closes the gaps an audit would exploit. Across our buyer side work, clients who account for third party Java properly reach an average reduction of 68 percent versus Oracle's opening number. We sit between you and Oracle, we never take vendor money, and we run the discovery and the vendor correspondence with you. A Fixed Fee starts from $18,000, agreed up front. Or choose Gainshare, a share of verified savings or avoided exposure, with zero retainer and no risk to you. We have defended more than $120M in Java exposure and over 300 Java audits, with more than 20 years of combined experience.

Where to go next

Third party Java is the part of the exit that rewards patience and evidence. Ground the work in our Oracle Java licensing guide for 2026, then read partial migration as an exit strategy to see how these applications fit a phased plan. To map the bundled Java in your own estate, book a Strategy Call.