
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.
Resources
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
Streamlined Incident Management, Powerful Alerts
Reliable Alerting, Seamless Integration
Reliable Alerting and Quick Incident Response
Fast, User-Friendly, and Perfect for Trend Analysis
Reliable incident paging has kept outages under control but separate client notes are still missing
What is our primary use case?
My usual use cases with PagerDuty Operations Cloud involve handling incidents through a full flow. When there is an outage, an incident is created that can be either severity one or severity two. As the person on call that day, I receive a page from PagerDuty on the app and three calls on my cell phone. When I pick up the call, PagerDuty IVR asks me to acknowledge the incident. Once I acknowledge the incident from the call, I go to PagerDuty through the website, which is much easier to navigate than the mobile app. I then page other teams responsible for the incident, as well as the stakeholders and product owners.
PagerDuty is integrated with Microsoft Teams, so I open a Teams bridge call to resolve the issue and update all incident details in PagerDuty notes, which automatically integrates with ServiceNow incident and sends messages to stakeholders' phone numbers.
One time while hanging out in the mountains, there was no internet signal but there was cell reception. An incident happened while I was on call that day. Normally, without internet, I would not be able to know about it, but because of PagerDuty, I was paged three times on my cell phone as well as through text message. I managed to call another colleague from my work and told him to take care of the incident. This helped me avoid breaching the SLAs on incident acknowledgment and allowed me to access remote incidents without relying solely on the internet.
What is most valuable?
The features of PagerDuty Operations Cloud that I find most valuable involve being automatically paged whenever an incident is triggered. PagerDuty has group names embedded into it, and when we set up PagerDuty in our organization, we embedded the group name, allowing me to page other respondents without having to go separately into Microsoft Teams, add everybody's name, and then ping and call them. I can do this directly from PagerDuty itself.
The notes update feature allows me to put the details of the incident in the notes and click post, and it is integrated everywhere. Everything is centralized.
PagerDuty Operations Cloud has improved my team's ability to focus on core tasks rather than routine issues primarily due to its availability and reliability. We do not worry about whether PagerDuty will call us when an incident triggers, allowing us to focus on that incident. The notes update process ensures that everyone gets informed with just one update.
What needs improvement?
I think PagerDuty Operations Cloud could be improved by having two fields for incident updates. In my work, I handle incidents that have two fields: work notes visible only to developers working on the incident and additional comments visible to the client. When I update through PagerDuty, everything gets updated into the additional comments. There should be two fields, perhaps based on how it is integrated with ServiceNow.
I have not used PagerDuty's autonomous AI agents or generative AI, so I am not sure whether it is integrated.
I can evaluate the effectiveness of PagerDuty Operations Cloud in providing insights for decision-making, and I rate it around seven out of ten. PagerDuty Operations Cloud is really helpful. With generative AI integrated and a chatbot, I think it would bump the rating up to nine, but I have not used it yet, so I cannot say for certain.
For how long have I used the solution?
I have been using PagerDuty Operations Cloud for around one and a half years.
What do I think about the stability of the solution?
Regarding the reliability and stability of this product, I find it really stable. Based on my personal experience in the mountains, I can vouch for it. My organization measures the acknowledgment rate by checking how many times a call rings and how quickly the responder acknowledges the incident. The acknowledgment rate is really good, around ninety to ninety-five percent.
What do I think about the scalability of the solution?
I think the scalability of PagerDuty Operations Cloud is superb. It can handle many requests according to demand. As other members and teams are added to our organization, it has not impacted the latency, call failure, or anything else. The performance is really good.
How are customer service and support?
I do not often communicate with the technical support of PagerDuty. The manuals are created by our team, so we use those.
Which solution did I use previously and why did I switch?
I did not use a different solution for the same use case before PagerDuty Operations Cloud. PagerDuty Operations Cloud was the first solution I used.
How was the initial setup?
I did not participate in the initial setup of PagerDuty Operations Cloud. When I joined the organization after one and a half years of use, it was already set up for me by the IT team.
What about the implementation team?
I have not personally implemented automation through PagerDuty for incident response, but I think some of my colleagues may have done so.
What was our ROI?
I am not aware of the impact of PagerDuty's alert reduction feature on preventing costly incidents in our organization, as that metric is not shared with me.
What's my experience with pricing, setup cost, and licensing?
I am not sure about the influence of PagerDuty Operations Cloud on revenue protection in terms of reducing alert fatigue and incident costs, as these are organizational-level decisions, and employees are not involved in those discussions.
Which other solutions did I evaluate?
Before PagerDuty Operations Cloud was chosen, I did not evaluate other options, as the decision was made by the board members.
What other advice do I have?
My review rating for PagerDuty Operations Cloud is seven point five out of ten.