The Java band table, where one employee is worth $269,874
Two companies one employee apart can be $269,874 a year apart, and that is not a discount question: it is what happens when the band rate applies to the whole ordered quantity rather than to the excess. The ladder produces cliffs, the cliffs produce six windows where ordering more than your headcount is strictly cheaper, and no Oracle quote arrives with any of it modeled.
Prepared by Redress Compliance · August 7, 2026 · Oracle advisory. Based on 35 to 45 Java pricing engagements worked 2024 to 2025.
Executive summary
The band rate applies to everyone, which makes cliffs. The Java SE Universal Subscription ladder runs from $15.00 to $5.25 per employee per month across eight published bands, and the rate applies to every employee in the order, not only those above the threshold.
The result: a company with 9,999 employees pays $1,259,874 a year at list while a company with 10,000 pays $990,000, one extra person removing $269,874 from the annual bill.
Six windows exist where ordering up is strictly cheaper. For every band edge there is a range below it where a larger order costs less in absolute terms: the widest runs from 7,858 to 9,999 employees, worth up to $269,874 a year, and the largest single saving, $377,919, sits at the 30,000 edge.
This is arithmetic, not a loophole, and in four of our engagements the customer sat inside a window nobody on the Oracle side had mentioned. There is no reason they would.
The larger order also buys true up immunity.
The worked case: an 8,500 employee company ordering 8,500 pays $1,071,000 a year, ordering 10,000 pays $990,000, saving $81,000 a year while carrying 1,500 employees of growth headroom at no cost, roughly three and a half years of protection at 5 percent annual growth.
The right comparison is the whole term including the true up you did not have to have.
The published rate is not the cost.
An annual uplift of up to 8 percent compounding turns a three year commitment at $1.62 million a year into roughly $5.26 million rather than $4.86 million, and roughly one order in three carries a minimum annual floor of $50,000 to $100,000 that stops the bill falling when headcount does.
The uplift cap, the floor, and the renewal quantity clause decide the term; the band decides only its first year.
The published bands, and the cliff at every edge
| Employee band | List per employee per month | Annual list at the band edges |
|---|---|---|
| 1 to 999 | $15.00 | $180 to $179,820 |
| 1,000 to 2,999 | $12.00 | $144,000 to $431,856 |
| 3,000 to 9,999 | $10.50 | $378,000 to $1,259,874 |
| 10,000 to 19,999 | $8.25 | $990,000 to $1,979,901 |
| 20,000 to 29,999 | $6.75 | $1,620,000 to $2,429,919 |
| 30,000 to 39,999 | $5.70 | $2,052,000 to $2,735,932 |
| 40,000 to 49,999 | $5.25 | $2,520,000 to $3,149,937 |
| 50,000 and above | Quoted by Oracle | Negotiated, and can settle below $5.25 |
The ladder is steep at the bottom and flat at the top. Moving from the first band to the second cuts the rate 20 percent; moving from the 30,000 band to the 40,000 band cuts it under 8.
The practical consequence: small and mid sized organizations gain most from band positioning, large ones from negotiated discount, and above 49,999 the ladder stops and everything is a quote. Verify the current ladder against Oracle's published material before modeling, because list prices move.
The six windows, exactly where ordering up wins
| If your count is between | Order instead | Break even headcount | Maximum annual saving |
|---|---|---|---|
| 801 and 999 | 1,000 | 800 | $35,820 at 999 employees |
| 2,626 and 2,999 | 3,000 | 2,625 | $53,856 at 2,999 |
| 7,858 and 9,999 | 10,000 | 7,857 | $269,874 at 9,999 |
| 16,364 and 19,999 | 20,000 | 16,363 | $359,901 at 19,999 |
| 25,334 and 29,999 | 30,000 | 25,333 | $377,919 at 29,999 |
| 36,843 and 39,999 | 40,000 | 36,842 | $215,931 at 39,999 |
The Java renewal and exit brief
The full commercial framework around the band table: the uplift caps, the floor clauses, the renewal quantity language, and the exit paths priced against staying.
Get the white paper →How to order up safely, and where not to
- Order a quantity, never misstate a headcount. The licensed quantity must be at least your employee number and nothing stops it being more; the count itself is never inflated in a written representation.
- Get the rate on the ordering document, quantity and unit price stated explicitly, because the band applies to what is ordered, not what was discussed.
- Model the floor interaction: a larger quantity can push you above a minimum that would otherwise have bound.
- Fix the renewal clause: a larger quantity is a larger renewal base unless the contract renews on the then current count, so ask for the reduction right.
- Skip the smallest band: below 800 employees, ordering 1,000 costs more than ordering your actual number.
The tactical execution is symmetrical and quiet: ask for both quotes in writing at the same time, one at the counted headcount and one at the band edge quantity, on identical terms.
Oracle sales teams price what they are asked to price, and the second quote comes without argument because it is a larger quantity at a published rate. Keep the reasoning internal; there is no advantage in explaining the arithmetic to the account team and no requirement to.
Who lands inside the count in the first place, contractors and consultants included, is its own dispute, and the metric's full mechanics sit in the employee metric analysis.
- Percentile standing for your exact deal size and industry, from real closed transactions
- Scenario simulation before the call: test alternative terms and see the financial impact of each
- A negotiation playbook, talking points, and a two page executive brief on day one
What we saw across Java pricing engagements, 2024 to 2025
Across roughly 35 to 45 Oracle Java engagements Fredrik Filipsson worked in 2024 and 2025, not one Oracle quote arrived with the band edge modeled:
Every quote priced the stated headcount at the band it fell into, and nothing else.
Sitting where a larger order was strictly cheaper, with nobody on the Oracle side mentioning it.
The term mechanics decide as much as the band: the compounding uplift converts headline list into materially more over three years, the floor clauses in one order in three convert falling headcount into flat bills.
And the renewal quantity language decides whether the band position survives the term.
The wider pricing context sits in the Java pricing analysis, the free alternatives in which Java versions are free, and the audit posture that shadows every count conversation in the Java audit defence sequence.
Your first five moves
- Locate your headcount on the ladder and check the six windows, because a position inside one is money on the table every year.
- Request both quotes in writing simultaneously, counted headcount and band edge quantity, on identical terms.
- Cap the uplift and price the floor, because the published rate is year one and the compounding is the term.
- Write the reduction right into the renewal clause, so the ordered quantity does not become a ratchet.
- Model the whole term, true up included, because the headroom is half the value of ordering up. The Java calculator and the Oracle practice run the math with you.
Frequently asked questions
How much does the Oracle Java subscription cost per employee?
Between $15.00 and $5.25 per employee per month at list across eight published bands, with the rate applying to every employee in the order, not only those above the threshold. Above 49,999 employees the ladder stops and pricing is quoted, often settling below $5.25.
Verify the current ladder before modeling, because list prices move.
Why can ordering more Java employees than you have be cheaper?
Because the lower band rate applies to the whole quantity: at 9,999 employees the annual list is $1,259,874 and at 10,000 it is $990,000, so the larger order is $269,874 cheaper.
Six windows exist where this holds, the widest from 7,858 to 9,999 employees, and the arithmetic survives any discount applied equally to both quotes.
Is ordering above headcount allowed on the Java subscription?
Yes: the licensed quantity must be at least your employee count, and nothing prevents ordering more.
The discipline is to order a quantity rather than misstate a headcount, get the quantity and unit price stated on the ordering document, and never inflate the count itself in any written representation.
What does the Java subscription really cost over a term?
More than the band suggests: an annual uplift of up to 8 percent compounding turns a three year commitment at $1.62 million a year into roughly $5.26 million rather than $4.86 million.
And one order in three carries a minimum annual floor of $50,000 to $100,000 that stops the bill falling with headcount.
The uplift cap and floor terms decide the term.
What headroom does ordering at the band edge buy?
True up protection: the 8,500 employee company ordering 10,000 saves $81,000 a year and carries 1,500 employees of growth room, roughly three and a half years at 5 percent growth, removing the most common mid term price event entirely.
The whole term comparison, including the avoided true up, is the honest one.
Will Oracle offer the band edge quote?
If asked, yes: request both quotes in writing at the same time, the counted headcount and the band edge quantity on identical terms, and the second is produced without argument because it is a larger quantity at a published rate.
No quote in our 35 to 45 engagements arrived with the edge modeled unprompted, and there is no reason it would.
How to Negotiate the Oracle Java Employee Agreement: Honest Leverage in a Captive Deal
Priced per employee, every employee, from $15 down to $5.25. At renewal your leverage is thin and OpenJDK threats rarely land. The one-year runway, trading through the wider Oracle relationship, and containing what you sign.
