The PagerDuty Operations Cloud is essential infrastructure for all unplanned, time-sensitive, critical work. It automatically detects and diagnoses disruptive events mobilizes the right team members to respond and automate infrastructure and workflows across your digital operations. This means you can resolve unplanned, unstructured, time-sensitive, and high-impact issues quickly - with fewer escalations to your technical teams while minimizing the impact on your customers and maintaining brand trust.
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
Get personalized pricing in minutes - New
If qualified, an express private offer gets you custom pricing and terms. Finalize your purchase in the AWS Marketplace console.
AWS Marketplace now accepts line of credit payments through the PNC Vendor Finance program. This program is available to select AWS customers in the US, excluding NV, NC, ND, TN, & VT.
Pricing is based on the duration and terms of your contract with the vendor, and additional usage. You pay upfront or in installments according to your contract terms with the vendor. This entitles you to a specified quantity of use for the contract duration. Usage-based pricing is in effect for overages or additional usage not covered in the contract. These charges are applied on top of the contract price. If you choose not to renew or replace your contract before the contract end date, access to your entitlements will expire.
Additional AWS infrastructure costs may apply. Use the AWS Pricing Calculator to estimate your infrastructure costs.
Pricing centers on per-user incident response plans. You pick Professional or Business based on the depth of workflow and admin features your team needs. CustomerServProfessional and CustomerService Business apply the same tiering to support-to-engineering coordination. Several dimensions are usage- or add-on-based: AIOps bills by annual events, with a separate charge for events over your contracted amount. Runbook Automation, Automation Actions, Live Call Routing, and Runbook Auto Job Runner add capabilities on top of a plan. Stakeholder Users sell in bundles of 50, and Status Pages sell in 1,000-user packs.
Top-of-mind questions for buyers
How is AIOps counted, and what happens if I go over my contracted event volume?
AIOps is licensed per accepted event. An accepted event is any valid event sent to and processed by PagerDuty with a successful 2xx response. Your contract covers up to 96,000 annual events. If you exceed that amount, the Additional events over contracted value dimension charges for the overflow.
What counts as a billable user on the Professional and Business plans?
Every person added to your PagerDuty account is a paid user. This includes anyone who receives notifications or appears in an on-call schedule. Read-only business stakeholders are handled separately through Stakeholder Users, which sell in bundles of 50.
Can I buy AIOps, Runbook Automation, or the add-ons on their own?
No. You must first purchase at least one user on a Professional or Business incident response plan before you can add AIOps. Add-ons such as Automation Actions, Live Call Routing, and Runbook Auto Job Runner layer on top of a base plan rather than standing alone.
www.pagerduty.com
Helpful?
Vendor refund policy
All fees are non-cancellable and non-refundable except as required by law.
Request a private offer to receive a custom quote.
How can we make this page better?
Tell us how we can improve this page, or report an issue with this product.
Give us feedbackReport a problem with this product or seller
Legal
Vendor terms and conditions
Upon subscribing to this product, you must acknowledge and agree to the terms and conditions outlined in the vendor's End User License Agreement (EULA).
Content disclaimer
Vendors are responsible for their product descriptions and other product content. AWS does not warrant that vendors' product descriptions or other product content are accurate, complete, reliable, current, or error-free.
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.
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.
Machine learning-powered functionality that reduces alert noise by up to 98% through adaptive models based on user behavior patterns and 10+ years of data ingestion.
Incident Response Orchestration
End-to-end incident response orchestration with service ownership model that mobilizes appropriate team members and automates infrastructure workflows across digital operations.
Process Automation and Runbook Management
Managed cloud service enabling creation and delegation of automated operational tasks including service provisioning, CI/CD, configuration management, and incident diagnosis and remediation.
Multi-Platform Integration
Over 700 integrations, APIs, and applications supporting connectivity with AWS services including CloudWatch, GuardDuty, CloudTrail, EventBridge, Security Hub, DevOps Guru, Control Tower, Outposts, and S3 Storage Lens.
Mean Time to Resolution Acceleration
Critical context delivery for faster triage and effective automation to drive down MTTR with machine learning-powered AIOps functionality.
Unified Observability Platform
Comprehensive visibility across applications, infrastructure, logs, databases, networks, and digital experiences through a single-pane-of-glass interface
AIOps and Machine Learning
AIOps enhanced with machine learning capabilities to simplify management of distributed environments and automatically prioritize alerts to reduce alert fatigue
Automated Instrumentation and Dependency Mapping
Automated instrumentation with dependency mapping and service relationship views to identify multi-level relationships across services
Open-Source and Container Support
Support for open-source frameworks, container technologies, and third-party integrations for cloud-native environments
Rapid Deployment
Quick installation and easy configuration designed for rapid time to value with minimal setup complexity
AI-Powered Monitoring and Anomaly Detection
Cognitive AI engine automates issue classification, pattern detection, and anomaly identification across managed applications
Multi-Source Data Integration
Combines CloudWatch, CloudTrail logging, and fully configurable real-time metrics collection for comprehensive application monitoring
Automated Root Cause Analysis and Response
System provides root cause analysis, corrective action recommendations, and automated response actions integrated with ServiceNow, email, and Slack
Multi-Region Failover and Business Continuity
Supports multi-region deployment with automatic failover, failback coordination, and state monitoring across AWS regions
Application Topology and Automation Management
Enables definition of application topology views, task lists, notifications, and automation runbooks for resource management and reporting
Structured alerting has reduced recurring incidents and enables faster resolution for our team
Reviewed on Sep 04, 2026
Review provided by PeerSpot
What is our primary use case?
My main use case for PagerDuty Operations Cloud is to manage alerts and to monitor AI-powered workflows. For example, whenever a service goes down, it needs attention, and PagerDuty Operations Cloud helps in keeping track of all these things.
PagerDuty Operations Cloud helps me when a service goes down by notifying everyone. Prior to this, we were using Slack, but we were relying on messages, and this platform gives more clear visibility to the team rather than a message.
PagerDuty Operations Cloud identifies the right person and notifies that person, so it is way faster and efficient.
What is most valuable?
The best features PagerDuty Operations Cloud offers for us include incident management and automated alerting, which are helping us. These are the only reasons we started and onboarded this.
Automated alerting and incident management features make my team's life easier on a day-to-day basis. We have set the hierarchy, and if the first person does not respond, it moves to the second person, so that way we do not miss any escalations or issues.
PagerDuty Operations Cloud has positively impacted my organization by making us more structured. All the production-related issues which we were facing before are sorted.
Since using PagerDuty Operations Cloud, I have noticed specific outcomes such as faster incident resolution. Recurring issues were monitored properly, and recurring incidents were corrected and have stopped.
What needs improvement?
PagerDuty Operations Cloud can be improved. The product itself is a bit complicated, and the initial configuration takes time, making it very difficult for new members to understand.
The product is strong, but making the setup simpler and easy to operate is an area that can be improved.
For how long have I used the solution?
I have been using PagerDuty Operations Cloud for the last year.
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?
PagerDuty Operations Cloud is highly scalable.
How are customer service and support?
Customer support is good. I would rate customer support nine out of ten.
Which solution did I use previously and why did I switch?
We have not used any different solution previously.
What was our ROI?
I have seen a return on investment. The ROI is great for us as repetitive incidents have decreased, the time in solving those issues has also decreased, and the team needs more projects and fewer team members.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing revealed that licensing is fine. However, the pricing was a bit high, and the setup, as I mentioned, is a bit complicated, costing us four weeks and roughly one hundred dollars.
Which other solutions did I evaluate?
Before choosing PagerDuty Operations Cloud, one of the team heads suggested this to us, and we implemented it because they were using this in their previous organization.
What other advice do I have?
Regarding PagerDuty Operations Cloud's AI capabilities, I think its governance and security are trying to cope up. For now, this has not been a challenge for us, but we keep an eye always.
Regarding PagerDuty Operations Cloud's AI capabilities, I find its accuracy and reliability of output to be very accurate and quite reliable.
My advice to others looking into using PagerDuty Operations Cloud is that it helps a lot with production issues and solving them on time. I suggest they go ahead and set this up properly, as initially it takes time but will provide ROI.
PagerDuty Operations Cloud is one of the reliable solutions that help in solving production issues. I have rated this review eight out of ten.
adithya k.
Streamlined Alert Management with Seamless Integrations
Reviewed on Sep 01, 2026
Review provided by G2
What do you like best about the product?
I like the flexible scheduling, rotations, and override rules in PagerDuty that ensure the right person is always notified. I appreciate how it integrates with numerous monitoring tools to suppress noise and group related events. The ChatOps feature is a highlight for me, and Slack enables teams to acknowledge, reassign, and resolve issues via chat commands. Additionally, the deep integration with various tools makes the experience seamless. The initial setup for PagerDuty is generally straightforward, taking about 15 to 30 minutes for basic configuration.
What do you dislike about the product?
All good
What problems is the product solving and how is that benefiting you?
I use PagerDuty for flexible scheduling and to integrate with monitoring tools, suppressing noise and grouping events. ChatOps and deep integration let our team acknowledge incidents and resolve issues via chat.
Gowhar S.
Reliable Incident Management and Alert Response
Reviewed on Sep 01, 2026
Review provided by G2
What do you like best about the product?
What I like most about PagerDuty is how it turns alerts into a clear, structured incident response process. Real-time notifications, flexible on-call scheduling, and well-defined escalation policies make it easier to ensure critical issues reach the right person quickly, without unnecessary delays. I also appreciate the integrations with monitoring and collaboration tools, since they let teams manage incidents in one place instead of constantly switching between platforms. Overall, PagerDuty improves visibility and accountability, and it helps teams respond faster when incidents happen.
What do you dislike about the product?
PagerDuty can feel a bit complex to configure, especially for new users. If the initial setup isn’t done thoughtfully, managing multiple alerts and notifications can quickly become overwhelming. Pricing may also be a concern for smaller teams.
What problems is the product solving and how is that benefiting you?
PagerDuty helps us manage critical alerts by routing incidents to the right teams and reducing our response times. It also improves overall visibility, supports timely escalation, and makes it less likely that important issues will be missed.
Akriti Chawla
Automated incident workflows have reduced downtime and now protect revenue and customer experience
Reviewed on Sep 01, 2026
Review provided by PeerSpot
What is our primary use case?
I am using PagerDuty Operations Cloud for handling all the operations in our organization to resolve all the issues. PagerDuty Operations Cloud detects outages and issues if something happens on a website, and assigns it directly to the right team so that it is easy for us to fix and track the resolution.
Sometimes, over the call, we schedule and automatically notify the responsible engineer. Sometimes we trigger an automatic workflow. For example, if any user is searching for a product on our website and adding it to the cart, if an issue occurs proceeding to payment or any issue occurs due to product availability, then it automatically notifies us so that we can fix it to maintain the same experience.
Primarily, I am using PagerDuty Operations Cloud for our API outage. If our production API is giving a 400, 500, or 404 error, it automatically notifies us. Sometimes the payment gateway starts failing and transactions are impacted. It is easy for us to know the impact so that we can fix it to keep things the same.
What is most valuable?
PagerDuty Operations Cloud mainly offers on-call and escalation management. It offers to automatically alert the right engineer. It has in-built intelligent alert grouping, so it reduces duplicate notifications. It has in-built AI operations so we can identify important scenarios and reduce unnecessary alerts. Event orchestration is also in-built, so events automatically process based on the incident conditions.
It gives the operational console in which all things are on the centralized dashboard. It gives us a transparent and real-time view of all the incidents so that we can track and resolve them as soon as possible.
Post-incident review captures incident information and helps our team to analyze what is going on on our website so that we can improve our future responses.
It reduced the downtime because critical incidents reach the right engineer, so we can fix them for a faster resolution. It also reduces the maintenance cost to save money and helps us to deliver the best customer experience. It reduced the operational cost as well as improved the product team's productivity.
It gives us insights and recommendations. We are continuously improving ourselves by using PagerDuty Operations Cloud.
What needs improvement?
If AI can detect the root cause analysis without any human intervention would be beneficial. I would like to see predictive incident prevention, because sometimes an engineer is busy with some task, so if a task is a low priority, AI can fix it on our behalf. Business-focused dashboards where we can check the revenue and the customer impact, and how we are reducing the downtime in real-time would be valuable.
PagerDuty Operations Cloud has AI capability but needs some optimization. Sometimes it fixes the issues but takes too much time compared to a human doing it manually.
We can improve by combining alerts with the addition of metrics. We can also collect the recommendations based on the feedback to improve future prediction.
For how long have I used the solution?
I have been using PagerDuty Operations Cloud for the last one year.
What do I think about the stability of the solution?
PagerDuty Operations Cloud is very stable. It is fabulous and very scalable, rated ten out of ten.
What do I think about the scalability of the solution?
The scalability is superb.
How are customer service and support?
I see a good ROI because it reduces our operations cost as well as the human effort and makes our application more robust and reliable.
Which other solutions did I evaluate?
I did consider alternate solutions, but I finalized PagerDuty Operations Cloud.
What other advice do I have?
I would always recommend PagerDuty Operations Cloud for all production applications because it automatically detects and monitors our application if something happens related to the API. It really detects the issue and responds quickly. PagerDuty Operations Cloud is a fabulous solution for all production applications. I give this solution a perfect rating of ten out of ten.
Aaron Held
Automated alerting has streamlined incident response and improved team coordination
Reviewed on Aug 26, 2026
Review provided by PeerSpot
What is our primary use case?
The usual use cases for PagerDuty Operations Cloud include incident management. I ran the infrastructure teams and SRE, so the primary use case was incident management and spinning up RCAs, tracking remediation. We also used it for identifying key stakeholders of projects. We relied on the escalation chains and the groups. Even if it wasn't an incident, if somebody had a question or they needed to get a hold of the CMS team, they would go into PagerDuty. We had a lot of integrations into Teams chat.
The heart of it was obviously kicking off pages from alerts within PagerDuty Operations Cloud. It was fully automated so that when an anomaly was detected, it automatically created an incident in PagerDuty. That automation was just table stakes. We also had some good automations to follow up and close out Jira tickets that would integrate with the PagerDuty incident. The primary one was simply calling the people when something happens.
What is most valuable?
My favorite feature about PagerDuty Operations Cloud is that it just worked. It was one of the tools we didn't have to worry or think about. It was very well polished. It did what they said they were going to do, and it didn't require a lot of customization. I think it facilitated us organizing the teams, groups, and escalation chains really well. However, there is no feature that stands out significantly.
PagerDuty Operations Cloud absolutely requires maintenance on my end. Escalation chains and people get stale very quickly. I wish it would integrate into org charts or an HR system so that when people get terminated or shift roles, PagerDuty knows about the changes. We had one escalation chain where it went up to an executive that wasn't in the company anymore.
What needs improvement?
The users would complain that they always had a hard time maintaining their schedules, their escalations, and installing the app. I got a lot of complaints from the people that responded to pages rather than from the people who administered PagerDuty.
The complaints I remember were about how users wanted to be notified. It was very common for somebody to misconfigure their own communication chain and not test it, so when an alert went off, their excuse was they didn't get the page or they didn't get the SMS. I got a lot of feedback from users that they struggled to do their shift when they needed someone to cover their shift. Often that wouldn't get done. Anything that can be done to make that as easy and simple as possible would be helpful.
For how long have I used the solution?
I have probably used PagerDuty Operations Cloud for about five years total.
What do I think about the stability of the solution?
The stability of PagerDuty Operations Cloud has been great. I have not experienced any stability issues.
What do I think about the scalability of the solution?
I have no problems with scalability. I have used it for like 500 engineers and experienced no issues.
How are customer service and support?
I did not have any partnerships with them. I was just a customer and user.
Which solution did I use previously and why did I switch?
I have used some alternatives. I used Grafana incident management a lot and we used something called RingCentral.
How was the initial setup?
The initial deployment for a new client when starting with PagerDuty Operations Cloud was moderate. I would say it was more difficult because the biggest problem we had was just identifying who the responders were. It does take a bit of setup. We also did the Teams integration, which requires security and permission. The setup is always hard, though this is not necessarily a criticism on PagerDuty.
What's my experience with pricing, setup cost, and licensing?
I am not current on what the current pricing is for PagerDuty Operations Cloud, but I assume it is per seat and per responder.
Which other solutions did I evaluate?
If I were to pick one, PagerDuty Operations Cloud is the one I would pick if there were no budget concerns. If I was budget-constrained, I would pick Grafana.
What other advice do I have?
PagerDuty Operations Cloud did influence the volume and nature of alerts. We had more of them. I have implemented this three major times in my career, and the number of incidents immediately shot up and then came down. What happens is you identify the incidents more aggressively and then you actually fix the problems. I think that is a good thing.
I have not used Incident Workflows or Event Orchestration to automate toil from the incident management process. We played with it, but I did not use them in practice.
I did not use the AI agents at all. I would rate this review a 9.