Embedded Java is a distinct question.
When Oracle Java is embedded in a product that you build and ship to your own customers, the licensing question is different from the question of running Java inside your own enterprise. Embedded use means the Java runtime is distributed as part of your application to end users who are not your employees. The way Oracle treats redistribution, and the interaction with the current Java SE Universal Subscription, creates a set of traps that are easy to fall into and expensive to discover at audit. This article is for independent software vendors, device manufacturers, and any organisation that ships software containing an Oracle Java runtime. We sit on the buyer side and have no interest in selling you Oracle Java.
The end of the free embedded path.
For many years Oracle offered specific licensing routes that allowed Java to be embedded in a product at modest cost or, under older terms, redistributed under permissive licenses. The licensing model has tightened significantly. The free public updates path closed, the old binary code license that permitted certain redistribution was replaced, and Oracle moved to subscription based licensing. The practical effect is that an organisation shipping Oracle Java inside a product can no longer assume the embedded runtime is free or cheap. The buyer side discipline is to stop relying on historical assumptions about embedded Java and to establish the current license basis for every product that ships a Java runtime.
The employee metric problem.
The current Java SE Universal Subscription is priced per employee of the subscribing organisation, counting all full time, part time, temporary, and contractor staff, not merely the people who use Java. This metric was designed for internal enterprise use and fits embedded distribution poorly. If an ISV subscribes under the universal metric to cover Java that it ships inside a product, the subscription cost is driven by the ISV's total headcount rather than by the number of products shipped or customers served. For a small software company shipping a widely deployed product, the employee metric can be either a bargain or a disaster depending on the ratio of headcount to deployment. The buyer side discipline is to model the employee metric cost carefully and to challenge whether it is the right basis for embedded distribution at all. We explain the metric in our Java SE Universal deal type page.
Embedded Java licensing checklist
- Identify every product that ships an Oracle Java runtime to customers.
- Determine the Java distribution, Oracle JDK or an OpenJDK build.
- Establish the current license basis for each redistributed runtime.
- Model the employee metric cost against your total headcount.
- Assess whether an OpenJDK build removes the Oracle license entirely.
- Document the redistribution terms for audit defence.
- Review any ISV or distribution agreement with Oracle before renewal.
The OpenJDK alternative.
The single most important option for embedded Java is OpenJDK. OpenJDK is the open source reference implementation of the Java platform, and high quality production ready builds are available from several providers at no license cost. For most embedded use cases an OpenJDK build is functionally equivalent to the Oracle JDK, and shipping it inside your product removes the Oracle license obligation entirely. The migration from Oracle JDK to an OpenJDK build is usually straightforward for standard applications. The buyer side discipline is to evaluate OpenJDK seriously before accepting an Oracle Java subscription for embedded use, because in many cases the right answer is to remove the Oracle dependency rather than to license it. We cover the broader compliance picture in our Java licensing pillar guide.
When Oracle Java is genuinely required.
There are cases where Oracle Java is genuinely required for embedded use, such as dependence on a specific Oracle feature, a certification requirement that names the Oracle JDK, or a support obligation that mandates Oracle's runtime. In those cases the licensing must be negotiated rather than accepted at list. The negotiation levers for embedded Java include challenging the employee metric basis, negotiating a redistribution specific agreement, capping the subscription growth, and securing favourable terms before a renewal when Oracle has the most leverage. The buyer side discipline is to treat an unavoidable Oracle Java dependency as a negotiation rather than a fixed cost, and to bring the same rigour you would bring to any Oracle deal.
The audit exposure for ISVs.
Organisations that ship Java are an audit target precisely because redistribution multiplies the deployment footprint. Oracle can argue that every installed copy of your product that contains the Oracle runtime is a licensable instance, and the numbers escalate quickly. The buyer side defence is to document the license basis for every redistributed runtime, to maintain records of which products ship which Java distribution, and to be able to demonstrate that OpenJDK builds carry no Oracle obligation. The defence is built before the audit, not during it. We handle Java audit exposure through our audit defense service, and any redistribution agreement should pass through a formal contract review before signature. The Java product itself is covered on our Oracle Java product page. For the sales pressure side, see our Java sales pressure tactics article.
Related resources.
- Java Licensing pillar guide
- Audit Defense service
- Contract Review service
- Java SE Universal deal type page
- Oracle Java product page
- Oracle Java Negotiation Guide 41 page reference paper.
- Java Sales Pressure Tactics related sub article.