Know what you hold before anyone calls
Which contract generation are you? Holders of the older per-user and per-processor subscriptions have generally been allowed to renew on legacy metrics, which for a company with contained Java usage is a position worth protecting like an heirloom. Run the agreement through the decoder and know exactly what you have, what its renewal terms say, and what conduct might forfeit it. Nobody should trade a grandfathered metric for a per-employee one absent a very deliberate calculation.
What is actually deployed? The exposure question is an inventory question: which machines run Oracle JDK builds, at which versions, under which license terms, versus the OpenJDK builds that carry no Oracle bill at all. Your SAM tooling answers this, and answering it internally, before any conversation with Oracle, is the entire game. The company that knows its estate negotiates. The company that does not gets audited into knowing it, at the auditor's valuation.
And when the outreach email arrives, it is the soft opening of the audit playbook, and the same rules apply: one owner, nothing volunteered, no calls without preparation, and no "quick usage review" run on Oracle's terms. Friendly is a tone, not a legal posture.
app.isvcosell.com/benchmarking/run
The quote in context: per-employee pricing benchmarked against modelled Java cohorts, by size and term.
THE SAME JOB, TWICE
TODAY, BY HAND
Oracle's friendly email about your JDK downloads arrives, and nobody knows which machines run Oracle builds versus OpenJDK.
A licensing manager digs out the old Java SE agreement, unsure whether it is a grandfathered per user contract or already on the per employee metric.
The Universal Subscription quote gets sanity checked against nothing, because nobody knows what comparable companies actually pay per employee.
The OpenJDK migration is discussed in hallways but never priced, so the estate drifts toward a headcount priced subscription by default.
Months of drift, ending in a quote priced on your entire payroll
WITH ISVCOSELL
Run the agreement through the decoder and establish which contract generation you hold, what its renewal terms say, and what conduct might forfeit a grandfathered metric.
Pull the deployment inventory from your SAM tooling: every Oracle JDK install, version, and license basis, counted before Oracle counts it for you.
Benchmark the per employee quote against modelled Java cohorts by size and term.
Open the Java playbook and price the OpenJDK migration as a real project, so the walkaway is a costed number, then treat the outreach with the audit defense sequence: one owner, nothing volunteered.
About a week to hold both futures priced, before the email gets a reply
What changes: the drift becomes a decision made on arithmetic. For a 10,000 employee company with contained Java usage, a per employee subscription can run into the millions a year for a handful of applications; a costed one time migration to OpenJDK typically competes with a small number of years of that bill, and answering the download email with a document instead of a shrug changes the entire conversation.
"The company that knows its estate negotiates. The company that does not gets audited into knowing it, at the auditor's valuation."
PART TWO
The real decision: subscribe, or make the estate boring
Java is the rare vendor negotiation with a genuinely complete alternative, because the technology's core is open source and the OpenJDK distributions, Eclipse Temurin, Amazon Corretto, Azul, Red Hat's builds and their peers, run the same workloads without an Oracle line item. For most estates the honest engineering assessment is that migration is a testing and rollout project, not a rewrite: swap the runtime, run the regression suite, handle the handful of components with genuine Oracle-specific dependencies, and manage patch cadence through the distribution's support channel or a commercial OpenJDK support contract that costs a fraction of the per-employee bill.
That does not make migration free, and pricing it honestly is the point. Testing time across hundreds of applications, the stragglers pinned to ancient versions, commercial support for the pieces that need a throat to choke: put real numbers on all of it, the same credible-alternative arithmetic that works on every locked-in vendor. What comes out, for most companies, is a one-time project cost that competes with a small number of years of Universal Subscription, and a permanent exit from a metric that scales with hiring rather than usage.
If subscribing genuinely fits, an estate deep in Oracle-specific tooling, GraalVM Enterprise needs, or simply a headcount small enough that the tiers are tolerable, then negotiate it like the enterprise agreement it is: the per-employee rate against the benchmark, the employee definition nailed down in writing, divestiture and reduction language for a metric that otherwise only ratchets, and a term that does not outlive your migration option. The subscription is not the mistake. The unexamined subscription is.
app.isvcosell.com/tooling
The Java playbook: the generation check, the migration math, and the negotiation, in one guided sequence.
PART THREE
The Java sequence, in five moves
1 Inventory before anything. Every Oracle JDK install, version, and license basis, from your own tooling, this quarter, whether or not Oracle has called yet. The estate you can name is the estate you can defend.
2 Protect a legacy contract like the asset it is. If you hold per-user or per-processor terms, decode the renewal mechanics and renew cleanly and early. The grandfathered metric is worth more than any discount you will ever negotiate on the new one.
3 Price the boring estate. The OpenJDK migration, costed like a real project: testing, stragglers, commercial support where wanted. This number is your walkaway, and unusually for a walkaway, it is usually true.
4 If you subscribe, subscribe on defined terms. Benchmarked rate, written employee definition, reduction rights, short term. The metric ratchets with headcount by design; the contract is where you install the brakes.
5 Treat the outreach as the audit it politely is not yet. One owner, the defense sequence, and your own count already done. The download-log conversation goes very differently when the answer to "what are you running?" is a document instead of a shrug.
The honest close: some organizations should pay Oracle for Java, because they use what only Oracle sells or value the single-vendor support posture, and the per-employee tiers at genuine enterprise scale can be tolerable when negotiated hard. What no organization should do is drift into a headcount-priced subscription because an email arrived and nobody knew the estate. Java's peculiar gift to buyers is that the alternative is real, mature, and mostly a matter of diligence. Vendors price your inertia everywhere. Here, unusually, the inertia is optional.
About the author
Morten Andersen, Cofounder, ISVCOSELL
Morten brings two decades of enterprise and software procurement, with stints across Oracle, IBM, SAP, and Salesforce shaping how he reads a deal. He has led sourcing through hundreds of renewals, from mid market order forms to nine figure global agreements, and learned that the buyers who win are the ones who walk in knowing the market. He built ISVCOSELL to make that pattern recognition repeatable.
More posts by Morten Connect on LinkedIn →
See it in the product
How benchmarking works → Browse the use cases → Every feature → Calculate your time saved →
FREE TRIAL · FULL PLATFORM · NO CARD REQUIRED
Price both Java futures before Oracle prices one for you.
The free trial opens the benchmarking database, 1,483 vendors deep, plus the negotiation guides, playbooks, and talking points for your own renewals. No card needed, a corporate email is all it takes.
Start your free trial → Or decode a contract free, no account
Free for 30 days, no card needed. Your data stays isolated at the database, and you can export or delete it any time.
Watch it in action
The audit letter Price the Fusion order What discount should we expect?
Browse the full demo library →
THE ISVCOSELL AI BRIEF · WEEKLY
The week in enterprise software buying, in one email.
What shipped on the platform, and the pricing and licensing moves worth knowing before your next renewal. One email a week, to your work address. Unsubscribe any time.
Subscribe