# openstatus — Uptime Monitoring & Status Pages

openstatus by openstatus holds a panel rating of 3.5/5 from 6 AI judges (category median 3/5), as of 2026-11-02. Provenance: EU-Made; sovereignty: not determined.

- Vendor: openstatus (https://www.openstatus.dev)
- Category: [Uptime Monitoring & Status Pages](https://whats-best.ai/software/uptime-monitoring.md)
- Provenance (editorial classification): EU-Made
- Canonical page: https://whats-best.ai/software/uptime-monitoring/openstatus
- Alternatives: https://whats-best.ai/software/uptime-monitoring/openstatus/alternatives ([markdown](https://whats-best.ai/software/uptime-monitoring/openstatus/alternatives.md))
- Data as of: 2026-11-06 · evaluated 2026-11-02 · oldest source captured 2026-11-01

**AI-generated.** Every score, rationale and verdict here is written by a panel of AI judges from public evidence — an analysis, not a hands-on test. Every fact quotes the vendor page it was read from. No score can be bought. How scores are made: https://whats-best.ai/methodology

## 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 [S7]

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

## Scores by judge and criterion

Scores out of 5, each judge scoring independently against the published rubric (v1). "n/r" = not rated: the vendor publishes no price, or the judge found no public information on that criterion.

| Criterion | The Agency Developer | The SaaS Platform Engineer | The Customer Support Lead | The E-Commerce Operations Manager | The Information Security Officer | The Skeptic |
| --- | --- | --- | --- | --- | --- | --- |
| Checks, locations & failure confirmation | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 |
| Alerting, escalation & on-call | 3/5 | 3/5 | 3/5 | 3/5 | 3/5 | 3/5 |
| Status pages & incident communication | 3.5/5 | 4/5 | 4/5 | 4/5 | 3.5/5 | 3.5/5 |
| API, monitoring as code & team administration | 3.5/5 | 4.5/5 | 4/5 | 3.5/5 | 3.5/5 | 3.5/5 |
| Uptime reports, data & the vendor's own reliability | 3/5 | 3/5 | 3.5/5 | 3/5 | 3/5 | 3/5 |
| European sovereignty | 3.5/5 | 3/5 | 3.5/5 | 3/5 | 3/5 | 3/5 |
| Pricing transparency | 3.5/5 | 3.5/5 | 4/5 | 3.5/5 | 3.5/5 | 3.5/5 |
| **Weighted verdict** | **3.5/5** | **3.5/5** | **3.5/5** | **3.5/5** | **3/5** | **3.5/5** |

### The judges

- **The Agency Developer** (v1.0): Runs hosting and maintenance at a fifteen-person web agency with sixty client sites on WordPress, TYPO3 and Shopware. Has learned about an expired certificate from a client's angry phone call once and does not want a second time. Wants HTTP, keyword, SSL and domain expiry checks set up in bulk, client groups with their own status pages and monthly uptime reports, and a price per monitor that still works at two hundred monitors.
- **The SaaS Platform Engineer** (v1.0): Platform engineer at a forty-person B2B SaaS in Berlin, one of four people on the on-call rotation. Wants multi-step API checks with assertions, kept in Terraform next to the services they test, failures confirmed from a second location before anyone is woken, phone calls and escalation when an alert is not acknowledged, and a status page that updates without someone logging in at 3 a.m.
- **The Customer Support Lead** (v1.0): Leads a support team of nine at a software company whose customers are tax advisers and payroll offices. During the last outage the team answered three hundred tickets that all asked the same question. Wants a status page on the company's own domain with components customers recognise, incident templates, subscribers notified by email, a private page for the largest accounts, and an uptime history they can point to in a contract renewal.
- **The E-Commerce Operations Manager** (v1.0): Runs operations for an online shop selling garden furniture in Germany, Austria and Switzerland, with half the year's revenue between March and June. The homepage once answered 200 while the checkout threw an error for six hours. Wants the checkout and the payment page checked, not only the homepage, an SMS or call to whoever is on duty that night, and a report that shows the agency what the downtime cost.
- **The Information Security Officer** (v1.0): Information security officer at a mid-sized logistics company that falls under NIS2 and is working towards ISO 27001. Needs every outage recorded with detection time, response and resolution, in a form an auditor accepts. Reads the subprocessor list before the feature page, because the on-call staff's mobile numbers and the status page subscribers are personal data, and wants single sign-on and an audit log before anyone gets a login.
- **The Skeptic** (v1.0): Has seen "30-second checks from 20 locations" that paged the whole team for a single probe's network glitch, a status page that went down with the product it reported on, and "unlimited SMS" with a fair-use clause on page nine. Asks how a failure is confirmed, how long the history is kept and whether it can be exported, where the monitor itself publishes its own outages — and what leaving would cost.

## European sovereignty — proven facts

Built only from facts on the vendor's own pages; a dimension we could not prove is left open, never scored as zero. Headline: not determined.

| Dimension | Finding | Points | Source |
|---|---|---|---|
| Legal entity | Not determined | — | — |
| Hosting location | Not determined | — | — |
| Hosting options | Not determined | — | — |
| Open source | Not determined | — | — |
| Data processing agreement | Not determined | — | — |
| Transfer impact assessment | Not determined | — | — |

## Key facts

Each fact is the vendor's own statement, cited to the source page it was read from ([S*n*] → Sources).

**Compliance**
- Applicable frameworks: GDPR · UK GDPR · CCPA [S10]
- Privacy contact email: privacy@openstatus.dev [S10]
- Rfc9116 contact: /.well-known/security.txt · yes [S12]
- SOC 2: reports timestamped and archived for SOC 2 CC2.3 [S3]
- SOC 2:  [S1]

**Data**
- Account deletion window days: 30 [S10]
- Account information collected: name, email, profile photo, OAuth identifiers (GitHub/Google) [S10]
- Billing record retention: 7 [S10]
- Export available: yes [S10]
- Integration token deletion: 30 [S10]
- Log retention: 30 [S10]
- No advertising cookies: no [S10]
- No sale of data: no · no [S10]
- Payment processor: Stripe · no [S10]
- Retention: yes [S4]
- Telemetry retention: retention window depends on subscription plan [S10]

**Hosting**
- EU default: yes · GCP · Tinybird · Resend · Openpanel [S12]
- Global providers: Vercel · Fly · Koyeb · Railway · Turso [S12]
- Self hosting: AGPL-3.0 · yes · 8.5 [S21]
- Status page dns: 76.76.21.21 · Vercel DNS · cname.vercel-dns.com [S16]

**Integrations**
- API:  [S1]
- API endpoint: api.openstatus.dev [S6]
- API token source: workspace settings [S18]
- Audit export: CSV · JSON [S1]
- Cli: yes [S2]
- Cli:  [S1]
- Cli: yes [S6]
- Cli terraform export: openstatus terraform generate · yes [S19]
- Github:  [S1]
- Mcp server: yes [S6]
- Node sdk: yes · @openstatus/sdk-node · Node · Deno [S6]
- Notification channels: Slack · Discord · PagerDuty · Opsgenie · email · SMS · webhook [S2]
- Notification channels extra: Telegram · Google Chat · Microsoft Teams · WhatsApp · Grafana OnCall · ntfy [S2]
- Notification slack terraform: Slack notifications configurable via Terraform using webhook_url [S19]
- Openapi explorer: yes [S6]
- Openapi spec URL: api.openstatus.dev/openapi · yes [S6]
- Private location cloudflare containers: yes [S14]
- Sdk docs URL: jsr.io/@openstatus/sdk-node [S6]
- Sdk other languages: on request only [S6]
- Self hosting docker images: ghcr.io/openstatushq/private-location:latest · ghcr.io/openstatushq/openstatus-private-location:latest [S5]
- Self hosting prebuilt images: yes [S5]
- Self hosting service architecture: 3001 · 3002 · 3000 · 5001 · 8080 · 3003 · 7181 · 8081 [S5]
- Shadcn: yes [S3]
- Social notifier example: statuspage-socials-notifier reference receiver cross-posts updates to X (Twitter) and Bluesky [S17]
- Source github: yes [S1]
- Status page connectrpc: ConnectRPC StatusPageService [S16]
- Status page custom domain: https://<slug>.openstatus.dev [S18]
- Status page v1 deprecated: public · password · email-domain · yes [S16]
- Terraform:  [S1]
- Terraform auth: api_token_variable [S18]
- Terraform authentication: api_token [S19]
- Terraform export scope: monitors · status pages · notifications · maintenance windows [S18]
- Terraform generate command: yes · openstatus terraform generate [S18]
- Terraform import support: yes [S18]
- Terraform notification types: 12 · PagerDuty · Discord · Email · OpsGenie · webhooks · Slack [S18]
- Terraform provider: HTTP · TCP · DNS · ICMP monitors · notification channels · status pages · private locations [S2]
- Terraform provider: yes [S6]
- Terraform provider: yes · openstatusHQ/openstatus · ~> 0.1 [S19]
- Terraform provider source: openstatusHQ/openstatus · ~> 0.1 [S18]
- Terraform scope: monitors · status pages · component groups · notifications · private locations [S19]
- Terraform workflow: standard Terraform plan/apply workflow supported [S19]
- Tooling: yes · yes · yes · yes [S8]
- Webhook generic payload versioned: 1 · bumped on breaking change [S17]

**Legal**
- Entity name: OpenStatus · openstatus.dev · cloud platform as a service [S9]
- Governing law: France [S9]
- Liability limitation: broad disclaimer of all damages of any kind [S9]
- Product description: OpenStatus provides an open source monitoring and status page tool [S9]
- Self funded:  [S1]
- Suspension rights: yes [S9]
- Term change rights: Terms may be revised at any time; changes effective immediately upon posting [S9]
- Venue: federal courts of France [S9]
- Warranty disclaimer: yes [S9]

**Pricing**
- Addons: workspace-level · monthly regardless of plan billing cycle [S7]
- Annual billing: 2 months free · 1000 · 5000 · 300 [S7]
- Annual discount: 2 [S2]
- Billing cycles: yes · yes [S7]
- Cancellation: yes · yes [S7]
- Check intervals: 30s · 30s · 1m [S7]
- Components limits: 50 · 500 · 20 [S7]
- Currencies: EUR · USD [S7]
- Custom theme addon: Pro · Scale · 20 [S3]
- Custom theme price: 20 · yes [S7]
- Data retention: 12 · 24 · 3 [S7]
- Enterprise plan: SOC2 reports · SAML/SSO · custom regions · higher limits · dedicated SLA · custom contracts · invoicing · yes [S7]
- Free plan: Hobby · 1 · yes · 3 · 10 minutes [S7]
- Free plan: yes · 6 · no · 1 · 1 [S21]
- Free trial: 14 · no · 30 [S3]
- Hobby: 1 · 1 · 10 min · 0 [S1]
- Hobby free: Hobby · 3 · 1 · no [S3]
- Hobby plan: yes · 10m · 1 [S2]
- Ip restriction price: 100 · yes [S7]
- Monitor limits: 50 · 10 · 15 · 50 · 20 [S7]
- No per seat: flat · no [S1]
- Notification channels: 20 · 20 · 10 [S7]
- Over limit behavior: yes [S7]
- Paid start: 20 · 30 · yes [S21]
- Private location cost model: included with monitor checks · you pay for the host/container [S14]
- Pro: all 28 regions · custom theme · 50 · 30 sec · 100 [S1]
- Pro monthly: 100 [S7]
- Pro plan: 28 · 30s · 50 · 100 [S2]
- Proration: yes · yes [S7]
- Regions: 28 [S7]
- Regions per monitor: 28 · 28 · 6 [S7]
- Scale: white label · email auth · IP restriction · 500 · 500 [S1]
- Scale monthly: 500 [S7]
- Scale plan: 500 [S2]
- SSO price: 250 [S7]
- Starter: 100 · 500 · 2 · 30 · 20 [S3]
- Starter: custom domain · subscribers · 20 · 1 min · 30 [S1]
- Starter monthly: 30 [S7]
- Starter plan: 6 · 1m · 20 · 30 [S2]
- Status pages limits: 5 · 20 · 10 · 1 [S7]
- Trial: 14 · no [S2]
- Trial: 14 · Starter · no · 30 [S1]
- Trial: 14 · Starter · no [S7]
- White label price: 300 · yes [S7]

**Product**
- Adr practice: yes [S12]
- Alert channels: email · Slack · WhatsApp [S13]
- Alert channels: yes [S7]
- Alert integrations: WhatsApp · PagerDuty · OpsGenie · Grafana OnCall · yes [S7]
- Alert quorum logic: alerts aggregate across regions [S2]
- API audit log: yes · apiKey [S6]
- API auth header: x-openstatus-key [S6]
- API key generation: Settings > General > API Keys [S6]
- API key shared surfaces: API · CLI · Terraform · MCP server [S6]
- API manageable resources: monitors · status pages · status reports · maintenance windows · notification channels [S6]
- API method shape: POST /rpc/openstatus.v1.<Service>/<Method> [S6]
- API protocol: ConnectRPC · JSON over HTTP [S6]
- API scoped keys: yes [S12]
- Assertions: status code · header · body · degraded · timeout [S2]
- Audit log:  [S1]
- Audit log: Pro · Scale [S7]
- Audit log: yes [S12]
- Audit log access: /settings/audit-logs · Pro [S12]
- Auth methods: GitHub OAuth · Google OAuth · email magic link · SSO [S12]
- Automatic subscriber notifications: status reports · scheduled maintenance · yes [S21]
- Capabilities: yes · yes · yes · yes [S13]
- Check definition: single execution of a monitor at a point in time [S13]
- Check interval options: 30s · 1m · 5m · 10m [S2]
- Check types: yes · yes [S13]
- Code review practice: yes · yes [S12]
- Community subscriptions: email · RSS/Atom · JSON [S21]
- Component subscribe: yes [S3]
- Components groups: yes · yes · yes [S3]
- Custom domain: yes · yes [S3]
- Custom domain: yes [S1]
- Dashboard email no confirmation: no [S17]
- Data sharing controls: uptime_percentages · response_times · manual_reports_only [S3]
- Declared incidents: severity · commander · internal timeline · postmortem · dashboard · Slack [S20]
- Deployment models: yes · yes [S8]
- Description: open-source synthetic monitoring platform for websites and APIs with downtime/slowness notifications [S10]
- Doc positioning: Infra as code for uptime monitoring, status pages and incident response, updatable by agents [S4]
- Docs last updated: 2026-10-25 [S19]
- Encryption at rest: Turso · Tinybird · Vercel · Fly · yes [S12]
- Failed check retry: yes [S13]
- Feeds: RSS 2.0 · Atom 1.0 · JSON · yes [S17]
- Feeds password query param: yes [S17]
- Founded: 2023 [S8]
- Free plan components: 6 · 1 · 3 [S21]
- Hobby components: 3 · 10m [S1]
- Http methods: yes · yes [S2]
- Https tls: yes [S12]
- Hybrid monitor locations: yes [S14]

**Subprocessors**
- Categories: Stripe · Slack · Discord · Microsoft Teams · OpsGenie · PagerDuty · hosting and database providers · payment processor · transactional email provider · error-monitoring provider · notification platforms [S10]
- Fly: Fly · Server hosting · Global [S11]
- Gcp: GCP · Queue · EU [S11]
- Koyeb: Koyeb · Server hosting · Global [S11]
- Openpanel: Openpanel · Product analytics · EU [S11]
- Page exists: yes [S8]
- Public list: yes · /subprocessors [S12]
- Railway: Railway · Server hosting · Global [S11]
- Resend: Resend · Email sending · EU [S11]
- Stripe: Stripe · payment processing · US [S11]
- Tinybird: Tinybird · Analytical database (Clickhouse) · EU [S11]
- Turso: Turso · Relational database (SQLite) · Global [S11]
- Vercel: Vercel · Server hosting · Global [S11]

**Support**
- Community: Discord · GitHub · Twitter · BlueSky · YouTube · LinkedIn [S1]
- Community discord: yes · yes [S8]
- Privacy response days: 30 [S10]
- Private location guide: yes [S14]
- Related templates: Related templates include Network Connectivity Issues and Security Incident Response [S15]
- Vulnerability reporting: 3 business days [S12]

151 more facts on the canonical page: https://whats-best.ai/software/uptime-monitoring/openstatus

## Questions

### 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](https://whats-best.ai/evidence/15508).

### What are the best alternatives to openstatus?

As of 2 Nov 2026, the panel rates [Hyperping (3.5/5)](https://whats-best.ai/software/uptime-monitoring/hyperping), [Checkly (3.5/5)](https://whats-best.ai/software/uptime-monitoring/checkly) and [Oh Dear (3.5/5)](https://whats-best.ai/software/uptime-monitoring/oh-dear) 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](https://whats-best.ai/software/uptime-monitoring/hyperping) (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: [how scores are made](https://whats-best.ai/methodology#ordering). The full list, with European products first: [openstatus alternatives](https://whats-best.ai/software/uptime-monitoring/openstatus/alternatives).

## What this page leaves out

- 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.
- 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.
- 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.
- 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.
- 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.
- 3 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown.

## Sources

- [S1] Vendor homepage: https://www.openstatus.dev/ (checked 2026-11-01)
- [S2] Features page (uptime monitoring): https://www.openstatus.dev/uptime-monitoring (checked 2026-11-01)
- [S3] Features page (status pages): https://www.openstatus.dev/status-page (checked 2026-11-01)
- [S4] Documentation: https://www.openstatus.dev/docs (checked 2026-11-01)
- [S5] Documentation (self-hosting): https://www.openstatus.dev/docs/guides/self-hosting-openstatus (checked 2026-11-01)
- [S6] API documentation: https://www.openstatus.dev/tooling/api (checked 2026-11-01)
- [S7] Pricing page: https://www.openstatus.dev/pricing (checked 2026-11-01)
- [S8] About page: https://www.openstatus.dev/about (checked 2026-11-01)
- [S9] Terms of service: https://www.openstatus.dev/terms (checked 2026-11-01)
- [S10] Privacy policy: https://www.openstatus.dev/privacy (checked 2026-11-01)
- [S11] Subprocessor list: https://www.openstatus.dev/subprocessors (checked 2026-11-01)
- [S12] Security / trust page: https://www.openstatus.dev/security (checked 2026-11-01)
- [S13] Checks, locations & failure confirmation — found from sitemap: https://www.openstatus.dev/docs/concept/uptime-monitoring (checked 2026-11-01)
- [S14] Checks, locations & failure confirmation — found from sitemap: https://www.openstatus.dev/docs/concept/private-locations (checked 2026-11-01)
- [S15] Alerting, escalation & on-call — found from sitemap: https://www.openstatus.dev/guides/scheduled-maintenance (checked 2026-11-01)
- [S16] Status pages & incident communication — found from sitemap: https://www.openstatus.dev/docs/reference/status-page (checked 2026-11-01)
- [S17] Status pages & incident communication — found from sitemap: https://www.openstatus.dev/docs/reference/subscriber (checked 2026-11-01)
- [S18] API, monitoring as code & team administration — found from sitemap: https://www.openstatus.dev/docs/guides/how-to-manage-openstatus-with-terraform (checked 2026-11-01)
- [S19] API, monitoring as code & team administration — found from sitemap: https://www.openstatus.dev/docs/concept/uptime-monitoring-as-code (checked 2026-11-01)
- [S20] Uptime reports, data & the vendor's own reliability — found from sitemap: https://www.openstatus.dev/docs/concept/status-reports-and-incidents (checked 2026-11-01)
- [S21] Uptime reports, data & the vendor's own reliability — found from sitemap: https://www.openstatus.dev/use-case/open-source (checked 2026-11-01)
- [S22] Open-source licence page — found from the homepage: https://www.openstatus.dev/github (checked 2026-11-01)

---

Cite as: whats-best.ai, "openstatus — Uptime Monitoring & Status Pages", AI panel analysis, as of 2026-11-06. https://whats-best.ai/software/uptime-monitoring/openstatus

Corrections: https://whats-best.ai/correct/1350?target=page