Pricing-wise, it is very reasonable, with an initial pay-as-you-go structure, meaning the more you use, the higher the cost. Initially, we utilized a subscription-based model for enterprise licensing through Red Hat, and pricing included enterprise support, security patches, certified updates, and long-term maintenance. The initial setup cost was moderate due to the required enterprise planning; clustering, security, and environment configuration took time. However, once standardized, deployment became much more manageable and predictable. Licensing provided reliable enterprise support, stable certified releases, good documentation, and patch management. There were challenges as costs can significantly rise at larger scales, making it more expensive than alternatives such as Apache Tomcat, which was a lightweight container solution. For mission-critical enterprise Java applications, the stability and enterprise support justified the investment.
Senior Infrastructure Architect - Technology Transformation and infrastructure design at a computer software company with 10,001+ employees
Real User
Jul 7, 2021
JBoss is totally subscription-based and it's less costly for us. As a solution architect, I would say licensing is key. The cost involved in implementing the solution is a key factor now that most companies are looking to cut costs. WebSphere is really costly and less flexible. I think the JBoss subscription is quite competitive. Most people understand that the EAP kind of solution will save a lot of money in terms of licensing.
Learn what your peers think about JBoss Enterprise Application Platform. Get advice and tips from experienced pros sharing their opinions. Updated: June 2026.
JBoss Enterprise Application Platform offers modularity and flexibility to support on-premise and cloud installations, enhancing development efficiency with fast delivery, reduced costs, robust security, and seamless integration capabilities.JBoss Enterprise Application Platform is designed to facilitate rapid scalability and easy deployment for Java-based applications, offering valuable features such as high availability and efficient resource utilization. With options for performance...
Pricing-wise, it is very reasonable, with an initial pay-as-you-go structure, meaning the more you use, the higher the cost. Initially, we utilized a subscription-based model for enterprise licensing through Red Hat, and pricing included enterprise support, security patches, certified updates, and long-term maintenance. The initial setup cost was moderate due to the required enterprise planning; clustering, security, and environment configuration took time. However, once standardized, deployment became much more manageable and predictable. Licensing provided reliable enterprise support, stable certified releases, good documentation, and patch management. There were challenges as costs can significantly rise at larger scales, making it more expensive than alternatives such as Apache Tomcat, which was a lightweight container solution. For mission-critical enterprise Java applications, the stability and enterprise support justified the investment.
The customer needed to implement on a server with 32 processes, and the price from a local provider was approximately $64,000.
It is an open source solution.
The solution is cost-effective.
JBoss is totally subscription-based and it's less costly for us. As a solution architect, I would say licensing is key. The cost involved in implementing the solution is a key factor now that most companies are looking to cut costs. WebSphere is really costly and less flexible. I think the JBoss subscription is quite competitive. Most people understand that the EAP kind of solution will save a lot of money in terms of licensing.