Oracle Java Embedded Licensing and OEM. The 2026 guide.

Embedded Java covers Java SE redistributed inside an Independent Software Vendor product, an Original Equipment Manufacturer device, or an enterprise built application packaged with a Java runtime. Each pattern carries a different commercial model.

This guide breaks the embedded Java licensing position into the ISV embedded model, the OEM device model, the royalty structures, the runtime choice between Oracle JDK and OpenJDK, and the audit defense playbook.

Read this alongside the Oracle Java licensing reference, the Java audit negotiations playbook, the Java knowledge hub, and the Oracle knowledge hub.

ISV embedded model in detail

The ISV embedded model covers an Independent Software Vendor that packages Java SE inside its product for redistribution to downstream end customers. The ISV holds the embedded Java contract. The end customer typically inherits the embedded runtime as part of the ISV product installation.

ISV embedded contract anatomy

• Redistribution scope. Defined Java SE version, defined product, defined geography.
• Royalty model. Per end customer, per device, per processor, or per employee at the downstream end customer.
• Support obligation. ISV obligation to provide first line support to downstream end customer.
• Security patch obligation. ISV obligation to ship security patches inside the product update cadence.
• Product roadmap commitment. Java SE version support timeline aligned to Oracle product lifecycle.
• Termination provision. Notice period, downstream end customer transition obligation.

Common ISV embedded patterns

ISV product type	Typical Java runtime	Royalty pattern
Enterprise content management	Eclipse Temurin or Oracle JDK 17	Per end customer per year
Engineering simulation	Amazon Corretto or Oracle JDK 11	Per workstation per year
Financial trading platform	Azul Zing or Oracle JDK 17	Per processor per year
Healthcare informatics	Eclipse Temurin or Oracle JDK 11	Per end customer per year
Industrial automation	OpenJDK or Oracle Java SE Embedded	Per device manufactured

OEM device model

The OEM device model covers an Original Equipment Manufacturer that ships hardware devices with Java SE pre installed. The OEM holds the embedded Java contract. The device end customer receives the device with the Java runtime as a factory installed component.

OEM contract anatomy

• Per device royalty. A fixed per device royalty paid by the OEM to Oracle per device manufactured or per device sold.
• Volume commitment. Minimum annual device count commitment with discount banding above the floor.
• Hardware platform scope. ARM, x86, RISC-V, or other architecture specific entitlement.
• Geographic scope. Distribution geography, frequently global.
• Support obligation. OEM obligation to provide device level support including the Java runtime.
• Security update obligation. OEM obligation to ship firmware level Java security updates.

Common OEM device patterns

• Set top boxes and media gateways. Historical Java ME and Java SE Embedded deployments. Most have migrated to Linux native or to OpenJDK.
• Point of sale terminals. Retail POS hardware with embedded Java for application runtime. Mixed Oracle JDK and OpenJDK adoption.
• ATM machines. Banking ATM hardware historically used Java SE Embedded. Migrating to OpenJDK or other runtime.
• Industrial control PLCs. Some PLC manufacturers ship with Java ME Embedded. Most have migrated to native code or to OpenJDK.
• Automotive infotainment. Some infotainment platforms used Java ME. Most have moved to Android Automotive OS or QNX.

Royalty structures across embedded models

Embedded Java royalty structures vary by deployment pattern. The contracted metric in the original ISV or OEM order form determines the count methodology and the audit data request format.

Royalty model comparison

Royalty model	Fits	Typical rate
Per device manufactured	OEM device shipments	0.50 to 4.00 USD per device
Per device sold	OEM with high return rate	1.00 to 6.00 USD per device
Per end customer installation	ISV with discrete end customers	800 to 5,000 USD per end customer per year
Per processor at end customer	ISV running server side	2,000 to 12,000 USD per processor per year
Per employee at end customer	ISV running client side broadly	5.70 to 15.00 USD per employee per month
Annual flat subscription	ISV or OEM with predictable volume	Negotiated band

Royalty protection clauses

• Annual escalator cap. 3 to 5 percent annual cap inside the original embedded order form.
• Volume discount banding. Step down rates above defined volume thresholds.
• True down provision. Right to reduce the contracted commitment value where downstream end customer or device volume drops.
• Exit notice provision. 30 to 60 day exit notice window with downstream end customer transition obligation.

Runtime choice between Oracle JDK and OpenJDK

The single most consequential decision in embedded Java sits at the runtime layer. Oracle JDK requires the contracted embedded license. OpenJDK distributions including Eclipse Temurin, Amazon Corretto, Microsoft Build of OpenJDK, and Azul Zulu Community carry no Oracle license requirement.

OpenJDK distribution catalog

Distribution	Steward	Support model
Eclipse Temurin	Eclipse Adoptium Working Group	Community plus commercial via members
Amazon Corretto	Amazon Web Services	Community, free Corretto support
Microsoft Build of OpenJDK	Microsoft	Community plus Microsoft commercial
Azul Zulu Community	Azul Systems	Community, paid Azul Platform Core
Red Hat OpenJDK	Red Hat	RHEL subscription bundled
BellSoft Liberica JDK	BellSoft	Community plus commercial

Runtime decision factors

• Production support requirement. Commercial support level required for the downstream end customer base.
• Performance sensitivity. Some workloads benefit from Azul Zing or Oracle GraalVM specialized JVM features.
• Security patch cadence. Quarterly aligned to Oracle Critical Patch Update, or commercial accelerated.
• Long Term Support window. Java 11, 17, 21 LTS release support timeline.
• Hardware platform coverage. ARM 64, x86 64, RISC-V availability across distributions.
• License inheritance. GPL v2 plus Classpath Exception inherited by all OpenJDK distributions.

Embedded Java audit defense playbook

Oracle audits embedded Java by working backward from the downstream end customer to the ISV or OEM that holds the embedded license. The audit data request typically covers redistribution count, support contract status, security patch posture, and version inventory.

Audit sequence for embedded Java

1. Audit letter to end customer. Oracle opens with the downstream end customer who deploys an ISV product containing Java.
2. End customer escalates to ISV. The end customer escalates the Java audit to the ISV under the product support contract.
3. ISV produces embedded contract. The ISV produces the embedded Java contract showing the upstream commercial relationship with Oracle.
4. Oracle audits ISV embedded contract. Oracle audits the ISV directly against the contracted redistribution scope and royalty terms.
5. Settlement at the ISV level. Settlement order signed between Oracle and the ISV, with downstream end customer position resolved.

Buyer side audit defense moves

• Document the embedded redistribution scope. Defined Java SE version, defined product, defined geography from the original ISV or OEM order form.
• Validate the metric application. Per device, per end customer, per processor, per employee against the contracted metric.
• Verify the deployment evidence. Active downstream end customer count, device count, processor count, employee count.
• Identify OpenJDK migration scope. Portion of downstream deployment already on OpenJDK with no Oracle license requirement.
• Counter on verified evidence. Settlement at the verified deployment count, not the Oracle opening claim.

OpenJDK migration playbook

The OpenJDK migration from Oracle JDK eliminates the Oracle Java license dependency for the migrated portion of the deployment. The migration runs in three phases: technical compatibility, distribution adoption, contractual amendment.

Migration phases

1. Technical compatibility testing. Test the embedded application across the target OpenJDK distribution. Validate JVM tuning parameters, garbage collector behavior, JNI compatibility, monitoring instrumentation.
2. Pilot deployment. Roll OpenJDK to a pilot downstream end customer cohort. Monitor performance, stability, and support load over a 60 to 90 day window.
3. Full rollout. Roll OpenJDK across the full downstream end customer base. Phase the rollout across the product release cadence to minimize disruption.
4. Contractual amendment. Amend the original Oracle embedded contract to reflect the reduced Oracle JDK deployment count. Recover the contracted royalty on the migrated portion.
5. Deprecation. Deprecate the Oracle JDK dependency in the next major product release. Lock the OpenJDK distribution as the supported runtime.

Migration risk register

• JIT performance variance. Some workloads see 5 to 12 percent JIT performance variance between Oracle JDK and OpenJDK at first run, typically converging within 90 days of monitoring.
• Security patch cadence variance. Free OpenJDK distributions ship security patches on community cadence, which can lag the Oracle Critical Patch Update by 14 to 60 days.
• Native library compatibility. JNI native libraries built against Oracle JDK headers occasionally need rebuild against OpenJDK headers.
• Monitoring tool compatibility. Some Application Performance Monitoring tools have varying support across OpenJDK distributions.
• Support contract continuity. Downstream end customer support contracts referencing Oracle JDK need amendment language for OpenJDK.

Five recommendations for 2026

1. Inventory the embedded Java estate. Every ISV product, every OEM device, every enterprise application that packages a Java runtime. Version, distribution, deployment count.
2. Decide the runtime per pattern. Oracle JDK with embedded license, OpenJDK with no license, or hybrid by product line.
3. Migrate the easy patterns first. Enterprise applications with internal deployment and standard JDK usage migrate to OpenJDK in 6 to 12 weeks.
4. Renegotiate the ISV or OEM order form annually. True down the contracted royalty as the migration progresses.
5. Engage independent advisory before audit response. Embedded Java audit defense requires independent advisory with no Oracle channel conflict.

What to do next

1. Pull the embedded Java contract portfolio. Every ISV embedded contract, every OEM device contract, every Java SE Universal Subscription with embedded redistribution rights.
2. Inventory the deployed runtime. Across every ISV product release, every OEM device generation, every enterprise application.
3. Model the OpenJDK migration cost benefit. Quantify the contracted royalty savings against the migration cost.
4. Run a pilot OpenJDK deployment. Select the highest royalty cost pattern and run a 90 day pilot.
5. Engage independent advisory. Independent on embedded Java means no Oracle channel partner status, no Oracle resale revenue, no Oracle implementation partner conflict.

Frequently asked questions

How Redress engages on embedded Java

Redress engages on embedded Java licensing through Vendor Shield, the Oracle services practice, the Renewal Program, and the Benchmark Program.

Read the related Java licensing reference, the Java audit negotiations playbook, the Java knowledge hub, the Oracle knowledge hub, the ULA decision framework, the Java license calculator, the contract renewal strategy, the contract negotiation service, the database licensing guide, the benchmarking page, the about us page, and the contact page.