
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
Details
Features and programs
Buyer guide

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

Standard contract
Customer reviews
Flexible Alerting Options That Keep Us on Top of Incidents
Scalable Event Orchestration with AIOps and Easy Integrations
PagerDuty Simplifies Major Incident Management and Escalations
Dependable Alerts, Smart Incident Grouping, and Deep Integrations
Automated incident response has reduced manual effort and protects revenue with faster recovery
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.