SaaS Ranking
Menu

SaaS transparency ranking · Engineering and data

Incident management software

34 vendors · updated 2026-10-17

On-call and incident response tools, ranked by what they publish about how they handle your data.

Public transparency score, not a product or security rating. Transparency means: published on the vendor's own site, readable without a login, found by us at the addresses we checked.

+13points above the median of every category we measure

  • Incident management30
  • All categories17
Median transparency score, out of 100. Incident management sits above the median across every category we measure.
  1. A0 0%
  2. B1 3%
  3. C4 12%
  4. D6 18%
  5. E12 35%
  6. F11 32%
34 vendors with a score. Bands have fixed thresholds, see how the score works.
All filters
Show only vendors where we found

Transparency band

0 without enough data for a band

34 vendors

Sort by

Not in the ranking

We could not measure these products with our method, so they are listed here instead of being scored. This says something about our method, not about the vendor.

Narrow it down

Each of these lists the Incident management vendors that meet one condition, with the source for each, and appears only where at least 8 of them meet it.

Shared dependencies

7 of 8 Incident management vendors whose subprocessor list we could read name Amazon Web Services on it, that is 88 %.

Of the 8 Incident management vendors whose subprocessor list we could read, these names appear on the most of them. A vendor without a published list cannot be missing from one, so it is not in the denominator.

Named on the list ofVendorsShareWhat that says
Amazon Web Services 7 88 % 7 of 8 Incident management vendors whose subprocessor list we could read name Amazon Web Services on it.
Twilio 6 75 % 6 of 8 Incident management vendors whose subprocessor list we could read name Twilio on it.
Slack 4 50 % 4 of 8 Incident management vendors whose subprocessor list we could read name Slack on it.
Atlassian 3 38 % 3 of 8 Incident management vendors whose subprocessor list we could read name Atlassian on it.
Microsoft Azure 3 38 % 3 of 8 Incident management vendors whose subprocessor list we could read name Microsoft Azure on it.
Cloudflare 2 25 % 2 of 8 Incident management vendors whose subprocessor list we could read name Cloudflare on it.
Datadog 2 25 % 2 of 8 Incident management vendors whose subprocessor list we could read name Datadog on it.
DigitalOcean 2 25 % 2 of 8 Incident management vendors whose subprocessor list we could read name DigitalOcean on it.

This is a naming, not a dependency. A name on a subprocessor list means the vendor published it there. Whether anything actually runs on it, how much of it, and what the fallback is, is on none of these pages. What the figure does show is concentration: if three of your four candidates name the same provider, you have one path and not four.

This category, criterion by criterion

How this market does on each criterion, with its own share and how it compares with the rest.

Every result links its source on the vendor page. A grey segment means we could not measure it, not that it is missing. See how we score.