Thank you to everyone who joined our Q4 2025 Pega As-a-Service Release & Roadmap webinar on January 15, 2026. Ivan Anikanov and Satya Mishra covered exciting developments in Pega Cloud, and we received several excellent questions during the session. Below you'll find the questions and answers from our live Q&A segment.

Watch the full webinar recording

Watch demo the latest MyPegaCloud features

Read the blog post

Question 1: Documentation for Switching from On-Premise to Pega Cloud

Question: What documentation would you suggest for different roles (admins, developers, architects) that are switching to Pega Cloud from on-premise?

Answer: The transition from on-premise to Pega Cloud is designed to be as seamless as possible for developers, with approximately 95% of the development experience remaining similar. The key differences involve areas like storage architecture, where developers need to understand cloud storage instead of local file directories.

We strongly recommend reviewing the Pega Cloud book on docs.pega.com, which provides comprehensive coverage of architectural differences, including SFTP configuration, cloud file storage, repository configuration, and other cloud-specific implementations. The documentation includes a dedicated journey specifically focused on migrating from on-premise to cloud environments.

Our migration team performs a thorough assessment of your on-premise deployment to calculate the necessary compute, storage, and infrastructure controls needed for Pega Cloud. They identify required changes, such as modifying local directory structure references in applications or planning database migrations from platforms like Oracle to Pega Cloud's supported databases. The migration team handles the majority of this work and provides clear guidance on any application changes required from your team.

Once live on Pega Cloud, the operational experience is largely consistent with on-premise, with the added benefits of enhanced security, automated maintenance, and self-service capabilities through MyPegaCloud.

Question 2: Authentication and Authorization for Blueprint Pipelines

Question: How about the authentication/authorization? Who is authorized to create new applications and pipelines with Blueprint?

Answer: Authentication and authorization for both Pega Blueprint and Deployment Manager are governed through MyPega's role-based access control system. Users need appropriate permissions and roles assigned through MyPega to create blueprints and access Deployment Manager for pipeline creation.

To create applications using Blueprint, users require access to Dev Studio along with the necessary MyPega permissions. Similarly, creating and managing deployment pipelines in Deployment Manager requires specific roles granted through MyPega. Access to MyPegaCloud for administrative functions is also controlled through the same MyPega authentication framework.

This centralized approach ensures consistent security and access management across all Pega Cloud services, allowing administrators to maintain precise control over who can perform various operations within their Pega Cloud environments.

Continue the Conversation

Have additional questions about Pega Cloud's Q4 2025 releases or 2026 roadmap? We'd love to hear from you! Share your questions, insights, or experiences in the comments below, or join the Pega as-a-Service Expert Circle for ongoing discussions with product experts and the wider Pega community.

Upcoming Events: Join us at the Pega Cloud Summit in February 2026 for more in-depth sessions on cloud innovations, including presentations from Satya Mishra and other product leaders.