The SDLC: Deployment Manager session at Pega Cloud Summit 2026 brought together Madhuri Vasa, Product Owner for Deployment Manager, and host Ivan Anikanov, Technical Solutions Director at Pega EMEA Consulting, for a focused, practical look at how Deployment Manager (DM) is transforming the way teams release Pega applications on the cloud. Whether you are new to Deployment Manager or looking to level up your CI/CD maturity, this session delivered clear, actionable guidance. A recording of the session is available via the Pega Cloud Summit 2026 event page.
What Is Deployment Manager — and Why Does It Matter?
At its core, Deployment Manager Service is a no-code, automated CI/CD solution built exclusively for Pega Cloud. Unlike generic DevOps tooling, DM is purpose-built to understand Pega-native paradigms — the situational layer cake, guardrails, and ruleset versioning — making it uniquely suited to the Pega SDLC.
Madhuri framed the value proposition simply: DM gives teams a "shift-left" strategy — catching quality, security, and compliance issues earlier in the development lifecycle, before they become costly production incidents.
With near-zero infrastructure level setup required, teams can be operational from day one.
From Day Zero to Value: A Practical Onboarding Approach
One of the session's most useful takeaways was Madhuri's recommended adoption path:
- Start with gated merges — enforce quality gates and unit test checks before any code is merged.
- Automate deployments to higher environments — remove manual handoffs between Dev, QA, UAT, and Production.
- Add stability gates — integrate PDC (Pega Diagnostic Cloud) checks as deployment quality signals.
This staged approach means teams can begin generating value immediately while progressively increasing their automation maturity.
Stitching CI and CD Together
A key capability highlighted in the session is the ability to stitch Continuous Integration (CI) with Continuous Delivery (CD) using the "Trigger Deployment" task. When a developer successfully merges code directly from Dev Studio, DM can automatically trigger the downstream deployment pipeline — eliminating manual intervention from the release manager and accelerating the path to production.
Madhuri also highlighted intelligent dependency management: DM automatically recommends functional dependencies, such as shared layers and reusable components, enabling Release Managers to handle complex modular applications without requiring a deep architectural review from a Lead System Architect at every step.
GenAI Meets DevOps: The DevOps Assistant
One of the standout features introduced in the session was the DevOps Assistant, a GenAI-powered capability embedded directly within Deployment Manager. It helps practitioners answer functional questions about pipelines and — critically — diagnoses failed deployments by surfacing the likely root cause and suggesting next best actions. This brings intelligent automation to a part of the SDLC that has traditionally relied heavily on manual troubleshooting.
Visibility and Metrics That Matter
The session also covered two powerful reporting capabilities:
- Application Quality Report — tracks trends in guardrail scores, unit testing success rates over time and adherence towards best practices in deployments, giving teams a clear picture of application health.
- Pipeline Report — monitors industry-standard DORA metrics: deployment frequency, lead time for changes, change failure rate, and mean time to recovery. These are the metrics that engineering leadership and clients increasingly expect.
Practical Q&A Highlights
The session featured a lively Q&A. A few highlights:
- Hotfix handling — rather than creating a separate pipeline, use the "stage-level skip" feature within your standard release pipeline to fast-track a fix to production.
- Rollbacks — DM now supports environment-level rollbacks to specific restore points generated during deployment, making recovery from a bad release significantly less stressful.
- Artifact security — the deployment artifact (product file) never leaves the client's VPC; it is stored in a secure repository (typically an S3 bucket) shared across root-to-live environments.
Reflection
Post summit we asked our presenters to reflect on their experience and Madhuri has provided powerful insight:
"I personally stepped out knowing our responsibility just grew. I had seen the audience welcoming and involving into the session with questions asked on real time day-to-day scenarios. The more trust clients place in the vision, mission, and capabilities of the product, the more we must obsess over guardrails, clarity, and realistic problem statements from predictable DevOps modeling to visible and improving release maturity to environment readiness to compliance, and auditability" - Madhuri Vasa.
What's Coming Next
The roadmap is equally exciting. Madhuri previewed three capabilities on the horizon:
- Case Data Migration — moving production data to non-production environments with automated data masking, enabling more realistic troubleshooting.
- Autopilot Test Execution — running UI-based tests generated by Pega Autopilot directly within Pega Cloud infrastructure.
- Accelerated Onboarding — automatic pipeline creation as soon as a new application is imported via Pega Blueprint, closing the loop on the "Blueprint to Go-Live" journey.
Join the Conversation
Have questions about Deployment Manager, or want to explore how it fits into your SDLC strategy? The Pega as-a-Service Expert Circle is the place to go — a dedicated community for clients, partners, and practitioners to share insights, ask questions, and access exclusive webinar content.
You can also join the Q&A conversation thread directly on the Community and post any follow-up questions you may have — our team will make sure they are answered.
