Payara Platform Release Stream and Software Changes

Payara

Starting with our June 2020 release (coming soon!), we’re rolling out separate editions of Payara Server and Payara Micro – collectively known as the Payara Platform.

We’ll now provide a Payara Platform Enterprise Edition, designed to increase stability and security in production environments and provide customers with access to production-oriented features, tools, and capabilities; and a Payara Platform Community Edition, targeted for developers looking to play with the latest features and APIs during development before potentially moving to Payara Enterprise in production.

Enterprise vs Community Landscape JPG-01-1

 

What’s Changing?

In the past, you may remember that the Payara Platform offered three release streams:

  • Community – quarterly releases containing new features, bug fixes, and patches, available to all Payara Server and Payara Micro users.
  • Features – monthly patches and fixes added to the regular quarterly releases, available to customers only.
  • Stability – monthly bug fixes and security patches and no new features for 12 months to boost the stability of production environments, available to customers only.

The Stability Stream and Features Stream are now combining to form Payara Platform Enterprise. Instead of choosing between the potential instability of the Features stream, or having no features for 12 months in the Stability stream, customers receive the benefits of both with Payara Server Enterprise or Payara Micro Enterprise. Payara Platform Enterprise is designed for stability and security in production environments and new features are added to Payara Platform Enterprise after they have been thoroughly tested for stability.

Learn more about why you should choose Payara Enterprise, the features and benefits, and included support options:

{{cta(’34d3a46c-2d44-4544-aa7f-1d0cc48d2cb3′)}}

The Community Stream becomes the Payara Platform Community Edition and provides a frequent release cycle to drive faster innovation. Payara Server Community and Payara Micro Community are dedicated to rapid change and innovation, giving developers a place to play with the latest features of the Payara Platform as soon as possible.

Learn more about Payara Platform Community Edition here:

{{cta(‘9e3c808d-8f20-4c7f-81a8-5450d37a2ae2’)}}

What do the Changes Mean for You?

If you’re running Payara Server or Payara Micro in production environments, you should move to Payara Platform Enterprise – our fully supported and stable version designed for mission critical systems.

{{cta(‘1edeca72-b437-4cce-9d4c-26465137ba6e’)}}

Comments (0)

Post a comment

Your email address will not be published. Required fields are marked *

Payara needs the contact information you provide to us to contact you about our products and services. You may unsubscribe from these communications at any time. For information on how to unsubscribe, as well as our privacy practices and commitment to protecting your privacy, please review our Legal & Privacy Policy.

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Related Posts

Timeline showing Payara Platform Enterprise 4, 5, and 6 support phases (Full, Extended, Lifetime) from 2023–2033, along with JDK 8, 11, 17, and 21 support periods and end-of-life markers. 4 minutes
Thought Leadership

Understanding the Payara Platform Enterprise Software Lifecycle: How We Support Long-Term Stability 

Keeping an application server running smoothly isn’t so much about new features, but more about predictability and consistency. Software […]

Patrik Dudits presenting at Devoxx Belgium 2025 5 minutes
Cloud & Microservices

Devoxx BE 2025: It Only Starts with a Container & How Abstraction Becomes Reality 

At Devoxx Belgium 2025, I was able to talk about what happens after you build your container. In theory, […]

payara qube logo 5 minutes
Payara

Payara Cloud Is Now part of Payara Qube family of Unified Platforms for Enterprise Java

Payara Cloud is becoming part of Payara Qube family of Java application deployment runtimes. This move reflects how the […]