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
Incident Response Orchestration
End-to-end incident management with service ownership model that mobilizes appropriate team members and automates infrastructure workflows
Runbook Automation
Managed cloud service enabling creation and delegation of automated operational tasks including service provisioning, CI/CD, configuration management, and incident remediation
Multi-Platform Integration
Over 700 integrations, APIs, and applications supporting integration with AWS services including CloudWatch, GuardDuty, CloudTrail, EventBridge, Security Hub, and DevOps Guru
Event Detection and Diagnosis
Automatic detection and diagnosis of disruptive events with machine learning-powered AIOps functionality leveraging over 10 years of data ingestion
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 and Integration
Quick installation with automated setup and easy integration with SolarWinds Hybrid Cloud Observability for reduced time to value
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 real-time metrics collection for comprehensive application monitoring
Automated Incident Response and Remediation
Provides root cause analysis, corrective action recommendations, and automated response actions integrated with ServiceNow, email, and Slack
Multi-Region Failover and Business Continuity
Supports automatic failover, failback coordination, and state monitoring across multiple AWS regions with automated recovery processors
Application Topology and Resource Management
Delivers topology views, task lists, notifications, and automation runbooks for resource management and operational reporting
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.
Aryan Dwivedi
Real-time alerts have protected client sites and now keep our team focused on critical issues
Reviewed on Aug 25, 2026
Review provided by PeerSpot
What is our primary use case?
PagerDuty Operations Cloud is used for real-time alerts when something goes wrong with our system so the team can fix it right away, and for setting up on-call schedules to ensure the right person is always ready to answer the problem at any time of the day. We also use it for scaling up discovery calls with our clients and prospects.
Last month, one of our main web servers stopped working in the middle of the day, and the system sent an instant notification to the team, who automatically used our on-call schedule to contact the right engineer on duty, saving us precious time instead of guessing who to call.
We have used PagerDuty Operations Cloud to control the external noise from the alerts.
What is most valuable?
The real-time notification is top-notch, and critical warnings reach the right person right away without delay. Smart tools that reduce extra alert noise are great for keeping the team focused on real-time problems. The large number of connections to over 700 different software tools allows us to bring all work together in one workflow.
PagerDuty Operations Cloud has helped fix critical problems much faster, including the ads we are running that do not crash, the websites we run for our clients, and our CRM website.
I cannot say that PagerDuty Operations Cloud has reduced downtime or improved our team's response time because we have been using it for around two months only. However, we have seen reduced downtime and quick resolution of issues because everyone is notified when something is damaged, whereas earlier we would only find out about issues when the client called us. This also gave us a demerit because the client thought we could not do the work properly, resulting in a significant reduction in our monthly retainer. Now we are stable with our monthly retainer.
The security governance of PagerDuty Operations Cloud is pretty good.
Regarding its accuracy and reliability of output, I would say it is pretty much accurate.
PagerDuty's generative AI is pretty good, although sometimes the decision can be a bit generic and not very reliable, but they are improving it.
What needs improvement?
The learning curve for PagerDuty Operations Cloud is a bit steep, with its complicated rules and schedules, and we have to dedicate a proper team to use that tool.
For how long have I used the solution?
I have been using PagerDuty Operations Cloud for two months.
What do I think about the stability of the solution?
PagerDuty Operations Cloud is pretty much stable and I have not seen it crashing.
What do I think about the scalability of the solution?
PagerDuty Operations Cloud is pretty much scalable.
How are customer service and support?
I have not used customer support until now, but I believe they will be great.
Which solution did I use previously and why did I switch?
We were not using any different solution; this is the first time we are going for an on-cloud platform.
What about the implementation team?
I cannot share how my team has leveraged automation within PagerDuty Operations Cloud because it is a bit confidential.
What was our ROI?
It helps us save manual hours of work every week.
For me as an employee, I would say the time has been reduced and the downtime has been reduced.
Which other solutions did I evaluate?
I was not on the team that evaluated options before choosing PagerDuty Operations Cloud, so I cannot tell you about this.
What other advice do I have?
We are still in the process of implementing AI and automation through PagerDuty for incident response.
I cannot answer that question right now because we are still testing PagerDuty's autonomous AI agents.
The alert reduction feature has been reporting to us issues such as a client's website being down or the CRM website being down, which I would say has saved us.
I would say that if your team can purchase PagerDuty Operations Cloud, you can definitely use it, although it is a bit costly for a startup, as was pointed out by my team too, but we have saved a lot of time.
I gave this review a rating of 9 out of 10.
Raj kuruhuri
Alert noise has been cut and on-call teams respond faster to critical incidents
Reviewed on Aug 10, 2026
Review from a verified AWS customer
What is our primary use case?
Our main use case for using PagerDuty Operations Cloud is because our L1 team was under constant stress from alert storms and missed escalations that were threatening our service reliability. We chose it to streamline the escalation matrices, and it has been excellent for us. It has streamlined our escalation metrics and drastically reduced erroneous notifications, meaning my engineering teams are now only waking up in the middle of the night for actual revenue-impacting emergencies. It has brought stability to our operations and allowed us to respond accurately and swiftly.
The main use case is to ensure that our services run uninterrupted while optimizing our operational cost. We are using it as the central hub for IT alerting, incident management, and automated on-call scheduling across the organization.
How has it helped my organization?
PagerDuty Operations Cloud has definitely been a game changer for the organization. The return on investment has been significant and highly visible. It has helped us reduce alert noise and surface resolution insight. We have saved an average of 30 minutes per incident, which totals a time savings of at least 70% to 80% per year. On a broader operational scale, the built-in ticketing management, the macros, and the automation have saved us the equivalent of at least three to four full-time employees, which has minimized our cost.
Most importantly, it has minimized our downtime by catching signals earlier and translated that to productive revenue, which has avoided an estimated loss worth one million dollars for our company.
What is most valuable?
PagerDuty Operations Cloud has given us very clear AI-driven alert grouping. The autonomous AI agent calculated alerts and suppressed the noise. We used to get temporary traffic spikes or minor upgrade dips, and it has ensured that wherever there is a need for a security alert, it provides the security alert in real time, 24/7.
PagerDuty Operations Cloud includes automated escalation, which helps us set up a call and join the right person via SMS, mobile push, or direct phone call. Another valuable feature is historical data insight, which gives clear insight during an incident and surfaces the historical data on forward-looking resolution from similar past events. This helps the team resolve issues faster.
These features have given us real-time insight and a historical and present-time alert system via SMS, mobile push, or direct phone call. Even if the team has missed an alert at the regular time, it provides historical data and insight to ensure we understand why an incident has been raised or why a security breach has occurred.
What needs improvement?
PagerDuty Operations Cloud is working as expected, but if I were to suggest one improvement, I believe that the AI could be better. The accuracy can be improved because during consistent critical events, it occasionally groups unrelated alerts or misses a correlation, which forces our on-call team to fall back to manual triage.
For how long have I used the solution?
We have been using PagerDuty Operations Cloud in our organization for the last three and a half years.
What do I think about the stability of the solution?
We experienced 100% stability. We did not face any challenges.
What do I think about the scalability of the solution?
It is definitely a scalable product. We can easily scale up and down as per our needs. It has great scale.
How are customer service and support?
Customer support is a 10 out of 10. We had an interaction with them for one of the incidents, and they resolved it within 30 minutes.
What's my experience with pricing, setup cost, and licensing?
Our experience with the pricing, setup cost, and licensing of PagerDuty Operations Cloud has been excellent. We have chosen the pay-as-you-go licensing through AWS Marketplace, which has been a great option for us.
Which other solutions did I evaluate?
Before choosing PagerDuty Operations Cloud, we definitely evaluated other options and alternatives to ensure we were selecting the right solution. Some solutions we considered included Opsgenie by Atlassian, Better Stack, xMatters, and Splunk On-Call.
What other advice do I have?
The alert reduction feature of PagerDuty Operations Cloud has given us at least 30 minutes per incident and has reduced the overall tasks and work that was being done. We have seen a reduction in time and a reduction in the incidents, and we have saved a lot of money as well.
The team has leveraged PagerDuty Operations Cloud to optimize the incident workflows in a positive way. It has given us clear insight into all incidents. We can easily track them in the history section. The impact is significant because it has optimized our workflows, optimized team capacity, and optimized the quality of incidents. The major impact is on time. The team has been allocated tasks on time, and they are able to deliver them on time.
I give PagerDuty Operations Cloud a rating of nine out of ten. Since it has provided us exceptional results, I have given it a nine, and one point is deducted for the improvement I have suggested. Anyone who is looking for a dedicated platform for alerting and automation-related incidents should definitely go with PagerDuty Operations Cloud. They are the best in this category.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Anonymous
Reliable On-Call Alerting with AIOps Benefits
Reviewed on Aug 03, 2026
Review provided by G2
What do you like best about the product?
I like using PagerDuty for its reliability, as it ensures that we don't miss major critical issues. I use it mainly for on-call schedules and catching alerts when things go wrong in the infrastructure. I find the AIOps and noise reduction features valuable. The setup was pretty simple, which I appreciated.
What do you dislike about the product?
I find PagerDuty can get expensive over time.
What problems is the product solving and how is that benefiting you?
I use PagerDuty for on-call scheduling and catching alerts for critical issues, like server failures. It helps us avoid missing major critical issues.
Marketing and Advertising
Easy-to-Use Urgent Agent Pings with a Great Mobile App
Reviewed on Aug 03, 2026
Review provided by G2
What do you like best about the product?
Useful way to ping agents urgently for cases based on severity. UI in browser is easy to use.
Integrated mobile application is great for agents who are away from the office to keep up-to-date.
What do you dislike about the product?
Inability to modify the notification settings can be irritating.
Browser calendar can become clunky when a large number of agents are on the same roster.
Integration with Slack can break sometimes and leads to distrust of notifications.
What problems is the product solving and how is that benefiting you?
PagerDuty allows my managers to concisely organise agents into schedules that fit around their daily lives.
It allows me to know when I am required access to my work computer, or when I'm free to leave it at home.