# Squadcast — On-Call & Incident Management

Squadcast by Squadcast, Inc. holds a panel rating of 2/5 from 6 AI judges (category median 3/5), as of 2026-11-18. Provenance: provenance unknown; sovereignty: not determined.

- Vendor: Squadcast, Inc. (https://www.squadcast.com)
- Category: [On-Call & Incident Management](https://whats-best.ai/software/incident-management.md)
- Provenance (editorial classification): provenance unknown
- Canonical page: https://whats-best.ai/software/incident-management/squadcast
- Alternatives: https://whats-best.ai/software/incident-management/squadcast/alternatives ([markdown](https://whats-best.ai/software/incident-management/squadcast/alternatives.md))
- Data as of: 2026-11-21 · evaluated 2026-11-18 · oldest source captured 2026-11-17

**AI-generated.** Every score, rationale and verdict here is written by a panel of AI judges from public evidence — an analysis, not a hands-on test. Every fact quotes the vendor page it was read from. No score can be bought. How scores are made: https://whats-best.ai/methodology

## At a glance

- Vendor: Squadcast, Inc.
- Headquarters: Not stated on the vendor’s pages as of 17 Nov 2026
- Data hosting: Not stated on the vendor’s pages as of 17 Nov 2026
- Free plan: Not stated on the vendor’s pages as of 17 Nov 2026

## The panel's verdict

Squadcast, an on-call and incident management platform, is strongest at on-call scheduling, scored 6 to 6, on daily, weekly and monthly rotations, assignee groups acting as separate rotations, override shifts, gap warnings, shift reminders and local-time views, with per-service escalation policies carrying round-robin and up to three repeats. Alerting and routing follows at 4 to 6: tag-based rules with Golang regex, rule priority and OR evaluation override the default escalation policy and write the routing reason into the incident timeline. The weakest result is reliability and compliance at 2 to 2, where EU and US data centers are the only operational fact and no public information covers availability, an SLA, encryption, certifications or penetration testing. Sovereignty spans 2 to 4: the EU data center is on record, but judges weigh the undocumented subprocessor chain, contracting entity and data processing agreement differently; the vendor is listed as Squadcast, Inc. while its documentation is served from a SolarWinds domain. Incident response runs 4 to 6, pairing well-documented status pages with an undocumented process core; plan names appear without prices.

**Speaks for it:**
- On-call scheduling scores 6 to 6, covering daily, weekly and monthly rotations, override shifts, gap warnings and timezone-aware schedule views
- Tag-based routing rules with Golang regex, rule priority and OR evaluation override the default escalation policy and log the routing reason in the incident timeline
- Per-service escalation policies support round-robin within a level and up to three repeats, and past schedule events stay immutable
- Public and private status pages offer components, email and webhook subscribers, custom domains and message templates, with postmortems exporting to Markdown or PDF
- EU and US data centers are on record, giving a documented European hosting region

**Held against it:**
- Reliability and compliance scores sit at 2 to 2, with no public information on availability figures, an SLA with credits, encryption, certifications or penetration testing
- Escalation time inputs run only from 1 to 48 hours, with no public information on a shorter step for a deputy
- No public information covers deduplication, grouping, suppression windows, heartbeats or delivery receipts
- The captured pages name no monitoring tools among the integrations, only Slack, Microsoft Teams, Google Hangouts, Jira Server, Jira Cloud and CircleCI
- No public information covers a data processing agreement, subprocessors or the contracting entity's domicile behind the documented EU and US data centers

**Best for:**
- You need structured rotations — daily, weekly or monthly repeats, assignee groups, overrides and gap warnings — with per-service escalation policies
- You route incidents by tags such as customer or contract to a user, squad or escalation policy and want the routing reason recorded in the incident timeline
- You publish customer-facing status pages — public or private, with components and subscribers — and export postmortems to Markdown or PDF for regular reporting
- You must show an accurate record of who held the pager — past schedule events cannot be updated

**Avoid if:**
- You need a deputy paged within minutes of the first alert — escalation time inputs are documented from 1 to 48 hours
- You need routing-rule changes to apply immediately — changes carry a documented five-minute caching delay
- Your procurement must see an SLA, availability figure or certifications before adopting a paging service — reliability and compliance scored 2 to 2
- You want to reach your hotline by SMS — sending an SMS to a routing number is not supported

## Scores by judge and criterion

Scores out of 5, each judge scoring independently against the published rubric (v1). "n/r" = not rated: the vendor publishes no price, or the judge found no public information on that criterion.

| Criterion | The SRE Lead | The IT Operations Manager | The MSP NOC Lead | The ICT Risk Officer | The Engineering Manager | The Skeptic |
| --- | --- | --- | --- | --- | --- | --- |
| On-call schedules, rotations & escalation | 3/5 | 3/5 | 3/5 | 3/5 | 3/5 | 3/5 |
| Alert delivery, routing & noise reduction | 3/5 | 2/5 | 3/5 | 2.5/5 | 3/5 | 3/5 |
| Incident response, status pages & post-incident review | 2/5 | 2/5 | 3/5 | 2/5 | 2.5/5 | 2.5/5 |
| Integrations, API & administration | 2/5 | 1.5/5 | 2/5 | 1.5/5 | 2/5 | 2/5 |
| Platform reliability, security & compliance | 1/5 | 1/5 | 1/5 | 1/5 | 1/5 | 1/5 |
| European sovereignty | 2/5 | 1.5/5 | 2/5 | 2/5 | 1/5 | 2/5 |
| Pricing transparency | n/r | n/r | n/r | n/r | n/r | n/r |
| **Weighted verdict** | **2/5** | **2/5** | **2.5/5** | **2/5** | **2.5/5** | **2/5** |

### The judges

- **The SRE Lead** (v1.0): Leads site reliability at a Berlin SaaS company with sixty engineers in eight product teams, Prometheus and Grafana for metrics, Sentry for errors and everything discussed in Slack. Wants an incident declared with one command, a channel with roles and a timeline, the status page updated from the same place, alerts grouped so one database outage does not page five teams, schedules kept in Terraform, and a postmortem that writes its first draft.
- **The IT Operations Manager** (v1.0): Runs IT operations for a packaging manufacturer with 900 staff and three plants running around the clock, with Checkmk and PRTG watching servers, networks and the production line. Five administrators share a weekly standby. Wants a Checkmk alert to become a phone call that the right person acknowledges by keypad, the deputy called after ten minutes, no pages during planned maintenance, and an alerting service that still works when the plant's own network is the thing that is down.
- **The MSP NOC Lead** (v1.0): Leads the network operations centre of a managed service provider in Nuremberg that looks after sixty mid-sized customers, with Zabbix, Microsoft Sentinel and Autotask in the stack. Wants alerts routed by customer and contract hours, tickets opened and closed in the PSA without anyone copying text, a separate on-call rota for the night shift and for each key account, one customer never seeing another's data, and a monthly report per customer on response times.
- **The ICT Risk Officer** (v1.0): ICT risk officer at a Frankfurt payments company supervised by BaFin, where DORA requires major ICT incidents to be classified and reported within hours. The incident tool is itself an ICT third-party service in the register. Reads the subprocessor list, asks where incident timelines and the AI summaries of the response channel are processed, wants an SLA, audit logs and a DORA addendum in the contract, and needs the timeline to hold up as evidence for the regulator.
- **The Engineering Manager** (v1.0): Engineering manager at a logistics software company in Hamburg with developers in Germany, Portugal and Poland, where the works council has agreed an on-call policy with paid standby hours and rest periods after a night call. Wants a follow-the-sun rota across three time zones, swaps from the phone, on-call hours exported to payroll each month, a warning when the same person is paged three nights running, and a price per responder that does not charge for the managers who only read along.
- **The Skeptic** (v1.0): Has seen "never miss an alert" from a pager that was down in the same cloud region as the outage it should have reported, "unlimited notifications" that meant twenty SMS a month outside the US, and an "AI incident assistant" that sent the whole response channel to a model nobody named. Asks which carriers deliver the calls, what the SLA pays, whether schedules and history can be exported when leaving — and what the plan costs once the stakeholders need seats.

## European sovereignty — proven facts

No sovereignty finding yet.

## Key facts

Each fact is the vendor's own statement, cited to the source page it was read from ([S*n*] → Sources).

**Hosting**
- Data centers: EU · US [S5]

**Pricing**
- Live call routing availability: Enterprise · add-on package [S4]

**Product**
- Alert routing cache delay: 5 [S3]
- Alert routing description: Route alerts to the right responder(s) based on the tags they carry. [S3]
- Alert routing escalation policy override: yes [S3]
- Alert routing operators: == · != · matches/contains · does not contain · yes [S3]
- Alert routing or evaluation: yes [S3]
- Alert routing priority: yes [S3]
- Alert routing regex: Golang · yes [S3]
- Alert routing rule engine: parameters, arithmetic, logical, and string operations [S3]
- Alert routing rule search: yes [S3]
- Alert routing targets: User · Squad · Escalation Policy [S3]
- Alert routing timeline visibility: yes [S3]
- Alert routing UI builder: yes [S3]
- Alert sources: Alert Sources integrate with monitoring, observability, log management & error tracking tools [S7]
- Alert sources mechanism: webhooks [S7]
- Call strategies: Simultaneous (default) and Sequential [S4]
- Component groups: yes [S5]
- Component statuses: Operational · Degraded · Major Outage · Partial Outage · Under Maintenance [S5]
- Dmarc spf records: v=spf1 include:incidents.eu.squadcast.com ~all · v=spf1 include:incidents.squadcast.com ~all [S5]
- Edit restrictions: Routing number, country, and number type cannot be edited [S4]
- Escalation deletion restriction: yes [S2]
- Escalation policy integration: schedules must be attached to escalation policies to notify on-call users [S1]
- Escalation policy recipients: Users · Squads · Schedules · yes [S2]
- Escalation policy role permission: yes [S2]
- Escalation repeat limit: 3 [S2]
- Escalation round robin: yes [S2]
- Escalation rule order: yes [S2]
- Escalation time range: 48 · 1 [S2]
- Escalation triggered state: yes [S2]
- Extensions chatops: Slack · Microsoft Teams · Google Hangouts [S7]
- Extensions cicd: CircleCI [S7]
- Extensions custom build: yes [S7]
- Extensions ticketing: Jira Server · Jira Cloud [S7]
- Fallback support email: yes [S5]
- Gap detection: yes [S1]
- Integration types: 3 · Alert Sources · Webhook connectors · Extensions [S7]
- Issue states: Investigating · Identified · Monitoring · Resolved [S5]
- Keypad service mapping: Keypad keys map to services with alias names and attached schedules [S4]
- Live call routing: Routes incoming calls and voicemails to on-call responders [S4]
- Max concurrent responders: 10 [S4]
- Max routing numbers: 5 [S4]
- Message templates: yes [S5]
- Notification rule channels: Email · Push · SMS · Phone · yes [S2]
- Oncall reminders: yes [S1]
- Override shifts: yes [S1]
- Past events immutable: past schedule events cannot be updated [S1]
- Postmortem attachment limits: 10 · 5 [S6]
- Postmortem attachment storage limits: 50 · unlimited [S6]
- Postmortem attachments: drag and drop · copy-paste · yes [S6]
- Postmortem checklist: yes [S6]
- Postmortem export any stage: yes [S6]
- Postmortem export formats: Markdown (MD) · PDF [S6]
- Postmortem file upload deletion: no [S6]
- Postmortem requires resolved incident: yes [S6]
- Postmortem statuses: In Progress · Under Review · Published [S6]
- Postmortem supported file types: images · word processors · spreadsheets · pdfs · presentations · miscellaneous [S6]
- Postmortem templates: yes [S6]
- Postmortem update: yes [S6]
- Postmortems purpose: Postmortems summarize incident resolution and build a knowledge-base of failures and fixes shared across the team [S6]
- Private page access: Private pages visible only to authenticated Squadcast users with permissions [S5]
- Rotation groups: Assignee Groups act as rotations; multiple groups supported [S1]
- Rotation switch: group switch frequency configurable by number of shifts [S1]
- Routing behaviours: Play greeting and go to voicemail; Play greeting and call the current on-call responder [S4]
- Schedule repeats: shifts can repeat daily, weekly, or monthly with time-of-day/day-of-week restrictions [S1]
- Search engine settings: yes [S5]
- Search URL uniqueness: yes [S5]
- Sessions tracking: Caller ID · Incident ID · Recording · Assigned To · Selected Service · Duration [S4]
- SMS support: no [S4]
- Squad rotation behavior: no rotation within a Squad; members are all on-call [S1]
- Stakeholders readonly: Stakeholders/Observer roles cannot be on schedules [S1]
- Status page creation steps: Add Status Page Details · Add Component · Customize Your Page · Add Your First Issue · 4 [S5]
- Status page custom domain: yes [S5]
- Status page customization: yes [S5]
- Status page domain verification: A and TXT DNS records [S5]
- Status page domain verification deadline: 30 [S5]
- Status page inactive if unverified: yes [S5]
- Status page public private: yes [S5]
- Status page purpose: Single page showing latest status messages for ongoing or past incidents [S5]
- Status page subscriptions: yes [S5]
- Status page visibility immutable: Public/private visibility cannot be changed after page creation [S5]
- Supported regions: local · toll-free · India · USA · Canada · UK [S4]
- Timezone configuration: yes [S5]
- Timezone local: timezone defaults to local machine; schedules viewable in local time [S1]
- Webhook connectors: proxy scripts transforming Squadcast outgoing webhook payloads for 3rd party systems [S7]

## Questions

### Is Squadcast European?

Not determined: the vendor’s pages as captured do not say where Squadcast is based.

### Where does Squadcast store data?

Not stated on the vendor’s pages as of 17 Nov 2026.

### Does Squadcast have a free plan?

Not stated on the vendor’s pages as of 17 Nov 2026.

### What are the best alternatives to Squadcast?

As of 18 Nov 2026, the panel rates [ilert (4/5)](https://whats-best.ai/software/incident-management/ilert), [All Quiet (3.5/5)](https://whats-best.ai/software/incident-management/all-quiet) and [OneUptime (3.5/5)](https://whats-best.ai/software/incident-management/oneuptime) highest among the other 16 On-Call & Incident Management products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is [ilert](https://whats-best.ai/software/incident-management/ilert) (EU-Made, Germany). Ratings are the AI panel’s opinion, formed from public evidence: [how scores are made](https://whats-best.ai/methodology#ordering). The full list, with European products first: [Squadcast alternatives](https://whats-best.ai/software/incident-management/squadcast/alternatives).

## What this page leaves out

- We found no public information on compliance on the pages we read (support.incidents.cloud.solarwinds.com/schedules/schedules-legacy/create-and-manage-on-call-schedules-and-rotations, support.incidents.cloud.solarwinds.com/escalation-policies/create-and-manage-escalation-policies, support.incidents.cloud.solarwinds.com/services/alert-routing, support.incidents.cloud.solarwinds.com/live-call-routing/live-call-routing, support.incidents.cloud.solarwinds.com/status-page/status-page, support.incidents.cloud.solarwinds.com/postmortems/create-postmortems and 1 more). If the vendor publishes it somewhere else, send us the page.
- 5 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material.
- We read 7 of the 11 pages we planned to read for this product; the others could not be captured yet. Everything on this page rests on the pages we read.

## Sources

- [S1] On-call schedules, rotations & escalation — found from sitemap: https://support.incidents.cloud.solarwinds.com/schedules/schedules-legacy/create-and-manage-on-call-schedules-and-rotations (checked 2026-11-17)
- [S2] On-call schedules, rotations & escalation — found from sitemap: https://support.incidents.cloud.solarwinds.com/escalation-policies/create-and-manage-escalation-policies (checked 2026-11-17)
- [S3] Alert delivery, routing & noise reduction — found from sitemap: https://support.incidents.cloud.solarwinds.com/services/alert-routing (checked 2026-11-17)
- [S4] Alert delivery, routing & noise reduction — found from sitemap: https://support.incidents.cloud.solarwinds.com/live-call-routing/live-call-routing (checked 2026-11-17)
- [S5] Incident response, status pages & post-incident review — found from sitemap: https://support.incidents.cloud.solarwinds.com/status-page/status-page (checked 2026-11-17)
- [S6] Incident response, status pages & post-incident review — found from sitemap: https://support.incidents.cloud.solarwinds.com/postmortems/create-postmortems (checked 2026-11-17)
- [S7] Integrations, API & administration — found from sitemap: https://developers.squadcast.com/build-integrations/ (checked 2026-11-17)

---

Cite as: whats-best.ai, "Squadcast — On-Call & Incident Management", AI panel analysis, as of 2026-11-21. https://whats-best.ai/software/incident-management/squadcast

Corrections: https://whats-best.ai/correct/2032?target=page
