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.
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.
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
Himanshu J.
Centralized Incident Response with Practical AI Summaries
Reviewed on May 14, 2026
Review provided by G2
What do you like best about the product?
It does a really good job centralizing incident response, rather than forcing teams to juggle alerts across email, Slack, monitoring tools and random dashboards. The event orchestration and escalation workflows are genuinely useful, especially once they’re set up properly.
What’s improved a lot recently is the AI side. The incident summarization and contextual insights are actually practical during active incidents, because nobody wants to sift through a flood of alerts just to figure out what changed. The AI-generated summaries help speed up triage, instead of feeling like a checkbox feature.
What’s improved a lot recently is the AI side. The incident summarization and contextual insights are actually practical during active incidents, because nobody wants to sift through a flood of alerts just to figure out what changed. The AI-generated summaries help speed up triage, instead of feeling like a checkbox feature.
What do you dislike about the product?
Alert noise is still the biggest risk. Even with AI/event intelligence, if monitoring inputs are messy, PagerDuty can still overwhelm people with too many notifications. That’s more of a setup issue, but it becomes a product experience issue quickly.
What problems is the product solving and how is that benefiting you?
It solves the operational chaos problem during outages. incidents get routed immediately to the right people with escalation if nobody responds. PagerDuty can route it to the correct on-call engineer, summarize related incident context and keep collaboration structured
Arkajit D.
PagerDuty Brings Order to Production Incidents with Smart Escalations
Reviewed on May 12, 2026
Review provided by G2
What do you like best about the product?
The best part about PagerDuty is its ability to minimize operational mayhem during actual production incidents, especially for firms where every second of downtime is associated with lost dollars, customer confidence, and regulatory risk.
For example, in a fintech firm, we had an incident with our payment reconciliation system whereby our payment reconciliation process would fail at times during our settlement periods due to delays in queue processing between our bank partners and internal ledgers. Prior to implementing structured incident management, there was chaos in the way alerts were being handled via our Slack channels and email. However, after introducing PagerDuty, there was a defined process of alert escalations based on services. Every time latency levels increased, the relevant backend, infra, and database engineering teams would be escalated through the incident process to help minimize any delay in resolving the issue.
Another benefit about PagerDuty was its ability to cut down on noise and prioritize critical alerts. When you work within fast-growing systems and event-driven architectures, it is easy for engineers to get used to too many alerts.
For example, in a fintech firm, we had an incident with our payment reconciliation system whereby our payment reconciliation process would fail at times during our settlement periods due to delays in queue processing between our bank partners and internal ledgers. Prior to implementing structured incident management, there was chaos in the way alerts were being handled via our Slack channels and email. However, after introducing PagerDuty, there was a defined process of alert escalations based on services. Every time latency levels increased, the relevant backend, infra, and database engineering teams would be escalated through the incident process to help minimize any delay in resolving the issue.
Another benefit about PagerDuty was its ability to cut down on noise and prioritize critical alerts. When you work within fast-growing systems and event-driven architectures, it is easy for engineers to get used to too many alerts.
What do you dislike about the product?
Another point that I find unappealing about PagerDuty is that as more complex environments scale, the system tends to be noisy and harder to manage operationally without proper management and maintenance of alert hygiene at the early stages of the project lifecycle.
For example, in an environment for a fintech company, where real-time fraud detection and transactions monitoring applications operate, we originally set too many infrastructure and application-level alerts within PagerDuty. Over time, engineers began receiving numerous low-information content alerts in peak transaction periods, coming from various dependent microservices that were downgraded in performance but did not impact customers. This led to engineers spending more time dealing with notifications than solving the underlying problem. In no way PagerDuty was problematic here, but the platform requires precise incident design and management for large-scale distributed environments.
The second point I'd like to make is that maintaining escalation policies becomes more challenging in terms of operational costs as the team grows larger. Engineering organizations often undergo frequent changes in terms of responsibilities and service ownership, so keeping escalation structures up-to-date is important for proper incident resolution.
For example, in an environment for a fintech company, where real-time fraud detection and transactions monitoring applications operate, we originally set too many infrastructure and application-level alerts within PagerDuty. Over time, engineers began receiving numerous low-information content alerts in peak transaction periods, coming from various dependent microservices that were downgraded in performance but did not impact customers. This led to engineers spending more time dealing with notifications than solving the underlying problem. In no way PagerDuty was problematic here, but the platform requires precise incident design and management for large-scale distributed environments.
The second point I'd like to make is that maintaining escalation policies becomes more challenging in terms of operational costs as the team grows larger. Engineering organizations often undergo frequent changes in terms of responsibilities and service ownership, so keeping escalation structures up-to-date is important for proper incident resolution.
What problems is the product solving and how is that benefiting you?
The PagerDuty product line is currently addressing one of the most pressing operational challenges facing modern engineering organizations: the lag between identifying a problem and aligning the necessary resources to address it effectively.
In a financial technology setting with transaction processing and settlement flows, even small delays can result in downstream operational problems such as payment failures, accounting discrepancies, customer complaints, and regulatory risks. In the absence of formal incident management protocols, alerts would be scattered throughout various monitoring services, emails, and communication channels, sometimes resulting in ownership disputes when outages occurred. The PagerDuty suite unified this entire workflow process, routing all incidents according to their respective ownership and priority automatically.
For example, there was an actual operational situation where we received latency alerts from our banking integration partner due to API requests being slow during peak payout periods. The initial challenge for us was to determine whether the problem was in our infrastructure, in our database, or if it was coming from our integration partner. However, with PagerDuty integrated with our monitoring systems and escalation processes, the backend engineers, infrastructure responders, and platform leads could be notified simultaneously and collaborate to resolve the bottleneck much faster than before.
In a financial technology setting with transaction processing and settlement flows, even small delays can result in downstream operational problems such as payment failures, accounting discrepancies, customer complaints, and regulatory risks. In the absence of formal incident management protocols, alerts would be scattered throughout various monitoring services, emails, and communication channels, sometimes resulting in ownership disputes when outages occurred. The PagerDuty suite unified this entire workflow process, routing all incidents according to their respective ownership and priority automatically.
For example, there was an actual operational situation where we received latency alerts from our banking integration partner due to API requests being slow during peak payout periods. The initial challenge for us was to determine whether the problem was in our infrastructure, in our database, or if it was coming from our integration partner. However, with PagerDuty integrated with our monitoring systems and escalation processes, the backend engineers, infrastructure responders, and platform leads could be notified simultaneously and collaborate to resolve the bottleneck much faster than before.
Telecommunications
Peace of mind for on-call teams, though setup takes time
Reviewed on May 11, 2026
Review provided by G2
What do you like best about the product?
What really stands out is its unmatched reliability and sophisticated incident orchestration. The platform is incredibly effective at cutting through alert noise with AIOps, so our team is only paged for high-priority, actionable incidents. The on-call scheduling and escalation policies are also very robust, which gives us full confidence that critical issues won’t go unacknowledged.
What do you dislike about the product?
To be honest, what I dislike most is the pricing structure, which can get quite expensive as you scale your team or add more advanced features. The initial configuration and setup can also feel a bit overwhelming; there are so many options and integrations that the learning curve for a new administrator is steeper than I expected. On top of that, the mobile app notifications can sometimes be a little too aggressive if you haven’t fine-tuned your alert rules perfectly.
What problems is the product solving and how is that benefiting you?
PagerDuty helps solve the problem of fragmented incident response and alert fatigue. Before we started using it, we often missed critical notifications, or multiple people would jump on the same issue without clear coordination.
For me, the biggest benefit is a lower Mean Time to Repair (MTTR) and a clear, automated escalation path. It gives me peace of mind that if something breaks at 3 AM, the right person is notified immediately. I also have the context I need to fix the issue quickly, which ultimately helps us maintain our service level agreements (SLAs) with our customers.
For me, the biggest benefit is a lower Mean Time to Repair (MTTR) and a clear, automated escalation path. It gives me peace of mind that if something breaks at 3 AM, the right person is notified immediately. I also have the context I need to fix the issue quickly, which ultimately helps us maintain our service level agreements (SLAs) with our customers.
Arkajit Das
Real-time incident response has improved but alert grouping and setup still need refinement
Reviewed on May 10, 2026
Review provided by PeerSpot
What is our primary use case?
My main use case for PagerDuty Operations Cloud is to handle all technical perspectives of incident management and real-time alerting. I primarily use PagerDuty Operations Cloud for the health tech environment, specifically in telemedicine platform and EHR-related applications, where it is required to ensure high availability.
What is most valuable?
PagerDuty Operations Cloud offers excellent features including the alert system and automated incident escalation capability, which is effective for routing issues to the right team through mobile notifications, SMS, or phone calls.
The real-time monitoring feature in PagerDuty Operations Cloud makes the biggest difference for my team, as it is quite helpful for on-call management and day-to-day operations.
PagerDuty Operations Cloud has positively impacted my organization by working effectively with most cloud service providers like AWS or Azure , improving visibility and reliability of incident responses.
I have seen a reduction in incident response time, with MTTR efficiently reduced by 30 to 40%, better SLA compliance, and improved operational visibility through incident analytics and reporting dashboards since implementing PagerDuty Operations Cloud.
The alert reduction feature in PagerDuty Operations Cloud has minimized downtime and improved incident response efficiency in my organization.
What needs improvement?
There are a couple of areas where PagerDuty Operations Cloud can be improved, such as enhancing Event Intelligence and alert grouping features and simplifying the initial configuration of escalation policies.
For how long have I used the solution?
I have been using PagerDuty Operations Cloud for more than two years.
What do I think about the stability of the solution?
PagerDuty Operations Cloud is stable.
What do I think about the scalability of the solution?
The scalability of PagerDuty Operations Cloud is quite good, as it works well with enterprise-level systems.
How are customer service and support?
Customer support for PagerDuty Operations Cloud is quite effective.
Which solution did I use previously and why did I switch?
Before implementing PagerDuty Operations Cloud, I relied on basic monitoring tools and email alerts for health tech monitoring, and I noticed a significant improvement after switching.
What was our ROI?
I have not reached ROI yet, but I am close, with a reduction in downtime and faster incident resolution.
What's my experience with pricing, setup cost, and licensing?
I would say the pricing is quite mid-range, but the setup cost and licensing can sometimes be a little challenging.
Which other solutions did I evaluate?
Before choosing PagerDuty Operations Cloud, I evaluated basic monitoring tools and email alert systems but found that PagerDuty offered stronger integration and operational visibility.
What other advice do I have?
I would advise others to clearly define their incident management strategy before implementing PagerDuty Operations Cloud. I would rate this solution a 7 out of 10.
Kevin N.
User-Friendly with Simple Setup
Reviewed on May 09, 2026
Review provided by G2
What do you like best about the product?
I use PagerDuty for note-taking and incident management. I like the ease of use interface, which is user-friendly and makes things relatively simple.
What do you dislike about the product?
I think the trending of info could be improved. Specifically, it could be better at showing the number of incidents and the length of time.
What problems is the product solving and how is that benefiting you?
I use PagerDuty for note taking and incident management, mainly to monitor outages.