Employee for Java SE Universal Subscription – What is it?
Oracle has recently published a new pricing model for Java SE subscriptions, replacing the old Named User Plus Licensing (user licenses) and Processor licenses (server licensing) with a new license model called “Employee for Java SE Universal Subscription.” This new pricing model is based on the number of employees, with different price tiers for different ranges of employee numbers.
The new pricing model has generated many questions and concerns among Java SE customers and users. In this article, we will explore the key aspects of the new pricing model, its impact on existing customers, and the options available for customers and users.
What is the new pricing model for Java SE subscriptions?
- Oracle has replaced the old Named User Plus Licensing (user licenses) and Processor licenses (server licensing) with a new license model called “Employee for Java SE Universal Subscription.”
- The new pricing model is based on the number of employees, with different price tiers for different ranges of employee numbers:
- $15.00 Employee for Java SE Universal Subscription employees 1-999
- $12.00 Employee for Java SE Universal Subscription employees 1,000-2,999
- $10.50 Employee for Java SE Universal Subscription employees 3,000-9,999
- $8.25 Employee for Java SE Universal Subscription employees 10,000-19,999
- $6.75 Employee for Java SE Universal Subscription employees 20,000-29,999
- $5.70 Employee for Java SE Universal Subscription employees 30,000-39,999
- $5.25 Employee for Java SE Universal Subscription employees 40,000-49,999
What happens to existing Java SE customers?
- Oracle has stated in its FAQ that existing customers may renew their subscriptions on existing terms and pricing.
- However, it is expected that Oracle sales teams will not renew orders under the older licensing model and will instead try to convince customers to switch to the new employee license metric.
What should existing Java SE customers do?
- Review your current Java licensing situation, as many organizations may not realize that they also need to license older versions of Java, such as those that have not been upgraded to Java 11 or later or have not applied security patches.
- With a clear understanding of your current Java licensing position, you can design a strategy to determine whether it is feasible to move away from Oracle Java
