Uptime Monitoring & Status Pages
openstatus
EU-Made Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by openstatus · www.openstatus.dev
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.
openstatus at a glance
- Vendor
- openstatus
- Headquarters
- Not stated on the vendor’s pages as of 1 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 1 Nov 2026
- Free plan
- Yes, per the vendor’s own page source, captured 1 Nov 2026
- Panel verdict
- The AI panel rates openstatus 3.5/5, the mean of 6 judges. OpenStatus is an open-source uptime monitoring and status page tool — AGPL-3.0, managed SaaS or self-hosted — with weighted totals from 6.4 to 7.3. how scores are made
- As of
- Vendor pages captured 1 Nov 2026; evaluated by the panel 2 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
OpenStatus is an open-source uptime monitoring and status page tool — AGPL-3.0, managed SaaS or self-hosted — with weighted totals from 6.4 to 7.3. It is strongest on automation and teams, spanning 7 to 9, the widest spread: higher scores credit the official Terraform provider, a CLI that exports the workspace to Terraform files, a typed API with a published OpenAPI spec for every dashboard action, and an append-only audit log; lower scores cite no public information on SCIM provisioning, granular roles or client sub-accounts. Status pages scores 7 to 8 on custom domains, component groups fed from monitors, subscriber feeds and password or IP-restricted access. Alerting and on-call is weakest at 6: channels span email, SMS, Slack, PagerDuty and Opsgenie, but judges found no public information on on-call schedules, rotations, phone-call alerts, escalation policies or SMS costs. Reports and reliability and sovereignty score 6 to 7, flagging an SLA only inside the tailored Enterprise plan, application hosting and the primary database running globally, and payments through Stripe in the US. Pricing transparency scores 7 to 8 with tiers and add-ons public.
Speaks for it
- An incident opens only when at least half of a monitor's regions report a failure, and maintenance windows never count against uptime
- The official Terraform provider manages monitors, status pages, component groups, notifications and private locations, with a CLI that exports the workspace into Terraform files
- Every mutation lands in an append-only audit log with actor and source, exportable as CSV or JSON
- Status pages support custom domains, component groups auto-filled from monitors, email, RSS, Atom, JSON and Slack Connect subscribers, and password, magic-link or IP-restricted access
- All tiers and add-ons are priced publicly — Starter $30/mo, Pro $100/mo, Scale $500/mo, extra monitors at $15/mo./10, SSO/SAML at $250/mo — with annual billing giving two months free
Held against it
- We found no public information on on-call schedules, rotations, phone-call alerts or escalation policies with timeouts
- We found no public information on browser or transaction checks, or on SSL certificate and domain expiry checks
- We found no public information on SMS delivery costs or VAT treatment
- We found no public information on scheduled email reports, response-time percentiles, published probe IP addresses or an SLA with credits outside the tailored Enterprise plan
- Application hosting and the primary database run globally on Vercel, Fly, Koyeb, Railway and Turso, payment runs through Stripe in the US, and we found no public information on a data processing agreement or security certifications
Best for
- You manage infrastructure as code and want monitors, status pages and notifications under Terraform with a CLI that exports the whole workspace
- You run customer-facing status pages per client or product and need component groups, subscriber feeds and password, magic-link or IP-restricted access
- You want an open-source AGPL-3.0 edition you can self-host with Docker or a Helm chart to keep monitoring records on your own servers
- You already carry the pager in PagerDuty, Opsgenie or Grafana OnCall and want multi-region checks that alert those channels
Avoid if
- You need the monitoring tool itself to run on-call rotations, schedules, phone-call alerts and escalation policies rather than forwarding to an external paging service
- Your checks must cover multi-step user flows like a login or checkout, since the documented monitor types are HTTP, TCP, DNS and ping
- Your procurement requires a published data processing agreement, security certifications or a named contracting legal entity before signature
- You need an SLA with credits on a standard plan, since the dedicated SLA is listed only in the tailored Enterprise plan
The scores
| Criterion | Panel median |
|---|---|
| Checks, locations & failure confirmation | 3.5 of 5 |
| Alerting, escalation & on-call | 3 of 5 |
| Status pages & incident communication | 4 of 5 |
| API, monitoring as code & team administration | 3.5 of 5 |
| Uptime reports, data & the vendor's own reliability | 3 of 5 |
| European sovereignty | 3 of 5 |
| Pricing transparency | 3.5 of 5 |
Checks, locations & failure confirmation
Show reasoningHide reasoning
How this is scored
What can be monitored and how reliably a failure is detected: HTTP(S) with status code and keyword checks, TCP and port, ping, DNS records, SSL certificate and domain expiry, cron jobs and heartbeats, multi-step API checks with assertions, browser or transaction checks of a login or checkout, the shortest check interval, the number and regions of probe locations, the re-check from a second location before an alert, timeouts and response time thresholds, and private locations inside the customer's own network.
0 — Runs no checks of its own; a status page or alerting tool that only receives signals from other monitors.
3 — HTTP checks of a URL at a fixed interval with an up or down result; keyword, SSL, cron and the probe locations are basic or not described.
5 — HTTP(S), keyword, TCP or port, ping and SSL expiry checks, cron or heartbeat monitoring, an interval of one minute or less, several named probe locations, a failure confirmed from a second location before alerting, and response times recorded per check.
8 — Multi-step API checks with assertions on headers and body, browser or transaction checks of a user flow, DNS and domain expiry checks, sub-minute intervals, probe locations listed by city with the confirmation logic documented, private locations or agents for internal services, and maintenance windows that pause checks.
10 — Coverage and accuracy a reliability team runs on: every check type above with code-based checks (for example Playwright or scripted tests) in version control, location-specific thresholds, false-positive handling and probe health published, and the detection method documented so a result can be reproduced.
The Agency Developer
HTTP(S) checks with status-code, header and body assertions, TCP, DNS and ping monitors, 30-second intervals on the paid tiers and 28 named regions — that covers the bulk of what my sixty client sites need, and an incident only opens when at least half of a monitor's regions confirm the failure, with DNS, connect, TLS, first-byte and transfer recorded per check. Private probes run as a Docker container behind the firewall over an outbound-only connection, and maintenance windows are excluded from uptime. We found no public information on SSL certificate expiry or domain expiry checks — the exact gap that once cost me an angry phone call — nor on browser or transaction checks of a login or checkout. 2 13 7 18 14
The SaaS Platform Engineer
HTTP checks with assertions on status code, headers and body plus degraded and timeout limits, TCP, DNS and ping monitors, 30-second intervals on paid plans and 28 regions — and the confirmation logic is documented: an incident opens only when at least half of a monitor's regions report failure, which is exactly the noise control I want before a page goes out. Private locations run as a documented 8.5 MB Docker probe with outbound-only connectivity, and maintenance windows stop counting against uptime. We found no public information on browser or transaction checks of a user flow or on domain expiry checks, which keeps this below the top band. 2 7 13 14 18 20
The Customer Support Lead
The failure-confirmation logic is documented precisely — an incident opens only when at least half a monitor's regions report an error — alongside HTTP, TCP, DNS and ping monitor types with status-code, header and body assertions, degraded and timeout thresholds, 30-second checks on paid plans, 28 named regions, a DNS/connect/TLS/first-byte/transfer breakdown per check, and self-run Docker probes behind our firewall for internal services. We found no public information on browser or transaction checks of a user flow, SSL certificate expiry checks or cron heartbeat monitoring. 2 13 14 18 20
The E-Commerce Operations Manager
The documented checks include HTTP and TCP with assertions on status code, headers and body, DNS and ping monitor types in the Terraform provider, all HTTP methods with custom headers, 30-second intervals on the paid tiers, 28 regions in total (6 per monitor on Starter), private probes behind our own firewall, and maintenance windows that stop counting against uptime. Confirmation discipline is documented: a failed check is retried from the same location, and an incident opens only when at least half the monitor's regions report a failure — the multi-region quorum I want before an alert wakes the duty phone. We found no public information on browser or transaction checks of a checkout or payment flow, on cron or heartbeat checks, or on SSL certificate and domain expiry monitoring. 2 7 13 14 18 20
The Information Security Officer
HTTP(S) checks with status-code, header and body assertions, TCP, DNS and ICMP checks run from 28 named regions at intervals down to 30 seconds, and a failure is confirmed only when at least half of a monitor's regions report it — a documented quorum, with maintenance windows excluded from uptime, latency recorded per phase and private locations deployable as a self-operated probe alongside public regions. The confirmation logic, probe providers and region identifiers are published, which is what I need to reproduce a result. We found no public information on SSL certificate or domain expiry checks, cron job or heartbeat monitors, or browser-based transaction checks. 2 13 14 18 19
The Skeptic
Failure confirmation is written down, not implied: an incident opens only when at least half of a monitor's regions report the error, and a single region's failure is explicitly called noise. HTTP with assertions on status code, header and body, TCP, DNS and ICMP checks, 30-second intervals on paid plans, 28 regions and customer-run private location probes are all evidenced. I found no public information on browser or multi-step transaction checks, cron job or heartbeat monitoring, SSL certificate or domain expiry checks, or published probe health. 2 7 13 14 18 19
Alerting, escalation & on-call
Show reasoningHide reasoning
How this is scored
How the right person learns about a failure: alert channels (email, SMS, phone call, push app, Slack, Microsoft Teams, Telegram, webhooks), alerts to PagerDuty, Opsgenie or similar tools, escalation policies when an alert is not acknowledged, on-call schedules and rotations, acknowledge and resolve from the app, alert grouping and noise reduction, recovery notifications, maintenance windows that mute alerts, and whether SMS and calls are included or charged per message.
0 — No alerting at all; results can only be viewed in the dashboard.
3 — Email alerts and one or two chat integrations; escalation, phone calls and schedules are basic or not described.
5 — Email, SMS, a mobile push app, Slack, Microsoft Teams and webhooks, alerts forwarded to PagerDuty or Opsgenie, per-monitor alert contacts, recovery notifications, a delay or threshold before alerting, and maintenance windows that mute alerts.
8 — Phone call alerts, escalation policies with timeouts, on-call schedules and rotations with overrides, acknowledge and resolve from the app or chat, alert grouping, incident timelines with who did what, and the price of SMS and calls stated per country or included in the plan.
10 — On-call that replaces a separate incident tool: follow-the-sun schedules, escalation across teams, alert routing by service and severity, post-incident reviews generated from the timeline, and delivery of every alert channel monitored and reported.
The Agency Developer
Email, SMS, WhatsApp, Slack, Microsoft Teams, Discord, PagerDuty, Opsgenie, Grafana OnCall and webhooks are all listed channels, alerts only fire once half the regions confirm, and recovery notifications are sent. Incidents can be acknowledged and resolved from the dashboard and auto-resolve when checks recover, and one Slack slash command opens a dedicated channel with the incident card pinned. We found no public information on phone-call alerts, escalation policies with timeouts, or on-call schedules and rotations, and no per-message SMS pricing. 2 7 13 20 1
The SaaS Platform Engineer
The channel list is broad — email, SMS, Slack, Discord, Microsoft Teams, Telegram, PagerDuty, Opsgenie, Grafana OnCall and webhooks — with recovery notifications and incidents that can be acknowledged and resolved, auto-resolving when checks recover. But for someone on a rotation, we found no public information on phone call alerts, escalation policies with timeouts, or on-call schedules and rotations, and the pricing pages do not state what SMS delivery costs. The incident side — declare from Slack with severity, commander, timeline and an agent-drafted postmortem — is real, but it is not a pager replacement. 1 2 7 13 20
The Customer Support Lead
The channel list is broad — PagerDuty, Opsgenie, SMS, WhatsApp, Microsoft Teams, Telegram, Grafana OnCall among them — and an incident can be declared from a Slack slash command with a severity, commander, internal timeline and postmortem, then acknowledged and auto-resolved on recovery, with recovery notifications documented. For whoever carries the pager, we found no public information on phone-call alerts, escalation policies with timeouts, on-call schedules and rotations, or the price of an SMS. 1 2 13 20
The E-Commerce Operations Manager
Alerts can go out by email, SMS, Slack, Discord, Microsoft Teams, Telegram, WhatsApp and webhook, with forwarding to PagerDuty, Opsgenie and Grafana OnCall on the paid tiers, the failing requests attached, and recovery notifications when checks come back — the SMS to the duty phone is documented. Incidents can be acknowledged and resolved (and auto-resolve on recovery), carry an internal timeline with a commander, and noise is handled by the half-regions rule. We found no public information on phone-call alerts, escalation policies with timeouts, on-call schedules or rotations, or the price of an SMS per country, so the rota itself would still live in PagerDuty. 2 7 13 20
The Information Security Officer
Alerts route to email, SMS, Slack, Discord, Microsoft Teams, Telegram, WhatsApp, Google Chat, PagerDuty, Opsgenie, Grafana OnCall, ntfy and webhooks, with per-monitor channel routing, a regional quorum before alerting and recovery notifications; incidents carry severity, commander, an internal timeline, acknowledge and auto-resolve, and can be declared from Slack with a postmortem drafted from the timeline afterwards. For a NIS2-regulated on-call rota, the gaps matter: we found no public information on phone-call alerts, escalation policies with timeouts, on-call schedules and rotations, or the per-message cost of SMS alerts. 1 2 7 20
The Skeptic
Channels run wide — PagerDuty, Opsgenie, Grafana OnCall, Slack, Microsoft Teams, Telegram, WhatsApp, ntfy, email, SMS and webhooks, with the failing requests attached — and the region-quorum rule does real noise reduction. Incidents can be acknowledged, auto-resolved on recovery, and declared from Slack with a severity, commander and internal timeline. I found no public information on escalation policies, on-call schedules or rotations, phone call alerts, or what SMS delivery costs. 1 2 7 13 20
Status pages & incident communication
Show reasoningHide reasoning
How this is scored
How customers and colleagues are told: public status pages on a custom domain with SSL, components and component groups fed automatically by monitors or set by hand, incident updates and scheduled maintenance announcements, subscribers notified by email, SMS, RSS or webhook, uptime history shown per component, private or password-protected pages for internal teams or single customers, branding and custom CSS, several languages, page templates, and how the status page itself stays online when the main product is down.
0 — No status page of any kind.
3 — A public status page listing monitors with their current state; custom domain, incident updates and subscribers are basic or not described.
5 — Public status pages on a custom domain, components linked to monitors, incident updates and scheduled maintenance, email subscribers, uptime history per component, the vendor's branding removable, and a password-protected or private page option.
8 — Component groups, SMS, RSS and webhook subscribers with per-component subscriptions, private pages with single sign-on or IP restriction, several languages, incident templates, embeddable status widgets, audience-specific pages for single customers, and the status page hosting kept separate from the main service and documented.
10 — Incident communication end to end: incidents drafted from monitor events and approved by a person, updates published to the page, subscribers, chat and social channels at once, a full incident archive with post-mortems, status page uptime published, and accessibility of the page stated.
The Agency Developer
Custom domains with published DNS records, components grouped and auto-filled from monitors, incident updates running from investigating to resolved, scheduled maintenance that never counts against uptime, and subscribers via email, RSS, Atom, JSON and Slack Connect with optional per-component scoping — precisely the per-client page model I run. Password, magic-link and CIDR-allowlist protection, white label, themes with CSS overrides, seven languages and incident templates from a communication guide are documented. We found no public information on SMS subscribers, an embeddable status widget, or how the hosted page stays online when the main service is down. 3 16 17 20 21
The SaaS Platform Engineer
Custom domain, components and component groups fed by monitors, per-component impact updates from investigating to resolved, scheduled maintenance with subscriber notice, subscribers by email, RSS, Atom, JSON and Slack Connect with optional per-component scoping, seven languages, incident and maintenance templates, and password, magic-link or CIDR-restriction access control. Monitors can update the page automatically and incidents open on their own when half the regions fail, so nobody logs in at 3 a.m. to flip a banner. We found no public information on embeddable status widgets, and the pages show the status page DNS pointing at Vercel, which also hosts the application; we found no public information on hosting kept separate from the main service. 3 16 17 20 21
The Customer Support Lead
A page on our own domain with component groups customers recognise, monitors feeding the uptime automatically, incident updates through investigating to resolved with per-component impact, email subscribers confirmed by opt-in plus RSS, Atom, JSON and webhook feeds with optional per-component scope, a password-, email-domain- or IP-restricted page for our largest accounts, seven languages and scenario-based incident and maintenance templates are all documented, and once approved an update goes to the page, subscribers and Slack at once with every update keeping its timestamp. We found no public information on SMS subscribers, an embeddable status widget, or the status page's own hosting being kept separate from the main service. 1 3 15 16 17 20 21
The E-Commerce Operations Manager
Custom domain with DNS instructions, components and component groups that fill from the monitors, incident updates moving through investigating, identified, monitoring and resolved with per-component impact, scheduled maintenance that never counts against uptime, and a published incident-communication guide with templates. Subscribers can be reached by email, RSS 2.0, Atom 1.0, JSON feeds, Slack Connect and webhook with optional per-component choice; pages can be public, password-protected, magic-link or IP-restricted; white label drops the branding line; and seven languages including German are supported — that covers telling my DACH customers in the March-to-June crunch. We found no public information on SMS subscribers, embeddable widgets, or how the page itself stays online if the main service is down. 3 15 16 17 20
The Information Security Officer
Public pages on a custom domain with components and component groups fed by monitors, incident updates moving through investigating, identified, monitoring and resolved, scheduled maintenance with advance subscriber notice, and email, RSS, Atom, JSON, webhook and Slack Connect subscribers with per-component scoping are all documented. Private access by password, email-domain magic link or IP restriction, seven languages with a locale switcher, incident and maintenance templates, white-label branding and a reference receiver cross-posting to social channels round out the picture. We found no public information on embeddable status widgets, SMS delivery to status-page subscribers, or the status page hosting being kept separate from the main service. 3 16 17 20 21
The Skeptic
A serious incident-communication surface: component groups fed automatically from monitors, custom domains, seven languages, incident and maintenance templates, RSS, Atom and JSON feeds, per-component subscriptions, and password, magic-link or IP-restriction privacy. As a skeptic I still found no public information on SMS subscribers, embeddable widgets, or any statement that status page hosting is kept separate from the main service when the product itself goes down. 3 15 16 17 21
API, monitoring as code & team administration
Show reasoningHide reasoning
How this is scored
How the tool fits a team and a deployment pipeline: a documented REST API to create and read monitors, status pages and incidents, a Terraform provider, CLI or monitoring-as-code workflow, checks run from CI/CD before a deploy, bulk import of monitors, integrations with ticketing and chat tools, team members with roles, single sign-on (SAML) and SCIM, audit logs, several teams or client accounts in one organisation, white-label or client reporting for agencies, and two-factor authentication.
0 — No API, no team accounts; one login per account and monitors are set up only by hand.
3 — A web dashboard with a few team members; the API, roles and multi-client set-up are basic or not described.
5 — A documented REST API covering monitors and status pages, webhooks, team members with roles, two-factor authentication, bulk import or a CSV upload of monitors, and several projects, teams or client groups in one account.
8 — A Terraform provider or monitoring-as-code CLI with checks kept in version control, checks triggered from CI/CD, single sign-on (SAML), SCIM provisioning, audit logs, sub-accounts for clients with their own logins, and white-label client reports.
10 — Administration that scales across many teams and clients: every setting reachable by API and code with parity stated, granular roles per resource, SSO enforced with SCIM, audit logs exportable to a SIEM, and agency or reseller accounts with separate billing.
The Agency Developer
The official Terraform provider manages monitors, status pages, component groups, notifications and private locations with in-place updates, the CLI exports the whole workspace to Terraform files, and the API is typed with a published OpenAPI spec and a Node SDK, with the explicit claim that every dashboard action is reachable from it. Every mutation lands in an append-only audit log exportable to CSV and JSON, API keys are scoped, and there is an importer from Atlassian Statuspage, Better Stack and Instatus with a preview before anything is written. Team seats are unlimited on the paid plans and SSO is a $250/mo add-on; we found no public information on SCIM provisioning, checks triggered from CI/CD, or client sub-accounts with their own logins. 6 18 19 12 7 3
The SaaS Platform Engineer
This is the part I care about most and it is strong: an official Terraform provider covering monitors, status pages, component groups, notifications and private locations, with a CLI that exports an existing workspace into Terraform files and imports them into state, plus a typed API with a published OpenAPI spec that the documentation says covers every action the dashboard performs. Every mutation lands in an append-only audit log with actor and source, exportable as CSV or JSON, and API keys are scoped. We found no public information on SCIM provisioning, granular per-resource roles, or checks triggered from CI/CD. 1 3 6 12 18 19
The Customer Support Lead
The official Terraform provider manages monitors, status pages, component groups, notifications and private locations with in-place updates, a CLI exports the entire workspace into ready-to-use Terraform files, and the API states every dashboard action is reachable programmatically with an append-only audit log exportable as CSV or JSON and scoped keys. Import from Atlassian Statuspage, Better Stack or Instatus with a preview would ease switching. We found no public information on granular roles, SCIM provisioning, client sub-accounts with their own logins, or checks triggered from CI/CD. 3 6 7 12 18 19
The E-Commerce Operations Manager
The API is typed JSON-over-HTTP with a published OpenAPI spec and a Node SDK, and the pages state that every action the dashboard performs is reachable from the API, under one key shared with the CLI, Terraform and the MCP server. The official Terraform provider manages monitors, status pages, component groups, notifications and private locations, the CLI can export the whole workspace into.tf files, monitors can be imported from Atlassian Statuspage, Better Stack or Instatus, SSO/SAML exists as a $250/mo add-on, and an append-only audit log records every mutation with export to CSV or JSON. We found no public information on SCIM provisioning, granular per-resource roles, separate client logins per sub-account, or checks run from CI/CD before a deploy. 1 3 6 7 12 18 19
The Information Security Officer
An official Terraform provider manages monitors, status pages, component groups, notifications and private locations with import support and in-place updates, a CLI exports the whole workspace to Terraform files, and every dashboard action is reachable through a documented ConnectRPC API with an OpenAPI spec, a typed SDK and scoped API keys. Every mutation is recorded in an append-only audit log with actor and source, exportable as CSV or JSON — the artifact I would put in front of an auditor — and SSO is available, priced as a monthly add-on and bundled with the enterprise plan. We found no public information on SCIM provisioning, granular per-resource roles, two-factor authentication, or client sub-accounts with their own logins. 6 7 12 18 19
The Skeptic
Monitoring as code with parity claimed outright: every dashboard action reachable through a typed API with a published OpenAPI spec, an official Terraform provider managing monitors, status pages, component groups and private locations, a CLI that exports the workspace to Terraform, an MCP server, and an append-only audit log exporting as CSV or JSON. I found no public information on SCIM provisioning, two-factor authentication or granular per-resource roles; seats are unlimited with no per-seat fee. 3 6 7 12 18 19
Uptime reports, data & the vendor's own reliability
Show reasoningHide reasoning
How this is scored
What the record is worth and whether the monitor itself can be trusted: uptime and SLA reports per monitor and period, response time charts and percentiles, scheduled reports by email, client-facing reports, how long check results and incident history are kept, export of results by CSV or API, the vendor's own public status page and incident history, its SLA, the probe IP addresses and user agent published for allow-listing, and an open-source or self-hosted edition.
0 — No history of any kind; only the current state is shown.
3 — An uptime percentage and a response time chart per monitor; retention, export and the vendor's own status are basic or not described.
5 — Uptime and response time reports per monitor and period, SLA reports, scheduled email reports, the retention period of check results stated, CSV or API export, the probe IPs published, and the vendor's own public status page.
8 — Response time percentiles and breakdowns (DNS, connect, TLS, first byte), client-ready branded reports, retention of a year or more stated per plan, a raw export of check results, the vendor's incident history and post-mortems public, and an SLA with credits published.
10 — A record that holds up in an audit: SLA calculations with their method stated, incident records suitable for ISO 27001, NIS2 or DORA evidence, full history exportable in an open format, a self-hosted or open-source edition with feature parity stated, and the vendor's own availability over several years published.
The Agency Developer
Uptime calculation is documented with impact weighting — a major outage counts fully, a partial one half, degraded not at all — every check records DNS, connect, TLS, first-byte and transfer phases separately, and retention is stated per plan at three, twelve and twenty-four months with response logs on all plans. Reports are timestamped and archived and positioned as SOC 2 CC2.3 evidence, workspace data can be exported, and a public changelog exists. We found no public information on scheduled email reports — the monthly client report is my bread and butter — nor on percentiles, published probe IPs for allow-listing, or an SLA with credits outside the tailored Enterprise plan. 4 20 7 2 10 3
The SaaS Platform Engineer
The uptime calculation is documented — a major outage counts fully, a partial outage half, degraded performance not at all, maintenance never — which is reproducible math I could defend in a review, and every check records DNS, connect, TLS, first byte and transfer separately. Retention is stated per plan at 3, 12 and 24 months, and an AGPL self-hosted edition with Docker and a Helm chart is documented. We found no public information on response time percentiles, scheduled email reports, the probe IP addresses for allow-listing, the vendor's own incident history, or an SLA with credits. 2 4 5 7 10 20
The Customer Support Lead
The uptime calculation is documented, including how major, partial and degraded impacts are weighted, which is a number I can defend in a renewal, and retention is stated per plan at 3, 12 and 24 months with response logs on every plan and a phase-by-phase latency breakdown. The AGPL-3.0 licence with Docker and Kubernetes self-hosting means the record can live on our own servers. We found no public information on response-time percentiles, scheduled or client-facing reports, probe IP addresses for allow-listing, the vendor's own public status history, or a published SLA with credits. 2 4 5 7 20 21
The E-Commerce Operations Manager
The uptime calculation is documented — a major outage counts fully, a partial outage half, degraded performance not at all, and maintenance is excluded — every check records DNS, connect, TLS, first byte and transfer separately, retention is stated per plan at 3, 12 and 24 months, workspace data can be exported, and status reports are timestamped and archived so the trail exists for SOC 2 CC2.3. The product is fully open source under AGPL-3.0 and self-hostable with Docker or Kubernetes, which is the strongest guarantee that the record survives. We found no public information on scheduled email reports, response-time percentiles, client-ready reports of what downtime cost, the probe IP addresses for allow-listing, or the vendor's own published availability history, and a dedicated SLA appears only inside a tailored Enterprise plan. 2 3 5 7 20 21
The Information Security Officer
Uptime calculation and impact weighting are documented, latency is recorded separately for DNS, connect, TLS, first byte and transfer, retention is stated per plan at 3, 12 and 24 months, workspace data and the audit log are exportable, and status reports are timestamped and archived in a form the vendor itself frames as SOC 2 CC2.3 evidence. An AGPL-3.0 self-hosted edition with Docker Compose, a Helm chart and a lightweight status-page-only setup exists. We found no public information on the vendor's own public status page and incident history, an SLA with credits, probe IP addresses for allow-listing, or percentile breakdowns and scheduled email reports — the pieces an ISO 27001 auditor would ask me to produce. 4 5 7 10 21
The Skeptic
Retention is stated per plan — 3, 12 and 24 months — and the uptime calculation, including how major, partial and degraded states count, is documented, with every check recording DNS, connect, TLS, first-byte and transfer phases. My standing questions are unanswered: I found no public information on the vendor's own status page or public incident history, response time percentiles, scheduled email reports, published probe IP addresses, or an SLA with credits outside a custom enterprise plan. Workspace data can be exported from the dashboard and the code is open, though the self-hosted path is documented to work with private locations only and to show no dashboard data without a working Tinybird setup. 2 4 5 7 10 20
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Who the contracting entity and the parent company are, where account data, alert contacts (names and phone numbers of the people on call), status page subscribers and check results are stored and processed, and who the subprocessors are (hosting, SMS and phone gateways, email delivery, support and payment tools). Independently sourced by the sovereignty pipeline. Probe locations outside Europe 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 or open-source 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 call gateways, email, 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, or a self-hosted open-source edition with no call home, data export and deletion documented, and certifications published with their scope rather than implied.
The Agency Developer
The subprocessor list is public with each provider's location, infrastructure defaults to EU hosting where the provider offers it, and the terms are governed by the internal laws of France. The primary application hosting and database are described as running globally on Vercel, Fly, Koyeb, Railway and Turso with payment through Stripe in the US, and we found no public information on a named legal entity, a published data processing agreement, or security certifications. The AGPL-3.0 self-hosted edition is documented down to ports and Docker images and can keep records on our own servers, which is the chain I would trust for client work. 11 12 9 10 5 21
The SaaS Platform Engineer
French governing law with a Paris address in the structured data, a public subprocessor list with locations, and EU hosting wherever the provider offers it — queues on GCP, analytics on Tinybird, email on Resend. But the application hosting and primary database are listed as global on Vercel, Fly, Koyeb, Railway and Turso, payment runs through Stripe in the US, the SMS gateways are unnamed, no contracting legal entity is named on the pages, and we found no public information on a data processing agreement or security certifications. The AGPL self-hosted edition, with a local analytics container and your own ingest endpoint, is the escape hatch that keeps every record on my own servers. 5 9 10 11 12 21
The Customer Support Lead
The subprocessor list is public with each provider's location, the terms are governed by the law of France, and EU-hosted infrastructure is the default where the provider offers it — queues on GCP, analytics on Tinybird, email on Resend — though application hosting and the primary database run globally on Vercel, Fly, Koyeb, Railway and Turso and payment is processed by Stripe in the US. The self-hosted edition is documented down to the compose services with a local analytics service and probes pointed at your own ingest endpoint, which keeps the records on the customer's own chain. We found no public information on a data processing agreement, a named SMS gateway, a security certification stated with its scope, or a legal entity name beyond OpenStatus. 5 9 10 11 12 14 21
The E-Commerce Operations Manager
The subprocessor list is public with purposes and locations — queues on GCP in the EU, analytics on Tinybird in the EU, email on Resend in the EU, product analytics on Openpanel in the EU, payment through Stripe in the US — while the application hosting and the primary database run globally on Vercel, Fly, Koyeb, Railway and Turso. The terms are governed by French law, and an AGPL-3.0 self-hosted edition is documented that can run on our own servers, which would put the whole chain in our hands. The pages name no legal entity behind the brand, and we found no public information on a published data processing agreement or on certifications such as ISO 27001 or SOC 2 for the vendor itself. 5 9 11 12 21
The Information Security Officer
The subprocessor list is public and specific — Stripe in the US for payment, server hosting on Vercel, Fly, Koyeb and Railway with global locations, queues on GCP in the EU, email on Resend and analytics on Tinybird and Openpanel in the EU — and infrastructure defaults to EU hosting wherever the provider offers it, though application hosting and the primary database are stated to run globally. French governing law and venue are named, but the captured pages name no contracting legal entity, and we found no public information on a published data processing agreement or the vendor's own security certifications. An AGPL-3.0 self-hosted edition, documented with a local analytics service in the stack, lets a customer keep records in their own chain, with stated limits such as external cron and private-location-only operation. 5 9 11 12 21
The Skeptic
The subprocessor list is public with locations — GCP, Tinybird, Resend and Openpanel in the EU, Stripe in the US — but application hosting and the primary database are described as running globally on Vercel, Fly, Koyeb, Railway and Turso, so where account data and alert contacts actually sit is not committed to Europe. The terms name no legal entity and are governed by the laws of France, and I found no public information on a published data processing agreement or certifications. An AGPL-3.0 self-hosted edition with local services is documented, which a customer can run as its own European chain. 5 9 10 11 12
Pricing transparency
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real annual cost from public pages alone: price per tier by number of monitors, check interval and status pages, team seats and on-call responders, what SMS and phone alerts cost, which features (multi-step or browser checks, SSO, longer retention, private locations, white-label) cost extra, the free tier and its limits, overage handling, minimum term and VAT.
0 — No public prices at all; every customer is a sales call.
3 — A starting price or a free tier exists, but how cost scales with monitors, intervals, seats or alerts is unclear.
5 — Tiers are public with their monitor count, interval and main inclusions, but at least one commonly needed piece (SMS or call alerts, extra seats, extra status pages, SSO, longer retention) is unpriced or "on request".
8 — Every tier priced publicly with its scaling rule (monitors, interval, seats, responders, status pages), SMS and call costs stated, add-ons priced, overage handling stated, minimum term and VAT treatment stated.
10 — Complete price computability: annual cost derivable for a given number of monitors, interval, team size and alert volume, with every add-on, overage and support fee and the cancellation and data-return terms published.
The Agency Developer
Every tier is public with its monitor count, interval, regions, status pages, components, retention and channel limits — Starter $30/mo, Pro $100/mo, Scale $500/mo, annual billing two months free — and the scaling rules are priced: extra monitors at $15/mo per ten, extra status pages $20/mo each, white label $300/mo, SSO/SAML $250/mo, with unlimited team members. Cancellation, proration, over-limit behaviour and EUR/USD billing are stated, so I can price two hundred monitors from the page alone. We found no public information on per-message SMS costs or VAT treatment, which keeps this short of the top band. 7 1 14 21
The SaaS Platform Engineer
Nearly everything a buyer needs is public: every tier's monitor count, interval, regions, status pages, components, notification channels and retention; extra monitors at $15/mo per 10; extra status pages at $20/mo each; and priced add-ons for the custom theme ($20/mo), email authentication ($100/mo), IP restriction ($100/mo), SSO/SAML ($250/mo) and White Label ($300/mo), with annual billing giving two months free, proration, cancellation terms and EUR/USD support. What we found no public information on is the cost of SMS delivery and the VAT treatment — both of which I would need before signing, since my alerts travel by SMS. 2 3 7 14 21
The Customer Support Lead
The real annual cost is computable from the pricing page: Starter $30/mo, Pro $100/mo and Scale $500/mo with monitor counts, intervals, regions per monitor, status pages, components, notification channels and retention per tier, annual billing with two months free (Starter at $300/year, Pro at $1,000/year, Scale at $5,000/year), and add-ons priced exactly — extra monitors at $15/mo per ten, extra status pages at $20/mo each, white label $300/mo, SSO/SAML $250/mo — plus unlimited team members, proration, cancel-anytime and a stated over-limit behaviour of never stopping monitors without notice. We found no public information on VAT treatment or any per-message cost for SMS, and the Enterprise plan is tailored on request. 1 3 7
The E-Commerce Operations Manager
Every tier is public with its scaling rule: the free Hobby plan at $0 with one monitor and 10-minute checks, Starter at $30/mo with 20 monitors and 1-minute checks, Pro at $100/mo with 50 monitors, 30-second checks and all 28 regions, Scale at $500/mo, and annual billing giving two months free ($300/year, $1,000/year, $5,000/year). Add-ons are priced openly — extra monitors at $15/mo./10, extra status pages at $20/mo./each, SSO/SAML at $250/mo, White Label at $300/mo, Custom theme at $20/mo — with unlimited team members, no per-seat fees, proration, cancellation anytime, and a stated over-limit policy of reaching out rather than stopping monitors. What I still cannot compute from the public pages is the cost of an SMS alert, and VAT treatment is not stated, both of which matter for my German bookkeeping. 1 2 3 7
The Information Security Officer
Every tier is public with monitor count, interval, regions per monitor, components, notification channels, status pages and retention, plus scaling rules (monitor add-on packs at $15/mo./10, extra status pages at $20/mo./each) and add-on prices (custom theme $20/mo., email authentication $100/mo., IP restriction $100/mo., SSO/SAML $250/mo., white label $300/mo.); seats are unlimited with no per-seat fee, annual billing gives two months free, proration and cancellation are stated, and exceeding limits is handled by outreach rather than shutoff. Private probes bill as the customer's own host or container cost. We found no public information on the cost of SMS and phone alerts, VAT treatment, or a minimum term, and the enterprise plan is priced on request. 1 7 14
The Skeptic
The pricing page lets a buyer do arithmetic: per-tier monitors, interval, regions, components, status pages, notification channels and retention in the open, flat unlimited seats, SSO at $250/mo, White Label at $300/mo, extra monitors at $15/mo./10, extra status pages at $20/mo. each, annual billing as two months free, proration, and a promise never to stop monitors at a limit. Two gaps remain: SMS alert costs are not stated, and I found no public information on VAT treatment; everything above Scale is a tailored enterprise conversation. 1 2 3 7
European sovereignty — proven facts
0 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined | — | uncited Report an error |
|---|---|---|---|
| Hosting location | Not determined ⚠ unverified | — | uncited Report an error |
| Hosting options | Not determined ⚠ unverified | — | uncited Report an error |
| Open source | Not determined ⚠ unverified | — | uncited Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about openstatus
Is openstatus European?
Yes. whats-best.ai classifies openstatus as EU-Made.
Where does openstatus store data?
Not stated on the vendor’s pages as of 1 Nov 2026.
Does openstatus have a free plan?
Yes. openstatus has a free plan, per the vendor’s page captured 1 Nov 2026.
What are the best alternatives to openstatus?
As of 2 Nov 2026, the panel rates Hyperping (3.5/5), Checkly (3.5/5) and Oh Dear (3.5/5) highest among the other 14 Uptime Monitoring & Status Pages 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 Hyperping (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: openstatus alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 1 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 — Hosting location, Hosting options, Open source. Not confirmed on the vendor’s own pages as captured.
- 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.
- 13 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
- 11 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
- 4 compliance 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 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 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
- 3 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. 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.openstatus.dev Checked 1 Nov 2026 Details →
- 2 Features page (uptime monitoring) www.openstatus.dev Checked 1 Nov 2026 Details →
- 3 Features page (status pages) www.openstatus.dev Checked 1 Nov 2026 Details →
- 4 Documentation www.openstatus.dev Checked 1 Nov 2026 Details →
- 5 Documentation (self-hosting) www.openstatus.dev Checked 1 Nov 2026 Details →
- 6 API documentation www.openstatus.dev Checked 1 Nov 2026 Details →
- 7 Pricing page www.openstatus.dev Checked 1 Nov 2026 Details →
- 8 About page www.openstatus.dev Checked 1 Nov 2026 Details →
- 9 Terms of service www.openstatus.dev Checked 1 Nov 2026 Details →
- 10 Privacy policy www.openstatus.dev Checked 1 Nov 2026 Details →
- 11 Subprocessor list www.openstatus.dev Checked 1 Nov 2026 Details →
- 12 Security / trust page www.openstatus.dev Checked 1 Nov 2026 Details →
- 13 Checks, locations & failure confirmation — found from sitemap www.openstatus.dev Checked 1 Nov 2026 Details →
- 14 Checks, locations & failure confirmation — found from sitemap www.openstatus.dev Checked 1 Nov 2026 Details →
- 15 Alerting, escalation & on-call — found from sitemap www.openstatus.dev Checked 1 Nov 2026 Details →
- 16 Status pages & incident communication — found from sitemap www.openstatus.dev Checked 1 Nov 2026 Details →
- 17 Status pages & incident communication — found from sitemap www.openstatus.dev Checked 1 Nov 2026 Details →
- 18 API, monitoring as code & team administration — found from sitemap www.openstatus.dev Checked 1 Nov 2026 Details →
- 19 API, monitoring as code & team administration — found from sitemap www.openstatus.dev Checked 1 Nov 2026 Details →
- 20 Uptime reports, data & the vendor's own reliability — found from sitemap www.openstatus.dev Checked 1 Nov 2026 Details →
- 21 Uptime reports, data & the vendor's own reliability — found from sitemap www.openstatus.dev Checked 1 Nov 2026 Details →
- 22 Open-source licence page — found from the homepage www.openstatus.dev Checked 1 Nov 2026 Details →