
Overview
High customer expectations and increasingly distributed systems mean disruptions to digital service can have catastrophic effects on sales, brand loyalty, and operating costs. The PagerDuty Operations Cloud deflects unnecessary work from teams and subject matter experts so they can focus on delivering business value. Urgent work is escalated to the right teams and routine work is made self-service. Teams can automate and accelerate issue resolutions with minimal human interruption -and improve system resilience and team capacity while reducing the strain of operational complexity and the unexpected.
With more than 700 integrations, APIs, and apps for customer service, the PagerDuty Operations Cloud empowers rapid responses in any environment. And thanks to more than 10 years of data ingestion, its machine learning-powered AIOps functionality can reduce alert noise by up to 98% and drive down MTTR with critical context for faster triage and effective automation.
PagerDuty integrates with various AWS services, including AWS CloudWatch, Amazon GuardDuty, AWS CloudTrail, AWS Personal Health Dashboard, Amazon EventBridge, AWS Security Hub, Amazon DevOps Guru, AWS Control Tower, AWS Outposts, and AWS S3 Storage Lens.
AIOps PagerDuty AIOps helps teams reduce noise, triage efficiently to drive the right actions towards resolution, and remove manual, repetitive work from the incident response process. Noise reduction baked in with an ML model that learns and adapts based on user behavior means teams see fewer incidents overall. And automating toil from manual event processing results in greater efficiency, saving teams valuable time for innovating.
Process Automation PagerDuty Runbook Automation is a managed cloud service that enables DevOps teams and SREs to create and delegate operational tasks in automated runbooks to other stakeholders such as developers, NOC personnel, and incident responders. Runbook Automation provides automated workflows and task automation focused on IT and developer process automation. Examples include service provisioning, CI/CD, configuration management, incident diagnosis and remediation, and more. With PagerDuty Runbook Automation, you can resolve requests in minutes, rather than days, optimize security and compliance, and give your engineers more time to spend on innovation rather than firefighting.
Incident Response PagerDuty helps you save time and money by bringing together the right teams with the right information to resolve incidents faster. Replace manual processes with automation to streamline incident response, freeing up time and resources for more innovation. Orchestrate end-to-end incident response with a service ownership model that only brings in the teams you need. Over 21K organizations trust PagerDuty to help them adopt DevOps best practices and build more resilient operational practices to minimize costly downtime and protect the customer experience.
Custom Private Offer We can create a custom offer tailored to your needs. Please contact us at aws-sales@pagerduty.com
Highlights
- Incident Response - Manage incidents end-to-end
- Process Automation - Automate and delegate business and IT processes
- AIOps - Maximize IT capacity with fewer incidents and faster resolution
Details
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Buyer guide

Financing for AWS Marketplace purchases
Pricing
Dimension | Description | Cost/12 months |
|---|---|---|
Professional | On-call and incident response for growing teams | $252.00 |
Business | Streamlined incident response for the enterprise | $492.00 |
CustomerServProfessional | Bi-directional comms between CS & Dev, protect SLAs, & lower MTTR | $252.00 |
CustomerService Business | Bi-directional comms between CS & Dev, protect SLAs, & lower MTTR | $492.00 |
Runbook Automation | Automate manual procedures in runbooks | $1,500.00 |
Automation Actions | Add-on: Automate steps to diagnose & remediate incidents | $240.00 |
Live Call Routing | Add-on: For on-call schedules & escalations (by line) | $1,890.00 |
Runbook Auto Job Runner | Add-on: For Runbook Automation | $750.00 |
Stakeholder Users | Bundle of 50 Stakeholder users | $1,800.00 |
PagerDuty Status Pages | 1000 User Pack | $1,068.00 |
The following dimensions are not included in the contract terms, which will be charged based on your usage.
Dimension | Cost/unit |
|---|---|
Additional events over contracted value | $0.06 |
Vendor refund policy
All fees are non-cancellable and non-refundable except as required by law.
Custom pricing options
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
Software as a Service (SaaS)
SaaS delivers cloud-based software applications directly to customers over the internet. You can access these applications through a subscription model. You will pay recurring monthly usage fees through your AWS bill, while AWS handles deployment and infrastructure management, ensuring scalability, reliability, and seamless integration with other AWS services.
Support
Vendor support
Our team provides multiple resources for customers to find answers to questions and get help with our product. Users may browse our integration guides (pagerduty.com/integrations) to integrate with partner tools, our knowledge base (support.pagerduty.com) to learn more about using PagerDuty, and our developer docs (developer.pagerduty.com) to use our APIs. Additionally, anyone can interact with other PagerDuty users and PagerDuty employees via the PagerDuty Community (community.pagerduty.com). Our Support team is available during regular business hours around the globe, Monday through Friday, and can be contacted at: Email: support@pagerduty.com or via a ticket submitted at tickets.pagerduty.com
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.

Standard contract
Customer reviews
Real-time monitoring has reduced downtime and ensures failed jobs are resolved quickly
What is our primary use case?
We receive a notification if there are any failed jobs or operations. We have some Bamboo agents working, so if one of the jobs fails on one of these servers, PagerDuty Operations Cloud creates an incident and notifies us. We use PagerDuty Operations Cloud for monitoring purposes, and it works great for our current needs.
What is most valuable?
The best features PagerDuty Operations Cloud offers include quick access to failed jobs and the ability to add descriptions about the failed job. The quick access allows us to rapidly identify which job or operation has failed because it sends the job name or the operation name that has failed.
I have heard that integration between our systems and PagerDuty Operations Cloud was easy to implement. For efficiency, we can monitor our deployment process in real time. For incident response, PagerDuty Operations Cloud creates alarms that make calls to the specific person who can handle these issues.
We have fewer missed incidents because it keeps calling regarding the incidents until they are resolved. We have also reduced downtime because we notice errors and failed jobs, and we work to fix them.
What needs improvement?
The system is very smooth right now.
For how long have I used the solution?
We have been using the solution for about one year.
What do I think about the stability of the solution?
We have not experienced any stability issues.
What do I think about the scalability of the solution?
We have not experienced any scalability issues.
How are customer service and support?
We did not try to reach out to customer service because we did not face any issues.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
I prefer not to use previous solutions.
How was the initial setup?
I joined the team after they had already purchased and configured PagerDuty Operations Cloud, so I did not have knowledge about the setup process.
What about the implementation team?
I do not have any experience with the implementation team.
What was our ROI?
Time saved.
What's my experience with pricing, setup cost, and licensing?
There was no relationship between setup cost and other factors.
Which other solutions did I evaluate?
We did not consider alternate solutions.
What other advice do I have?
PagerDuty Operations Cloud is a great tool that saves time and is worth starting to use. I would rate this product nine out of ten because nothing is fully perfect. My overall review rating for this product is nine out of ten.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
On-call teams have reduced downtime and respond faster through integrated alerting workflows
What is our primary use case?
My main use case for PagerDuty Operations Cloud is monitoring and on-call management for downtime.
Recently, we had a service go down last week, and we were alerted via PagerDuty Operations Cloud of the issue. One of our on-call engineers responded to the page and quickly resolved the problem through PagerDuty Operations Cloud app.
What is most valuable?
The best features PagerDuty Operations Cloud offers include the ability to integrate its app through various platforms such as Teams and various monitoring platforms such as New Relic and DynaTrace. It is easy to use, easy to log in and configure your on-call rotation, as well as utilizing their business services and technical services to properly configure how you want things monitored and alerted.
The integrations and easy configuration help our team by saving time and reducing errors. We use Terraform to create various modules, including integrations with PagerDuty Operations Cloud and our monitoring platform, New Relic . When a team creates a new application, we ask them to use our monitoring module to monitor their service using New Relic and PagerDuty Operations Cloud. By doing that, we save time and errors by preventing people from manually having to set up their PagerDuty Operations Cloud operations; it is all done through this module, which is easy to use.
PagerDuty Operations Cloud has positively impacted our organization by allowing us to be immediately paged when a system or service is down, enabling us to quickly respond and provide updates to the organization on issues and their resolution.
This quick response has led to measurable improvements, with reduced downtime and faster incident resolution times, as our on-call engineers are appropriately alerted when things happen. We understand based on the page what is going on and how to quickly respond to it, and if we need help, we can loop in other engineers and our managers that own the product to resolve it quicker.
What needs improvement?
PagerDuty Operations Cloud can be improved by using automation or AI to advance the product in such a way that it allows the implementation of automation to resolve issues or speed up workflows.
For how long have I used the solution?
I have been using PagerDuty Operations Cloud for six years.
What do I think about the stability of the solution?
PagerDuty Operations Cloud is stable.
What do I think about the scalability of the solution?
Its scalability is impressive; it scales very well, allowing us to add licenses, add services, and more very quickly and easily.
How are customer service and support?
The customer support is great; we have never had an issue when reaching out to someone in customer service when we have questions.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
Previously, we were using New Relic for monitoring, which sent us alerts when issues went down, but we ended up using PagerDuty Operations Cloud alongside it because PagerDuty Operations Cloud is used for on-call alerting.
How was the initial setup?
Our experience with pricing, setup cost, and licensing has been straightforward and easy. We have been using PagerDuty Operations Cloud for several years, so our pricing and cost have definitely increased over time, especially as we have hired additional engineers. Adding additional users and/or licenses is very straightforward, and we have always had a good experience with customer service from PagerDuty Operations Cloud side.
What was our ROI?
The best return on investment comes from being alerted and paged for ongoing issues or new issues appropriately, allowing us to set up those schedules and engineers. The fact that PagerDuty Operations Cloud allows us to be alerted when things go down and configure how our engineers are alerted speaks to the return on investment due to the quick response it facilitates.
What's my experience with pricing, setup cost, and licensing?
Our experience with pricing, setup cost, and licensing has been straightforward and easy. We have been using PagerDuty Operations Cloud for several years, so our pricing and cost have definitely increased over time, especially as we have hired additional engineers. Adding additional users and/or licenses is very straightforward, and we have always had a good experience with customer service from PagerDuty Operations Cloud side.
Which other solutions did I evaluate?
I did not evaluate other options before choosing PagerDuty Operations Cloud.
What other advice do I have?
I recommend PagerDuty Operations Cloud as a great service and application to anyone that needs to improve their on-call process at their company. I gave this product a rating of 10.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
On-call automation has reduced downtime and has enabled faster incident response at scale
What is our primary use case?
PagerDuty Operations Cloud is a platform that helps teams manage incidents, automate operations, and ensure system reliability by bringing alerts, on-call schedules, and real-time responses into one place. When we had to push things into production, we set up PagerDuty schedules on a weekly or biweekly basis. If an issue occurred at night, a roster would pop up, and the respective engineer would have to handle that use case.
A specific incident where PagerDuty Operations Cloud helped my team was during the peak season in America when lakhs of orders were placed in December, and a major S1 severity production issue suddenly happened. If no monitoring tool had been in place, the company would have faced doomed circumstances, incurring lakhs of dollars in losses. PagerDuty came to our rescue at the last moment when nothing was happening. At 3:00 a.m. my time, I received a message and subsequently a call while sleeping, and I learned that this issue had occurred. I logged in quickly, promptly fixed that issue, and within an hour or so, the issue was resolved with minimal damage. I even received appreciation for my quick response.
PagerDuty Operations Cloud helps in similar situations because whenever some issue happens and we are not aware of it, PagerDuty comes with a flag telling us that there is an issue that needs to be fixed before it becomes a major problem.
What is most valuable?
Some of the best features PagerDuty Operations Cloud offers are comprehensive incident management, automation, and AI operations, all integrated into one platform. Second, it provides noise reduction and smarter alert grouping through global intelligent alert grouping that uses machine learning to group and correlate alerts across services. It also provides automation to reduce toil and speed up resolutions and artificial intelligence, including generative AI assistance, to help teams respond faster and smarter. Additionally, it has built-in workflows with standardized, repeatable processes, improved visibility, collaboration, and a unified operations view, and support for bridging customer-facing teams and engineering and the SRE teams. The last thing it provides is scalability for enterprise environments.
The AI-powered alert grouping and automation have made a difference in my day-to-day work by reducing alert noise. It automatically groups multiple related alerts into a single incident, so instead of 20 separate alerts, I get one meaningful alert, which prevents on-call engineers from being spammed. It also helps in faster root cause understanding because AI looks at patterns across systems including logs, metrics, alarms, and graphs, finally providing a broad summary about that. This cuts down the response time, helps in prioritization, and reduces the burnout of on-call teams.
PagerDuty Operations Cloud has positively impacted my organization by helping in faster incident detection and resolution with less downtime. It has reduced noise and fewer false alerts, allowing better focus for teams, meaning that on-call engineers can focus only on real and important issues rather than all the duplicate and negligible issues. It has helped with automation and efficiency, better collaboration and communication among teams, improved post-incident learning and prevention, and has not only helped in operational cost savings and better return on investment, but also in scalability and readiness for growth.
What needs improvement?
Even though PagerDuty Operations Cloud is a strong platform, many things can be improved. Analytic and reporting depth can be improved with better depth. Noise suppression and alert grouping robustness can be improved because sometimes the grouping becomes vague and somewhat unclear. Usability can improve, and user interface and user experience can improve because it becomes quite complex for new users. Integration and ecosystem limitations can be improved, as well as cost because for small or mid-sized organizations, it would become quite expensive to pay for this solution. Complexity for smaller teams or simpler needs can also improve.
I think we can have richer analytics, and the reporting dashboards can improve. More robust noise suppression can help us. Native support for alert attachment can help us. A simpler user interface and user experience can be implemented, and pricing tiers and models should be more favorable. Accessible documents and easier onboarding can help a lot.
For how long have I used the solution?
I have been using PagerDuty Operations Cloud since the first year of my job, and I have worked on four projects, using it in all of them.
What do I think about the stability of the solution?
PagerDuty Operations Cloud is one of the most stable platforms.
What do I think about the scalability of the solution?
The scalability of PagerDuty Operations Cloud is quite great. I have seen it scale in a very easy and robust manner.
PagerDuty Operations Cloud has met my needs as my team and workload have grown. The workload would definitely grow because since we are going online, production issues might happen, but PagerDuty has helped reduce that workload.
How are customer service and support?
I never faced an issue that would make me have to reach out to PagerDuty customer support because I think it worked fantastically. However, if that happens in the future, I would be happy to share my experience.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
This is my first company, and I have been working here since the beginning of my career, so PagerDuty Operations Cloud is the only solution I have worked with.
How was the initial setup?
Before using PagerDuty Operations Cloud, my team often took longer to identify the root cause of incidents because alerts were scattered across different tools. After moving to PagerDuty Operations Cloud, AI-powered alert grouping and automated flows have helped us detect issues much faster. We now mobilize the right team within minutes, and our overall incident resolution time has dropped significantly, which has directly reduced our downtime and improved service reliability.
What about the implementation team?
It was not a team-level decision whether my organization evaluated other options before choosing PagerDuty Operations Cloud.
What was our ROI?
Cost savings happened since losses were prevented. Time savings also occurred, response time reduced, and many such things happened which I have already mentioned.
What's my experience with pricing, setup cost, and licensing?
Pricing, setup cost, and licensing were not my headaches, and the organization already provided me with everything set up. I just had to log in and start using it.
Which other solutions did I evaluate?
I did not purchase PagerDuty Operations Cloud through the AWS Marketplace because it is an organization-wide decision, so my company would have done that.
What other advice do I have?
I would definitely recommend trying this solution. If you are thinking to go with production in the near future, definitely give it a try. If someone is trying to go to production and wants to have reduced service level agreements and reduced time for root cause analysis and everything, definitely give it a try. It is a tool that you should work with, and I rate this product a 10 out of 10.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Reliable Alerting and Seamless On-Call Management for 24x7 Teams
PagerDuty excels at getting the right alerts to the right people quickly through multiple channels like mobile app, phone, SMS, and email, which is crucial for reducing MTTR in production environments. Users consistently highlight that alerts are timely, granular, and dependable, which helps avoid missed incidents and supports 24x7 operations.
On‑call scheduling and escalations
The on‑call management features make it easy to build fair rotations, escalation policies, and handoffs without manual spreadsheets or ad‑hoc processes. This structure improves accountability, prevents burnout, and ensures someone is always available to respond, which is especially valuable for global or follow‑the‑sun teams.
Integrations and workflow automation
PagerDuty integrates with most major monitoring, logging, and ITSM tools, turning raw alerts into actionable incidents and routing them automatically. Automation capabilities (including AI-driven and runbook automation) can trigger diagnostics, remediation steps, and collaboration workflows, cutting noise and speeding up resolution.
Collaboration and visibility
Incident dashboards, status updates, and post‑incident features give teams and stakeholders a shared view of what is happening during outages. This improves coordination across SRE, infrastructure, app teams, and management, and makes it easier to learn from incidents and improve reliability over time.
UI and usability issues
The interface is often called unintuitive, overwhelming for schedule overrides, rotations, and configs, with extra steps for simple tasks like editing overrides (requiring delete/recreate). Mobile app notifications nag about settings, and setup complexity adds a steep learning curve, especially for non-experts managing on-call.
Alert noise and reliability
Multiple rapid alerts can overwhelm phones with repeated calls, preventing acknowledgment and escalating stress during outages. While upstream monitoring fixes help, PagerDuty's lack of built-in noise reduction in lower tiers contributes to fatigue and morale hits for on-call staff
PagerDuty tackles unreliable alerting by providing real-time, multi-channel notifications (mobile, SMS, phone) that ensure critical issues reach the right responders without delay. It fixes chaotic on-call scheduling through flexible rotations, escalations, and handoffs, eliminating spreadsheets and ad-hoc emails for 24x7 coverage. Noise reduction via AIOps and automation filters out low-value alerts, while integrations with 600+ tools (Jira, Slack, Azure, Datadog) centralize workflows and prevent tool sprawl.
Operational Benefits
Teams see faster MTTR and reduced downtime from automated triage, guided remediation, and runbook automation that standardize responses and cut manual steps. On-call burnout drops with fair rotations and stakeholder updates, improving morale and accountability during outages. Post-incident analytics and PIRs drive continuous improvement, identifying trends for proactive reliability enhancements.
Business Impact
Downtime minimization protects revenue and SLAs, with users reporting 40% fewer unnecessary alerts and quicker resolutions. Cross-team visibility boosts collaboration, bridging ops, dev, and support for scaled service ownership. In your Azure/Jira/Slack setup, it would streamline Severity A escalations and incident war rooms by automating Jira pulls and Slack posts
Streamlines incident response and has built customer trust but needs deeper analytics insights
What is our primary use case?
My main use case for PagerDuty Operations Cloud is incident management, as we use it for alerting people who are on call.
I definitely use PagerDuty Operations Cloud for incident management; we have set up the account, schedule, teams, etc., and we continuously monitor our logs for any anomalies with proactive alerts. We define priority because we don't want to alert people on the phone unnecessarily, thus we categorize alerts based on severity and business disruption, sending information via the integrated APIs to the relevant teams, specifying whether to communicate through Slack or phone based on the severity.
This is the main use case we have; it's a tool that last mile connect kind of people use.
How has it helped my organization?
PagerDuty Operations Cloud positively impacts my organization by helping us win customer trust; when problems occur, the speed of our reaction and involvement with customers is crucial, and PagerDuty Operations Cloud facilitates quick responses to potential issues. PagerDuty Operations Cloud allows our team to react swiftly, which can be challenging without it, as we can't manually sift through all logs. Automation for remediation is also in place, enhancing confidence and allowing some issues to be resolved without manual intervention.
What is most valuable?
The best features of PagerDuty Operations Cloud include integration, mobile app, reporting, and analytics, which I find very useful based on the access I have.
We review the data periodically to see our performance; for example, we check for alert fatigue, how many alerts have been addressed, and our TDX metrics such as time to respond. The analytics of PagerDuty Operations Cloud is so good that it gives me good visibility with just a few clicks, which helps in discussions with the team for continuous improvements.
What needs improvement?
More analytics can be brought into PagerDuty Operations Cloud; while I know there are some, they still seem basic to me, and having options for user-customized charts would be really helpful, especially in this GenAI world where prompts can yield valuable data.
The analytics provided by PagerDuty Operations Cloud can be significantly improved, as they still feel basic to me.
For how long have I used the solution?
I have been using PagerDuty Operations Cloud for more than five years.
What do I think about the stability of the solution?
PagerDuty Operations Cloud is stable.
How are customer service and support?
I don't think I have ever needed customer support because our usage and the lack of issues may prevent any corner cases or other problems, or perhaps it relates to licensing. I personally have never utilized customer support.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
I previously used another solution which I won't name because it's proprietary, but the user experience was not great; when I learned about PagerDuty Operations Cloud, it had a lot of positive discussions, and I was excited to find we were already using it when I joined this company.
What was our ROI?
TDX metrics are definitely improving due to PagerDuty Operations Cloud being in place; time to respond, time to initiate, and time to mitigate are key metrics influenced positively.
What's my experience with pricing, setup cost, and licensing?
I usually am not involved in pricing, setup cost, or licensing, as that's handled by another team, so I don't have much visibility on that part.
What other advice do I have?
I advise others to use PagerDuty Operations Cloud, as it's going to help in building customer trust. There's an operations team for those aspects. My overall review rating for PagerDuty Operations Cloud is 7 out of 10.