AlertOps
Rest of world Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 3 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by AlertOps, Inc. · alertops.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.
AlertOps at a glance
- Vendor
- AlertOps, Inc.
- Headquarters
- Not stated on the vendor’s pages as of 6 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 6 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 6 Nov 2026
- Panel verdict
- The AI panel rates AlertOps 3/5, the mean of 6 judges. how scores are made
- As of
- Vendor pages captured 6 Nov 2026; evaluated by the panel 6 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
No written verdict for this product
The panel scored AlertOps, but the summary our synthesizer wrote did not survive our own contradiction check — twice. Rather than print a paragraph we cannot stand behind, we print none. Every score, rationale and source below is unaffected; read them and draw the conclusion yourself.
The scores
| Criterion | Panel median |
|---|---|
| On-call schedules, rotations & escalation | 3 of 5 |
| Alert delivery, routing & noise reduction | 3.5 of 5 |
| Incident response, status pages & post-incident review | 3 of 5 |
| Integrations, API & administration | 3.5 of 5 |
| Platform reliability, security & compliance | 3.5 of 5 |
| European sovereignty | 1.5 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
The knowledge base documents real rotation mechanics — Fixed or Rotating shifts with daily, weekly or monthly cadence, Primary/Secondary/standby/Manager roles, per-shift time zones, override shifts and out-of-office cover — plus escalation with unlimited tiers, time-based triggers and automatic re-escalation, calendar export, and a documented API covering schedules and escalation policies. Schedules are only editable in the web UI, and we found no public information on coverage-gap warnings, follow-the-sun hand-offs, or on-call hours reports for pay and working-time rules. 18 17 3 4 9
The IT Operations Manager
Rotations are well covered for my five-admin standby: fixed and rotating shifts with daily, weekly or monthly periods, eleven shift templates, per-shift time zones, override shifts and out-of-office covering persons, plus unlimited escalation tiers where secondaries are only tried if no primary acknowledges inside the policy's wait window and the manager is paged last — my deputy-after-ten-minutes pattern. Schedules and escalation policies are also reachable through the documented API, with calendar export to Outlook. The mobile app can view but not edit schedules, and we found no public information on on-call hours reports for pay, follow-the-sun hand-offs or coverage-gap warnings. 3 4 9 17 18
The MSP NOC Lead
Scheduling is genuinely deep: Fixed and Rotating shifts with daily, weekly or monthly rotation, Primary/Secondary/standby/Manager layers, per-shift time zones, override shifts for vacations and holidays, out-of-office cover with a covering person per group, calendar export and schedule reminders — enough to run a night rota per key account — plus unlimited escalation tiers with configurable acknowledgement windows and automatic re-escalation, and schedules and escalation policies reachable through the API. We found no public information on follow-the-sun hand-offs, coverage-gap warnings before they happen, or on-call hours exported per person for pay and working-time rules, and schedules are edited in the web UI only, not the mobile app. 3 4 9 17 18
The ICT Risk Officer
Scheduling is documented in real depth: fixed and rotating shifts with daily, weekly and monthly rotation, Primary/Secondary/Manager roles with a standby tier, per-shift time zones, overrides and out-of-office cover with named covering persons, calendar export, shift reminders, and unlimited escalation tiers with configurable acknowledgement windows and a manager paged last. The REST API exposes schedules and escalation policies, and escalation analytics with audit trails are described. We found no public information on follow-the-sun hand-offs, round-robin escalation, coverage-gap warnings or on-call hours exported for pay and working-time rules, and the captured help pages state schedules cannot be added or edited in the mobile app, only in the web interface. 3 4 9 17 18
The Engineering Manager
Rotation mechanics are documented in real depth — fixed and rotating shifts with daily, weekly and monthly cadences, Primary/Secondary/standby/Manager layers, per-shift time zones that would carry a Hamburg–Lisbon–Kraków rota, overrides and out-of-office cover with a named covering person, shift reminders, calendar export, and unlimited escalation tiers with time-based triggers, all reachable through the API. Two things stop it going higher for me: the documentation states schedules cannot be added or edited in the mobile app, so swaps from the phone are out, and we found no public information on coverage-gap warnings, on-call hours exported per person for payroll, or any fatigue warning when someone is paged night after night. 18 17 3 4 9
The Skeptic
Rotations are documented in real depth — Fixed and Rotating shifts at daily, weekly or monthly cadence, a standby rotation role, per-shift time zones, overrides and out-of-office cover per group, calendar export via ICAL and Webcal, and escalation tiers with configurable time thresholds, with schedules and escalation policies also reachable as API objects. But the help pages state schedules cannot be added or edited through the mobile app — only the web UI — and we found no public information on on-call hours reports for pay and working-time rules, follow-the-sun hand-offs, or warnings for coverage gaps. 3 4 9 17 18
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
Delivery runs across SMS, voice, email, push, Slack and Teams with per-responder preferred channels and automatic failover, and the correlation engine's logic is documented — similarity modelling, NLP and configurable thresholds grouping related alerts, with a claimed 68% noise reduction. Routing on payload fields, heartbeats, and deeply documented live call routing with IVR menus and voicemail transcription are all evidenced; we found no public information on delivery receipts per alert, suppression rules beyond maintenance windows, or which countries SMS and voice reach. 4 7 8 24 3 5
The IT Operations Manager
This is the strong suit: voice, SMS, push, email, Slack and Teams delivery with automatic failover between channels, live call routing straight to whoever the schedule names, call trees that keep trying responders until someone picks up, heartbeat checks for silent failures and maintenance windows — a Checkmk webhook into this would cover the phone-call alert, the acknowledgement and the quiet maintenance weekend. Correlation logic is documented (similarity modelling, NLP, configurable thresholds) with a stated 68 percent noise-reduction figure, and routing can key off payload fields. We found no public information on which countries SMS and voice reach or which carriers carry them, which is why I hold below the top band. 3 4 5 7 8 20 24
The MSP NOC Lead
Push, SMS, voice, email, Slack and Teams delivery with automatic channel failover, real-time acknowledgement tracking, priority-based routing, heartbeat checks and maintenance windows are documented. The correlation engine's grouping logic is written down — similarity modelling, NLP and customisable settings — duplicates are recognised, a vendor-stated 68% alert noise reduction is published, routing on alert payload fields is shown in a worked integration example, and live call routing with IVR, auto-attendant and timestamped call-activity logs is unusually well documented. We found no public information on delivery receipts for paging channels, suppression rules as a distinct feature, or the countries where SMS and voice are delivered — the last matters when I page German phones. 1 3 4 5 7 8 22 23 24
The ICT Risk Officer
Delivery covers SMS, voice, email, push, Slack and Teams with automatic failover to the responder's next channel, and the correlation engine's grouping logic is documented — similarity modelling, NLP and configurable thresholds — with a claimed 68 percent noise reduction and duplicate alerts recognised and ignored. Live call routing is documented down to per-line configuration, auto-attendant, time-stamped call activity logs with playable voicemail, heartbeats are supported as an inbound type, and workflows trigger on payload fields. We found no public information on the countries and channels where SMS and voice are delivered, or on critical alerts overriding do-not-disturb on mobile. 3 4 7 8 15 20 24
The Engineering Manager
Delivery is broad and documented — SMS, voice, email, push, Slack and Teams with automatic channel failover, real-time acknowledgement tracking, priority-based routing and AI reasoning over custom alert fields — and the correlation engine's logic is actually described (similarity modelling, NLP, configurable settings), alongside dedup, maintenance windows, heartbeat checks and live call routing with time-stamped call activity and playable voicemail. We found no public information on critical alerts overriding do-not-disturb, the countries where SMS and voice are delivered, or redundant carriers; a 68% noise-reduction figure is claimed on the integrations page. 4 7 22 5 20 23 8
The Skeptic
Delivery over SMS, voice, email, push, Slack and Microsoft Teams with automatic failover between channels, priority-based routing, duplicate detection, heartbeat checks, documented email and webhook intake, and live call routing with IVR menus, call trees, voicemail transcription and a time-stamped call activity log with playable voicemails. The correlation logic is described — similarity modelling, NLP and configurable thresholds — with a published 68% noise-reduction figure. We found no public information on delivery receipts per notification, the countries where SMS and voice are delivered, redundant carriers, or critical alerts overriding do-not-disturb. 4 5 7 8 20 23 24
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
The documentation states an incident can only be created by manually promoting an alert in the web app — not via API, email or integration — and we found no public information on declaring from Slack or Teams, a commander role, runbooks, or follow-up actions tracked into Jira. Strong elsewhere: public, SSO-protected and internal status pages with subscribers and stage templates, timelines and responder actions captured automatically, AI-drafted postmortems built from real alert data with a stated no-training policy, and MTTA/MTTR analytics. 21 6 22 2 12
The IT Operations Manager
Incidents are a distinct object carrying the preserved timeline, audit log and responder actions, and the review side is genuinely strong — AI-drafted postmortems with root cause, contributing factors and action items shareable as PDF, status pages in public, SSO-protected or internal form with subscribers and stage templates, and MTTA and MTTR analytics. The boundary is documented and deliberate: an alert becomes an incident only through human promotion, and the pages state incidents cannot be created via API, email or integration; we found no public information on incident roles such as a commander, a dedicated response channel or follow-up actions tracked into Jira. 2 4 6 13 21 22
The MSP NOC Lead
Incidents exist as a distinct object promoted from an alert with the timeline, audit log and responder actions preserved; public, SSO-protected and internal status pages come with components, subscribers, stage templates and 90-day incident history; MTTA and MTTR analytics and AI-drafted postmortems built from real alert data and activity logs, with root cause, contributing factors and action items, are all documented. The vendor states that promotion requires a human — incidents cannot be created via API, email or integration — and we found no public information on incident roles such as a commander, follow-up actions tracked into Jira or Linear, or a service catalogue, though AI data handling is partly addressed (no training on customer data, model providers covered by the data processing addendum). 2 4 6 12 13 21 22
The ICT Risk Officer
The incident record would hold up in an audit: manual promotion from an alert preserves the original content, timeline and audit log, every incident keeps a full stage timeline, and Chronicle drafts versioned postmortems from real alert data and activity logs that can be edited, approved and exported as PDF. Public, SSO-protected and internal status pages with subscribers, stage templates, stakeholder notifications and MTTA/MTTR analytics are documented, and the vendor states AI does not train on customer data with model providers covered by the data processing addendum, though the trust centre lists the dedicated AI data-handling disclosure as a draft still to be produced. We found no public information on incident roles such as a commander, runbooks and task tracking, follow-up actions flowing into Jira or Linear, or regulatory reporting templates for DORA-class incidents. 2 5 6 12 21 22
The Engineering Manager
Incidents are a distinct object with severity, a preserved timeline and audit trail, and the post-incident side is strong — AI drafts a timeline-accurate postmortem with root cause and action items on closure, its data handling is described (no training on customer data, model providers covered in the DPA), and status pages come public, SSO-protected or internal with stage templates, subscribers and MTTA/MTTR analytics. But the documentation states incidents can only be created by a human promoting an alert — not via API, email or integration — and we found no public information on incident commander roles, a channel created per incident, or follow-ups tracked into Jira or Linear. 21 22 6 2 12 5
The Skeptic
Incidents are a distinct object with a preserved timeline and audit log, human promotion from an alert with a customisable escalation policy, AI-drafted postmortems covering root cause, contributing factors and action items that you edit and approve, status pages in public, SSO-protected and internal form with subscribers and stage templates, stakeholder notifications, and MTTA/MTTR analytics; AI data handling is stated — no training on customer data, model providers covered by the DPA. The help pages state incidents cannot be created via API, email or integration and that no automatic promotion rules exist, and we found no public information on incident roles such as a commander, a created chat channel per incident, or follow-up actions tracked into Jira or Linear. 2 6 12 21 22
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
Two hundred-plus connectors including a certified bidirectional ServiceNow app and native ConnectWise, a documented REST API covering schedules, escalation policies, groups, workflows and incidents, Terraform workflows and code-as-configuration claimed, SAML/OIDC/AD single sign-on, role-based access, an audit trail, and an Opsgenie migration offer. We found no public information on SCIM provisioning, multi-tenant setups for service providers, or exporting audit logs to a SIEM. 8 9 1 12 11 22
The IT Operations Manager
The REST API is documented across alerts, incidents, schedules, escalation policies, groups, users and maintenance windows, alongside 200-plus connectors, a certified two-way ServiceNow app, native ConnectWise, bidirectional sync, SSO over SAML, OIDC and Active Directory, enforced MFA, role-based access and an audit trail, plus an Opsgenie migration offer. We found no public information naming Checkmk or PRTG among the pre-built connectors, so my stack would ride the generic webhook and REST path or their custom-integration offer, and we found no public information on SCIM provisioning or multi-tenant separation for service providers. 1 8 9 11 12 22
The MSP NOC Lead
The ITSM side is strong: a certified ServiceNow app with two-way sync, native ConnectWise, 200+ claimed bi-directional connectors, inbound API, email, chat and heartbeat, a documented REST API covering schedules, escalation policies, incidents and workflows, webhook set-up, Terraform providers and code-as-configuration, single sign-on via SAML, OIDC and Active Directory, enforced MFA, role-based access and an audit trail. For a provider like me two things hold it back: we found no public information naming Zabbix, Autotask or Azure Monitor connectors (a free custom integration is offered for tools not covered), and no public information on SCIM provisioning or multi-tenant and customer-separation set-ups. An Opsgenie migration path is offered. 1 8 9 11 12 22 24
The ICT Risk Officer
Two hundred plus connectors with bi-directional sync, a certified ServiceNow app with two-way incident and ticket flow, native ConnectWise, REST API sections covering schedules, escalation policies, incidents, workflows and maintenance windows, SSO via SAML, OIDC and Active Directory with enforced MFA, role-based access control, an audit trail and an Opsgenie migration offer are all documented. We found no public information on SCIM provisioning, multi-tenant or service-provider administration, or exporting audit logs to a SIEM, and the Terraform provider is mentioned on the integrations page without documentation of what it manages. 1 8 9 11 12 22
The Engineering Manager
Stack coverage is real: 200+ connectors with native bi-directional ServiceNow sync (a certified app) and ConnectWise, a documented REST API whose sections cover schedules, escalation policies, incidents, workflows and users, webhooks, Terraform and code-as-configuration mentioned, SSO via SAML/OIDC/Active Directory, enforced MFA, role-based access, an audit trail, and a migration offer for Opsgenie users. We found no public information on SCIM provisioning or service-provider and multi-tenant separation, which I would want as an admin before rolling this across three countries. 8 9 11 12 22
The Skeptic
200+ connectors across monitoring, ITSM and chat categories, a certified ServiceNow app with bi-directional sync and automatic alert resolution, native ConnectWise, a documented REST API covering schedules, escalation policies, groups, users, workflows and maintenance windows, Terraform support stated on the integrations page, SSO via SAML, OIDC and Active Directory with MFA enforced, role-based access, an audit trail, and a migration offer for Opsgenie users. We found no public information on SCIM provisioning, multi-tenant or service-provider separation, or export of audit logs to a SIEM. 1 8 9 11 12 22
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
Azure hosting with multi-region redundancy and automated failover, a two-hour recovery time and recovery point objective, SOC 2 Type II examined by an independent audit firm with the report on request, AES-256 at rest and TLS in transit, 24/7 threat monitoring, 72-hour breach notification, and a public status page with a 90-day history and incident archive. The captured pages state both a 99.99% uptime SLA and a 99.9% figure for the architecture; we found no public information on SLA credits, redundant notification carriers, or a DORA or NIS2 mapping. 11 12 13 15
The IT Operations Manager
The pager runs outside my plant network on Microsoft Azure with multi-region redundancy, multi-location backups and automated failover, behind a public status page with incident history and component-level health, and a trust centre offering the SOC 2 Type II report on request, a disaster-recovery summary with two-hour recovery objectives, cyber insurance and a defined data-deletion SLA. The captured pages give different figures for the uptime commitment — 99.99 percent and a 99.9 percent architecture figure — and we found no public information on service-level credits, redundant SMS and voice carriers, or DORA and NIS2 documentation. 11 12 13
The MSP NOC Lead
Hosting on Microsoft Azure with multi-region redundancy, multi-location backups, automated failover and a two-hour recovery time and recovery point objective with tested failover is documented, alongside a public status page with component status, 90-day uptime and past incidents, SOC 2 Type II with the report on request, AES-256 at rest, TLS in transit with key rotation, 24/7 threat monitoring, penetration testing each release cycle and a 72-hour breach notification commitment. The captured pages give different figures for the uptime SLA — 99.99% and a 99.9% architecture figure — and we found no public information on SLA credits, an ISO 27001 certificate held by AlertOps itself rather than inherited from Azure, redundant notification carriers, or DORA and NIS2 documentation. 2 11 12 13
The ICT Risk Officer
Security is substantially evidenced: SOC 2 Type II with the report available on request, a public status page with 90-day history and monitored components, Azure multi-region redundancy with automated failover, a documented 2-hour RTO and RPO, AES-256 and TLS with key rotation, 72-hour breach notification and data deletion within a stated SLA. The captured pages give different figures for stated uptime — 99.99 percent on the security page and 99.9 percent as the architecture figure. We found no public information on SLA credits, redundant notification carriers, or a DORA or NIS2 addendum or mapping, and for a BaFin-supervised buyer that regulatory gap is what keeps this off the top tier. 11 12 13 15
The Engineering Manager
There is a public status page with a 90-day window, incident history and monitored components; Azure multi-region redundancy with automated failover, a 2-hour recovery time and recovery point objective, SOC 2 Type II with the report available on request, AES-256 at rest and TLS in transit, deletion within a defined SLA, 72-hour breach notification and a trust centre holding six documents on request. The captured pages give different figures for the uptime SLA — a stated 99.99% and a 99.9% architecture figure — and we found no public information on SLA credits, redundant notification carriers, or DORA and NIS2 documentation. 11 12 13 15
The Skeptic
A public status page shows all systems operational with 90-day uptime history and past incidents; the platform runs on Microsoft Azure with multi-region redundancy, multi-location backups and automated failover, encryption is AES-256 at rest and TLS in transit with key rotation, SOC 2 Type II is stated with the report available on request, and a trust centre publishes a security whitepaper, a BCDR summary with 2-hour RTO and RPO, and a DPA template. The captured pages give different figures for the SLA — 99.99% in one place and 99.9% in another — and we found no public information on SLA credits, named redundant notification carriers, or documentation for DORA and NIS2. 11 12 13 15
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
The contracting entity is AlertOps, Inc. under Illinois law, the service is SaaS-only with US data residency on Microsoft Azure, and the terms state the platform is based in Illinois and makes no claims of suitability outside the United States. A data processing addendum and a GDPR-aligned privacy policy exist, but we found no public information on an EU hosting option or on a subprocessor list beyond the Azure hosting. 15 12 16 11
The IT Operations Manager
The contracting entity is AlertOps, Inc. of Bloomingdale, Illinois under Illinois law, production runs on Microsoft Azure with US data residency the only region choice the pages describe, and the privacy policy states that data of users outside the US may be processed in the US where laws may be less stringent. A data processing addendum and GDPR-aligned handling with transfer safeguards are offered on request, which keeps this above the floor, but we found no public information on an EU hosting region, a self-hosted edition, or the subprocessors in the chain. 11 12 15 16
The MSP NOC Lead
The contracting entity is AlertOps, Inc. under Illinois law at a Bloomingdale, Illinois address, the service runs SaaS-only on Microsoft Azure with US data residency as the only region choice, and the terms state the service is US-based and make no claims of accessibility outside the United States, with personal information of users outside the US possibly processed in the US. A privacy policy with GDPR processing commitments for EEA, UK and Swiss users, a data processing addendum template on request, and statements that AI models are not trained on customer data and that model providers are covered by the addendum do exist. We found no public information on an EU hosting option, an EU contracting entity or representative, or a subprocessor list with locations — a real obstacle for my customers' alert histories and phone numbers in Germany. 11 12 15 16
The ICT Risk Officer
AlertOps, Inc. contracts under Illinois law from a Bloomingdale, Illinois address, production runs on Microsoft Azure, and the only region choice described on the captured pages is US data residency, with the terms stating the service makes no claims of appropriateness outside the United States. A data processing addendum template is available on request and the privacy policy commits to GDPR handling for EEA residents with generic transfer safeguards, but we found no public subprocessor list — the status page runs on Atlassian Statuspage and the AI model providers behind OpsIQ and Ada are unnamed beyond a statement that any provider touching customer data is covered by the DPA. For an entry in my ICT third-party register under DORA this chain cannot be assessed from public pages, and no EU hosting option is described. 11 12 13 15 16
The Engineering Manager
AlertOps, Inc. contracts under Illinois law and the service runs on Microsoft Azure with US data residency as the documented region choice; we found no public information on an EU hosting region or a self-hosted edition. A privacy policy with GDPR-aligned handling and transfer safeguards exists and a DPA template is available on request, but we found no public information naming the subprocessors — the SMS and voice carriers, push services and AI model providers behind my responders' phone numbers — beyond the statement that any model provider touching customer data is included in the DPA. 15 11 12 16
The Skeptic
A privacy policy and a data processing addendum template exist — the latter on request — but the contracting entity is AlertOps, Inc. under Illinois law with the service US-based on Microsoft Azure, and US data residency is the only region option described. The privacy policy states personal information may be processed in the United States where laws may be less stringent than in your country, and no subprocessor list was published on the captured pages. 11 12 15 16
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
We found no public price per user or per plan on the captured pages, and the terms place the subscription fee and any text or phone overage fees on the Proposal or Order Form. A free trial exists and the terms document USD invoicing, tax-exclusive fees, monthly auto-renewal with 30 days' notice and no mid-term cancellation — but an annual cost is not computable from public pages alone. 10 15 3
The IT Operations Manager
We found no public information on prices at all — no per-user or per-plan figure on any captured page, only a free trial and a book-a-demo call — and the terms place the subscription fee, the text and phone communication limits and the overage fee "as specified on the Proposal or Order Form", so nothing is computable for my budget without a sales negotiation. Monthly auto-renewal with 30 days' notice, no mid-term cancellation, taxes exclusive of fees and a 1.5 percent monthly late charge are the only commercial terms stated. 1 10 15
The MSP NOC Lead
We found no public price per user or per plan on the pages captured, the pricing page included; the terms place fees and the text/phone overage fees in the Proposal or Order Form, so the path to cost runs through a trial and sales proposal. What is public is commercial mechanics: fees in U.S. dollars exclusive of all taxes, monthly invoicing on request payable within 30 days, automatic renewal with 30 days' notice, no mid-term cancellation or refunds, a service charge of 1.5% per month on late payments, and suspension once an account is 30 days overdue. We found no public information on plan tiers, included SMS and voice volumes, or add-on and stakeholder pricing. 1 3 10 15
The ICT Risk Officer
The captured pricing page yields no plan prices, and the terms route all fees to a Proposal or Order Form: a subscription fee plus an overage fee for exceeding specified text and phone communication limits as set out there, invoiced in US dollars within thirty days, taxes exclusive, with monthly auto-renewal, thirty days' notice, no mid-term cancellation and no refunds. A free trial is offered, but a buyer cannot compute an annual cost from public pages. 3 10 15
The Engineering Manager
We found no public price per user or per plan on the captured pages, including the pricing page; the terms place the subscription fee and the text and phone overage limits in a Proposal or Order Form, with U.S. dollar invoicing on 30-day terms, monthly auto-renewal, 30 days' notice to terminate, no mid-term cancellation and no refunds, and fees exclusive of taxes. A free trial is offered, but we found no public information on stakeholder or read-only viewer seats — the exact thing I need so managers who only follow along are not charged per seat. 15 3 10
The Skeptic
The captured pricing page yielded no plan prices, per-user rates or notification allowances; the terms instead place the communication limits and the overage fee for exceeding them "as specified on the Proposal or Order Form", with fees in US dollars, exclusive of all taxes, monthly auto-renewal that cannot be cancelled mid-term with no refunds, and a service charge of 1.5% per month on late payments. A free trial is offered, but on what was captured a buyer cannot compute an annual cost from public pages alone. 3 10 15
European sovereignty — proven facts
3 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined | — | uncited Report an error |
|---|---|---|---|
| Hosting location |
Not determined
unverified
Why unverified?Not confirmed on the vendor’s own pages as captured. |
— | uncited Report an error |
| Hosting options |
Cloud service only
unverified
Why unverified?No self-hosted, on-premises or EU region option is mentioned anywhere; the only region choice offered is US data residency, not an EU one. |
0/1 pts | 15 Report an error |
| Open source | Proprietary | 0/1 pts | 15 Report an error |
| Data processing agreement |
On request
unverified
Why unverified?The trust center shares documents only after a request is reviewed, with reports given to 'customers and prospects in active evaluation', so the DPA cannot be concluded online. |
0/1 pts | 12 Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about AlertOps
Is AlertOps European?
No. whats-best.ai classifies AlertOps as Rest of world.
Where does AlertOps store data?
Not stated on the vendor’s pages as of 6 Nov 2026.
Does AlertOps have a free plan?
Not stated on the vendor’s pages as of 6 Nov 2026.
What are the best alternatives to AlertOps?
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: AlertOps alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 6 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Data processing agreement. The trust center shares documents only after a request is reviewed, with reports given to 'customers and prospects in active evaluation', so the DPA cannot be concluded online.
- Weak sourcing — Hosting location. Not confirmed on the vendor’s own pages as captured.
- Weak sourcing — Hosting options. No self-hosted, on-premises or EU region option is mentioned anywhere; the only region choice offered is US data residency, not an EU one.
- 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.
- 21 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
- 18 pricing 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
- 2 integrations 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
- 2 support 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
- 1 compliance fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 legal fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown. Know more? Tell us
- 6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. Know more? Tell us
- The panel’s written verdict is withheld: our own re-read found claims in it that the evidence does not carry, and a second synthesis did not fix them. The scores and the material below are unaffected. Know more? Tell us
Sources (24)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage alertops.com Checked 6 Nov 2026 Details →
- 2 Features page alertops.com Checked 6 Nov 2026 Details →
- 3 Features page (on-call scheduling) alertops.com Checked 6 Nov 2026 Details →
- 4 Features page (escalations) alertops.com Checked 6 Nov 2026 Details →
- 5 Features page (live call routing) alertops.com Checked 6 Nov 2026 Details →
- 6 Features page (status pages) alertops.com Checked 6 Nov 2026 Details →
- 7 Features page (AI) alertops.com Checked 6 Nov 2026 Details →
- 8 Integrations page alertops.com Checked 6 Nov 2026 Details →
- 9 API documentation api.alertops.com Checked 6 Nov 2026 Details →
- 10 Pricing page alertops.com Checked 6 Nov 2026 Details →
- 11 Security / trust page alertops.com Checked 6 Nov 2026 Details →
- 12 Trust centre alertops.com Checked 6 Nov 2026 Details →
- 13 Public status page status.alertops.com Checked 6 Nov 2026 Details →
- 14 About page alertops.com Checked 6 Nov 2026 Details →
- 15 Terms of service alertops.com Checked 6 Nov 2026 Details →
- 16 Privacy policy alertops.com Checked 6 Nov 2026 Details →
- 17 On-call schedules, rotations & escalation — found from sitemap help.alertops.com Checked 6 Nov 2026 Details →
- 18 On-call schedules, rotations & escalation — found from sitemap help.alertops.com Checked 6 Nov 2026 Details →
- 19 Alert delivery, routing & noise reduction — found from sitemap help.alertops.com Checked 6 Nov 2026 Details →
- 20 Alert delivery, routing & noise reduction — found from sitemap help.alertops.com Checked 6 Nov 2026 Details →
- 21 Incident response, status pages & post-incident review — found from sitemap help.alertops.com Checked 6 Nov 2026 Details →
- 22 Incident response, status pages & post-incident review — found from sitemap alertops.com Checked 6 Nov 2026 Details →
- 23 Integrations, API & administration — found from sitemap help.alertops.com Checked 6 Nov 2026 Details →
- 24 Integrations, API & administration — found from sitemap alertops.com Checked 6 Nov 2026 Details →