Changes in Pega Platform ‘25 supported platforms 

These changes were announced in the recently released Pega ‘25.

• Non-containerized deployments (“virtual machine deployments”) are de-supported. Only Pega Docker images orchestrated with Kubernetes will be supported. Kubernetes provides cloud native scalability and reliability. See “Install and update Pega Platform”. 

• The move to Pega Docker images also results in all non-Tomcat app/web servers being de-supported (e.g., WebSphere, WebLogic, JBoss).  For questions on this, please see the Pega Infinity Deployment Changes FAQs. 

• Tomcat 10.1 is the only version supported in the Pega Docker image. Previous Tomcat versions will not be supported. Due to breaking changes in Tomcat 10.1, applications must be updated to avoid use of Java EE 8 in favor of Jakarta EE 9 as part of the Pega Platform ‘25 upgrade process. Comprehensive instructions on using the platform upgrade utilities, along with the update strategy, are included in the Pega Infinity ‘25 documentation. 

• In Pega Platform ‘25, Pega has evolved its internal caching and communications algorithms. As a result, Hazelcast has been removed as a product dependency. It will no longer be shipped with Pega software nor required as an external service. Please note that its use in previous versions will be supported for the standard support period. 

• Pega User Defined Functions (UDFs) for Reporting and Connect SQL capabilities (e.g., pr_read_from_stream) will no longer be supported in Staging (Production Level – 4) and Production (Production Level – 5) environments. However, application developers can continue leveraging them in Development (Production Level – 2) and Quality Assurance (Product Level – 3) environments to expedite development processes. 

Changes in Pega Platform ‘26.1 supported platforms 

These changes are anticipated in the upcoming Pega ‘26 release.

• Pega User Defined Functions (UDFs) for Reporting and Connect SQL capabilities (e.g. pr_read_from_stream) will no longer be operable in Staging and Production Environments. However, application developers can continue leveraging them in Development (Production Level – 2) and Quality Assurance (Product Level – 3) environments to expedite development processes. 

Changes in Pega Platform relational database support 

See the Support Lifecycle for Relational Databases in Pega’s Platform Support Guide. 

• PostgreSQL 16 is supported as of Q3 of 2025. 

• PostgreSQL 17 support is anticipated in 2026.

Other projected changes in 2026 

These changes are anticipated in upcoming releases during the 2026 calendar year: 

• De-supporting Java 17 and moving to a minimum of Java 21. 

• Java 25 support 

• Kafka 4.1 support 

• Elasticsearch 9 and OpenSearch 3 support 

As always, consult the up-to-date Platform Support Guide and Technology Support Roadmap for current and future technology support profiles for Pega Infinity. 

This general information about Pega’s product vision and future direction is for informational purposes only. These statements are not a commitment, promise or legal obligation to deliver any material, code, or functionality.  The development, release and timing of any features or functionality described for our products remains at our sole discretion. 

Communication Strategy update 

We are currently reviewing our communication strategy and are looking for ways to reduce the number of direct client advisories [CAD cases] created. Going forward we want to restrict CAD cases to specific 'calls to action' with clear instructions on what you need to do.  

As a result, when a CAD case is created for your account, you'll know you need to act upon it as soon as possible.  

Messages which are informational or require long term planning will be communicated by other methods. We'll provide more information on those methods in the near future.