For most of its life, Java was the part of the stack nobody budgeted for. It shipped with the operating system image, it ran everywhere, and finance never saw it. That era ended in stages, and the final stage arrived when Oracle introduced the Java SE Universal Subscription priced per employee. Under that model, an organization that wants a commercial Oracle Java SE subscription pays for its total employee count, not for the servers or the users that actually touch Java. For a company with twenty thousand employees and a few hundred Java installations, the quote that lands on the table is sized to the company, not to the footprint. That is how a runtime most people thought was free became a recurring agenda item in budget reviews.
This article is part of our series on Oracle licensing on OCI, and it covers the corner of that topic that surprises people most pleasantly: Oracle's own cloud is the one place where Oracle Java does not carry a separate price tag. We will lay out the entitlement, draw the boundary around it carefully, and then do something Oracle's own material will not do, which is tell you when the entitlement does not matter at all because free OpenJDK builds already solve your problem.
How Java became a board level cost question
A short history makes the present situation legible. In 2019 Oracle ended free public updates of Oracle JDK 8 for commercial use, and organizations that wanted patched Oracle binaries needed a Java SE subscription, then priced per processor for servers and per named user for desktops. In 2021 Oracle softened the picture with the No Fee Terms and Conditions license for Java 17 and later, which allows free commercial use of current Oracle JDK versions, but only until a defined period after the next long term support release, after which continued patching again requires a subscription. Then in 2023 Oracle replaced the legacy metrics for new customers with the Java SE Universal Subscription, priced per employee across the whole organization.
The per employee metric is what changed the conversation. Under the old metrics, a contained Java estate produced a contained bill. Under the employee metric, the bill is decoupled from usage: one licensable installation can, in Oracle's framing, justify a subscription sized to the entire workforce. Organizations renewing legacy Java agreements have found themselves quoted the new metric at renewal, often at multiples of the previous cost. Whatever one thinks of the model, the practical effect is that CIOs and CFOs now ask pointed questions about where Java runs and why, and the answer to those questions interacts directly with cloud platform decisions.
What Oracle includes with OCI
Here is the OCI angle in one sentence: Oracle includes the entitlement to use Oracle Java SE, including the commercial features and access to support, for workloads running on OCI compute at no additional charge. If your application runs on an OCI compute instance, a container on OCI, or an OCI platform service, you may run the Oracle JDK there, patched and supported, without buying a Java SE Universal Subscription for those workloads. The entitlement covers the things that historically separated the commercial Oracle JDK from the free builds: advanced monitoring and diagnostics such as Java Flight Recorder and Mission Control, access to older patched versions, and the right to raise support requests through My Oracle Support for Java issues on OCI.
This is not a promotional credit or a time boxed offer. It is a standing program benefit of running on OCI, and Oracle uses it explicitly as a migration incentive: bring your Java workloads to our cloud and the Java licensing question disappears for those workloads. For an organization staring at a per employee subscription quote, that sentence understandably gets attention. The discipline is to read it precisely, because the boundary of the entitlement is exactly where the misunderstandings start.
What it covers, and what it does not
The entitlement attaches to where the Java process runs. Oracle Java executing on OCI compute is covered. Oracle Java executing anywhere else is not, and moving some workloads to OCI does nothing for the rest of the estate. This second point is the one that gets glossed over in sales conversations, so it deserves to be stated plainly: the Java SE Universal Subscription is priced per employee, and your employee count does not change because thirty percent of your Java workloads now run on OCI. If you need a subscription for the on premises and other cloud remainder, you need it for the full employee count, the same as before the migration. The OCI entitlement only changes your total Java cost if it lets you take the subscription count to zero, or if it is one part of a broader plan to eliminate licensable Oracle Java use everywhere else.
| Where Java runs | Oracle JDK | OpenJDK and third party builds |
|---|---|---|
| OCI compute and OCI services | Included with OCI at no additional charge, commercial features and support included | Free, as everywhere |
| On premises servers | Requires a Java SE subscription, or current versions under the no fee license with its time limits | Free, support optional from the distributor |
| Other public clouds | Requires a Java SE subscription on the same terms as on premises | Free, support optional from the distributor |
| Employee desktops | Requires a subscription once licensable use exists, and the per employee metric counts everyone | Free |
Two further boundary notes. First, the entitlement is about Java as a runtime on OCI; it does not license Oracle middleware products that happen to be written in Java. WebLogic, for example, has its own licensing logic on OCI, including a restricted use Java entitlement that comes with WebLogic licenses themselves, and we cover that whole topic in BYOL for WebLogic on OCI. Second, the entitlement is also distinct from the database licensing choices that dominate the rest of this series; picking between license models for the database tier, which we treat in BYOL versus License Included, has no bearing on Java, because the Java entitlement on OCI is simply included rather than chosen.
GraalVM: the same idea, extended
The Java entitlement on OCI has a sibling that performance minded teams should know about. Oracle GraalVM, the high performance JDK with the native image compiler that turns Java applications into fast starting native executables, is also free to use on OCI, including the features that were once part of the paid GraalVM Enterprise edition. Beyond OCI, Oracle has moved GraalVM toward broader free availability under its newer free license terms, so certain GraalVM editions are now free for production use anywhere. For teams containerizing Java services, native image can cut cold start times and memory footprints dramatically, and on OCI you get the Oracle supported toolchain for it without a separate commercial agreement. As with everything in this article, the precise edition and license boundaries have shifted more than once, so check the current terms before standardizing on a particular distribution.
The honest part: OpenJDK was always free, everywhere
An independent article has to say what a vendor article will not. The Oracle Java entitlement on OCI is only valuable if you specifically want Oracle's Java. OpenJDK, the open source reference implementation that Oracle JDK itself is built from, is free for any use on any platform, and high quality third party builds of it are produced and patched by serious organizations: Eclipse Temurin from the Adoptium project, Amazon Corretto, Azul's builds, Red Hat's builds, and others. For a very large share of Java workloads, these distributions are functionally interchangeable with the Oracle JDK, and organizations have migrated thousands of applications to them precisely to step out of the Java subscription question altogether. Those builds are just as free on OCI as they are anywhere else.
So the OCI entitlement matters to a specific audience: organizations that want Oracle's binaries for certification or policy reasons, that depend on the commercial features in production, that want a vendor support contract behind their runtime, or that simply do not have the appetite to validate and migrate hundreds of applications onto a different distribution. For that audience the entitlement is genuinely valuable. For an organization already standardized on Temurin or Corretto, it changes nothing, and pretending otherwise would be selling rather than advising.
The audit context you should plan around
Java has become one of the most active areas of Oracle license review activity, and the pattern is well documented across the industry. Oracle retains records of which organizations downloaded Oracle JDK binaries and security patches, and that download history shows up in outreach: a polite email noting downloads, asking about Java usage, and proposing a conversation. These soft inquiries are the front end of a process that can escalate, and the per employee metric raises the stakes of getting the response wrong, because the remedy Oracle proposes is rarely sized to the installations found.
The defensive posture is unglamorous and effective: know what you actually run before anyone asks. That means a real inventory of Java installations, version by version and vendor by vendor, distinguishing Oracle JDK from OpenJDK builds, and distinguishing licensable use from use that is covered, whether by the no fee terms, by a restricted use entitlement bundled with another Oracle product, or by running on OCI. Organizations that respond to outreach with confident, accurate data have a fundamentally different negotiation than organizations that discover their estate during the inquiry. We cover how Java audits fit into the broader pattern of Oracle license questions in our answers to twenty CIO questions on OCI licensing.
Counting Java in an OCI business case
When an OCI migration is on the table for other reasons, the Java entitlement deserves a deliberate line in the model rather than a footnote. For estates heavy in Java, the arithmetic can be material: every workload that lands on OCI compute is a workload whose Oracle Java runtime needs no subscription, and if the migration scope covers the whole licensable Java footprint, the subscription itself may become avoidable. The mirror image also matters: a partial migration leaves the per employee subscription intact for the remainder, so the model should only credit Java savings that the migration actually unlocks. The clean way to build the case is to model three scenarios side by side: status quo with a subscription, migration to OCI with the entitlement, and a distribution switch to OpenJDK builds with or without paid third party support. The right answer is often a blend, with OCI workloads on Oracle Java, the remainder on OpenJDK, and the subscription either eliminated or shrunk to a deliberately chosen scope.
One standing caveat belongs in every version of this analysis: program terms change. Oracle has revised Java licensing repeatedly in recent years, in both directions, and the OCI entitlement is defined by Oracle's current program documentation, not by blog posts, ours included. Before a business case is signed off or a subscription is terminated, verify the current Oracle Java on OCI terms in writing and keep a copy of what you relied on.
A six step framework for the Java position
Whether or not OCI is in your future, the work below is the foundation for every good Java decision, and it is exactly the homework that makes both migrations and audit responses go well.
- Inventory every Java installation. Use discovery tooling and package data to find every JDK and JRE across servers, containers, build agents, and desktops, with version and patch level. The estate is always larger than anyone believes.
- Classify Oracle JDK against OpenJDK. For each installation, identify the vendor of the binary and the license it runs under. This single classification step separates the licensable footprint from the noise.
- Map what moves to OCI. Mark which workloads are in scope for the migration and would inherit the OCI entitlement, and which will remain on premises or in other clouds and keep their current licensing position.
- Decide a distribution strategy per tier. Choose deliberately where you want Oracle Java, where an OpenJDK build is the standard, and where GraalVM earns its place, rather than letting each team improvise.
- Quantify the subscription impact. Price the scenarios honestly under the per employee metric, remembering that the subscription only goes away when licensable use outside OCI goes away.
- Document the position. Write down the inventory, the classifications, the entitlements relied on, and the dates, so that any future inquiry is answered from a file rather than from a scramble.
Where we fit, and where we do not
Our role in this picture is the platform side. Through our OCI consulting practice we design the landing zones, plan the migrations, and build the architecture that lets a Java estate actually take advantage of the OCI entitlement, and we structure that work the way we structure everything: a fixed project fee for defined migration and design work, a Managed Monthly retainer for teams that want the estate run and reviewed on a cadence, and an Optimization fee charged as a percent of verified savings for engagements whose whole point is reducing spend. The Java entitlement and the license type reviews from elsewhere in this series are standing items in that optimization work.
What we deliberately do not do is play Oracle contract lawyer. For Java audit defense, subscription negotiations, and the contractual fine print of the per employee metric, independent licensing specialists handle the contract side while we handle the OCI architecture side. The two disciplines work best together: the licensing specialists establish what you owe and what you can negotiate, and we change the architecture so that next year the answer is smaller. We are not Oracle and not a reseller, which is precisely why we can tell you when OpenJDK is the better answer and when the OCI entitlement is worth building a migration around.
Free white paper
Go deeper on this topic with The Oracle ULA Exit Playbook, certification, BYOL, and using a credible OCI position as renewal leverage. An independent analyst style report with comparison tables and recommendations, free with a work email. Prefer a monthly summary instead? The OCI Brief delivers one practical OCI briefing a month.
Part of a series
This guide is part of OCI Cost & Licensing — our complete pillar guide on the topic.
Moving Oracle workloads to OCI, or already running on OCI and not sure the architecture or the spend is right? Most teams bring in a specialist before they commit to a region, a shape, or a Universal Credits number. OCISpecialists.com plans the landing zone, runs the migration, and manages the estate after go live, on a fixed project fee, a managed monthly retainer, or a cost optimization fee paid only on verified savings.