You bought Oracle Java licenses years ago, and now you are unsure what you still own. The 2023 shift to the Java SE Universal Subscription changed how Java is sold, but it did not erase the perpetual rights many companies already hold. Knowing exactly what those rights cover is one of the most useful things you can do before any audit or renewal.

This guide explains Oracle Java perpetual license rights after 2023, what they let you keep using, and where the limits are. For the broader picture, see our pillar on Oracle Java licensing explained.

What changed in 2023, and what did not

In January 2023 Oracle moved new Java SE sales to the Universal Subscription, priced per employee. That change applies to new subscriptions. It did not retroactively cancel perpetual licenses that customers had already purchased under earlier models.

If you hold a perpetual Java SE license, you generally retain the right to use the versions and quantities it covers, under the terms in force when you bought it. The key is to know precisely what you bought.

What a perpetual license typically allows

Continued use of covered versions

A perpetual license usually lets you keep running the specific product and version it covers, without an ongoing subscription, for as long as the terms allow.

Support is a separate question

Perpetual use and active support are not the same thing. Support and the right to new updates often required a separate, time limited agreement. When that lapsed, your use right may continue while access to new patches did not.

Defined quantities and metrics

Older licenses were measured in processors or named users. Those metrics still define the scope of what you own. They do not convert automatically into the per employee model.

Why this matters in an audit. Oracle may present the per employee subscription as if it were your only option. If you hold perpetual rights, those rights are an asset that reduces what you need to subscribe to. Bringing them to the table changes the conversation.

Where the limits are

Perpetual rights are valuable, but they are not unlimited. Watch for these boundaries:

  • Version scope. A perpetual license covers specific versions, not every future release.
  • Updates and security patches. Newer updates may require a current subscription, even where use rights continue.
  • Quantity and metric limits. Use beyond the licensed processors or users is not covered.
  • Product scope. A license for one Java SE product does not extend to other Oracle products.

How to confirm what you hold

Do not rely on memory or on Oracle's summary. Confirm your position from your own records:

  • Locate the original ordering documents and license terms.
  • Identify the exact product, version scope, metric, and quantity.
  • Map your current deployment against what the license covers.
  • Note where support has lapsed and where updates have been applied since.
  • Keep this position paper ready for any audit or renewal.

Not sure what you still own?

We review your Oracle Java entitlements, confirm your perpetual rights, and use them to reduce what you need to buy.

Get a Quote

Using perpetual rights in a renewal

Perpetual rights are a starting asset in any negotiation. They can shrink the population that needs a new subscription and give you a credible alternative to Oracle's opening offer. The work is in proving exactly what you hold and matching it to your real deployment.

Go deeper

To understand how versions affect your position, read our Oracle Java version comparison, and if you are weighing a move away from Oracle Java, see our guide to Oracle Java versus OpenJDK migration.

Talk to a buyer side Java advisor

We defend your position and negotiate your Oracle Java subscription down. Fixed Fee from $18,000, or Gainshare, a share of verified savings or avoided exposure, with zero retainer and no risk to you.

Get a Quote Book a Strategy Call