Squadcast
Provenance unknown Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Squadcast, Inc. · www.squadcast.com
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Squadcast 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
- Panel verdict
- The AI panel rates Squadcast 2/5, the mean of 6 judges. 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. how scores are made
- As of
- Vendor pages captured 17 Nov 2026; evaluated by the panel 18 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
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
The scores
| Criterion | Panel median |
|---|---|
| On-call schedules, rotations & escalation | 3 of 5 |
| Alert delivery, routing & noise reduction | 3 of 5 |
| Incident response, status pages & post-incident review | 2.5 of 5 |
| Integrations, API & administration | 2 of 5 |
| Platform reliability, security & compliance | 1 of 5 |
| European sovereignty | 2 of 5 |
On-call schedules, rotations & escalation
Show reasoningHide reasoning
How this is scored
Who is on call and what happens when nobody answers: schedules with daily, weekly and custom rotations, layers and follow-the-sun hand-offs across time zones, overrides, swaps and holiday cover, escalation policies with timeouts, repeat and fallback levels, round-robin and team escalation, calendar export and sync, reminders before a shift, on-call reports and hours exported for on-call pay and working-time rules, and a mobile app that shows the shift and lets a responder hand it over.
0 — No schedules or escalation of any kind; alerts go to a fixed list of people.
3 — A simple weekly rotation and one escalation step; overrides, layers, time zones and on-call reports are basic or not described.
5 — Schedules with several rotation types and layers, overrides and swaps from the app, escalation policies with timeouts and several levels, time-zone handling, calendar export, shift reminders, and a report of who was on call when.
8 — Follow-the-sun and multi-team schedules, round-robin and conditional escalation, coverage gaps flagged before they happen, schedules and policies managed as code or by API, and on-call hours exported per person for pay and working-time rules, all documented.
10 — Scheduling a large organisation runs on: every feature above with fairness and fatigue reports, rest-period rules enforced or warned, schedules imported from HR or workforce tools, and every scheduling limit documented per plan.
The SRE Lead
Daily, weekly and monthly repetitions, assignee groups acting as multiple rotations, override shifts, on-call reminders and a gap warning in the calendar view are all documented, and escalation policies target users, squads or schedules with round-robin, repeats up to three times and per-service policies. We found no public information on calendar export, on-call hours reports for pay and working-time rules, or managing schedules as code — the things my sixty-engineer organisation needs before committing rotations. 1 2
The IT Operations Manager
Daily, weekly and monthly rotations with assignee groups acting as layers, overrides, shift reminders, timezone-aware schedule views with a gap warning, and escalation policies to users, squads or schedules that can repeat up to three times with round-robin inside a level cover most of what my five-admin standby needs. The documented escalation time range of 1 to 48 hours is a problem for us, though: the deputy should be paged ten minutes after the first call, and we found no public information on setting a step that short. We also found no public information on calendar export or an on-call hours report for pay and working-time rules. 1 2
The MSP NOC Lead
Schedules repeating daily, weekly or monthly with time-of-day restrictions, multiple assignee groups as rotations with configurable switch frequency, override shifts, gap warnings in the calendar and on-call reminders are documented, and per-service escalation policies with round-robin levels and repeat limits let me keep a separate rota for the night shift and each key account. Past schedule events stay immutable as an accurate record of who was on call when. I found no public information on calendar export, swaps from a mobile app, or exporting on-call hours for pay and working-time rules. 1 2
The ICT Risk Officer
Rotations repeat daily, weekly or monthly, multiple assignee groups hand over after a configurable number of shifts, overrides exist, schedule gaps raise a banner before they bite, users get shift reminders and see schedules in their local time, and past events are immutable — that frozen record is what I would show a regulator who asks who held the pager. Escalations attach schedules, escalate by time-ordered levels between 1 and 48 hours, support round-robin within a level and up to three repeats. I found no public information on calendar export, on-call hours exported for pay and working-time rules, or managing schedules as code. 1 2
The Engineering Manager
Daily, weekly and monthly repeats, multiple assignee groups acting as rotations, override shifts, shift reminders, gap warnings and time-zone handling for geography-based rotations are documented, and escalation policies carry ordered levels, round-robin within a level and up to three repeats. But for our works-council setup we found no public information on an export of on-call hours for payroll, swaps from a mobile app, calendar export, or rest-period and fatigue warnings. 1 2
The Skeptic
Multiple assignee groups act as separate rotations with a configurable switch frequency, shifts repeat daily, weekly or monthly with time-of-day and day-of-week restrictions, overrides exist, the calendar warns of coverage gaps, reminders go out ahead of shifts, and schedules display in each member's local timezone. Escalation policies attach to schedules per service with round-robin within a level, up to three repeats and timers between one and forty-eight hours — a floor of one hour before anyone escalates is worth a hard question. We found no public information on calendar export, on-call hours reports for pay and working-time rules, or managing schedules as code. 1 2
Alert delivery, routing & noise reduction
Show reasoningHide reasoning
How this is scored
Whether the alert reaches a human and only the right one: notification by push, SMS, voice call, email and chat, critical alerts that override do-not-disturb on iOS and Android, personal notification rules with retries and fallbacks, acknowledgement by app, SMS reply or keypad, delivery receipts, live call routing for a hotline, routing rules by service, severity, payload and time, deduplication, grouping and correlation of related alerts, suppression and maintenance windows, heartbeats for silent failures, and inbound email and webhook endpoints.
0 — Sends no alerts to people; a dashboard or log viewer only.
3 — Push and email notifications with acknowledgement; SMS, voice, routing rules and noise reduction are basic or not described.
5 — Push, SMS, voice and email with personal notification rules and retries, critical alerts on mobile, acknowledgement from the app or by phone, routing by service and severity, deduplication, and maintenance windows.
8 — Alert grouping or correlation with its logic documented, routing on payload fields and time conditions, delivery receipts and a notification log per alert, live call routing, heartbeat monitoring, suppression rules, and the countries and channels where SMS and voice are delivered stated.
10 — Delivery that is evidenced, not promised: redundant SMS and voice carriers named with automatic failover, delivery statistics published, AI or rule-based noise reduction with measurable results, and every notification limit per plan documented.
The SRE Lead
Routing is genuinely documented: incoming incidents route on tag fields using Golang regex, case-sensitive operators, OR evaluation and rule priority, override the default escalation policy, and the routing decision appears in the incident's activity timeline, while live call routing adds simultaneous or sequential calling of up to ten responders, keypad service mapping and local and toll-free numbers in the USA, Canada, the UK and India. Email, push, SMS and phone are available as personal notification channels. We found no public information on deduplication, grouping, suppression and maintenance windows, heartbeats, retry and fallback behaviour or acknowledgement methods, so I cannot confirm one database outage pages one team rather than five. 2 3 4
The IT Operations Manager
Email, push, SMS and phone channels with personal notification rules, a genuinely capable tag-based routing engine (regex, rule priority, OR evaluation, override of the default escalation policy) and a hotline with keypad mapping and simultaneous or sequential calling, with routing numbers self-service in the USA, Canada and the UK, are all documented. However, we found no public information on how an alert call is acknowledged, critical-alert override of do-not-disturb, retries, deduplication, or maintenance windows to silence pages during planned plant work. Rule changes also carry a documented 5-minute caching delay, which matters at 3 a.m. 2 3 4
The MSP NOC Lead
Tag-based routing rules with case-sensitive operators, Golang regular expressions, rule priority and OR evaluation, routing to a user, squad or escalation policy with the routing reason shown in the incident timeline are well documented and would let me route by customer and contract, alongside notification channels of email, push, SMS and phone with admin-managed personal rules and live call routing with simultaneous and sequential strategies and numbers in the USA, Canada, UK and India. Routing rule changes carry a five-minute cache delay before taking effect. I found no public information on deduplication, grouping, maintenance windows, delivery receipts or heartbeats, which is the noise handling a sixty-customer shop lives on. 2 3 4
The ICT Risk Officer
Email, push, SMS and phone are all configurable per user as personal notification rules, and routing is strong: tag-based rules with expressions, Go-flavoured regex, priority ordering, OR evaluation and an override of the default escalation policy, with the routing reason written into the incident's activity timeline — that traceability matters to me. Live call routing is documented with simultaneous or sequential strategies, a keypad mapped to services, up to ten responders and session logs capturing caller ID and recordings, with numbers provisioned in the USA, Canada, the UK and India. I found no public information on deduplication, grouping, suppression or maintenance windows, heartbeats, delivery receipts or retries, and an SMS to a routing number is explicitly not supported. 2 3 4
The Engineering Manager
The tag-based routing engine is well documented with regex matching, rule priority and routing to users, squads or escalation policies, alongside personal notification rules across email, push, SMS and phone, and live call routing with simultaneous and sequential strategies for the US, Canada, UK and India. We found no public information on deduplication, grouping, suppression or maintenance windows, heartbeats, delivery receipts, or critical alerts overriding do-not-disturb. 2 3 4
The Skeptic
Personal notification rules cover email, push, SMS and phone, and the routing engine matches tag fields with case-sensitive operators, Golang regex, OR evaluation and rule priority, overriding the service's default escalation and logging the routing reason in the incident timeline. Live call routing takes incoming calls and voicemail with simultaneous or sequential strategies to at most ten responders, keypad-to-service mapping and session records, with numbers self-provisioned in the USA, Canada and the UK and via support in India; an SMS to a routing number is not supported and routing-rule changes take five minutes to apply. We found no public information on deduplication, grouping, suppression windows, heartbeats, delivery receipts or critical alerts overriding do-not-disturb. 2 3 4
Incident response, status pages & post-incident review
Show reasoningHide reasoning
How this is scored
What happens once the alert is a real incident: declaring an incident from Slack, Microsoft Teams or the app, a dedicated channel and video bridge, incident roles and commander, severities and incident types, runbooks, tasks and automated workflows, stakeholder updates, public and internal status pages with subscribers, a timeline, post-incident reviews and postmortem templates with follow-up actions, analytics such as MTTA and MTTR, and AI features that summarise, suggest causes or draft the review.
0 — No incident record of any kind beyond the alert itself.
3 — An incident list with status and notes; channels, roles, status pages and post-incident reviews are basic or not described.
5 — Incidents declared from chat or the app with severities, a Slack or Teams channel created, incident roles, a timeline, a public status page, stakeholder notifications, postmortem templates, and MTTA and MTTR reports.
8 — Workflows and runbooks that automate the response, incident types with their own process, internal and public status pages with components and subscribers, follow-up actions tracked into Jira or Linear, service catalogue and dependencies, and AI summaries with their data handling described.
10 — A response process a regulated enterprise runs on: every feature above with major-incident and regulatory reporting templates, cross-team analytics and learning reviews, AI features documented with model provider, data handling and an opt-out, and every limit per plan stated.
The SRE Lead
Status pages are well covered — public and private pages, components and component groups, four issue states, email and webhook subscriptions, custom domains and message templates — and postmortems offer templates, follow-up checklists, review statuses and Markdown or PDF export once an incident is resolved, with an activity timeline at least for routing decisions. We found no public information on declaring incidents from Slack, incident roles, severities, MTTA and MTTR analytics or AI-drafted reviews, which is the half of response my teams live in. 3 5 6
The IT Operations Manager
Public and private status pages with components, component groups, custom domains, subscribers by email or webhook and issue states are thoroughly documented, and postmortems come with templates, a follow-up checklist, review statuses and Markdown or PDF export with plan-based storage limits. We found no public information on declaring incidents from chat or the app, incident roles and severities, runbooks, or MTTA and MTTR reporting. For plant communications the status page story is strong; the response-process story is thin on these pages. 5 6
The MSP NOC Lead
Public and private status pages with components, component groups, five component states, email and webhook subscribers, custom domains and four issue states are documented, and postmortems after resolution with templates, follow-up checklists, review statuses and Markdown or PDF export would feed my monthly customer reporting. I found no public information on MTTA and MTTR reports, incident roles and commander, runbooks and automated workflows, or declaring an incident from chat, so the response-time reporting per customer I owe each month is not shown. 5 6
The ICT Risk Officer
Status pages are thoroughly documented — public and private, components and groups, email and webhook subscribers, custom domains, message templates and four issue states — and postmortems carry templates, review statuses, follow-up checklists and Markdown or PDF export. An incident activity timeline exists that records, among other things, why an alert was routed where. I found no public information on declaring an incident from chat or the app, incident roles and a commander, runbooks or automated workflows, MTTA and MTTR analytics or AI summaries — the process core I would rely on for a DORA-classified major incident is undocumented. 3 5 6
The Engineering Manager
Public and private status pages with components, component groups and email and webhook subscribers, plus postmortems with templates, review statuses, follow-up checklists and PDF/Markdown export, are documented, and incidents carry an activity timeline. We found no public information on declaring incidents from chat, incident roles and severities, runbooks or automated workflows, or MTTA and MTTR reporting. 3 5 6
The Skeptic
Status pages come in public and private forms with components, component groups, five component states, issue states from Investigating to Resolved, email and webhook subscribers, custom domains and message templates, and each incident carries an activity timeline. Postmortems open only once an incident is resolved and support templates, review statuses, follow-up checklists and export to Markdown or PDF, with attachments capped at five files of ten MB and storage at 50 MB on the free plan — and a file, once uploaded, cannot be deleted. We found no public information on declaring incidents from chat, incident roles and commanders, runbooks, workflows or MTTA and MTTR analytics. 3 5 6
Integrations, API & administration
Show reasoningHide reasoning
How this is scored
How the tool fits the stack and the organisation: inbound integrations with monitoring and observability tools (Prometheus, Grafana, Datadog, Zabbix, Checkmk, PRTG, Azure Monitor, CloudWatch, Sentry), outbound integrations with chat, ticketing and ITSM tools (Slack, Microsoft Teams, Jira, ServiceNow, ConnectWise, Autotask), bidirectional sync, a documented REST API, webhooks and a Terraform provider, teams and services, roles and permissions, single sign-on (SAML or OIDC) and SCIM, audit logs, multi-tenant or customer separation for service providers, and migration help from other tools.
0 — No integrations and no administration beyond a single shared account.
3 — Email and webhook intake and a few named integrations; the API, roles and single sign-on are basic or not described.
5 — Dozens of named inbound and outbound integrations including Slack or Teams and Jira, a documented REST API and webhooks, teams with roles, two-factor authentication, single sign-on, and an import path from at least one other tool.
8 — Bidirectional ITSM and ticketing sync, a Terraform provider or configuration as code, SCIM provisioning, granular roles per team, audit logs, service-provider or multi-tenant set-ups, and API coverage of schedules, escalations and incidents documented.
10 — Administration that scales across many teams and customers: every setting reachable by API with parity stated, audit logs exportable to a SIEM, SSO enforced with SCIM, white-label or sub-account management for service providers, and documented migration from the major competitors.
The SRE Lead
Three integration types are documented — webhook-based alert sources for monitoring, observability and error-tracking tools, outbound webhook connectors that transform payloads for third-party systems, and extensions for Slack, Microsoft Teams, Google Hangouts, CircleCI and Jira — alongside team roles with permission gating and read-only Stakeholder and Observer users. We found no public information naming individual alert sources such as Prometheus or Sentry, or on a documented REST API, Terraform, single sign-on, SCIM, audit logs or migration paths, so schedules in Terraform is not something I can confirm. 1 2 7
The IT Operations Manager
All alert sources arrive by webhook, which is presumably how Checkmk and PRTG would reach it, but the captured pages name no specific monitoring integrations — the named ones are Slack, Microsoft Teams, Google Hangouts, Jira Server and Cloud, and CircleCI, with custom extensions available on request. Role permissions are documented for managing escalation policies, but we found no public information on a documented REST API, single sign-on, SCIM, audit logs or a Terraform provider. 7 2
The MSP NOC Lead
Three integration types built on webhooks are described — alert sources, webhook connectors that transform outgoing payloads for third-party systems, and extensions — with named ChatOps for Slack, Microsoft Teams and Google Hangouts, Jira Server and Cloud for ticketing, and CircleCI, plus read-only stakeholder and observer roles and role permissions for escalation policies. We found no public information on a documented REST API, single sign-on, SCIM, audit logs or multi-tenant separation for service providers. The captured pages name Jira only for ticketing, so we found no public information on connectors for Autotask or ConnectWise, and the PSA sync without anyone copying text is not shown. 7 1 2
The ICT Risk Officer
Three integration families are documented — alert sources over webhooks, outgoing webhook connector scripts, and extensions — with Slack, Microsoft Teams, Google Hangouts, Jira Server and Cloud, and CircleCI named, plus custom extensions on request. Role permissions gate who may manage escalation policies. I found no public information on a documented REST API and its coverage, single sign-on, SCIM provisioning, audit logs, bidirectional ticketing sync, or migration help from other tools. 2 7
The Engineering Manager
Webhook-based intake for monitoring tools, outgoing webhook connectors, and named extensions for Slack, Microsoft Teams, Jira and CircleCI are documented, as are teams with role-based permissions and read-only stakeholder roles. We found no public information on a documented REST API, single sign-on, SCIM, audit logs, Terraform, or a migration path from another on-call tool. 1 2 7
The Skeptic
Three integration types are documented: webhook-based alert sources from monitoring, observability, log-management and error-tracking tools — we found no public information naming the specific monitoring products — outgoing webhook connectors that reshape payloads for third-party systems, and extensions naming Slack, Microsoft Teams, Google Hangouts, Jira Server, Jira Cloud and CircleCI, with custom extensions on request. Role permissions govern escalation-policy management and stakeholders hold read-only roles that cannot sit on schedules. We found no public information on a documented REST API's coverage, single sign-on, SCIM, audit logs or migration paths from other tools. 1 2 7
Platform reliability, security & compliance
Show reasoningHide reasoning
How this is scored
Whether the pager works on the day everything else is down and holds up in an audit: an architecture independent of the customer's own cloud, multi-region or multi-zone hosting with failover, a stated availability or SLA with credits, the vendor's own public status page and incident history, delivery via redundant carriers, encryption in transit and at rest, security certifications (ISO 27001, SOC 2, BSI C5), penetration tests, data retention and deletion, audit trails, and what the vendor documents for DORA, NIS2, HIPAA or other regulated customers.
0 — Nothing on availability, security or how the service is operated.
3 — A claim of high availability or "enterprise security"; the SLA, status page, certifications and architecture are basic or not described.
5 — A public status page, a stated availability or SLA, hosting regions named, encryption in transit and at rest, ISO 27001 or SOC 2 stated, and data retention described.
8 — An SLA with credits published, the incident history public, multi-region failover or redundancy documented, redundant notification carriers named, certifications with their scope, a trust centre with reports on request, and a DORA or NIS2 addendum or mapping offered.
10 — Operation evidenced end to end: failover tested and published, independent audits (ISO 27001, SOC 2 Type II, BSI C5) with reports available, regulatory obligations for financial and critical-infrastructure customers explained in plain language, and the vendor's own post-incident reviews public.
The SRE Lead
The captured pages name EU and US data centres as hosting regions. We found no public information on an availability or SLA commitment, the vendor's own status page and incident history, certifications, encryption, data retention or documentation for regulated customers — thin ground for trusting a pager on the worst day. 5
The IT Operations Manager
The captured pages show data centers in the EU and the US, and nothing else on how the service is operated: we found no public information on an availability commitment or SLA, the vendor's own status page and incident history, certifications, encryption, or penetration testing. For a paging service I need working on the night our own network is the thing that is down, this is the thinnest part of the record. 5
The MSP NOC Lead
The only fact bearing on this is that accounts sit in EU or US data centres. We found no public information on a stated availability or SLA, the vendor's own status page and incident history, certifications, encryption, penetration testing, or DORA and NIS2 documentation. 5
The ICT Risk Officer
The only operational facts the captured pages yield are EU and US data centres, plus call-session records that capture caller ID, assignment and duration. I found no public information on an availability figure or SLA with credits, the vendor's own status page, encryption, certifications, penetration testing, retention or deletion, or any DORA or NIS2 documentation. Since the tool itself would be a third-party ICT service in my register, what is documented is not enough to place it there. 5
The Engineering Manager
The only operational fact we found is that the service runs in EU and US data centers. We found no public information on availability or an SLA, the vendor's own status page and incident history, certifications, encryption, penetration tests, or documentation for regulated customers. 5
The Skeptic
The only operational fact we found is that the service runs in EU and US data centers, evidenced by separate regional email-sending records for status pages — which is where a customer signs up, with no failover story attached. We found no public information on an availability figure or an SLA with credits, the vendor's own status page and incident history, encryption, certifications or penetration tests. 5
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Who the contracting entity and the parent company are, where alerts, incident timelines, chat transcripts, contact data, phone numbers and account data are stored and processed, and who the subprocessors are (hosting, SMS and voice carriers, push services, email delivery, AI summary and transcription models, analytics, support and payment tools). Independently sourced by the sovereignty pipeline. Telephony and push providers needed to reach a responder in another country are part of what the product does and are not counted against it; where the data is stored and who processes it is. A self-hosted edition the customer runs on its own European servers counts as the customer's chain, whatever the vendor's seat.
0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and no data processing agreement offered.
3 — A privacy policy and a data processing agreement exist, but hosting location is unstated or non-EU and the subprocessors are not listed.
5 — EU hosting available and an EU contracting entity or EU representative, but parts of the chain (SMS and voice, AI, support, payment) run through non-EU providers without a stated safeguard.
8 — EU hosting on named infrastructure, EU contracting entity, subprocessors listed with their locations, a data processing agreement published, and security certifications (ISO 27001, SOC 2) stated — or a self-hosted edition documented that keeps every record on the customer's own servers.
10 — Sovereign end to end and evidenced: European ownership, entity, hosting and every subprocessor including the AI models and notification carriers, or a self-hosted edition with no call home, data export and deletion documented, and certifications published with their scope rather than implied.
The SRE Lead
EU hosting is evidenced by separate EU and US data centres with distinct SPF records for status page email. We found no public information on the contracting entity, subprocessors and their locations, or a data processing agreement, so the chain beyond hosting is unknown to me. 5
The IT Operations Manager
Data centers in the EU and the US are documented, with EU-hosted status page email sending for EU-signed customers, which answers where at least that data sits. We found no public information on the contracting entity's domicile, the subprocessors behind SMS, voice, push and email delivery, or a data processing agreement. 5
The MSP NOC Lead
An EU data centre is evidenced alongside the US one, with a separate EU record for status-page email sending, so European hosting is available. We found no public information on the contracting entity, subprocessors and their locations, or a published data processing agreement, so the rest of the chain around the EU hosting cannot be judged. 5
The ICT Risk Officer
An EU data centre is confirmed alongside a US one, with a European endpoint for status-page mail — that is the only sovereignty fact on record. I found no public information on the contracting entity's seat, a data processing agreement, or any subprocessor for hosting, SMS, voice or AI, and the support pages themselves are served under a SolarWinds domain. Routing numbers are documented for the USA, Canada, the UK and India, so I have no European processor chain to enter in the register. 4 5
The Engineering Manager
An EU hosting region is documented, which is a starting point for our data-protection review. We found no public information on an EU contracting entity or representative, the subprocessors behind SMS, voice and email delivery, or a published data processing agreement. 5
The Skeptic
EU and US data centers are on record, so a European hosting option exists, though we found no public information on the infrastructure provider or where each data category — alerts, timelines, phone numbers, contact data — is stored. The vendor is listed as Squadcast, Inc. while the captured documentation is served from a SolarWinds domain, and no parent company is disclosed in what we read. We found no public information on subprocessors, a data processing agreement or certifications. 5
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real annual cost from public pages alone: price per user or responder and per plan, whether stakeholders and viewers are free, how many SMS and voice notifications are included and what the rest cost per country, which features (incident response, status pages, AI, live call routing, SSO, audit logs) are add-ons or in higher plans, platform fees, minimum seats, annual versus monthly billing, and the currency and VAT treatment.
0 — No public prices at all; every customer is a sales call.
3 — A starting price per user exists, but notification limits, add-ons and the enterprise tier are unclear.
5 — Plans are public with their price per user and main inclusions, but at least one commonly needed piece (SMS and voice volume, status pages, AI, SSO or the top tier) is unpriced or "contact sales".
8 — Every plan priced publicly with its scaling rule, notification limits and overage prices stated, add-ons priced, stakeholder seats explained, minimum term and billing options and VAT treatment stated.
10 — Complete price computability: annual cost derivable for a given number of responders, stakeholders, notifications and status pages, with every add-on, overage and support fee and the cancellation and data-export terms published.
The SRE Lead
The captured pages name Free, Pro, Premium and Enterprise plans, place Live Call Routing as an add-on package for Enterprise accounts, and give postmortem attachment storage of 50 MB on the free plan and unlimited above it. We found no public information on any price — per user, per plan, notification volumes or overages — so a buyer cannot begin to compute an annual cost from these pages. 4 6
The IT Operations Manager
No price figures appear on the captured pages; what is documented is plan structure — a free plan with 50 MB of postmortem attachment storage and unlimited storage on Pro, Premium and Enterprise — and that Live Call Routing is an add-on package for accounts on the Enterprise plan. Before we could budget this for five admins across three plants, we would have to ask the vendor directly. 4 6
The MSP NOC Lead
The captured pages reveal plan names — Free, Pro, Premium and Enterprise — postmortem attachment storage limits per plan, and that live call routing is an add-on package for Enterprise accounts, but no price per user, notification limits, add-on prices, minimum terms, billing options or VAT treatment. No figure on these pages lets a buyer compute an annual cost. 4 6
The ICT Risk Officer
The plan lineup is documented — Free, Pro, Premium and Enterprise — along with the free plan's 50 MB postmortem storage limit, and live call routing is named as an add-on package restricted to the Enterprise plan. No price per user, notification volume, overage, add-on price, billing term or VAT treatment appears anywhere in the captured pages. A buyer cannot compute an annual cost from public material alone. 4 6
The Engineering Manager
The captured pages name plan tiers — Free, Pro, Premium and Enterprise — and show live call routing as an add-on for Enterprise accounts and postmortem storage limits per plan, but contain no price figures at all. We found no public information on the price per responder, whether read-only stakeholders are charged, or SMS and voice volumes and overage costs, so I cannot compute our annual cost from these pages. 1 4 6
The Skeptic
The captured pages disclose four plan tiers — Free, Pro, Premium and Enterprise — that live call routing is an add-on package available only on Enterprise, and that postmortem attachment storage is 50 MB on the Free plan and unlimited on Pro, Premium and Enterprise. That is the whole of it: we found no public information on per-user prices, notification volumes or overage costs per country, add-on prices, stakeholder seats, billing terms or VAT treatment, so no annual cost can be computed from these pages. 4 6
Questions about Squadcast
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), All Quiet (3.5/5) and OneUptime (3.5/5) 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 (EU-Made, Germany). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Squadcast alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 17 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 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. Know more? Tell us
- 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. Know more? Tell us
- 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. Know more? Tell us
Sources (7)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 On-call schedules, rotations & escalation — found from sitemap support.incidents.cloud.solarwinds.com Checked 17 Nov 2026 Details →
- 2 On-call schedules, rotations & escalation — found from sitemap support.incidents.cloud.solarwinds.com Checked 17 Nov 2026 Details →
- 3 Alert delivery, routing & noise reduction — found from sitemap support.incidents.cloud.solarwinds.com Checked 17 Nov 2026 Details →
- 4 Alert delivery, routing & noise reduction — found from sitemap support.incidents.cloud.solarwinds.com Checked 17 Nov 2026 Details →
- 5 Incident response, status pages & post-incident review — found from sitemap support.incidents.cloud.solarwinds.com Checked 17 Nov 2026 Details →
- 6 Incident response, status pages & post-incident review — found from sitemap support.incidents.cloud.solarwinds.com Checked 17 Nov 2026 Details →
- 7 Integrations, API & administration — found from sitemap developers.squadcast.com Checked 17 Nov 2026 Details →