Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 4 of 6 dimensions proven

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

by OneUptime, Inc. · oneuptime.com

Report an error on this page Is this your product? →

Link to this page

OneUptime: AI-assisted analysis on whats-best.ai OneUptime: AI-assisted analysis on whats-best.ai (dark)

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.

OneUptime at a glance

Vendor
OneUptime, Inc.
Headquarters
Incorporated in the United States source, captured 17 Nov 2026
Data hosting
Default not stated; pages mention the US and the EU source, captured 17 Nov 2026
Free plan
Yes, per the vendor’s own page source, captured 17 Nov 2026
Panel verdict
The AI panel rates OneUptime 3.5/5, the mean of 6 judges. OneUptime is an open-source platform for monitoring, on-call paging, incident response and status pages, judged strongest on reliability and compliance, where scores cluster at 8, with incident response, integration and administration and sovereignty at 7 to 8. how scores are made
As of
Vendor pages captured 17 Nov 2026; evaluated by the panel 18 Nov 2026. all sources

OneUptime alternatives, European ones first →

Read this page as one judge. Each weighs the same scores by what they care about.

The panel's verdict

OneUptime is an open-source platform for monitoring, on-call paging, incident response and status pages, judged strongest on reliability and compliance, where scores cluster at 8, with incident response, integration and administration and sovereignty at 7 to 8. The bench credits a 99.9% monthly uptime target on paid plans and 99.95% on Enterprise backed by service credits, hosting across AWS, Azure and GCP in customer-pinned regions, and a self-hosted Community Edition under Apache 2.0 that runs air-gapped. Pricing transparency is the weak point, at 4 to 5: paid plans start at $22 per user per month, active monitors at $1 each a month and telemetry at $0.10 per GB ingested, but the captured pages give no per-plan prices, SMS and voice costs by country, annual-discount percentage or VAT treatment. Alerting and routing sits at 6 and on-call scheduling at 6 to 7. The lone 7 on sovereignty reflects works-council concerns about subprocessor locations and the free edition's two daily outbound calls, removed only by an offline Enterprise license token.

Report an error

Speaks for it

  • Published SLA of a 99.9% monthly uptime target on paid plans and 99.95% on Enterprise, backed by service credits of 10%, 25% or 50% of a month's fees
  • Self-hosted Community Edition free under Apache 2.0 at any scale, able to run air-gapped with mail, webhooks and SMS through your own gateways
  • Five thousand plus integrations with a documented REST API, an official Terraform provider, a CLI and an MCP server, and on-call manageable as code
  • Immutable audit logs exportable to a SIEM, SCIM provisioning, custom roles with per-resource scoping and optional per-tenant physical isolation
  • AI incident investigations documented as read-only, secrets redacted and not trained on customer content by default, with your own model possible

Report an error

Held against it

  • Per-plan prices, SMS and voice volumes and per-country costs, the annual-discount percentage and VAT treatment are not published
  • Production use of the Enterprise Edition needs a license priced only through contact sales
  • We found no public information on time-zone handling, follow-the-sun hand-offs, shift reminders or on-call hours exported for pay and working-time rules
  • We found no public information on critical alerts overriding do-not-disturb, delivery receipts, heartbeats or the countries SMS and voice reach
  • We found no public information on MTTA and MTTR analytics, incident commander roles or a documented migration path from a competing pager

Report an error

Best for

  • You want to self-host your pager and incident records, air-gapped, with your own mail server and SMS gateway — the Community Edition is free under Apache 2.0 at any scale
  • You need an audit-ready reliability record — a published SLA with service credits, SOC 2 Type II, ISO 27001 with annual surveillance and quarterly disaster-recovery drills
  • You run infrastructure as code and want on-call, monitors and status pages managed through Terraform, a CLI, a REST API and an MCP server

Report an error

Avoid if

  • You must compute a full year of spend before purchase — only starting prices are public, discounts are stated without a percentage, and Enterprise production use is contact sales
  • You need a self-hosted install that never calls out — the free Community Edition makes two outbound calls a day unless activated with an offline Enterprise license token
  • You need SCIM provisioning and SIEM-exportable audit logs in the free self-hosted edition — the Enterprise Edition adds them under the OneUptime Enterprise License
  • Your procurement requires a European contracting entity — the cloud path contracts through HackerBay, Inc. of Delaware with a published subprocessor list

Report an error

The scores

Panel median The median of the judges’ scores per criterion. Each label opens its reasoning below.

On-call schedules, rotations & escalation

Show 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.

Report an error

The SRE Lead

Schedules with user overrides, escalation policies that page level by level until somebody acknowledges and record each run, repeat cycles with auto-resolve, and severity- or time-based rules are documented, along with unlimited policies per team and service, readiness lists showing who can actually be paged, calendar feeds, and on-call managed as code through the API, CLI and Terraform. We found no public information on rotation types and layers, follow-the-sun hand-offs across time zones, shift reminders, or on-call hours exported for pay and working-time rules. Good bones for eight teams, but the time-zone and reporting depth I need before trusting it with sixty engineers is not described. 6 7 8 9

Report an error

The IT Operations Manager

Our weekly standby with a deputy after ten minutes is what these pages describe: a schedule picks who is on call, a user override covers absence, and a policy pages level by level until somebody acknowledges, with repeat cycles of three times and a thirty-minute auto-resolve shown as an example. Severity- and time-based escalation, unlimited policies per team and service, a readiness list that flags who is unreachable before an incident asks, calendar feeds, and on-call managed as code through the API, CLI and Terraform provider take this well past the basics. We found no public information on time-zone handling, shift reminders, or on-call hours exported for standby pay and working-time rules. 7 8 6 9

Report an error

The MSP NOC Lead

Schedules with user overrides, escalation policies that page level by level until someone acknowledges and record each run, escalation by severity or time elapsed with repeat cycles and auto-resolve, unlimited policies per team and per service, a readiness view flagging unreachable responders before an incident, and on-call managed as code through the Terraform provider and API. We found no public information on follow-the-sun hand-offs, round-robin, shift reminders, or on-call hours exported for pay and German working-time rules — the report I need for sixty customers' rotas, night shift included. 6 7 8 9

Report an error

The ICT Risk Officer

Schedules, user overrides and escalation policies that page level by level until acknowledgement, with repeat cycles and auto-resolve, are documented, and I credit the readiness view that flags unreachable responders before an incident, plus on-call managed as code through Terraform. The pages describe fair-distribution rotation policies, but I found no public information on rotation types, layers, time-zone handling or follow-the-sun hand-offs, nor on-call hours exported for pay and working-time rules. 6 7 8 9

Report an error

The Engineering Manager

Escalation is well documented: policies page level by level until acknowledged with repeat cycles, routing by severity or elapsed time, per-person notification rules, user overrides and unlimited policies per team and service, plus on-call managed as code via the API, CLI and Terraform and a readiness view showing who can actually be paged. But for my follow-the-sun rota across three time zones, we found no public information on time-zone handling or hand-offs, on swaps from a phone, on exporting on-call hours to payroll, or on any warning when the same person is paged three nights running. 7 8 9 6

Report an error

The Skeptic

Escalation runs level by level until someone acknowledges and each run is recorded, with user overrides, severity- and time-based rules, repeat cycles, unlimited policies per team and per service, and a readiness list that flags unreachable responders before an incident pages them; schedules and on-call can also be managed as code through the API, CLI and Terraform. The captured pages do not describe rotation granularity, time-zone or follow-the-sun handling, swaps, shift reminders, or an on-call hours report for pay and working-time rules — the operational half is well documented and the payroll half is not. 1 6 7 8 9

Report an error

Alert delivery, routing & noise reduction

Show 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.

Report an error

The SRE Lead

Paging by phone, SMS, email, push, Slack and Teams is documented, with personal rules choosing which method is tried and after how long, three retry attempts, acknowledgement by email or SMS link or gateway call and reply, transparent logs of who was alerted and when, related alerts and incidents grouped into episodes, and maintenance windows. Bring-your-own telephony and a self-run signed gateway for SMS and calls give unusual control over the delivery chain. We found no public information on critical alerts overriding do-not-disturb, heartbeat monitoring, suppression rules, or the countries and channels where SMS and voice are delivered. 6 7 8 9 10

Report an error

The IT Operations Manager

The channels we need are there — phone calls, SMS, push, email, Slack and Teams — each person choosing which of their methods is tried and after how long, the delivery retried three times, and acknowledgement when the person answers the call or replies through the gateway, from the link in an email or SMS, or in chat. Related alerts are grouped into episodes, every notification is logged so I can debug a policy afterwards, routing follows severity or elapsed time, and scheduled maintenance windows exist for planned work. We found no public information on critical alerts overriding do-not-disturb, delivery receipts, heartbeats for silent failures, or the countries where SMS and voice are delivered. 7 8 6 10

Report an error

The MSP NOC Lead

Paging by phone, SMS, email, push, Slack and Teams, with personal rules setting each person's method order and delays, documented retries on the gateway route, acknowledgement from a link in email or SMS, transparent logs of who was alerted and when, and Episodes that fold related alerts into one. We found no public information on delivery receipts, critical alerts that override do-not-disturb, heartbeats for silent failures, suppression rules, or the countries where SMS and voice are delivered. 6 7 8 9

Report an error

The ICT Risk Officer

Paging by phone, SMS, email, push and chat, personal rules for which method is tried and after how long, retries, acknowledgement by email or SMS link or call reply, and a transparent log of who was alerted and when — that log is what I would put in front of the regulator. Related incidents group into episodes and severity- and time-based escalation rules are described, but I found no public information on heartbeat monitoring, suppression rules, delivery receipts, critical-alert override of do-not-disturb, or live call routing; telephony runs over the customer's own Twilio or gateway, which for me is control, not a gap. 7 8 9

Report an error

The Engineering Manager

Paging reaches people by phone call, SMS, email, push and Slack or Teams, with personal rules on which method is tried and after how long, retries, acknowledgement from a link in an email or SMS or through a call, and transparent logs of who was alerted and when; related incidents and alerts can be grouped as one episode and routing keys off severity and time. We found no public information on critical alerts overriding do-not-disturb, live call routing for a hotline, or the countries where SMS and voice are delivered — the documented route to full control is bringing your own telephony provider such as Twilio or running your own gateway. 7 8 9 6

Report an error

The Skeptic

Delivery by phone, SMS, email, push, Slack and Microsoft Teams is documented, with per-person rules on which method is tried and after how long, three-attempt retries, acknowledgement from an email link, an SMS reply or an answered call, per-alert logs of who was paged when, maintenance windows, and related alerts rolled up as episodes. I found no public information on critical-alert override of do-not-disturb, delivery receipts, heartbeats, suppression rules, or the countries and carriers SMS and voice actually reach — cloud telephony carriers are unnamed, though alerts can run through your own gateway or Twilio account. 6 7 8 9

Report an error

Incident response, status pages & post-incident review

Show 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.

Report an error

The SRE Lead

Incidents are declared by a monitor or a person, paged from a Slack slash command, worked on one timeline with custom severities and states like investigating and monitoring, with a video call startable in Meet, Teams or Zoom and public or private status pages auto-updated with unlimited subscribers — the one-place flow I want. Workflows and runbooks, Jira and ServiceNow connections, action-item tracking, published postmortems, topology maps, and an AI that writes a plain-English root cause with citations, read-only, secrets redacted, and no training on customer content by default, are all documented. We found no public information on incident commander roles, MTTA and MTTR reporting, or follow-up items synced into a tracker, which keeps the process short of enterprise-grade. 1 3 6 8 9 10

Report an error

The IT Operations Manager

Incidents run on one timeline with custom severities and states like investigating, a video call can be started from Google Meet, Teams or Zoom, and the team can acknowledge, escalate and resolve from Slack or Teams. Runbooks, visual no-code workflows connected to Jira and ServiceNow, public and private status pages with email, SMS, RSS, webhook and Slack subscribers, postmortems with action-item tracking, and an AI that posts a root-cause analysis with citations — read-only, secrets redacted, optionally pointed at a model inside our own cluster — cover most of what a real response needs. We found no public information on incident commander roles, a channel created automatically, or MTTA and MTTR reports. 1 9 10 3 4 6

Report an error

The MSP NOC Lead

Incidents declared by a monitor or a person with custom severities and states, runbooks and no-code workflows automating the response and updating public and private status pages with unlimited subscribers on email, SMS, webhooks, RSS and Slack, and postmortems carrying root-cause analysis, public and private notes and action-item tracking. The AI writes a root cause with citations, read-only, secrets redacted, no training on customer incident content by default, and able to run on a local model. We found no public information on incident roles such as a commander, or on MTTA and MTTR analytics — the per-customer response-time reporting I owe every month is not shown. 1 4 6 9 10

Report an error

The ICT Risk Officer

Incidents declared by a person or a monitor with custom severities and states, one timeline per incident, Slack paging with in-chat acknowledgement, runbooks and workflows connected to Jira and ServiceNow, public and private status pages with subscribers, and postmortems with root cause analysis and tracked action items. The AI summaries come with their data handling described — read-only, secrets redacted, own model possible, no training on customer content by default — which is exactly what I need to clear an AI feature with our DPO. I found no public information on MTTA or MTTR analytics, incident commander roles, or regulatory reporting templates. 1 6 8 9 10

Report an error

The Engineering Manager

Incidents are declared by a monitor or a person, carry custom severities like P1 and P2 and custom states, run on one timeline, and are acknowledged, escalated and resolved from Slack or Teams including a slash command to page a team; status pages are public or private with unlimited subscribers on email, SMS, webhooks, RSS and Slack, postmortems carry root-cause analysis and action-item tracking, and the AI investigator is documented as read-only with secrets redacted and no training on customer data by default. We found no public information on an incident commander role, postmortem templates, or MTTA and MTTR reporting. 9 10 8 4

Report an error

The Skeptic

Custom severities and incident states, episodes that group related alerts, no-code workflows and runbooks connected to Jira and ServiceNow, video bridges through Google Meet, Teams or Zoom, public and private status pages with unlimited subscribers on email, SMS, webhooks, RSS and Slack, and postmortems with action-item tracking are all on the record. The AI investigator is documented the way I wish everyone did it — read-only, secrets redacted, no training on customer content by default, your own LLM and keys, nothing merged without review — though the vendor's own model provider is not named. We found no public information on incident commander roles, MTTA and MTTR analytics, or postmortem templates. 1 3 4 6 9 10

Report an error

Integrations, API & administration

Show 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.

Report an error

The SRE Lead

Five thousand plus integrations including Slack, Teams, Jira and PagerDuty, OpenTelemetry and Prometheus-compatible intake, a REST API, CLI, MCP server and an official Terraform provider managing monitors, status pages and on-call as code, SAML and OIDC SSO with SCIM provisioning, custom roles with per-resource scoping, and immutable audit logs exportable to a SIEM are all documented. White-label status pages, optional per-tenant physical isolation and a managed private-cloud edition serve service-provider setups. We found no public information on bidirectional ITSM sync or a documented migration path from a competing pager. 4 5 6 10

Report an error

The IT Operations Manager

Five thousand plus integrations including Slack, Teams, Jira and PagerDuty, a documented REST API with an official Terraform provider plus CLI and MCP server, SAML and OIDC single sign-on, SCIM provisioning, custom roles with per-resource scoping, and immutable audit logs exportable to our SIEM give the administration depth my small team needs, with on-call, monitors and status pages managed as code. What matters most to me is the intake side, and Checkmk and PRTG are not named on the captured pages, though the REST API and OpenTelemetry paths are documented for anything that can push. We found no public information on bidirectional ITSM sync or migration help from other paging tools — only cloud-to-self-hosted moves on the same schema. 10 4 9 11 5

Report an error

The MSP NOC Lead

Five thousand plus integrations with Slack, Teams, Jira and ServiceNow named, a documented REST API with an official Terraform provider, CLI and MCP server, SAML and OIDC single sign-on included even in the free Community Edition, SCIM, immutable audit logs exportable to a SIEM, custom roles with per-resource scoping, and tenant isolation up to a dedicated database per tenant — the separation my sixty customers demand. We found no public information on bidirectional ticketing sync of the kind that opens and closes Autotask tickets automatically, on Zabbix as an inbound source, or on migration help from other paging tools. 4 5 6 9 11

Report an error

The ICT Risk Officer

Five thousand named integrations, a documented REST API with an official Terraform provider, a CLI and an MCP server, SAML and OpenID Connect single sign-on with SCIM on enterprise plans, custom roles with per-resource scoping, and immutable audit logs exportable to a SIEM — that last item is a hard requirement for our ICT third-party register. Physical isolation per tenant with dedicated databases and keys supports service-provider setups. I found no public information on a migration path from the major competitors, and bidirectional ITSM sync is not stated. 4 5 6 10 11

Report an error

The Engineering Manager

The fit is broad: thousands of integrations including Slack, Teams, Jira and ServiceNow, OpenTelemetry ingest, an MCP server and CLI, a REST API with an official Terraform provider covering on-call as code, and identity handled by SAML and OIDC single sign-on, SCIM provisioning, custom roles with per-resource scoping and immutable audit logs exportable to a SIEM. We found no public information on bidirectional ticketing sync or a migration path from PagerDuty or Opsgenie, and SCIM and audit logs sit in the Enterprise Edition rather than the core product. 10 11 4 6 1

Report an error

The Skeptic

Five thousand plus named integrations including Slack, Microsoft Teams, Jira, PagerDuty and ServiceNow, a documented REST API, webhooks that can reach private networks, an official Terraform provider, a CLI and an MCP server, SAML and OIDC single sign-on, SCIM provisioning, custom roles with per-resource scoping, and immutable audit logs exportable to a SIEM. What keeps it off the top: no stated parity between the API and every setting, no documented migration path from named competitors (PagerDuty appears as an integration, not a migration), and no sub-account management for service providers beyond status-page white-label. 1 4 5 6 10 11 12

Report an error

Platform reliability, security & compliance

Show 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.

Report an error

The SRE Lead

A 99.9% monthly uptime target on paid plans and 99.95% on Enterprise with 10%, 25% or 50% service credits, real-time and historical availability on their own status page, multi-cloud hosting across AWS, Azure and GCP in customer-pinned regions, and disaster-recovery targets of RPO within one minute and notification delivery within five, backed by quarterly full drills, are published. ISO 27001 with annual surveillance, ISO 27017 and 27018, SOC 2 Type II with a shareable SOC 3, PCI DSS attested, CSA STAR Level 2, HIPAA with a BAA, and annual third-party penetration tests are stated with meaningful scope. We found no public information on redundant notification carriers or a DORA or NIS2 mapping. 1 4 9 12 13

Report an error

The IT Operations Manager

The pager story holds up for the day our plant network is the problem: hosting spread across multiple clouds and continents with the claim that a major incident at one cloud provider does not take the service down, RPO within a minute, notification delivery restored within five, and full disaster-recovery drills quarterly with backup-restore validated weekly. A public status page with real-time and historical uptime, a 99.9% monthly uptime target on paid plans and 99.95% on Enterprise backed by service credits of 10, 25 or 50 percent, SOC 2 Type II, a SOC 3 shareable without an NDA, ISO 27001 with annual surveillance audits, ISO 27017 and 27018, CSA STAR Level 2 with the CAIQ published, annual independent penetration tests, TLS 1.2 or higher and AES-256 make an audit file I can hand over. We found no public information on redundant SMS and voice carriers with automatic failover, the vendor's own published post-incident reviews, or DORA and NIS2 documentation. 4 13 12 7 10

Report an error

The MSP NOC Lead

A published SLA with service credits of 10, 25 or 50 percent of a month's fees and a 30-day claim window, uptime targets of 99.9% on paid plans and 99.95% on Enterprise, the vendor's own status page with real-time and historical uptime, hosting across AWS, Azure and GCP in customer-pinned regions, DR targets of RPO within one minute and RTO within fifteen minutes for API and UI, quarterly DR drills, SOC 2 Type II attestation, ISO 27001 with annual surveillance, SOC 3 shareable without an NDA, and independent third-party penetration testing at least annually. We found no public information on a DORA or NIS2 addendum, or on named redundant SMS and voice carriers — though SMS and calls can run through your own gateway. 1 4 9 12 13

Report an error

The ICT Risk Officer

A published SLA with service credits of 10, 25 or 50 percent of monthly fees, a public status page with history, multi-cloud hosting on named providers in customer-pinned regions, disaster recovery targets of RPO one minute and notification RTO five minutes with quarterly drills, and certifications stated with scope — SOC 2 Type II, SOC 3 shareable without an NDA, ISO 27001 with annual surveillance. For a supervised buyer two things are missing: I found no public information on a DORA or NIS2 addendum or mapping, and none on named redundant notification carriers or public post-incident reviews of the vendor's own outages. 4 12 13

Report an error

The Engineering Manager

There is a published monthly uptime target of 99.9% on paid self-serve plans and 99.95% on Enterprise backed by service credits of 10%, 25% or 50%, real-time and historical uptime on their own status page, hosting across AWS, Azure and GCP in customer-pinned regions, disaster-recovery targets of RPO within one minute and notification delivery within five minutes, quarterly DR drills, and ISO 27001, 27017, 27018, SOC 2 Type II and SOC 3 with the SOC 3 shareable without an NDA. We found no public information on redundant SMS and voice carriers for cloud paging, or on a DORA or NIS2 mapping for regulated customers. 4 12 13 9

Report an error

The Skeptic

The pager's own survival case is written down: a 99.9% monthly uptime target on paid plans and 99.95% on Enterprise backed by published service credits of 10%, 25% or 50% of that month's fees, hosting on AWS, Azure and GCP in customer-pinned regions with multi-cloud distribution, an RPO of a minute or less and a five-minute notification RTO, quarterly full disaster-recovery drills, annual independent penetration tests, SOC 2 Type II with a SOC 3 shareable without an NDA, ISO 27001/27017/27018 with audit cadence, PCI DSS, CSA STAR Level 2, and a public status page at status.oneuptime.com. I found no public information naming redundant SMS and voice carriers, published failover test results, the vendor's own post-incident reviews, or DORA and NIS2 mappings. 1 4 7 12 13

Report an error

European sovereignty panel opinion

Show 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.

Report an error

The SRE Lead

The contracting entity is HackerBay, Inc. of Delaware, USA, with cloud hosting in US or EU datacenters and enterprise region choice on AWS, Azure or GCP, a published subprocessor list, a DPA with Standard Contractual Clauses, and ISO 27001 and SOC 2 stated; we found no public information on the subprocessors' locations. The self-hosted path is the strong one: the Community Edition runs free under Apache 2.0 and air-gapped with data never leaving the cluster, mail through your own server, SMS and calls through your own gateway, and AI on a local model, so every record can stay on European servers of our choosing. The community install still makes two disclosed daily calls out (a version check and a check-in), and only the offline enterprise license token removes them, which keeps it a step short of sovereign end to end. 2 3 5 10 13

Report an error

The IT Operations Manager

The contracting entity is HackerBay, Inc. of Delaware in the United States; cloud customers can pin US or EU datacenters and Enterprise customers choose their region on AWS, Azure, GCP or on-premises, with a published DPA carrying Standard Contractual Clauses and a published subprocessor list with thirty days' notice of changes. Decisive for us is the documented self-hosted path: the Community Edition runs free under Apache 2.0 on our own European servers, schedules, escalations and overrides stay inside our network, email goes through our own SMTP, SMS and calls through a gateway we run, and the captured pages state data never leaves the cluster we deployed. The free edition does make two outbound calls a day with the install's address and version; an Enterprise install activated with an offline license token never calls the vendor, and we found no public information on subprocessor locations or a transfer impact assessment. 2 13 3 10 5 8 6

Report an error

The MSP NOC Lead

The cloud is contracted through HackerBay, Inc. of Delaware, with EU datacenters and enterprise region choice on AWS, Azure or GCP, a DPA with Standard Contractual Clauses, and a subprocessor list published with 30 days' notice of changes; we found no public information on where those subprocessors are located or on an EU representative. The self-hosted route is the one I would run in Nuremberg: the Enterprise Edition on my own cluster with an offline licence token that never calls the vendor, my own mail server and SMS gateway, a local AI model, and documented data export and immediate hard deletion. 3 4 5 13

Report an error

The ICT Risk Officer

The cloud path contracts through HackerBay, Inc. of Delaware: EU regions on AWS, Azure or GCP are offered and a subprocessor list is published with thirty days' notice of changes, but no EU contracting entity or representative is documented, and I could not see where the subprocessors are located. What decides it for me is the self-hosted path — a documented edition that keeps schedules, incident timelines, paging, mail and even the AI model inside my own cluster, with an offline enterprise license token that never calls home; the free community edition, by contrast, makes two daily outbound calls to GitHub and oneuptime.com. For a Frankfurt payments firm that in-cluster chain is the sovereign answer. 2 4 5 10

Report an error

The Engineering Manager

The contracting entity is HackerBay, Inc. of Delaware, but EU data residency is documented — US and EU datacentres on the cloud edition with Enterprise choosing the region on AWS, Azure, GCP or an agreed data centre — alongside a DPA with Standard Contractual Clauses, a published subprocessor list and ISO 27001 and SOC 2. The Apache-2.0 Community Edition can run in our own cluster with our own mail server, webhooks and SMS gateway so alerts, timelines and phone numbers stay on our servers. For my works council the open points are the subprocessors' locations, and the daily outbound calls a self-hosted install makes unless it is activated with an offline Enterprise license token. 13 10 4 5 3 8

Report an error

The Skeptic

The contracting entity is HackerBay, Inc. of Delaware, and the cloud path leans on SCCs, the UK transfer addendum and a published subprocessor list with EU datacenters rather than a European entity. What lifts it is the documented self-hosted path: the Community Edition is free under Apache 2.0, runs air-gapped, keeps schedules, escalations, overrides and every record inside the customer's own cluster, and with an offline license token never calls the vendor, with data export and immediate hard deletion documented. The free edition does phone home twice a day with the install's address and version, which buyers wanting a silent install should weigh, but records still stay on their servers. 2 3 5 6 8 10

Report an error

Pricing transparency

Show 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.

Report an error

The SRE Lead

Paid plans start at $22 per user per month, active monitors are $1 each a month, telemetry is $0.10 per GB ingested, the Free plan needs no credit card to sign up, self-hosting the Community Edition is free at any scale, and unlimited status pages and subscribers cost nothing extra, with no product-imposed caps on monitors, team members, alerts or API calls. We found no public information on per-plan prices and inclusions, SMS and voice notification volumes or per-country costs, the Enterprise Edition licence price beyond contact sales, the annual discount percentage, or VAT treatment and minimum seats. I cannot compute a real annual paging cost from the public pages I read. 1 4 5 6 10

Report an error

The IT Operations Manager

Public numbers exist and they are concrete: paid plans start at $22 per user per month, telemetry is $0.10 per GB ingested, active monitors are $1 each a month on every plan, a free tier needs no credit card to sign up, status-page subscribers are unlimited at zero extra cost, and the Community Edition is free to self-host at any scale. What I cannot compute is the cost of paging itself — SMS and voice volumes and per-country overage prices are not published — and the captured pages give only the starting price, not the price of each plan, with the Enterprise tier at contact sales and VAT treatment unstated; annual billing is discounted at a published per-plan annual price but the discount percentage is not given. 1 4 10 8 5

Report an error

The MSP NOC Lead

Paid plans start at $22 per user per month, telemetry at $0.10 per GB ingested, active monitors at $1 each a month on every plan, unlimited status-page subscribers at no extra cost, the Community Edition free to self-host at any scale, and an Enterprise option at $0.10 per user per hour on your cloud bill. Annual billing is discounted against monthly with no published percentage, production use of the Enterprise Edition needs a licence priced only through contact sales, and we found no public information on SMS and voice notification volumes or their cost, per-plan prices, minimum seats, or VAT treatment. 1 4 5 6 10

Report an error

The ICT Risk Officer

Paid plans start at $22 per user per month with telemetry at $0.10 per GB ingested and active monitors at $1 each a month on every plan, a free plan needs no credit card, and unlimited status pages and subscribers come at no extra cost — enough to sketch a budget but not compute a year of it. The enterprise license is contact sales, annual and volume discounts are stated without their percentages, and I found no public information on VAT treatment, net payment terms, or per-country SMS and voice prices. 1 4 6 10

Report an error

The Engineering Manager

A starting price is public — paid plans at $22 per user per month, telemetry at $0.10 per GB ingested, active monitors at $1 each a month on every plan, a free tier with no credit card, the self-hosted Community Edition free at any scale, and Enterprise on cloud marketplaces at $0.10 per user per hour. What I cannot compute from the captured pages: per-plan prices beyond the start, SMS and voice volumes and their cost per country, whether read-only managers pay anything, the annual-versus-monthly discount, or VAT treatment — and production use of the Enterprise Edition is contact sales. 1 4 5 6

Report an error

The Skeptic

The floor is computable: paid plans start at $22 per user per month, active monitors are $1 each a month on every plan, telemetry is $0.10 per GB ingested, the Community Edition is free to self-host at any scale, and status-page subscribers are unlimited at zero extra cost. But the captured pages give no individual prices for the named paid tiers, no price for the Enterprise Edition license beyond contact sales, no SMS and voice volumes or per-country overage costs, no published annual-discount percentage, and no VAT treatment — a buyer can price monitors and telemetry but not a full year for a real team. 1 4 5 6 8 10

Report an error

European sovereignty — proven facts

4 of 6 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Hosting location Not determined — uncited Report an error
Hosting options Self-hostable 1/1 pts 5 Report an error
Open source Open source (permissive) unverified
Why unverified?

The Enterprise Edition modules in the ee/ directory are under the separate OneUptime Enterprise License, not the Apache 2.0 licence.

1/1 pts 6 Report an error
Data processing agreement Published, self-serve unverified
Why unverified?

The DPA text itself is not in the excerpts, so it is not shown whether it can be concluded fully online without contacting the vendor.

1/1 pts 5 Report an error
Transfer impact assessment Not determined — uncited Report an error

Questions about OneUptime

Is OneUptime European?

Not determined: the vendor’s pages as captured do not say where OneUptime is based. Its vendor, OneUptime, Inc., is incorporated in the United States, per the vendor’s page captured 17 Nov 2026.

Where does OneUptime store data?

The default storage location for customer data is not stated on the vendor’s pages as of 17 Nov 2026. The vendor’s pages mention the US and the EU as hosting locations, per the vendor’s page captured 17 Nov 2026.

Does OneUptime have a free plan?

Yes. OneUptime has a free plan, per the vendor’s page captured 17 Nov 2026.

What are the best alternatives to OneUptime?

As of 18 Nov 2026, the panel rates ilert (4/5), All Quiet (3.5/5) and FireHydrant (3/5) highest among the other 16 On-Call & Incident Management products evaluated. 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: OneUptime alternatives.

Where this could be wrong

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.

Sources (13)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

  1. 1 Vendor page oneuptime.com Checked 17 Nov 2026 Details →
  2. 2 Legal notice — found from the homepage oneuptime.com Checked 17 Nov 2026 Details →
  3. 3 Privacy policy — found from the homepage oneuptime.com Checked 17 Nov 2026 Details →
  4. 4 Security / trust page — found from the homepage oneuptime.com Checked 17 Nov 2026 Details →
  5. 5 Self-hosting / on-premises installation docs — found from the homepage oneuptime.com Checked 17 Nov 2026 Details →
  6. 6 Code repository (open-source licence) — found from the homepage github.com Checked 17 Nov 2026 Details →
  7. 7 On-call schedules, rotations & escalation — found from sitemap oneuptime.com Checked 17 Nov 2026 Details →
  8. 8 On-call schedules, rotations & escalation — found from sitemap oneuptime.com Checked 17 Nov 2026 Details →
  9. 9 Incident response, status pages & post-incident review — found from sitemap oneuptime.com Checked 17 Nov 2026 Details →
  10. 10 Incident response, status pages & post-incident review — found from sitemap oneuptime.com Checked 17 Nov 2026 Details →
  11. 11 Integrations, API & administration — found from sitemap oneuptime.com Checked 17 Nov 2026 Details →
  12. 12 Platform reliability, security & compliance — found from sitemap oneuptime.com Checked 17 Nov 2026 Details →
  13. 13 Platform reliability, security & compliance — found from sitemap oneuptime.com Checked 17 Nov 2026 Details →