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 BMC Software
Top
10
In Agile Lifecycle Management, IT Business Management, ML Solutions
Top
25
In Log Analysis
Top
50
In ELT/ETL
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
Workflow Orchestration
Application and data workflow orchestration with scheduling, management, and monitoring capabilities for production workflows
AIOps and Observability
Cloud-native observability and AIOps solution with topology rationalization and root cause analysis for hybrid-cloud environments
IT Asset Discovery and Mapping
IT asset discovery and dependency mapping solution with dynamic topology updates and visual representation of business services
Predictive Resource Optimization
Predictive analytics-driven optimization for IT resources and applications including Kubernetes, microservices, containers, and multi-cloud services
Edge Data Collection and Analysis
Operational technology data collection, aggregation, and analysis at the edge with IT and OT data integration for failure prediction
Standard contract
No
No
No
Customer reviews
Jajati Behera
Automated incident response has reduced manual effort and protects revenue with faster recovery
Reviewed on Apr 16, 2026
Review provided by PeerSpot
What is our primary use case?
The main use cases for PagerDuty Operations Cloud are incident management and handling high severity incidents in an automated way. For example, at midnight, if we get a high severity incident, PagerDuty throws alarms or notifications to our Slack or team channel so other people get notified and start working on it. Another use case is that we are also monitoring our cloud VMs using PagerDuty automation, which we have done using service integration with our cloud provider. It identifies situations such as our cloud VM going to high CPU usage or requests getting dropped, which can significantly damage the application. At that time, PagerDuty sends alerts to the respective persons, the person who is on-call.
Another use case is that we also use PagerDuty to execute some of the installation scripts using PagerDuty webhooks integration in a totally automated way. Suppose any cloud resource goes faulty and we need to ensure that the respective installation or script gets executed automatically by the use of PagerDuty webhook, so that the issue gets fixed automatically. Nobody is going to be informed or bothered, as it is a self-healing process. We also use another notification to our mobile phone for any P1, which is a high severity incident that will definitely have a business impact. At that moment, we have also leveraged this tool to get a phone call.
What is most valuable?
The best features of PagerDuty Operations Cloud that I find most valuable are incident management and webhooks. The reason is that if you go for any P1 incident, somebody would usually need to do all the manual efforts, such as creating the Slack channel, informing the team leads and other team members, gathering information related to any service outage or component outage, and providing it in a text format to the Slack channel. All these manual efforts take much time, but PagerDuty does that for you. It gathers the related services and people who are already in that Slack channel and sends the alerts. It automates the whole process, so no human intervention is required.
Another very good functionality is webhooks. They work exceptionally well. If my cloud infrastructure has an issue, a person needs to investigate, and if it requires a server reboot or installation of a script, that person needs to intervene manually. However, using this webhook, we can send one alert or notification to our automated job indicating that this issue requires execution of a particular script or file on that server, which fixes the ongoing issue without requiring human intervention. If this happens at midnight, people can sleep easily without any headache, and PagerDuty will take care of the task.
PagerDuty Operations Cloud has a very good impact on our company, especially regarding business and service level agreements, as well as reducing incident resolution time. It also helps automate manual work.
What needs improvement?
An additional feature I think would improve PagerDuty Operations Cloud is integration with development scenarios or the code building side. For example, if there is a service outage, I believe PagerDuty could have functionality to check that out and verify if there was any faulty code pushed to our GitHub repository. If there was an error in our repository structure, then having a functionality to find these errors would provide much clarity. This would help developers quickly identify and fix issues, making sure they can change code wherever necessary. That would work exceptionally well.
For how long have I used the solution?
I have been using PagerDuty Operations Cloud for more than three years.
What do I think about the stability of the solution?
PagerDuty Operations Cloud is stable, with very little chance of missed alerts. It catches almost all alerts, sending notifications in a timely manner. We have not seen PagerDuty Operations Cloud instance go down or fail; it works smoothly, so I would say PagerDuty Operations Cloud operates perfectly fine.
What do I think about the scalability of the solution?
The scalability of PagerDuty Operations Cloud is totally doable. For example, I have created a group where I defined incident priorities, and if my team grows from five members to nine, I can easily onboard these new users to PagerDuty Operations Cloud and configure the alerting system to scale up or down based on requirements. The scalability is quite easy. PagerDuty Operations Cloud also offers many integrations, allowing us to scale to other cloud providers if necessary.
How are customer service and support?
Customer service from PagerDuty is great. Sometimes we need help with setups, which are usually minor, but whenever we need support, we receive it promptly. I would say their support is quite good.
Which solution did I use previously and why did I switch?
Before choosing PagerDuty Operations Cloud, we evaluated other solutions including Grafana , which is for monitoring cloud infrastructure. While we used Grafana for automated monitoring, it lacks the incident management and webhook features that PagerDuty Operations Cloud provides. Therefore, we can manage tasks effectively with PagerDuty Operations Cloud. We also used Nagios, which is another application monitoring tool that only allows monitoring application logs and lacks a solid alerting system, unlike PagerDuty Operations Cloud.
How was the initial setup?
The initial setup of PagerDuty Operations Cloud was very straightforward. It was not complex at all. The documentation provided by PagerDuty is very handy and easy to understand, making the process comfortable and non-confusing.
What about the implementation team?
We did not use an integrator, reseller, or consultant for the deployment. Since we were able to set it up ourselves, we never felt the need for any consultants or assistance from PagerDuty while setting up our environment or workspace.
What was our ROI?
I have seen a return on investment with PagerDuty Operations Cloud, particularly in incident management. Using this mechanism reduces the number of incidents I need to raise manually, decreasing the effort required. For example, I could say that in a month, we need to raise 150 incidents manually, but with PagerDuty Operations Cloud, I can cut that down to 100 incidents. This results in a reduction of about 40 or 50 incidents.
What's my experience with pricing, setup cost, and licensing?
The setup cost and pricing for PagerDuty Operations Cloud are very cost-effective, but I have a suggestion: if PagerDuty could provide a trial version for individual users, rather than just corporate users, it would help others learn more about PagerDuty Operations Cloud. They could conduct proofs of concept, do hands-on testing, and recommend PagerDuty Operations Cloud in their respective companies or projects.
Which other solutions did I evaluate?
We did evaluate other tools and even assessed the trial version of those tools by checking all functionalities and use cases. Given that our use cases were larger, we ultimately chose to proceed with PagerDuty Operations Cloud.
What other advice do I have?
We have started using PagerDuty's autonomous AI agents, but we have not leveraged it in detail yet. We have started using it, and hopefully very soon we will implement the AI agent to create solutions in our architectures, which will definitely help us a lot.
For decision-making, when we leverage the AI agent, we need to deploy it in our workspace and feed data to the agent in more use cases, including data in a spreadsheet or JSON or XML format. Cases and scenarios will be added so that the agent will analyze all the data we feed. In the future, if any such scenarios occur in our workspace or infrastructure, PagerDuty Operations Cloud agent will react and make decisions based on the previous trained data.
The influence of PagerDuty's embedded AI on revenue protection is significant. PagerDuty Operations Cloud helps us resolve incidents much faster, which means we consistently meet our SLAs, thereby avoiding penalties for service outages. This helps us save revenue by ensuring that clients or stakeholders do not impose penalties due to outages.
PagerDuty Operations Cloud's AI functionality helps improve my team's ability to focus on core tasks rather than routine issues, particularly with cloud service monitoring and incident response time. These aspects significantly increase our productivity. The solution's alert reduction feature has a significant impact on preventing costly incidents in our company. Creating multiple incidents manually takes a lot of time, but PagerDuty Operations Cloud does that in seconds. This reduction in incident creation time greatly influences our project delivery. Overall, I would rate this product a perfect ten.
amit u.
Reliable Alerting and Strong On-Call Management
Reviewed on Apr 16, 2026
Review provided by G2
What do you like best about the product?
It has a reliable alerting system and strong on-call management. We receive call, email, and message notifications, which helps ensure we don’t miss important alerts.
What do you dislike about the product?
It has a complex setup, and I sometimes get confused when configuring alert routing and escalation policies, which can make it hard to set up correctly. It also takes time to fully optimize.
What problems is the product solving and how is that benefiting you?
PagerDuty is one of the best tools for incident alerting, and in our case it makes on-call management run smoothly. We’re a monitoring team, and it benefits us in several ways—most importantly, we don’t miss any important notifications.
Dhanush Hari
Incident response has become faster and on-call alerts stay reliable for critical operations
Reviewed on Apr 10, 2026
Review from a verified AWS customer
What is our primary use case?
I am an end user of PagerDuty Operations Cloud in my organization, with a background in incident management. I primarily use it for managing on-call schedules, triggering and handling incidents, and monitoring alerts. It helps ensure timely responses, efficient escalation, and better coordination during incidents, making it a key tool for maintaining operational reliability.
How has it helped my organization?
PagerDuty Operations Cloud has improved our incident response by ensuring reliable alerting and faster escalation to the right teams. It has significantly reduced alert fatigue through better alert filtering and deduplication. The platform has also lowered our mean time to resolve (MTTR) with runbook automation and streamlined on-call management, leading to fewer disruptions and improved overall operational efficiency.
What is most valuable?
The features of PagerDuty Operations Cloud that I have found the most valuable and useful include alerting, which is very reliable with minimal delays, and the escalation policies and routing rules that are more flexible. Additionally, the on-call scheduling capabilities are great, and it integrates well with any cloud platforms such as AWS , GCP, or Azure , and observability tools such as DataDog and New Relic for logging and checking out logs.
I have noticed that PagerDuty Operations Cloud influences revenue protection by reducing alert fatigue and incident costs. AIOps has helped recently in reducing noise and alert duplications, and runbook automations aid in lowering the mean time to resolve by integrating triggers to Slack and updating runbooks.
I see PagerDuty Operations Cloud as a very good incident management and on-call platform, mostly used by large-scale organizations because it comes with premium pricing, but it is very reliable with alerting and on-call scheduling, triggering incidents, escalation policies, rules, and runbooks.
What needs improvement?
I think an area of PagerDuty Operations Cloud that could be improved is their premium pricing, as it compares unfavorably with competitors such as Atlassian's Opsgenie and ServiceNow , which offer bundle deals, plus DataDog now has incident management capabilities. Overall, the premium pricing makes it less accessible for small to medium businesses.
I think the pricing of PagerDuty Operations Cloud is a bit too high, and also, the UI can feel a bit curvy for new users; the learning curve might be a bit dense for them. The initial setup is straightforward, but the event orchestration could be complex, and the automation workflow definitely requires great expertise.
For how long have I used the solution?
I have been using PagerDuty Operations Cloud for approximately four years.
What do I think about the stability of the solution?
I would rate the stability and reliability of PagerDuty Operations Cloud 9.5 out of 10. The platform is highly stable and dependable in production environments, especially for critical incident management workflows. We have experienced consistent alert delivery, reliable on-call scheduling, and minimal downtime or disruptions.
That said, no system is completely perfect, so I cannot say it is 100% flawless. However, overall it has proven to be very reliable for mission-critical operations, where even small delays or failures would have significant impact.
What do I think about the scalability of the solution?
I would rate the scalability of PagerDuty Operations Cloud 8 out of 10. From a technical perspective, the platform scales very well and can support large, distributed teams with complex incident management needs. It handles high volumes of alerts, multiple services, and integrations across cloud platforms efficiently.
However, the main limitation to scalability is its premium pricing. As organizations grow and onboard more users or services, the cost increases significantly, which can be a challenge for small to mid-sized teams. So while it is technically highly scalable, cost can be a limiting factor for broader adoption.
How are customer service and support?
I have had regular interactions with PagerDuty Operations Cloud’s technical support, and my overall experience has been positive. The support team is responsive and helpful in addressing queries.
For example, during a user audit, I requested specific data on active users and those who had not accepted invitations. The support team responded quickly and provided the required information without delays. Overall, the support experience has been efficient and reliable when assistance is needed.
Which solution did I use previously and why did I switch?
I have only been using PagerDuty Operations Cloud; recently with my new organization, I am also using Fire Hydrant.
How was the initial setup?
I was not directly involved in the initial setup of PagerDuty Operations Cloud , as it was handled by senior team members. However, from my observations, the setup process appears to be straightforward at a basic level for core features like alerting and on-call scheduling.
That said, advanced configurations such as event orchestration and automation can become complex. If rules are not configured properly, they may lead to alert storms or missed incidents. Additionally, runbook automation is not plug-and-play and typically requires scripting knowledge and careful setup to function effectively.
What was our ROI?
From an ROI perspective, I do not have direct visibility into financial metrics, so I cannot quantify exact cost savings. However, I have seen strong operational ROI from PagerDuty Operations Cloud .
It has improved incident response efficiency by reducing alert fatigue, ensuring faster escalation, and lowering mean time to resolve (MTTR) through runbook automation. These improvements have helped prevent prolonged outages and reduced the impact of incidents, which indirectly contributes to cost savings and better service reliability at an operational level.
What other advice do I have?
I have some exposure to its autonomous AI agents, I have not extensively used its AIOps or generative AI capabilities. Despite that, the platform has had a strong positive impact on our operations.
By properly configuring alerting rules, we have been able to significantly reduce alert fatigue and shift focus toward more critical issues rather than routine noise. PagerDuty has also helped in reducing the number of duplicate alerts through intelligent pattern recognition.
Additionally, runbook automation has contributed to lowering our mean time to resolve (MTTR), enabling faster and more efficient incident handling. Overall, it has helped prevent costly incidents and improved operational efficiency across the team.
My review rating for PagerDuty Operations Cloud is nine point five out of ten.
Which deployment model are you using for this solution?
Hybrid Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
yusuf a.
Reliable Alerts Undermined by Poor Billing Support
Reviewed on Apr 10, 2026
Review provided by G2
What do you like best about the product?
I find PagerDuty's reliability to be world-class, providing a technically superior tool for managing on-call rotations and incident response for our engineering team. The multi-channel alerting is flawless, and the Slack and Kubernetes integrations are seamless, which are crucial for ensuring high availability of our SaaS platform. It effectively solves the critical problem of alert fatigue by ensuring major incidents in our cloud infrastructure are routed to the right engineer immediately.
What do you dislike about the product?
I'm really frustrated with PagerDuty's billing support. It's extremely slow, and responses take over a week. Fixing invoice errors like missing tax IDs is a major struggle, which is a big problem. Despite PagerDuty being about 'urgent response,' their customer service is sluggish, and that's overshadowing its technical value. We need a partner that responds to business issues as quickly as their software responds to incidents. The billing and account setup process has been a nightmare due to this lack of support.
What problems is the product solving and how is that benefiting you?
I use PagerDuty to manage on-call rotations and incident response, solving alert fatigue and ensuring critical issues reach the right engineer immediately. It helps maintain SLA commitments through clear escalation paths, integrating with our monitoring tools for high availability.
Kasey K.
No More Missed Notifications Without Constant Email Checking
Reviewed on Apr 09, 2026
Review provided by G2
What do you like best about the product?
I don’t have to constantly check my email anymore to make sure I’m not missing any notifications.
What do you dislike about the product?
The queue functionality could support more advanced automations to ensure the right people are notified during a workflow incident.
What problems is the product solving and how is that benefiting you?
We had to consistently check and refresh our emails to make sure we weren’t missing any outage alerts. It gave us peace of mind, and we could see who had responded to the incident.