PagerDuty vs Resolve: who uses which
Customers, public proof and the companies that use both.
On usedby, 11 companies use PagerDuty and 24 use Resolve. 1 company uses both, including SAP.Latest check Nov 13, 2026: 34 of 35 public lines checked. Counts include every proof level, job-post signals included. A company on both tools counts at any proof level, and a job post on one side is marked as such.
Who uses PagerDuty, Resolve, or both
Every company with a public proof for at least one of the two tools.
10
listed for PagerDuty only
1
company uses both
23
listed for Resolve only
On usedby, 10 companies are listed for PagerDuty only, 23 are listed for Resolve only and 1 uses both, out of the 34 companies listed for at least one. An absent listing does not prove non-use.
Where it lands
Recently publicly listed customers
Who uses both
Companies with a public line on both tools, at any proof level: the strongest proofs come first, and a job post is marked.
| Company |
|---|
 SAP |
Side by side
Facts from our data and from each vendor's public pages. Each line says where it comes from.
Vendor facts checked: PagerDuty, 0 of 5; Resolve, 1 of 5. Missing facts remain unverified, not absent features.
PagerDuty
ResolveWhat customers report
Results as the vendor or the customer published them, with the source and the date.
PagerDuty
reducing initial response and communications times to critical incidents by 30%
SAP
Vendor case study, pagerduty.com, published Sep 16, 2023
MTTR is now under 30 minutes
DraftKings
Vendor case study, pagerduty.com, published Jun 15, 2023
Resolve
~60% reduction in mean time to resolve (MTTR)
Salesforce
Vendor case study, resolve.ai, published Apr 16, 2026
75 percent reduction in incident investigation time
Zscaler
Vendor case study, resolve.ai, published Dec 12, 2025
Evidence for your decision: Resolve
Source observations. Check the required plan and conditions before choosing.
Documented tasks
MSCIAutomate internal business workflows
Now, an alert lands in PagerDuty, ResolveAI joins the incident channel via Microsoft Teams, and the investigation starts automatically.
Choice criteria
Integration: Google CloudSourced observation
Plan: Unknown
Google Cloud Grafana Kubernetes Datadog Github Splunk custom-tool Prometheus Kloudfuse Slack Chronosphere Amazon Web Services Claude Codex Cursor Notion
Integration: GrafanaSourced observation
Plan: Unknown
Google Cloud Grafana Kubernetes Datadog Github Splunk custom-tool Prometheus Kloudfuse Slack Chronosphere Amazon Web Services Claude Codex Cursor Notion
Integration: KubernetesSourced observation
Plan: Unknown
Google Cloud Grafana Kubernetes Datadog Github Splunk custom-tool Prometheus Kloudfuse Slack Chronosphere Amazon Web Services Claude Codex Cursor Notion
Integration: DatadogSourced observation
Plan: Unknown
Google Cloud Grafana Kubernetes Datadog Github Splunk custom-tool Prometheus Kloudfuse Slack Chronosphere Amazon Web Services Claude Codex Cursor Notion
Integration: GithubSourced observation
Plan: Unknown
Google Cloud Grafana Kubernetes Datadog Github Splunk custom-tool Prometheus Kloudfuse Slack Chronosphere Amazon Web Services Claude Codex Cursor Notion
Integration: SplunkSourced observation
Plan: Unknown
Google Cloud Grafana Kubernetes Datadog Github Splunk custom-tool Prometheus Kloudfuse Slack Chronosphere Amazon Web Services Claude Codex Cursor Notion
Integration: PrometheusSourced observation
Plan: Unknown
Google Cloud Grafana Kubernetes Datadog Github Splunk custom-tool Prometheus Kloudfuse Slack Chronosphere Amazon Web Services Claude Codex Cursor Notion
Integration: SlackSourced observation
Plan: Unknown
Google Cloud Grafana Kubernetes Datadog Github Splunk custom-tool Prometheus Kloudfuse Slack Chronosphere Amazon Web Services Claude Codex Cursor Notion
Integration: Amazon Web ServicesSourced observation
Plan: Unknown
Google Cloud Grafana Kubernetes Datadog Github Splunk custom-tool Prometheus Kloudfuse Slack Chronosphere Amazon Web Services Claude Codex Cursor Notion
Integration: NotionSourced observation
Plan: Unknown
Google Cloud Grafana Kubernetes Datadog Github Splunk custom-tool Prometheus Kloudfuse Slack Chronosphere Amazon Web Services Claude Codex Cursor Notion
Integration: Google CloudSourced observation
Plan: Unknown
Conditions: Product scope needs verification
Product: resolve
Setup and limits: Named plan, contract entitlement, connector scopes, permissions, volume limits and regional eligibility remain unknown.; Documented only; not_tested. No authenticated vendor operation executed.; Named integration listing only; operation semantics and data direction are not established.
Google CloudGrafanaKubernetesDatadogGithubSplunk
Questions about PagerDuty and Resolve
Which is used more, PagerDuty or Resolve?
Resolve has more customers on usedby: 24 against 11 for PagerDuty.
Do companies use both PagerDuty and Resolve?
Yes. 1 company uses both on usedby, including SAP.
Who uses PagerDuty?
11 companies on usedby, each with the public page that shows it. See who uses PagerDuty.
Who uses Resolve?
24 companies on usedby, each with the public page that shows it. See who uses Resolve.
How does usedby count customers?
A company counts when a public page shows it: a vendor's customer page, a case study, a press release or a job post, most saved with a dated capture. Every line is a customer, at one of four proof levels: confirmed, declared by the company itself, observed or signal (a job post, the weakest). A company counts as using both tools when it has a line on each, at any level; the list shows the strongest proofs first and marks job posts.