Does Running Java on Oracle Cloud Change Your Subscription Position?

Oracle bundles free Java into every OCI subscription, and that is genuine value that no other cloud matches. It is also the single easiest boundary to misjudge, because a partial migration cuts your employee-metric bill by exactly nothing.

The short answer: OCI is the one cloud where Oracle Java is free, and that is exactly why it is dangerous

Oracle's own Cloud Infrastructure blog (July 24, 2023) states it without hedging: an OCI subscription includes licenses and full support for all Oracle Java SE and Oracle GraalVM versions at no extra cost. The JDK License FAQ confirms the mechanism, entitling OCI customers to use Oracle Java SE Products per the Oracle PaaS and IaaS Universal Credits and Service Descriptions. This is not a promotional credit or a time-boxed offer. It is a standing program benefit that Oracle uses explicitly as a migration incentive.

So yes, running Java on OCI changes your position, but only for the JVM that is actually running on OCI compute. Everywhere else on your estate the Java SE Universal Subscription and its employee metric still apply in full. The trap is not the entitlement. The trap is assuming the entitlement spreads. It does not. If you take one thing from this page, take this: OCI is the exception, and precisely because it is the exception, it is the one cloud where the boundary is easiest to get wrong. See our 2026 cloud and container licensing reality for how this fits the broader estate.

OCI Java is free at the point of use. The employee-count bill for everything else does not move because thirty percent of your workloads now run on OCI.

What the OCI entitlement actually covers, in contract terms

The Oracle Java SE license text grants a nonexclusive, nontransferable, limited license for only four permitted uses: Personal Use, Development Use, Oracle Approved Product Use, and Oracle Cloud Infrastructure Use. OCI Use is defined tightly. It refers to your use of the Programs on Oracle's Cloud Infrastructure with the OCI products identified in the PaaS and IaaS Universal Credits Service Descriptions (the current version effective June 25, 2024), and only during the period in which you maintain a subscription for those OCI products. Two words in that definition carry all the risk: "on" and "during."

The benefit is worth having. It covers the features that historically separated the commercial Oracle JDK from the free builds: Java Flight Recorder, Mission Control, access to older patched versions, and the right to raise support requests through My Oracle Support for Java issues on OCI. In market terms, that is a meaningful package for a shop that genuinely wants Oracle's JDK and Oracle's support. But the grant attaches to OCI compute, not to your organization. Oracle JDK installed on developer laptops, build machines outside OCI, or end-user desktops is explicitly out of scope.

That final row is the one buyers miss. If you migrate a workload off OCI, to your data center or to another cloud, the OCI Java right does not travel with it. The Oracle JDK that was free on OCI becomes ordinary, subscription-governed Oracle Java the moment it runs elsewhere. There is no grace period and no portability. The instant the JVM boots off OCI, you either hold a Universal Subscription or you are out of compliance.

The employee metric you think you are escaping

To understand why the partial-migration trap costs real money, you have to understand what the subscription actually meters. The Java SE Universal Subscription is sold by an employee-based metric, not by installs, cores, or actual Java usage. Published pricing starts at $15 per employee per month, dropping to $5.25 and lower at the largest tiers (above 50,000 employees). Crucially, "employee" is expansively defined. Oracle counts all your full-time, part-time, and temporary employees, plus all the full-time, part-time, and temporary employees of your agents, contractors, outsourcers, and consultants that support your internal business operations.

Oracle's own worked example makes the scale unmistakable. A company with 28,000 total counted personnel (23,000 direct plus 5,000 contractors) at $6.75 per month lands at $2,268,000 per year. Independent analysis (Java Negotiations, May 18, 2025) notes that a 20,000-employee enterprise can exceed $1.6M annually at list, even if only 5 percent of those people are developers or Java users, because the subscription must cover all 20,000. The metric is deliberately disconnected from your Java footprint. That disconnection is the whole point, and it is why OCI's inclusion looks so attractive on paper. We break the math down in the employee licensing 2026 guide and the bill-increase forecast.

The partial-migration trap, quantified

Here is the mechanism that turns an apparent saving into zero. Your employee count does not change because a slice of your Java workloads moved to OCI. If any Oracle Java remains on-premises, on AWS, on Azure, or on a single build server, and you want that remainder licensed, you need a Universal Subscription for the full employee count, the same as before the migration. The subscription is not fractional. It does not scale down to the workloads left behind. Moving 30 percent of Java to OCI leaves you paying 100 percent of the employee-metric bill for the other 70 percent.

That produces a hard, binary set of clean outcomes (Oracle Software Licensing advisory, June 23, 2025). Either consolidate all Oracle Java onto OCI and remove Oracle JDK everywhere else, or replace Oracle's JDK with a supported free OpenJDK distribution off OCI while using the OCI inclusion where you are on OCI. Both eliminate the per-employee charge. A half-measure eliminates nothing. In 25 years of watching Oracle position cloud incentives, this is the classic structure: the migration carrot is real, but it only pays if you complete the migration to the last JVM.

The clean outcomes are binary. Consolidate everything onto OCI, or remove Oracle JDK entirely off OCI. A 70 percent OCI migration still costs you 100 percent of the employee bill.

OCI versus AWS and Azure: the multicloud reality

The comparison most buyers actually face is not OCI versus on-premises. It is whether OCI's Java inclusion should steer a multicloud architecture. The blunt answer: a strategy that runs Java on AWS or Azure compute gains nothing from the OCI inclusion for that compute, because the inclusion is OCI-specific and does not travel. If your center of gravity is AWS or Azure, OCI's free Java is irrelevant to those workloads.

And the hyperscalers already solved this without Oracle. Amazon Corretto is distributed under GPLv2 with the Classpath Exception at no cost to you, and Amazon does not charge for its use or distribution regardless of where it runs. Microsoft's Build of OpenJDK is similar, with commercial support available but scoped to workloads running on Azure. The strategic contrast matters: Eclipse Temurin, Amazon Corretto, Azul Zulu, BellSoft Liberica, and Red Hat OpenJDK price the copies you run (or nothing at all), not the people you employ. That is the opposite of Oracle's headcount model. Our analysis of managed Java runtimes across the three hyperscalers and the BYOL versus provider OpenJDK choice covers this ground for architects.

Note one edge case so nobody trips on it. Oracle Database@AWS runs OCI hardware inside AWS data centers, but it does not change these rules. Universal Credits cannot pay for that service; it is sold and billed through the AWS Marketplace on your AWS bill (House of Brick, February 13, 2026). Do not assume that OCI-adjacent offerings inherit OCI Java use rights. They follow their own commercial terms.

The JMS and telemetry angle: OCI as an audit input

There is a quieter risk in choosing OCI for Java. OCI's Java Management Service gives Oracle visibility into your Java estate. Telemetry that helps you manage Java on OCI is the same telemetry that documents where Oracle JDK runs, versions, and usage. Based on our audit-defense experience, any Oracle-operated inventory mechanism should be treated as a potential audit input, not just an operations tool. The inclusion is genuine, but it comes with Oracle knowing your Java footprint in a way that a self-managed OpenJDK estate does not expose. If you run JMS, scope carefully what it reports and to whom, and understand that data can inform a later compliance conversation. See how autoscaling and container patterns amplify this in the processor-cap analysis and the Docker base image problem.

What buyers should actually do

Treat the OCI inclusion as a tactic inside a total-exit strategy, not as a strategy in itself. The value only lands if you reach one of the two clean endpoints. Here is the decision path we run with clients.

• Inventory first. Map every place Oracle JDK actually runs: OCI, on-prem, AWS, Azure, laptops, build agents. The OCI benefit is worthless as a plan until you know the remainder. Our exit migration map is the framework for this.
• Decide the endpoint before you migrate. Either all Oracle Java consolidates onto OCI, or Oracle JDK leaves your estate entirely (OCI keeps its free inclusion, everything else moves to a free OpenJDK build). Do not start a migration whose end state still leaves stray Oracle JDK off OCI.
• Assume the employee bill until Oracle JDK is fully gone. Any residual Oracle JDK off OCI, even on one build machine, re-triggers the full employee-count subscription. Price your plan against the full metric until you can certify zero off-OCI Oracle JDK.
• For multicloud, default to portable OpenJDK. Corretto, Temurin, and Zulu price the copies you run, not your headcount, and travel across every environment. Reserve Oracle JDK for OCI workloads only, if at all.
• Control JMS telemetry. If you use OCI's Java Management Service, understand it as a data source Oracle can leverage. Scope its reach deliberately.
• Model the true saving. Compare the OCI-consolidation path and the full-OpenJDK path against your current or projected Universal Subscription. In our experience the OpenJDK exit usually wins on flexibility because it does not lock your architecture to one cloud.

The leverage sits with you only if you commit to a clean endpoint. Oracle's incentive is designed to pull workloads onto OCI while the employee-metric subscription quietly persists on the remainder. That is not a saving; that is a migration that funds Oracle twice. Read the OCI inclusion for exactly what it is: a real, bounded, non-portable benefit that pays off only at the point of total consolidation or total exit. For the wider cloud strategy context, see adapting your cloud licensing strategy.

Related advisory: the full topic guide.

Frequently asked questions

Is Oracle Java really free on OCI?

Yes, for the running JVM on OCI compute. An OCI subscription includes Oracle Java SE and GraalVM at no extra Java charge, under the OCI Use rights defined in the PaaS and IaaS Universal Credits Service Descriptions. It covers commercial features like Java Flight Recorder and My Oracle Support access. It is a standing benefit, not a promotion.

Does running some Java on OCI reduce my Java SE subscription cost?

No. The subscription is priced per employee, and your employee count does not change when workloads move to OCI. If any Oracle Java remains off OCI (on-prem, AWS, Azure, or even a build server), you still need the full employee-count subscription. Only total consolidation or full OpenJDK exit removes the charge.

Does the OCI Java benefit travel if I move a workload off OCI?

No. The benefit attaches to OCI compute and does not travel. The moment a JVM runs off OCI (in your data center or another cloud), it becomes ordinary Oracle Java governed by the Universal Subscription. There is no grace period.

Do I get any Java licensing advantage running on AWS or Azure?

Not from Oracle's OCI inclusion, which is OCI-specific. But AWS offers Amazon Corretto and Azure offers the Microsoft Build of OpenJDK, both free. Portable OpenJDK builds like Temurin, Corretto, and Zulu price the copies you run rather than your headcount, which is why multicloud buyers usually avoid Oracle JDK off OCI entirely.

Is OCI's Java Management Service an audit risk?

Treat it as a potential audit input. JMS gives Oracle visibility into where Oracle JDK runs, which versions, and how it is used. That operational telemetry is the same data that can inform a later compliance conversation, so scope carefully what it reports and to whom.

Does Oracle Database@AWS inherit the OCI Java use rights?

No. Oracle Database@AWS runs OCI hardware inside AWS data centers but follows its own commercial terms. It is billed through the AWS Marketplace and cannot be paid with Universal Credits, so do not assume it carries OCI Java entitlements.