Oracle Java SE SMB Pricing: What Changed and What You Will Pay

Oracle Finally Gives Small Businesses a Java Price Break

On October 8, 2026, Oracle published a new Java SE Universal Subscription Global Price List. For the first time since the employee-based metric was introduced in January 2023, small and mid-size companies are getting a real price break. For example, a company with 100 employees that would have paid $18,000 a year under the March 2023 price list will now pay $1,000.

In this blog, I will walk through what changed, what it will actually cost you, and the fine print you need to understand before you sign an order.

How Oracle’s New Java SE SMB Pricing Works

Under the March 1, 2023, price list, everyone paid per employee, per month (though Oracle would generally only sell it to you annually). Companies with 1 to 999 employees paid $15.00, and companies with 1,000 to 2,999 employees paid $12.00. There was no break for being small. A 10-person shop paid the same per-head rate as a 900-person company.

The new price list creates a separate “SMB Pricing” structure for organizations under 3,000 employees, priced annually instead of monthly:

• Up to 10 employees: $100 per year
• Up to 100 employees: $1,000 per year
• Up to 500 employees: $10,000 per year
• 501 to 2,999 employees: the Up to 500 entitlement ($10,000), plus $147.20 per year for each employee above 500

The enterprise pricing for 3,000 employees and above did not change at all. It still starts at $10.50 per employee per month for 3,000 to 9,999 employees and still bottoms out at $5.25 before you hit “Contact [Oracle Sales] for Details” at 50,000.

A couple of other things are worth noting. SMB pricing is only available directly from Oracle, not through resellers. And the price list now spells out a minimum one-year subscription term.

One small irony: $147.20 per year works out to $12.27 per employee per month. That is a little more than the old $12.00 rate for the 1,000 to 2,999 band. Mid-size companies still come out ahead, but only because the flat $10,000 for the first 500 employees is a good deal.

Old vs. New: What You Will Actually Pay

The savings are dramatic for the smallest companies, and they taper off as you approach 3,000 employees, where the old and new prices meet. All figures below are annual list prices in US dollars.

Above 1,000 employees, the savings level off at roughly $55,000 to $60,000 a year. That is essentially the value of getting your first 500 employees for a flat rate of $10,000.

The new list also fixes an odd quirk in the old one. Under the 2023 pricing, a company with 2,999 employees paid $431,856 a year, while a company with 3,000 employees paid $378,000. You literally saved money by hiring one more person (or buying one more license you didn’t necessarily need). Under the new pricing, 2,999 employees cost $377,852.80, which lines up almost exactly with the $378,000 price at 3,000.

The Fine Print in Oracle’s New Java Price List

This is where you need to slow down and read carefully. Oracle did not just lower prices; it also added specific rules for each band, denoted by footnotes listed at the end of each band pricing row: https://www.oracle.com/a/ocom/docs/corporate/pricing/java-se-subscription-pricelist-5028356.pdf

You Can’t Stack Java SE SMB Pricing Bands

Each SMB price buys one entitlement covering usage up to that band’s limit. The price list states that these entitlements may not be stacked, combined, or accumulated. In other words, if you have 200 employees, you can’t buy two “Up to 100” entitlements for $2,000. You must buy the “Up to 500” entitlement for $10,000.

That creates some steep cliffs. Going from 10 to 11 employees takes you from $100 to $1,000 a year. Going from 100 to 101 takes you from $1,000 to $10,000. If your headcount sits right at one of those boundaries, you need to know exactly where you stand.

Your Processor Limit Now Depends on Your Headcount

Under the old price list, the Employee metric allowed you to run Java on up to 50,000 server processors, regardless of company size. With the 0.5 core factor for Intel/AMD, that was 100,000 cores. Very few organizations ever came close to that limit, so most people did not have to worry about monitoring that threshold. 

The new price list ties the processor limit to the number of employees you license:

Desktops and laptops are still excluded from the processor count. But for servers, these limits are counted using Oracle’s standard Processor definition, with the core factor table applied. A 10-person company is capped at 1,000 processors, which is 2,000 x86 cores at a 0.5 core factor. A small software company or managed service provider with a large server footprint could easily blow through that.

This is clearly how Oracle keeps a small company with a big data center from riding the cheap SMB bands. If you exceed the limit, you must obtain an additional license from Oracle, and the price list just says to contact Oracle for pricing. We all know how those conversations tend to go.

Note that the Processor definition itself did not change at all. What changed is that it now actually matters to small customers, who will need to count server cores and apply core factors, not just count heads.

The Employee Definition Now Includes a Mid-Term True-Up

Who counts as an employee did not change. It is still all of your full-time, part-time, and temporary employees, plus those of your agents, contractors, outsourcers, and consultants who support your internal business operations. And it is still every employee, not just the ones who use Java.

However, the old definition required your licensed quantity to equal your employee count as of the effective date of your order. The new definition adds that if your employee count exceeds the number of licensed employees at any time during the subscription term, you must obtain an additional license from Oracle.

That is a significant change. If you grow during the year, take on a large outsourcing contract, or acquire a company, you now have an explicit contractual obligation to buy more licenses right away. And with non-stackable bands, crossing from 100 to 101 employees in the middle of your term is not a small true-up.

A Drafting Error, Just for Fun

The 2,999-employee pricing example in the new price list refers to an “Additional Employee for Java SE Universal Subscription (501-2999) definition below”. That definition does not exist anywhere in the document. The “Up to 2999” band label is also misleading, since it reads like a flat fee when it is actually a per-employee price. Nonetheless, the pricing calculations are clear, and maybe Oracle will correct that errant language in the examples sometime down the road.

Conclusion

For organizations under 3,000 employees, Oracle’s new SMB pricing is a genuine price cut, and in some cases a very large one. If you have been paying for a Java subscription under the 2023 Employee metric, you should be able to renew at the new rates. The Oracle Store (store.oracle.com) currently has 10 and 500 employee quantities showing for purchase. With over 500 employees, you need to contact Oracle Sales. I expect they will add the 100-employee quantity in short order.

But cheaper does not mean simpler. Before you sign, make sure you know your true employee count, including contractors and outsourcers. Know how close you are to the next band boundary, and how much you expect to grow during the term. And count your server processors, with core factors applied, against the new limits. A low price is not much of a bargain if it comes with an audit finding attached.

As always, the cheapest Java subscription is the one you don’t need. Moving to an NFTC-licensed version or an OpenJDK build may still be the better long-term answer for some of your estate.

If you would like help figuring out what the new pricing means for your organization, let us know. A Java licensing assessment will show you which installations actually require a subscription, and we have the experience to make sure you never pay Oracle more than you must. We have your back!