How the plans score

Plans compared, scored and sourced

Each plan is scored 0–10 on six weighted criteria. Overall scores are the weighted average. Numbers in brackets point to how we measured.

Weighting
Check coverage25%
Alerting and on-call20%
Integrations15%
Data retention15%
Team and access15%
Support10%
Overall scoreweighted, out of 10
5.2
Starter
Solo developers and side projects
8.1
TeamOur pick for most teams
Product teams with an on-call rota
9.4
Scale
Several teams and regulated workloads
Check coverage[1]
regions, interval, protocols · weight 25%
6.5
8.5
9.5
Alerting and on-call[2]
routing, escalation, quiet hours · weight 20%
5.0
9.0
9.5
Integrations
chat, paging, ticketing, webhooks · weight 15%
6.0
8.0
9.0
Data retention[3]
raw results and incident history · weight 15%
4.0
7.0
9.5
Team and access
seats, roles, SSO, audit log · weight 15%
3.5
7.5
9.5
Support[4]
channels and response targets · weight 10%
5.0
7.5
9.0
Pick a plan
Start with Starter
Start with Team
Start with Scale
  1. Median of 3 test accounts per plan, 6 regions, 1 Aug – 31 Oct 2026. Checks at each plan’s shortest interval.
  2. Time from a failing check to a page, 200 simulated incidents per plan. Escalation needs Team or higher.
  3. Retention as listed in each plan’s terms on 1 Nov 2026; longer retention is available as an add-on on Starter.
  4. Response targets are business-hours targets from the support policy, not guarantees.