Changes in Pega Platform ‘25 supported platforms

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

• 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 will also result 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 will be 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, will be included in the Pega Infinity ‘25 release notes.

• 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 prior Pega releases still have the dependency on Hazelcast and its use in those versions will be required and 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 supported platforms

These changes are anticipated in the upcoming Pega Platform ‘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 (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 relational database support

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

• PostgreSQL 16 will be supported in Q3 of 2025.
• Due to changing support statements from Oracle related to on-premises deployments, Oracle 23ai support is being investigated. Oracle has extended support for 19c through 2032.

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.