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 IT Operations Manager

Weighted verdict

Runs IT operations for a packaging manufacturer with 900 staff and three plants running around the clock, with Checkmk and PRTG watching servers, networks and the production line. Five administrators share a weekly standby. Wants a Checkmk alert to become a phone call that the right person acknowledges by keypad, the deputy called after ten minutes, no pages during planned maintenance, and an alerting service that still works when the plant's own network is the thing that is down.

Same scores as the panel view — this lens weights them the way this judge cares.

Scored by The IT Operations Manager

Panel median The IT Operations Manager This judge’s scores over the panel median. Each label opens its reasoning below.
Scores per criterion, in stars out of 5
Criterion Panel median The IT Operations Manager
On-call schedules, rotations & escalation 3 of 5 3.5 of 5
Alert delivery, routing & noise reduction 3 of 5 3 of 5
Incident response, status pages & post-incident review 3.5 of 5 3.5 of 5
Integrations, API & administration 4 of 5 3.5 of 5
Platform reliability, security & compliance 4 of 5 4 of 5
European sovereignty 4 of 5 4 of 5
Pricing transparency 2 of 5 2 of 5

On-call schedules, rotations & escalation

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

Alert delivery, routing & noise reduction

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

Incident response, status pages & post-incident review

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

Integrations, API & administration

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

Platform reliability, security & compliance

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

European sovereignty

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

Pricing transparency

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

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 →