OnPage
Rest of world Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 1 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by OnPage Corporation · www.onpage.com
Compare with SIGNL4 → 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.
OnPage at a glance
- Vendor
- OnPage Corporation
- Headquarters
- Incorporated in the United States source, captured 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 OnPage 2/5, the mean of 6 judges. OnPage Corporation, of Waltham, Massachusetts, sells on-call alerting and incident alert management for IT and healthcare teams. 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.
The panel's verdict
OnPage Corporation, of Waltham, Massachusetts, sells on-call alerting and incident alert management for IT and healthcare teams. It is strongest on alerting and routing and pricing transparency, where scores cluster at 6-7: delivery over push, SMS, voice and email with SENT, DELIVERED and READ receipts is documented, and all three plans are priced publicly — $13.99 per user per month paid yearly, $16.99 paid quarterly on the base plan, Enterprise Silver $22.99, Enterprise Gold $28.99 — with a 7-day, no-credit-card trial. It is weakest on sovereignty, scored 1-2, and on reliability and compliance, scored 4: contracting runs under Massachusetts law, transfers of personal data outside the EU are acknowledged, and the captured pages give different positions on service levels, listing Standard and Enhanced SLA tiers on the pricing page while the terms state there are no service level guarantees whatsoever. Incident response scores 4-5. The judges split: one judge scored zero on every criterion, citing pages that do not evidence a European data chain, SCIM provisioning or payroll exports, while the other scores cluster at 6-7 on alerting, scheduling and pricing.
Speaks for it
- Critical alerts are documented to bypass the silent switch and persist for up to eight hours until acknowledged, with SENT, DELIVERED and READ receipts on time-stamped logs
- All three plans carry public per-user prices — $13.99 per user per month paid yearly or $16.99 paid quarterly, Enterprise Silver $22.99, Enterprise Gold $28.99 — with a 7-day trial and no credit card required
- The native scheduler documents rotations, multiple schedules per group, automatic time-zone adjustment across 24 time zones, fail-safe paging of the entire group on an empty slot, and a timestamped change log
- A claimed 200+ integrations include ServiceNow, ConnectWise and Autotask, bi-directional Slack and Microsoft Teams sync, and documented REST, SOAP and paging APIs, with free migration support for Opsgenie customers
- Stated certifications include SOC 2 and ISO 27001 for the facility, yearly penetration tests, SSL encryption in transit and at rest, and six-year message retention
Held against it
- The captured pages give different positions on service levels: Standard and Enhanced SLA tiers appear on the pricing page while the terms of use state there are no service level guarantees whatsoever
- Sovereignty is the lowest-scored criterion at 1-2, with the contract under Massachusetts law and binding arbitration in Waltham and no public information on hosting location, a subprocessor list or a data processing agreement
- Incident response scored 4-5, with no public information on incident roles or a commander, runbooks, or a public status page with subscribers
- We found no public information on SCIM provisioning, two-factor authentication or a Terraform provider, leaving the administration side far less documented than the integration side
- Live call routing is priced only by contacting sales, and the additional-costs table names SMS and additional minutes without stated figures, so a full annual total is not computable from public pages
Best for
- You need persistent, evidenced critical-alert delivery over push, SMS, voice and email, with receipts you can show a customer or regulator when a response time is disputed
- You are an IT operations team or MSP migrating from Opsgenie and want named ITSM integrations plus free migration support
- You want published per-user pricing and a 7-day trial with no credit card required before committing to a paging platform
- You need time-stamped audit trails and six-year retention for response-time reporting and regulatory evidence
Avoid if
- You must put a European data chain in front of a works council, a third-party register or data-residency clauses in your own customer contracts
- You require documented service-level commitments: the terms of use state there are no service level guarantees whatsoever
- You need incident command with roles, runbooks and a public status page rather than post-incident reports, status updates and mass notification
- You must budget SMS, additional-minute and live call routing costs before signing; live call routing is contact-sales only and the additional-costs table lists categories without figures
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 | 2 of 5 |
| Integrations, API & administration | 3 of 5 |
| Platform reliability, security & compliance | 2 of 5 |
| European sovereignty | 0.5 of 5 |
| Pricing transparency | 3 of 5 |
On-call schedules, rotations & escalation
panel disagrees
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 native scheduler is credible: rotations and multiple schedules per group, exceptions that revert automatically, escalation groups with configurable intervals, factors and orders, automatic time-zone handling across 175 countries, on-call reminders, a schedule change log, and fail-safe paging of the entire group when a slot is left empty. We found no public information on calendar export, schedules managed as code or by API, round-robin escalation, or on-call hours exported per person for pay and working-time rules, which I need for German working-time compliance. 3 4 9 13 14 15
The IT Operations Manager
The scheduler covers what my five-admin weekly standby needs: recurring rotations, multiple schedules per group, escalation with a customizable wait time before the next person is paged, on-call reminders, and a change log showing who altered the schedule and when; a fail-safe even pages the entire group if a slot is left empty. Time-zone handling across 175 countries and a mobile app showing my own and the team's shifts are documented. We found no public information on calendar export, handing a shift over from the app, or exporting on-call hours for pay and working-time rules, and integrating an existing external scheduler means users do not see the schedule in the app. 1 3 4 6 9 13 14
The MSP NOC Lead
The scheduler covers recurring rotations, multiple schedules per group, per-member parameters, automatic time-zone adjustment across 175 countries and 24 time zones, shift reminders, schedule exceptions that revert automatically, and a change log showing who altered what and when — close to what I need for a night-shift rota plus one per key account, and the fail-safe behaviour that notifies the entire group on an empty slot is a genuine safety net. We found no public information on calendar export, shift swaps from the mobile app, follow-the-sun hand-off management, or exporting on-call hours for pay and working-time rules, which keeps it off the higher levels. 3 13 14 9 6
The ICT Risk Officer
Rotations and recurring shifts, escalation intervals, factors and orders, fail-safe scheduling that notifies the entire team when a slot is left empty, and a schedule change log showing who changed what and when are all documented — that change log is exactly the kind of record I need for working-time and audit questions. Time-zone auto-adjust across 24 time zones, shift reminders and on-call analytics are listed. I found no public information on calendar export, swaps handled from the app, round-robin escalation, or schedules managed as code by API. 3 13 4 9
The Engineering Manager
The core of a follow-the-sun rota is there: rotations spanning 175 countries and 24 time zones with shifts built on local business hours, automatic time-zone adjustment, multiple schedules per group, fail-safe scheduling that pages the whole team when a slot is left empty, shift reminders, and a change log showing who altered the rota with timestamps. What I could not find documented is a shift swap handled from the phone, on-call hours exported to payroll each month, coverage gaps flagged before they happen, or any warning when the same person is paged night after night — the mobile app shows my team's rota, but handing a shift over from it is not described. 13 3 1 14 6
The Skeptic
Rotations and multiple schedules per group, escalation intervals and orders, automatic time-zone adjustment across 24 zones, on-call reminders, a schedule change log and fail-safe handling of empty slots are all documented. We found no public information on calendar export, round-robin or follow-the-sun patterns, schedules managed as code, or on-call hours exported per person for pay and working-time rules. The vendor itself notes a limit: teams can integrate an existing scheduling solution, but users then get no schedule visibility in the app. 13 3 9 6
Alert delivery, routing & noise reduction
panel disagrees
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
The paging core is genuinely strong: push, SMS, voice and email, critical alerts that bypass the silent switch and do-not-disturb and persist up to eight hours until acknowledged, SENT, DELIVERED and READ receipts with time-stamped message logs, deduplication and suppression, retries for up to eight hours, and live call routing as a priced add-on. Keyword-triggered routing and delay schedules are described. We found no public information on documented grouping or correlation logic, heartbeat monitoring for silent failures, or the countries where SMS and voice are delivered. 4 5 6 9 11 15 21
The IT Operations Manager
Delivery is the strong suit: push, SMS, phone call and email, critical alerts that bypass the silent switch and persist for up to eight hours until acknowledged, redundant phone, SMS and email channels, SENT/DELIVERED and READ receipts with time-stamped message logs, deduplication and suppression, plus live call routing through the on-call scheduler as an add-on. Routing by schedule, escalation policy and group, keyword-triggered responses and delay-notification schedules that queue messages for later delivery are documented. We found no public information on maintenance windows as such, heartbeat monitoring for silent failures, acknowledgement by phone keypad, or the logic behind the deduplication, so the persistent-until-acknowledged promise is evidenced but the quieter edges are not. 2 4 5 6 9 15 21
The MSP NOC Lead
Alerts go out over push, SMS, phone and email, bypass the silent switch, persist up to eight hours until acknowledged, and carry SENT, DELIVERED and READ receipts with full time-stamped logs — exactly the delivery evidence I need when a customer disputes a response time. Routing by schedule, group, escalation policy and priority, plus deduplication, suppression and delay windows, are described, and live call routing exists as an add-on. We found no public information on alert grouping or correlation logic, heartbeat monitoring for silent failures, or the countries and channels in which SMS and voice are delivered. 5 6 9 21 15 2 3
The ICT Risk Officer
Delivery is documented across push, SMS, voice and email, with alerts that bypass the silent switch and persist up to eight hours until acknowledged, and SENT, DELIVERED and READ receipts with time-stamped message logs — receipts of that kind are what make a delivery timeline usable as evidence for a regulator. Deduplication and suppression are named but their logic is not documented, and I found no public information on heartbeat monitoring or named redundant carriers with automatic failover. Live call routing exists as an add-on with pricing only on request. 9 15 6 21
The Engineering Manager
Delivery is multi-channel and stubborn: push, SMS, phone and email, high-priority alerts that bypass the silent switch on all devices and persist for up to eight hours until acknowledged, with SENT, DELIVERED and READ receipts on time-stamped message logs, plus deduplication and suppression named for noise control and live call routing as an add-on. Routing follows on-call schedules, escalation policies, groups and high versus low priority. I found no public information on maintenance windows, heartbeat monitoring for silent failures, routing on payload fields, or which countries SMS and voice are delivered in. 9 4 5 21 6 15
The Skeptic
Push, SMS, voice and email delivery, critical alerts that bypass the silent switch and persist up to eight hours until acknowledged, SENT, DELIVERED and READ receipts, time-stamped message logs, deduplication, suppression and off-duty muting are all documented, and live call routing exists as a priced add-on. We found no public information on heartbeat monitoring for silent failures, and no carriers or delivery statistics are named, so the channel list is promised rather than independently evidenced. 4 5 6 9 21 15
Incident response, status pages & post-incident review
panel disagrees
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
Post-incident reports and incident templates, response-time analytics, a web conference bridge, time-stamped audit trails and mass notification to vendors, customers and staff are described. This is alerting with reporting wrapped around it rather than a response workflow: we found no public information on declaring an incident from Slack or Teams into a created channel with roles, a public status page with subscribers, runbooks and automated workflows, follow-up actions tracked into Jira or Linear, or AI summaries. 1 9 15 17 18
The IT Operations Manager
The centre of gravity is after the event: post-incident reports, incident templates, time-stamped audit trails, status updates, response-time reporting with trends, a web conference bridge, high/low priority for severity, and mass notification through BlastIT are all documented. We found no public information on public status pages with subscribers, incident roles such as a commander, declaring an incident from Slack, Teams or the app, follow-up actions tracked into ticketing tools, or AI summaries, so this reads as alert follow-through rather than a full response process. 1 2 6 8 9 15 17 18
The MSP NOC Lead
There are incident templates, post-incident reports, real-time status updates, a web conference bridge, ticket creation and updates, and response-time reporting with trends — enough to feed my monthly per-customer response report. We found no public information on public status pages with subscribers, incident roles such as a commander, or declaring an incident from Slack or Teams, and severity is described only as high and low. 9 18 6 17 1 2
The ICT Risk Officer
Post-incident reports, incident templates, a real-time time-stamped audit trail, status updates, a web conference bridge and response-time reporting are listed, with BlastIT mass notification covering stakeholder updates — the time-stamped audit trail is the piece a DORA classification file could lean on. I found no public information on a public status page, incident roles such as a commander, runbooks and automated workflows, or follow-up actions tracked into a ticketing system. No AI summarisation is described anywhere on the captured pages. 9 6 17
The Engineering Manager
There is a genuine incident record — a time-stamped audit trail, high and low priority, post-incident reports with incident templates, response-time analytics, status updates, mass notification to stakeholders and a web conference bridge to discuss resolutions. Beyond that it thins out for my engineers: I found no public information on declaring an incident from Slack or Teams, incident roles or a commander, runbooks and automated workflows, or a public status page with subscribers. 9 18 17 6 1 2
The Skeptic
Post-incident reports, incident templates, time-stamped audit trails, response-time analytics, stakeholder status updates and mass notification are documented. We found no public information on a public status page with subscribers, incident roles or a commander, or a dedicated incident channel created in Slack or Teams; conference bridges are described only in general terms. 9 6 17 15
Integrations, API & administration
panel disagrees
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 integrations are claimed, with bi-directional Slack and Microsoft Teams sync, ServiceNow, ConnectWise and Autotask named, REST, SOAP and paging protocols behind public API documentation, single sign-on through Okta, Microsoft and OneLogin, and free migration support for Opsgenie customers. We found no public information on a Terraform provider or configuration as code, SCIM provisioning, bidirectional ITSM sync, or exportable administrative audit logs; schedules in Terraform is a hard requirement of mine and nothing captured speaks to it. 6 7 9 15 19 20
The IT Operations Manager
The stack side looks workable for my environment: a claimed 200+ integrations across monitoring, ITSM and ChatOps categories, bi-directional Slack and Microsoft Teams sync, ServiceNow, ConnectWise, Autotask, CloudWatch and Jenkins by name, REST and SOAP plus paging protocols (WCTP, SNPP, TAP) with public API documentation, single sign-on with Okta, Microsoft and OneLogin, team data restrictions, remote wipe, and free migration support for Opsgenie customers. We found no public information naming Checkmk or PRTG specifically, though the pages say anything that sends email, webhooks or HTTP requests can connect. We also found no public information on two-factor authentication, granular roles per team, SCIM provisioning, a Terraform provider, or API coverage of schedules and escalations. 6 7 9 19 20
The MSP NOC Lead
For my stack this is the strong part: ServiceNow, ConnectWise and Autotask are named integrations, Slack and Microsoft Teams sync bidirectionally, tickets can be created and updated, a documented REST API sits alongside webhooks and email intake with 200+ systems claimed, and free Opsgenie migration support is offered. Team-level data restrictions and visibility plus single sign-on with Okta, Microsoft and OneLogin cover the administration basics. We found no public information on SCIM provisioning, a Terraform provider or configuration as code, multi-tenant management for service providers, or two-factor authentication. 6 7 9 18 20 19
The ICT Risk Officer
Over two hundred integrations are claimed across ITSM, monitoring and DevOps categories, with Slack and Microsoft Teams bi-directional sync, ServiceNow, ConnectWise and Autotask named, REST and SOAP plus several paging APIs documented, single sign-on via Okta, Microsoft and OneLogin, and free migration support for OpsGenie customers. I found no public information on SCIM provisioning, a Terraform provider, or exportable administrative audit logs; the schedule change log and message audit trails are the nearest equivalent. Team-level data restrictions and visibility settings are listed. 7 6 9 20
The Engineering Manager
The stack fit is broad: a claim of 200+ integrations across ITSM, monitoring, ChatOps, DevOps and observability categories, bi-directional Slack and Microsoft Teams sync, ServiceNow, ConnectWise and Autotask, APIs in six protocols including REST, webhook and email intake, single sign-on via Okta, Microsoft and OneLogin, and free migration support for Opsgenie customers. Administration evidence stops at teams with data restrictions and visibility and a web console; I found no public information on SCIM provisioning, configuration as code, granular per-team roles or exportable admin audit logs. 7 6 9 8
The Skeptic
Two hundred plus integrations across named categories, ServiceNow, ConnectWise and Autotask, bi-directional Slack and Teams sync, a documented REST API plus WCTP, SNPP, TAP and SOAP, single sign-on with Okta, Microsoft and OneLogin, and free migration support for Opsgenie customers are all on the record. We found no public information on two-factor authentication, SCIM provisioning, a Terraform provider or administrative audit logs, so the organisation side of the product is far less documented than the integration side. 7 6 9 20
Platform reliability, security & compliance
panel disagrees
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 checklist lands real items: SOC 2 and ISO 27001 certified facility, HIPAA and PCI compliance, yearly penetration tests, full redundancy with hardware and software failovers, SSL encryption in transit and at rest, and six-year data retention. Against that, the terms of use state there are no service level guarantees whatsoever, and we found no public information on a vendor status page, named hosting regions, or documentation for DORA or NIS2 customers — thin for the system that carries my pages. 2 9 11 21 22
The IT Operations Manager
There is real audit substance: SOC 2 and ISO 27001 certification of the facility, PCI, HIPAA and GDPR claims, yearly penetration tests, full redundancy audited regularly, hardware and software failovers, SSL encryption in transit and at rest, six-year retention with remote wipe, and redundant phone, SMS and email channels when one path fails. The captured pages give different figures for service levels — the pricing page lists standard and enhanced SLA tiers while the terms of use state there are no service level guarantees whatsoever — and we found no public information on an availability figure, hosting regions, a public status page with incident history, or DORA and NIS2 documentation. For a service I rely on precisely when the plant's own network is down, that last part matters. 2 4 9 11 15 21 22
The MSP NOC Lead
A SOC 2 and ISO 27001 certified facility, yearly penetration tests, PCI, encryption in transit and at rest, six-year retention with customisable access, and audited full redundancy with hardware and software failovers are all stated. We found no public information on a public status page, an availability figure, or hosting regions, and the captured pages give different positions on service levels: the pricing page lists a Standard and Enhanced SLA while the terms of use state there are no service level guarantees whatsoever — for an MSP answering to sixty customers on response times, that gap is decisive. 2 21 22 12 9 11
The ICT Risk Officer
The captured pages give different statements on service levels: the pricing page lists Standard and Enhanced SLA tiers while the terms state there are no service level guarantees whatsoever and that transmission is attempted for up to eight hours — for a tool I would have to register as an ICT third-party service, that gap is decisive. ISO 27001, SOC 2 and PCI are claimed as certified facilities, encryption in transit and at rest and six-year retention are stated, and yearly penetration tests are claimed, but without certification scope, a public status page or incident history, named hosting regions, or anything on DORA or NIS2. I found no public information on an availability figure with credits. 2 21 22 11
The Engineering Manager
Security claims are stated plainly — a SOC 2 and ISO 27001-certified facility, PCI, yearly penetration tests, hardware and software failovers with audited full redundancy, and HIPAA with SSL encryption in transit and at rest and six-year retention. For a pager I also need to know it is up, and here the captured pages give different statements on service levels: the terms state there are no service level guarantees whatsoever while the pricing page lists Standard and Enhanced SLA tiers. I found no public information on a public status page, an availability figure, or hosting regions. 2 21 22 11 9
The Skeptic
The vendor states SOC 2 and ISO 27001 as a certified facility, yearly penetration tests, SSL encryption in transit and at rest for messages, and six-year retention. But the terms of use state THERE ARE NO SERVICE LEVEL GUARANTEES WHATSOEVER IN RESPECT OF THE SOFTWARE OR SERVICE while the pricing page lists Standard and Enhanced SLA tiers, so the captured pages give different positions on service levels, and we found no public information on a vendor status page, hosting regions or multi-region failover. 21 2 11 22 9
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 OnPage Corporation of Waltham, Massachusetts under Massachusetts law with binding arbitration in Waltham, user data is processed on unnamed cloud computing servers, and the privacy policy acknowledges transfers of personal information outside the EU under contractual measures. We found no public information on EU hosting, a published data processing agreement, or a list of subprocessors with their locations. 11 12
The IT Operations Manager
The contracting and operating entity is OnPage Corporation of Waltham, Massachusetts, under Massachusetts law with binding arbitration in Waltham, and the privacy policy acknowledges transfers of personal data to countries outside the European Union with adequate contractual measures as the safeguard. Where alerts, message content and contact data are hosted is not stated, no subprocessors are named (billing data is forwarded to an unnamed third-party billing or clearing company), and we found no public information on a data processing agreement, so a European data chain is not evidenced. 10 11 12
The MSP NOC Lead
OnPage Corporation contracts from Waltham, Massachusetts under Massachusetts law with binding arbitration in Waltham, the privacy policy states data may be transferred outside the European Union under adequate contractual measures, and we found no public information on hosting location, an EU contracting entity, a published data processing agreement, or a subprocessor list beyond an unnamed third-party billing or clearing company. A privacy policy with GDPR-compliance claims exists, which lifts this slightly, but nothing in the captured pages evidences a European chain — for a Nuremberg MSP with data-residency clauses in its customer contracts, that is close to disqualifying. 12 11 10
The ICT Risk Officer
OnPage Corporation contracts from Waltham, Massachusetts under Massachusetts law with binding arbitration there, and its privacy policy states that data including personal information may be transferred to countries outside the European Union under adequate contractual measures. I found no public information on hosting location, a subprocessor list, a published data processing agreement, transfer impact assessments, or an EU contracting entity or representative. For my third-party register there is no European chain to assess, and no way to verify where incident timelines and message content are processed. 12 11 10
The Engineering Manager
The contracting entity is OnPage Corporation of Waltham, Massachusetts, under Massachusetts law with arbitration in Waltham, and the privacy policy acknowledges transferring personal information to countries outside the European Union relying on adequate contractual measures. Hosting location and subprocessors are not stated on any page I read. For my works council in Hamburg that is not a chain I can put in front of them, and a GDPR-compliant badge does not substitute for named EU hosting and a published data processing agreement. 12 11 10 2
The Skeptic
The contracting entity is OnPage Corporation of Waltham, Massachusetts, under Massachusetts law with binding arbitration in Waltham, and the privacy policy acknowledges that personal data may be transferred to countries outside the European Union under contractual measures. We found no public information on hosting location, a subprocessor list including the unnamed third-party billing or clearing company, or a data processing agreement. 12 10 2
Pricing transparency
panel disagrees
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
All three plans are public with exact per-user prices — $13.99 per user per month paid yearly or $16.99 paid quarterly on the base plan, $22.99 for Enterprise Silver and $28.99 for Enterprise Gold per user per month paid yearly — plus a dedicated line add-on at $360.00 per year for up to 500 minutes per month and $5 per month per user for voicemail, an additional-costs table naming toll, international line, extra minutes and SMS, and a claim of unlimited global messaging for one monthly fee. Live call routing is contact sales, and we found no public information on VAT treatment, free stakeholder or viewer seats, or minimum seats. 4 9
The IT Operations Manager
The pricing page is unusually open for this market: three plans at "$13.99 PER USER, PER MONTH PAID YEARLY", "$22.99" for Enterprise Silver and "$28.99" for Enterprise Gold, a dedicated line add-on at "$360.00/year for up to 500 minutes per month", voicemail at "$5/month per user", an additional-costs table covering toll, international and SMS lines and additional minutes, card billing annually or quarterly, and one monthly fee claimed to cover unlimited global messaging. Live call routing is priced only by contacting sales, quarterly billing is not offered on the Silver and Gold plans, the terms reserve the right to change fees at any time, and we found no public information on stakeholder or viewer seats or VAT treatment, so a complete annual cost is not computable from public pages alone. 4 9 11
The MSP NOC Lead
All three plans are public per user — $13.99 per user, per month paid yearly or $16.99 paid quarterly, Enterprise Silver at $22.99 and Enterprise Gold at $28.99 per user, per month paid yearly — the dedicated line add-on is $360.00/year for up to 500 minutes per month with voicemail at $5/month per user, and one monthly fee is said to cover unlimited global messaging. Live call routing is contact-sales only, the additional-costs table names SMS and additional-minute categories without captured per-unit prices, and we found no public information on stakeholder seats, minimum terms or VAT treatment, so the true annual cost is not fully computable. 9 4
The ICT Risk Officer
All three plans carry a public per-user monthly price with yearly and quarterly options on the base plan, dedicated-line and voicemail add-ons are priced, and an additional-costs table covers toll, toll-free and international lines, additional minutes, voicemail, SMS and live call routing, though live call routing is contact sales and the remaining figures in that table are not stated on the captured pages. The captured pages give different signals on messaging costs — an unlimited global messaging claim for one monthly fee, and per-SMS and per-minute rows in the additional-costs table. I found no public information on VAT treatment or on stakeholder and viewer seats. 9 4 11
The Engineering Manager
Three plans are priced per user per month in dollars — OnPage at $13.99 and $16.99 paid quarterly, Enterprise Silver at $22.99 and Enterprise Gold at $28.99 paid yearly — with add-ons such as a dedicated line at $360.00/year for up to 500 minutes per month and voicemail at +$5/month per user, and bulk and non-profit pricing available. Live call routing is "contact sales", and the captured pages give different signals on messaging costs, with an SMS price listed among additional costs on one page and unlimited global messaging for one monthly fee on another. I found no public information on free seats for managers who only read along — the pricing model is per user, which matters to me — or on VAT treatment. 9 4
The Skeptic
Three plans are priced publicly per user per month paid yearly — OnPage $13.99, Enterprise Silver $22.99, Enterprise Gold $28.99 — with $16.99 paid quarterly for the base plan only, add-ons at $360.00/year for a dedicated line and $5/month per user for voicemail, named card payments, and a seven-day trial with no credit card required. The vendor states one monthly fee covers unlimited global messaging, but live call routing is please contact sales, the SMS price, additional minutes, toll, toll-free and international lines appear only as additional-cost categories with no figures in what we captured, and we found no public information on stakeholder seats, minimum seats or VAT treatment, so a full annual total is not computable from the public pages. 9 4
European sovereignty — proven facts
1 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 |
Incorporated in US
unverified
Why unverified?Only a company contact address in the USA is given; no register of incorporation or formation document is cited. |
0/2 pts | 12 Report an error |
|---|---|---|---|
| Hosting location | Not determined | — | uncited Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about OnPage
Is OnPage European?
No. whats-best.ai classifies OnPage as Rest of world. Its vendor, OnPage Corporation, is incorporated in the United States, per the vendor’s page captured 6 Nov 2026.
Where does OnPage store data?
Not stated on the vendor’s pages as of 6 Nov 2026.
Does OnPage have a free plan?
Not stated on the vendor’s pages as of 6 Nov 2026.
What are the best alternatives to OnPage?
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: OnPage 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 — Legal entity. Only a company contact address in the USA is given; no register of incorporation or formation document is cited.
- 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.
- 15 legal 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
- 13 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
- 11 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 hosting 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 support 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
Sources (22)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.onpage.com Checked 6 Nov 2026 Details →
- 2 Features page (on-call alerting) www.onpage.com Checked 6 Nov 2026 Details →
- 3 Features page (scheduling) www.onpage.com Checked 6 Nov 2026 Details →
- 4 Features page (escalation) www.onpage.com Checked 6 Nov 2026 Details →
- 5 Features page (alert routing) www.onpage.com Checked 6 Nov 2026 Details →
- 6 Features page (incident alert management) www.onpage.com Checked 6 Nov 2026 Details →
- 7 Integrations page www.onpage.com Checked 6 Nov 2026 Details →
- 8 Documentation docs.onpage.com Checked 6 Nov 2026 Details →
- 9 Pricing page www.onpage.com Checked 6 Nov 2026 Details →
- 10 About page www.onpage.com Checked 6 Nov 2026 Details →
- 11 Terms of service (names the operating company) www.onpage.com Checked 6 Nov 2026 Details →
- 12 Privacy policy www.onpage.com Checked 6 Nov 2026 Details →
- 13 On-call schedules, rotations & escalation — found from sitemap www.onpage.com Checked 6 Nov 2026 Details →
- 14 On-call schedules, rotations & escalation — found from sitemap www.onpage.com Checked 6 Nov 2026 Details →
- 15 Alert delivery, routing & noise reduction — found from sitemap www.onpage.com Checked 6 Nov 2026 Details →
- 16 Alert delivery, routing & noise reduction — found from sitemap www.onpage.com Checked 6 Nov 2026 Details →
- 17 Incident response, status pages & post-incident review — found from sitemap www.onpage.com Checked 6 Nov 2026 Details →
- 18 Incident response, status pages & post-incident review — found from sitemap www.onpage.com Checked 6 Nov 2026 Details →
- 19 Integrations, API & administration — found from sitemap docs.onpage.com Checked 6 Nov 2026 Details →
- 20 Integrations, API & administration — found from sitemap docs.onpage.com Checked 6 Nov 2026 Details →
- 21 Platform reliability, security & compliance — found from sitemap www.onpage.com Checked 6 Nov 2026 Details →
- 22 Platform reliability, security & compliance — found from sitemap www.onpage.com Checked 6 Nov 2026 Details →