Sold by: PagerDuty
Deployed on AWS
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.
4.5
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
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.
Details
Sold by
Delivery method
Deployed on AWS
Features and programs
Buyer guide
Gain valuable insights from real users who purchased this product, powered by PeerSpot.
Financing for AWS Marketplace purchases
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
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.
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 |
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
Request a private offer to receive a custom quote.
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.
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.
Updated weekly
By PagerDuty
By SolarWinds
By StreamScape
Top
10
In Agile Lifecycle Management, IT Business Management, ML Solutions
Top
25
In Log Analysis
Top
100
In Data Governance
Sentiment is AI generated from actual customer reviews on AWS and G2
Functionality
Ease of use
Customer service
Cost effectiveness
Positive reviews
Mixed reviews
Negative reviews
AI generated from product descriptions
Alert Noise Reduction
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
Standard contract
No
No
No
Customer reviews
Sofia V.
Powerful Incident Response, But Advanced Setup Takes Time
Reviewed on Jul 28, 2026
Review provided by G2
What do you like best about the product?
What I like best about PagerDuty is how it streamlines incident response and ensures the right people are notified immediately when critical issues occur. The alerting and escalation policies are highly customizable, making it easy to manage on-call rotations without worrying that important incidents will be missed.
What do you dislike about the product?
While PagerDuty is a powerful platform, some of its more advanced features come with a learning curve, especially when configuring complex escalation policies, event orchestration, and automation workflows. Initial setup can take time for larger organizations with multiple teams and integrations.
What problems is the product solving and how is that benefiting you?
PagerDuty helps us solve the challenge of responding quickly to critical incidents by ensuring alerts reach the right people at the right time. Instead of relying on manual notifications or monitoring dashboards, incidents are automatically routed through predefined escalation policies, reducing the risk of missed alerts and delayed responses.
reviewer2879727
Unified incident response has reduced alert noise and improves on-call focus and coordination
Reviewed on Jul 26, 2026
Review from a verified AWS customer
What is our primary use case?
I have used PagerDuty Operations Cloud for two years, so I have over two years of experience with it.
My main duties in PagerDuty Operations Cloud are incident routing, escalation policies, on-call management, incident response coordination, and integrations.
For incident routing, I connected AWS CloudWatch alarms to PagerDuty using the Event API. When our EC2 CPU crosses 85%, CloudWatch pushes the alert to PagerDuty, which then routes it to the backend services team. I also used event rules to auto-tag alerts and suppress duplicates. Another use case is on-call management. I used PagerDuty's mobile app to acknowledge alerts during off hours. For example, on weekends, such as Sunday morning, when there is an incident I acknowledged a high-priority alert from my phone and joined the Slack room directly from the PagerDuty incident link. This is helpful for those who are on call during off shifts. Regarding integrations, since we use many integrations on PagerDuty, we integrated PagerDuty with Slack so incidents automatically created a dedicated channel. I also connected it to Jira so incidents could generate tickets for follow-up actions, and also to ServiceNow as well.
What is most valuable?
PagerDuty Operations Cloud excels at routing alerts, managing on-call schedules, coordinating incidents, and automating remediation. These features make it helpful for the on-call team and the people who are working with PagerDuty Operations Cloud.
The feature I use the most is incident routing. We use incident routing more than anything else because it is the main foundation of PagerDuty Operations Cloud. If routing is incorrect, nothing else is going to work, no escalations, no on-call, and no automation at all. I use it the most because it is the first step in every incident; it ensures that alerts from different cloud platforms or any other third-party providers such as AWS, Azure, and other platforms including Datadog reach the right service. It prevents misrouted alerts and missed incidents and it directly impacts the MTTA, because responders get the alert instantly. Every other PagerDuty Operations Cloud feature depends on routing being accurate. I use incident routing daily in this way. This is the main foundation of PagerDuty Operations Cloud, to work with it and to make it a very easy platform for us to work with.
PagerDuty Operations Cloud excels at routing alerts, managing on-call schedules, coordinating incidents, and automating remediation. It ensures critical alerts reach the right teams instantly, reducing the MTTA and MTTR. It strengthened the on-call process with dependable escalations and real-time incident coordination, preventing missed alerts and speeding up resolution tasks. Automation and noise reduction features help cut down repetitive manual work and alert fatigue, allowing engineers to focus on real issues.
PagerDuty Operations Cloud significantly reduced alert noise and improved MTTA. Our acknowledgement time dropped almost by half, and MTTR improved by around 15–20% due to improved automation and routing.
The alert noise dropped by 20–25% after tuning event rules. After implementing PagerDuty Operations Cloud, we saw a 20–25% reduction in alert noise and a noticeable improvement in MTTA. Our acknowledgement time dropped by almost half and the MTTR improved by around 15–20%. MTTR improved by 15–20% due to major incident automation and better routing, which also reduced unnecessary on-call interruptions. It made a good impact on our current schedules and in my current organization.
PagerDuty Operations Cloud's alert reduction features helped lower operational cost by cutting unnecessary alerts and reducing on-call interruptions by grouping and suppressing noisy alerts. The team spent less time triaging low-value incidents, which directly reduced overtime and burnout. The biggest impact for us was fewer false alarms, meaning engineers could focus on real issues instead of constant alert fatigue.
What needs improvement?
PagerDuty Operations Cloud could improve its noise reduction by making deduplication and suppression more automated instead of manually tuned, and the service dependency graph could be more intuitive with cleaner visuals and easier-to-understand root cause tracing during major incidents. Automation could go further with smarter runbook triggers and AI-driven suggestions to help find root causes, which could save a lot of time for engineers who are struggling to understand what is actually happening. These AI capabilities could lower the time by maybe 50–60%. Analytics and reporting could be more flexible, allowing custom dashboards and filters and team-level MTTA and MTTR breakdowns, so that it is segregated based on teams and it is much easier to have custom dashboards for the teams to understand more.
Alert storms were a recurring frustration for the on-call team, and escalation overrides and service dependency graphs can get a bit confusing in larger environments. More customizable analytics and smarter automation would make the platform even easier, more flexible and more powerful for the team to understand.
PagerDuty Operations Cloud could improve its analytics flexibility with customized dashboards and AI capabilities to be more trained and more reliable. Service dependency mapping can also feel cluttered in big environments, making it harder to trace upstream and downstream impacts during bigger incidents.
We implemented PagerDuty Operations Cloud's AI to help with alert grouping and early incident insights, but accuracy was not consistent enough to rely on during critical events. It occasionally grouped unrelated alerts or missed correlations, which limited the operational efficiency gains we expected. The on-call team still depended heavily on manual triage because AI suggestions were not always aligned with the real root cause. Overall, AI added some value but it has not yet reached the reliability needed to significantly improve the incident response efficiency. It needs more training or more work.
What do I think about the stability of the solution?
PagerDuty Operations Cloud is stable in day-to-day use with no major outages or reliability issues affecting our on-call workflows. Alert delivery, incident routing and escalation chains have been consistently working without delays or missed notifications. Its cloud-native architecture also means updates and patches roll out smoothly without impacting uptime. Overall, the stability has been one of the strongest features for our team.
What do I think about the scalability of the solution?
PagerDuty Operations Cloud scales well for growing teams. Adding services, integrations and new on-call groups does not impact performance. Its native cloud architecture handles higher alert volumes smoothly, especially when paired with strong incident routing. We have seen it manage increased workloads without slowing down or causing notification delays. On the whole, scalability has been reliable even as our environment and service footprint has expanded.
How are customer service and support?
The customer support has been responsive and generally helpful when we have raised any issue. They provided clear troubleshooting steps and follow-ups. Resolution speed can vary depending on the severity of the issue, but support has been good and reliable for day-to-day operational needs.
Which solution did I use previously and why did I switch?
Before PagerDuty Operations Cloud, we used basic native alerting tools such as AWS CloudWatch since AWS is our primary cloud platform. We switched because those tools lacked valuable incident routing and consistent on-call escalation workflows. PagerDuty Operations Cloud offered stronger coordination, better noise reduction, and more mature incident response features. The move was mainly driven by the need for a unified and dependable on-call and incident management platform.
What was our ROI?
We have actually seen a moderate return on investment mainly through reduced alert noise and more efficient incident routing. Alert storms dropped by roughly 20–25%, saving the team several hours per week that used to be spent on low-value triage. We estimate a small cost reduction from fewer overtime hours and less on-call fatigue, though not enough to reduce headcount. Overall, the return on investment is positive but incremental — more time saved than money saved.
What's my experience with pricing, setup cost, and licensing?
PagerDuty Operations Cloud's pricing felt reasonable but it definitely is not the cheapest option. The value comes more from reliability than cost savings. Setup costs were minimal since it is a SaaS platform and onboarding did not require any infrastructure or hidden implementation costs or fees. Licensing is straightforward but scaling seats for larger teams can get expensive, especially when adding advanced features. Overall the experience was smooth but the price point could be more flexible for growing teams. Our team is small now but in the future it might become bigger.
Which other solutions did I evaluate?
Before adopting PagerDuty Operations Cloud, we evaluated options such as Opsgenie and Splunk On-Call for incident management. We also looked at other native cloud tools such as AWS CloudWatch, but they lacked the escalation workflows. Opsgenie had good features but did not match PagerDuty Operations Cloud's reliability and integrations for bigger teams. Overall, PagerDuty Operations Cloud offered stronger coordination and more consistent on-call performance which made us choose it.
What other advice do I have?
Escalation policies are a very helpful feature for managing the team, such as multi-step escalation logic which is extremely dependable and prevents missed alerts, and also the automation runbook. I rely on incident routing daily because it ensures the alerts reach the right team. The other features, such as integrations, are really good to integrate PagerDuty Operations Cloud with different platforms, such as Jira and ServiceNow platforms to automatically open an incident. These are really helpful top features.
I would give PagerDuty Operations Cloud eight out of ten, considering all the features I have been using and also the improvements I have suggested. I chose eight out of ten because PagerDuty Operations Cloud is generally strong in the areas that matter the most, especially incident routing and escalation management which are extremely reliable and directly reduce MTTA and MTTR. It stands out for dependable on-call orchestration and smooth incident response coordination, especially with Slack and Jira integrations. But it does not reach a ten because noise reduction still needs more automation, analytics lack deeper customization such as custom dashboards to filter among the teams, and the service dependency graph gets cluttered in large environments. With smarter automation and improved visualization of the analytics, it could easily move closer to a perfect ten.
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)
Or G.
Disappointing with Misleading Billing Practices
Reviewed on Jul 21, 2026
Review provided by G2
What do you like best about the product?
Not much really
What do you dislike about the product?
I don't like PagerDuty that much. The billing is misleading and expensive. The UI makes it seem like the seats are auto-allocated and you can't decrease the number easily. But it turns out they keep charging you for a high number of seats, and you need to contact human support to reduce the seats, which feels like a scam. Plus, it's hard to find things, and everything feels old.
What problems is the product solving and how is that benefiting you?
I use PagerDuty for alerting on production errors, but I find the billing misleading and expensive. The UI is confusing, making it look like seats are auto-allocated, requiring human support to reduce them.
Anonymous
Essential Tool for Incident Management and Team Coordination
Reviewed on Jul 18, 2026
Review provided by G2
What do you like best about the product?
I like PagerDuty's reliable alerting, which ensures that critical issues are escalated to the right team quickly. The on-call schedules are easy to manage, and the fast incident escalation greatly helps reduce response times and improve team coordination. I also appreciate its seamless integration with other tools and how the mobile app makes it easy to respond to incidents from anywhere.
What do you dislike about the product?
I find the initial setup and configuration complex, and I think the pricing is high for small teams. I would also welcome more customizable reporting and a simpler interface for managing advanced configurations.
What problems is the product solving and how is that benefiting you?
I use PagerDuty for on-call alerting, incident management, and ensuring critical issues are escalated to the right team quickly. It helps us respond to critical incidents faster by automating alerts, reducing missed notifications, and streamlining incident coordination.
Mukul Bhati
Automation has reduced manual support effort and has improved incident response accuracy
Reviewed on Jul 16, 2026
Review from a verified AWS customer
What is our primary use case?
My main use case for PagerDuty Operations Cloud is for doing the automation part and minimizing the efforts. It decreases the count of the L1 support team because most of the tasks have been handled by the operation of PagerDuty Operations Cloud and the AI.
What is most valuable?
PagerDuty Operations Cloud offers several valuable features that have significantly benefited our operations. The solution keeps the person available and only rings the alert while there is any outage or any issue generated in the live environment. Additionally, it has an automated section where it handles similar issues if they happen again and is able to troubleshoot them by itself by running those jobs or actions that have been put in PagerDuty Operations Cloud.
PagerDuty Operations Cloud positively impacts our organization by helping us increase the overall SLA delivery. Earlier, we were having a delivery count of 87% or 88%, but after setting up PagerDuty Operations Cloud, we were able to achieve the SLA up to 99.5% post-installation. The improvement in SLA and SLI is mostly because of the faster incident response and fixing the issues that are most generic and reoccurring, which has been minimized and helped us increase the SLA and SLI.
What needs improvement?
PagerDuty Operations Cloud is already at its best, but AI can be integrated just to set it up and continue learning and provide a list of fixes that can be applied as suggestions, as that might help improve PagerDuty Operations Cloud operations.
For how long have I used the solution?
I have been using PagerDuty Operations Cloud for around three years or more.
What do I think about the stability of the solution?
PagerDuty Operations Cloud is stable and much more stable than previous solutions.
What do I think about the scalability of the solution?
PagerDuty Operations Cloud's scalability is much more stable than expected. We can scale it up whatever the requirements are, so scalability is good.
How are customer service and support?
Regarding customer support, we never found any reason to get support from the customer. We were already supported while setting up the infrastructure and it was good. I would rate the customer support on a scale of one to ten as ten out of ten.
Which solution did I use previously and why did I switch?
Previously, we were using Teams for generating the alerts and Slack, but we prefer PagerDuty Operations Cloud, which offers many more options and setups that can be used.
How was the initial setup?
To deploy PagerDuty Operations Cloud in our organization, we have used public and private cloud. Earlier it was on-premises but we switched to private cloud.
What about the implementation team?
We have implemented the AI and automation through PagerDuty Operations Cloud for incident response. As mentioned earlier, it increased the SLA from 87% to 99% and our operations have been improved, and there is a very low count of clear or false alerts.
What was our ROI?
We have seen a return on investment. We have cost-cutting on the employees as we have decreased the headcount since there is less man labor required while PagerDuty Operations Cloud is able to handle all the alerts first as an L1. There is a lot of money saved compared to the pricing or the license that we have spent.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing for PagerDuty Operations Cloud is that pricing and license are good to go. Everything is perfect as per the licensing and pricing setup cost. There is no more suggestion I can provide based on that. We completely achieved whatever we are spending.
Which other solutions did I evaluate?
Before choosing PagerDuty Operations Cloud, we evaluated other options and chose Teams.
What other advice do I have?
We are using PagerDuty Operations Cloud to our maximum capacity and we appreciate the support that it has for continuing to learn from the issues that we have and to predict the outages or any alerts or whatever escalation is required. It can fulfill that.
PagerDuty Operations Cloud's embedded AI has significantly influenced revenue protection in terms of reducing alert fatigue and incident costs. We have improved a lot, and we have improved 25 to 27% of our overall incident management.
The alert reduction feature of PagerDuty Operations Cloud has a significant impact on preventing costly incidents in our organization. Alert reduction has been decreased as a result of removing false alerts. Earlier, we were getting 30 to 35 alerts per day. Now, there are only four or five general alerts that are genuine. That is a significant amount of alert reduction.
For others looking into using PagerDuty Operations Cloud, I would completely suggest that PagerDuty Operations Cloud is a good option to install or set up in infrastructure. It handles the infrastructure very well. I would rate this review nine out of ten overall.