# openstatus

> Openstatus is an open-source uptime monitoring and status page platform built for infra as code: monitors, status pages, and notification channels are declared in YAML or Terraform and driven from a CLI, a typed API, or an MCP server (Claude, ChatGPT, Cursor), so your agents can update them. It runs synthetic checks in parallel from 28 regions across Fly.io, Koyeb, and Railway and surfaces incidents on branded status pages. Available as managed SaaS or self-hosted (AGPL-3.0). Bootstrapped, founded in 2023.

## Who it's for

- Teams that manage uptime monitoring and status pages as infra as code and let agents (Claude, Cursor, ChatGPT, CI) open and resolve incidents over MCP, CLI, or API
- Development teams that want transparent incident communication
- Companies that need multi-region uptime monitoring
- Teams that prefer infrastructure-as-code workflows (YAML via the CLI, or the Terraform provider)
- Organizations that require self-hosted monitoring behind a firewall (private locations)
- Open-source projects and startups looking for a free or affordable monitoring solution

## Pricing

- **Hobby** — $0/month: 1 monitor, 6 regions, 10m check interval, 1 status page, 3 page components, 14-day data retention
- **Starter** — $30/month: 20 monitors, 28 regions, 1m check interval, 1 status page, 20 components, 3-month retention, subscribers, custom domain, WhatsApp/SMS/PagerDuty alerts
- **Pro** — $100/month: 50 monitors, 28 regions, 30s check interval, 5 status pages, 50 components, 12-month retention, private locations, OTel exporter, 20 notification channels
- **Scale** — $500/month: everything in Pro plus 10 status pages, 500 page components, and White Label, Magic Link auth, and IP Restriction included at no extra cost

Annual billing gives 2 months free (Starter $300/yr, Pro $1,000/yr, Scale $5,000/yr). Pricing is available in USD and EUR.

## Key Features

- **28-region monitoring** — Parallel checks across Europe, North America, South America, Asia, Africa, and Oceania; no round-robin, all selected regions fire simultaneously
- **Multi-cloud** — Monitors run on Fly.io, Koyeb, and Railway for true cloud diversity
- **Status Pages** — Branded public or password-protected pages with custom domains, themes, maintenance windows, and subscriber notifications (email, RSS, Slack)
- **API Monitoring** — Assertions, thresholds, status code checks, header and body validation
- **Infra as Code** — Define monitors, status pages, and notification channels in YAML (CLI, GitHub Actions) or Terraform
- **Private Locations** — 8.5MB Docker image for monitoring internal services behind firewalls
- **Alerting** — Email, Slack, Discord, webhook, WhatsApp, SMS, PagerDuty, OpsGenie, Grafana OnCall
- **OpenTelemetry** — Export synthetic check metrics to any OTLP endpoint
- **SDK** — Node.js SDK on JSR (@openstatus/sdk-node)
- **MCP server** — Streamable-HTTP MCP at https://api.openstatus.dev/mcp with OAuth 2.1, for status reports, maintenance windows, and monitor reads; every mutation lands in the audit log
- **Open-source** — AGPL-3.0-licensed, self-hostable, 8k+ GitHub stars

## Key Differentiators

- Built for humans and agents: MCP server, --json CLI output, typed API, read-only or read-write API key scopes
- Open-source and bootstrapped (no VC funding)
- Parallel scheduling — all selected regions check simultaneously (vs. round-robin competitors)
- Unlimited team members on paid plans
- Status page subscribers included (not a paid add-on)
- Private status pages included in the team plan (not an additional charge)
- Self-hosting option with full feature parity

## Product

- [Status Page](https://www.openstatus.dev/status-page): Create a public or private status page in minutes. Show real-time uptime, incidents and maintenance on a fully branded page with a custom domain.
- [Uptime Monitoring](https://www.openstatus.dev/uptime-monitoring): Monitor your websites, APIs and services from 28 regions. Get alerted the moment a check fails an assertion or exceeds your threshold.

## Tooling

- [API](https://www.openstatus.dev/tooling/api): A typed JSON-over-HTTP API powered by ConnectRPC — every endpoint the dashboard uses, with a fully typed Node SDK on top.
- [CLI](https://www.openstatus.dev/tooling/cli): Manage monitors, status pages, and incidents from your terminal — interactive for humans, scriptable for agents, and YAML-managed for monitoring as code.
- [MCP Server](https://www.openstatus.dev/tooling/mcp-server): Connect Claude, ChatGPT, Cursor, and any other Model Context Protocol client to your workspace — sign in with OAuth, pick a workspace, and get audit-logged mutations with explicit notify semantics.
- [Terraform](https://www.openstatus.dev/tooling/terraform): Manage monitors, notifications, and status pages as HCL — same plan-and-apply lifecycle as the rest of your infrastructure, with one command to bootstrap from an existing workspace.

## Documentation

- [Building Trust with Status Pages](https://www.openstatus.dev/docs/concept/best-practices-status-page): Understanding how to communicate effectively during incidents and build user trust through transparency.
- [Foundational Concepts](https://www.openstatus.dev/docs/concept/getting-started): Understand uptime monitoring, latency vs response time, SLA calculations, and the design decisions behind openstatus.
- [Understanding Latency vs Response Time](https://www.openstatus.dev/docs/concept/latency-vs-response-time): Deep dive into the difference between latency and response time, and why both matter for monitoring
- [Understanding Private Locations](https://www.openstatus.dev/docs/concept/private-locations): What a private location is, when to use one, how it talks to openstatus, and how it differs from a public probe.
- [Probes, Locations, and Regions](https://www.openstatus.dev/docs/concept/probes-and-locations): Three words that look interchangeable but aren't — what each one means in openstatus and how they fit together.
- [Understanding Status Reports and Incidents](https://www.openstatus.dev/docs/concept/status-reports-and-incidents): How openstatus separates detecting a problem (incidents) from communicating it (status reports and maintenance windows), and how report updates drive your status page.
- [Uptime Calculation and Shared Values](https://www.openstatus.dev/docs/concept/uptime-calculation-and-values): Understand how openstatus calculates uptime — absolute (duration or requests) and manual modes — and choose which values to share on your status page.
- [Understanding Monitoring as Code](https://www.openstatus.dev/docs/concept/uptime-monitoring-as-code): Why and how to manage monitoring configuration as code for GitOps workflows
- [Understanding Uptime Monitoring](https://www.openstatus.dev/docs/concept/uptime-monitoring): A deep dive into uptime monitoring concepts, architecture, and best practices
- [How-to Guides](https://www.openstatus.dev/docs/guides/getting-started): Practical guides for integrating openstatus with GitHub Actions, OTLP endpoints, Cloudflare, and more.
- [How to Deploy a Status Page to Cloudflare Pages](https://www.openstatus.dev/docs/guides/how-deploy-status-page-cf-pages): Learn how to use openstatus monitoring data to deploy a status page on Cloudflare Pages.
- [How to Add a Status Badge to a GitHub README](https://www.openstatus.dev/docs/guides/how-to-add-svg-status-badge): A step-by-step guide to adding a real-time SVG or PNG status badge to your GitHub repository.
- [Configure Your Status Page](https://www.openstatus.dev/docs/guides/how-to-configure-status-page): A step-by-step tutorial to customize and configure your status page
- [Connect openstatus to your coding agent](https://www.openstatus.dev/docs/guides/how-to-connect-openstatus-to-your-agent): Step-by-step tutorial to add the openstatus MCP server to Claude Code, Codex, opencode, Cursor, Claude Desktop, or ChatGPT so the agent can read and manage your status pages
- [Create a Private Location](https://www.openstatus.dev/docs/guides/how-to-create-private-location): Set up monitoring from your own infrastructure using Docker-based private probes
- [Create Your Own Status Page Theme](https://www.openstatus.dev/docs/guides/how-to-create-status-page-theme): A step-by-step guide to designing, testing, and contributing a community theme for openstatus status pages.
- [How to Deploy a Private Probe on Cloudflare Containers](https://www.openstatus.dev/docs/guides/how-to-deploy-probes-cloudflare-containers): A step-by-step guide to deploying an openstatus private monitoring probe on Cloudflare Containers.
- [How to Auto-Post Status Updates to X and Bluesky](https://www.openstatus.dev/docs/guides/how-to-deploy-statuspage-socials-notifier): A step-by-step guide to deploying the statuspage-socials-notifier and cross-posting your status page updates to X (Twitter) and Bluesky.
- [How to Embed a Status Page in an Iframe](https://www.openstatus.dev/docs/guides/how-to-embed-status-page-iframe): Embed a trimmed, chromeless version of your openstatus status page on any website using the `?embed` query parameter.
- [How to Export Metrics to an OTLP Endpoint](https://www.openstatus.dev/docs/guides/how-to-export-metrics-to-otlp-endpoint): A step-by-step guide to sending openstatus metrics to your observability platform via OTLP.
- [Import a Status Page from Another Provider](https://www.openstatus.dev/docs/guides/how-to-import-status-page): Import your existing status page setup from Atlassian Statuspage, Better Stack, or Instatus into openstatus
- [Manage Your openstatus Stack with Terraform](https://www.openstatus.dev/docs/guides/how-to-manage-openstatus-with-terraform): Use Terraform to manage monitors, status pages, and notifications as code — version-controlled, peer-reviewed, and reproducible.
- [How to Monitor an MCP Server](https://www.openstatus.dev/docs/guides/how-to-monitor-mcp-server): Monitor an MCP server with openstatus - JSON-RPC health checks, tools/list assertions, authenticated endpoints, and uptime alerts from 28 regions.
- [How to Run Synthetic Tests in GitHub Actions](https://www.openstatus.dev/docs/guides/how-to-run-synthetic-test-github-action): Integrate openstatus synthetic monitoring into your CI/CD pipeline
- [Set up SAML single sign-on](https://www.openstatus.dev/docs/guides/how-to-set-up-saml-sso): Let your team sign in to openstatus through Okta, Entra ID, or any SAML identity provider
- [Set Up the openstatus Slack Agent](https://www.openstatus.dev/docs/guides/how-to-setup-slack-agent): A step-by-step tutorial to install the openstatus Slack agent and manage incidents directly from Slack
- [How to translate your status page](https://www.openstatus.dev/docs/guides/how-to-translate-status-page): Enable multiple languages on your status page and contribute new translations.
- [How to Use openstatus React Widget](https://www.openstatus.dev/docs/guides/how-to-use-react-widget): Add an openstatus status widget to your React or Next.js app with the @openstatus/react package as a React Server Component, or build your own with the typed fetch helper.
- [Self-Host the openstatus Status Page (Lightweight)](https://www.openstatus.dev/docs/guides/self-host-status-page-only): How to self-host a status page - what you actually take on by running it yourself, when hosting it is the wrong call, and a Docker Compose setup that runs the status page without any monitoring infrastructure.
- [How to Self-Host openstatus](https://www.openstatus.dev/docs/guides/self-hosting-openstatus): Complete guide to deploying openstatus on your own infrastructure
- [Need help?](https://www.openstatus.dev/docs/help/support): We're always here to help.
- [API Rate Limits](https://www.openstatus.dev/docs/reference/api-rate-limits): Request limits for the openstatus API, what a 429 response looks like, and how to retry.
- [CLI Reference](https://www.openstatus.dev/docs/reference/cli-reference): Complete reference for the openstatus CLI — manage status pages, monitors, and incidents from your terminal.
- [DNS Monitor Reference](https://www.openstatus.dev/docs/reference/dns-monitor): Complete technical specification for DNS record monitoring
- [gRPC Monitor Reference](https://www.openstatus.dev/docs/reference/grpc-monitor): Complete technical specification for gRPC health check monitoring.
- [HTTP Monitor Reference](https://www.openstatus.dev/docs/reference/http-monitor): Complete technical specification for HTTP/HTTPS endpoint monitoring
- [ICMP Monitor Reference](https://www.openstatus.dev/docs/reference/icmp-monitor): Complete technical specification for ICMP (ping) monitoring.
- [Incident Reference](https://www.openstatus.dev/docs/reference/incident): Technical specification for incident management and lifecycle
- [Location Reference](https://www.openstatus.dev/docs/reference/location): Complete technical specification for Location monitoring
- [Maintenance Reference](https://www.openstatus.dev/docs/reference/maintenance): Technical specification for scheduled maintenance windows in openstatus.
- [MCP Server](https://www.openstatus.dev/docs/reference/mcp-server): Connect openstatus to AI assistants via the Model Context Protocol
- [Notification Channels Reference](https://www.openstatus.dev/docs/reference/notification): Technical specification for openstatus notification channels and alert payloads.
- [Reference Overview](https://www.openstatus.dev/docs/reference/overview): Technical specifications for openstatus monitors, status pages, notifications, locations, and the CLI, MCP, and Terraform integrations.
- [Page Components Reference](https://www.openstatus.dev/docs/reference/page-components): Complete specification for openstatus page components on status pages.
- [Private Location Reference](https://www.openstatus.dev/docs/reference/private-location): Technical specification for configuring and utilizing private monitoring locations.
- [Status Page Reference](https://www.openstatus.dev/docs/reference/status-page): Complete technical specification for openstatus status page configuration.
- [Status Report Reference](https://www.openstatus.dev/docs/reference/status-report): Technical specification for incident status updates within openstatus.
- [Subscriber Reference](https://www.openstatus.dev/docs/reference/subscriber): Technical specification for managing status page subscribers and their notifications.
- [TCP Monitor Reference](https://www.openstatus.dev/docs/reference/tcp-monitor): Complete technical specification for TCP service monitoring.
- [Terraform Provider Reference](https://www.openstatus.dev/docs/reference/terraform): Technical specification for the openstatus Terraform Provider.
- [Authentication](https://www.openstatus.dev/docs/sdk/nodejs/authentication): Configure API key authentication for the openstatus Node.js SDK
- [Error Handling](https://www.openstatus.dev/docs/sdk/nodejs/error-handling): Handle errors and implement retry strategies with the openstatus Node.js SDK
- [Getting Started](https://www.openstatus.dev/docs/sdk/nodejs/getting-started): Install and start using the openstatus Node.js SDK
- [Health Service](https://www.openstatus.dev/docs/sdk/nodejs/health-service): Check the openstatus API health status using the Node.js SDK
- [Maintenance Service](https://www.openstatus.dev/docs/sdk/nodejs/maintenance-service): Manage scheduled maintenance windows with the openstatus Node.js SDK
- [Monitor Service](https://www.openstatus.dev/docs/sdk/nodejs/monitor-service): Create and manage HTTP, TCP, and DNS monitors with the openstatus Node.js SDK
- [Notification Service](https://www.openstatus.dev/docs/sdk/nodejs/notification-service): Manage notification channels and providers with the openstatus Node.js SDK
- [Node.js SDK](https://www.openstatus.dev/docs/sdk/nodejs/overview): Interact with openstatus programmatically from your JavaScript and TypeScript applications
- [Private Location Service](https://www.openstatus.dev/docs/sdk/nodejs/private-location-service): Manage private locations — self-hosted probes that run monitors from your own network — with the openstatus Node.js SDK
- [Reference](https://www.openstatus.dev/docs/sdk/nodejs/reference): Complete reference for enums, regions, assertions, and TypeScript type exports in the openstatus Node.js SDK
- [Status Page Service](https://www.openstatus.dev/docs/sdk/nodejs/status-page-service): Manage status pages, components, groups, and subscribers with the openstatus Node.js SDK
- [Status Report Service](https://www.openstatus.dev/docs/sdk/nodejs/status-report-service): Manage incident reports and status updates with the openstatus Node.js SDK
- [TypeScript Tips](https://www.openstatus.dev/docs/sdk/nodejs/typescript-tips): Tips for working with bigint fields, oneof types, and migrating clients in the openstatus Node.js SDK
- [PHP SDK](https://www.openstatus.dev/docs/sdk/php/overview): Interact with openstatus programmatically from your PHP applications
- [Python SDK](https://www.openstatus.dev/docs/sdk/python/overview): Interact with openstatus programmatically from your Python applications
- [Create an Uptime Monitor in 5 Minutes](https://www.openstatus.dev/docs/tutorial/create-your-first-monitor): Set up your first uptime monitor with openstatus — track response time, status codes, and availability from 28 global regions.
- [Create a Status Page](https://www.openstatus.dev/docs/tutorial/create-your-first-status-page): A step-by-step tutorial to create and publish your first status page
- [Get Started with openstatus CLI](https://www.openstatus.dev/docs/tutorial/get-started-with-openstatus-cli): Step-by-step tutorial to install the openstatus CLI and export your workspace to Terraform
- [Tutorials Overview](https://www.openstatus.dev/docs/tutorial/getting-started): Step-by-step tutorials to create monitors, wire up notifications, publish status pages and reports, and drive it all from the openstatus CLI.
- [Manage Status Reports from the CLI](https://www.openstatus.dev/docs/tutorial/manage-status-reports-cli): Open, update, and resolve status reports from the terminal during an incident — the operational counterpart to managing your stack as code.
- [Wire Up Your First Notification](https://www.openstatus.dev/docs/tutorial/your-first-notification): Send your first alert from openstatus — create a notification channel, attach it to a monitor, and confirm an alert lands.
- [Publish Your First Status Report](https://www.openstatus.dev/docs/tutorial/your-first-status-report): Open, update, and resolve a status report from the openstatus dashboard — the four-state workflow your users will see during an incident.

## Guides

- [API Service Disruption Template](https://www.openstatus.dev/guides/api-service-disruption): Professional template for communicating API outages and third-party service failures to your users.
- [Best Hosted Status Page Tools in 2026](https://www.openstatus.dev/guides/best-hosted-status-page-2026): Compare the top hosted (SaaS) status page tools in 2026. We review openstatus, Atlassian Statuspage, Instatus, Betterstack, and Status.io to help you pick the right one for your team.
- [Best Incident Communication Tools in 2026](https://www.openstatus.dev/guides/best-incident-communication-tools-2026): Compare the top incident communication tools in 2026 — openstatus, incident.io, Rootly, Atlassian Statuspage, and Instatus — across internal coordination, external status pages, pricing, and team scale.
- [Best Self-Hosted Status Page Tools 2026](https://www.openstatus.dev/guides/best-opensource-status-page-2026): The self-hosted status page tools worth running on your own infrastructure in 2026 — compared on maintenance, built-in monitoring, and the real operational cost of hosting them yourself.
- [Status Pages Should Be Boring](https://www.openstatus.dev/guides/boring-is-better-for-status-pages): Your status page has one job: tell users if your service is down. Learn why the best status pages prioritize speed, reliability, and simplicity over flashy design and modern frameworks.
- [Connect Openstatus to ChatGPT (MCP Setup Guide)](https://www.openstatus.dev/guides/connect-openstatus-to-chatgpt): Add the openstatus MCP server to ChatGPT as a custom connector so the assistant can list status pages, draft incidents, and schedule maintenance from chat — sign in with OAuth, with audit-logged mutations and explicit notify semantics.
- [Connect Openstatus to Claude Code (MCP Setup Guide)](https://www.openstatus.dev/guides/connect-openstatus-to-claude-code): Wire the openstatus MCP server into Claude Code so the agent can list status pages, draft incidents, and schedule maintenance from your terminal — sign in with OAuth, no key to paste, with audit-logged mutations and explicit notify semantics.
- [Connect Openstatus to Claude Desktop (MCP Setup Guide)](https://www.openstatus.dev/guides/connect-openstatus-to-claude-desktop): Add the openstatus MCP server to Claude Desktop as a custom connector so the assistant can list status pages, draft incidents, and schedule maintenance from chat — sign in with OAuth, with audit-logged mutations and explicit notify semantics.
- [Connect Openstatus to Codex (MCP Setup Guide)](https://www.openstatus.dev/guides/connect-openstatus-to-codex): Wire the openstatus MCP server into OpenAI Codex so the agent can list status pages, draft incidents, and schedule maintenance from your terminal — sign in with OAuth, no key to paste, with audit-logged mutations and explicit notify semantics.
- [Connect Openstatus to opencode (MCP Setup Guide)](https://www.openstatus.dev/guides/connect-openstatus-to-opencode): Wire the openstatus MCP server into opencode so the agent can list status pages, draft incidents, and schedule maintenance from your terminal — sign in with OAuth, no key to paste, with audit-logged mutations and explicit notify semantics.
- [Database Performance Degradation Template](https://www.openstatus.dev/guides/database-performance-degradation): Technical template for communicating database latency and performance issues to your engineering-focused audience.
- [Deployment Rollback Template](https://www.openstatus.dev/guides/deployment-rollback): Template for communicating deployment failures and rollback procedures during service disruptions.
- [DORA Incident Reporting Requirements](https://www.openstatus.dev/guides/dora-incident-reporting-requirements): DORA's 4h/24h/72h reporting clock, how classification starts it, and the Article 19(3) duty to inform clients.
- [Error Budgets Explained](https://www.openstatus.dev/guides/error-budgets-explained): How to calculate an error budget from your SLO, what burn rate means, and what to actually do when the budget runs out. With a per-SLO downtime table.
- [Feature Degradation Template](https://www.openstatus.dev/guides/feature-degradation): Template for communicating partial service degradation where some features are impacted but the service remains available.
- [A Hosted Uptime Kuma Alternative](https://www.openstatus.dev/guides/hosted-uptime-kuma-alternative): Love Uptime Kuma but tired of running it yourself? openstatus is the open-source, managed, multi-region alternative — unlimited monitors, a status page, and no VPS to babysit. Self-host it too, if you want.
- [Status Page Pricing Compared: Atlassian, Instatus, Better Stack, Datadog & openstatus](https://www.openstatus.dev/guides/how-openstatus-compares-to-other-status-page-tools): What a status page actually costs across the major providers — list prices, per-seat charges, private-page add-ons, and what you pay separately for monitoring.
- [HTTP Headers Every Developer Should Know](https://www.openstatus.dev/guides/http-headers): A practical reference for common HTTP request and response headers, security headers, and the cloud provider-specific headers you'll encounter when monitoring APIs.
- [Incident Communication](https://www.openstatus.dev/guides/incident-communication): What to write during an outage, at which severity, and how often. The four update stages, a cadence table by severity, copy-paste templates by scenario, and the phrases that make incidents worse.
- [Incident Severity Matrix Template](https://www.openstatus.dev/guides/incident-severity-matrix): Ready-to-use templates for classifying and communicating incidents by severity level. Covers status page message templates, postmortem requirements, and real-world examples for SEV0 through SEV3.
- [ISO 27001 Incident Communication](https://www.openstatus.dev/guides/iso-27001-incident-communication): Which ISO 27001:2022 Annex A controls a status page evidences, what an auditor samples, and the far larger part it cannot cover.
- [How to Migrate from Atlassian Statuspage to openstatus](https://www.openstatus.dev/guides/migrate-from-atlassian-statuspage): Step-by-step guide to import your Atlassian Statuspage components, incidents, maintenances, and subscribers into openstatus.
- [How to Migrate from Better Stack to openstatus](https://www.openstatus.dev/guides/migrate-from-betterstack): Step-by-step guide to import your Better Stack monitors, status page, components, incidents, and maintenances into openstatus.
- [How to Migrate from Checkly to openstatus](https://www.openstatus.dev/guides/migrate-from-checkly): Step-by-step guide to import your Checkly checks as monitors, plus status pages, components, incidents, and maintenance windows into openstatus.
- [How to Migrate from Instatus to openstatus](https://www.openstatus.dev/guides/migrate-from-instatus): Step-by-step guide to import your Instatus status page, components, incidents, maintenances, and subscribers into openstatus.
- [How to Migrate from UptimeRobot to openstatus](https://www.openstatus.dev/guides/migrate-from-uptime-robot): A step-by-step guide to moving from UptimeRobot to openstatus — exporting your monitors, recreating them in the UI or as code, wiring up alerts, and publishing a status page. Most teams finish in under an hour.
- [Network Connectivity Issues Template](https://www.openstatus.dev/guides/network-connectivity-issues): Template for communicating network outages, CDN problems, and regional connectivity issues to affected users.
- [NIS2 Incident Reporting Requirements](https://www.openstatus.dev/guides/nis2-incident-reporting-requirements): NIS2 Article 23: the 24h/72h/one-month cascade to your CSIRT, and the separate duty to notify your own service recipients.
- [Public Postmortems are Underrated Marketing](https://www.openstatus.dev/guides/public-postmortem-underrated-marketing): Public incident postmortems build more trust than marketing campaigns. Learn why companies share detailed root cause analyses and how radical transparency during outages proves engineering maturity.
- [Public vs Private Status Pages](https://www.openstatus.dev/guides/public-vs-private-status-pages): Learn the key differences between public and private status pages, when to use each, and how to match transparency to your audience - customers, teams, and partners.
- [Scheduled Maintenance Template](https://www.openstatus.dev/guides/scheduled-maintenance): Proactive template for communicating planned maintenance windows, upgrades, and scheduled downtime to users.
- [Security Incident Response Template](https://www.openstatus.dev/guides/security-incident-response): Formal template for communicating security issues with professional, reassuring language that maintains user trust.
- [SLA vs SLO vs SLI Explained](https://www.openstatus.dev/guides/sla-vs-slo-vs-sli): Learn the critical differences between SLAs, SLOs, and SLIs. Understand how to measure service reliability, set internal targets, and make customer promises without over-committing or under-delivering.
- [Deliver Status Updates to Customer Slack Channels](https://www.openstatus.dev/guides/slack-status-page-subscriptions): Already share a Slack Connect channel with your enterprise customers? Route incident and maintenance updates into it, scoped to the components each customer depends on - no new channel, no integration code.
- [SOC 2 Status Page Requirements](https://www.openstatus.dev/guides/soc-2-status-page-requirements): Which SOC 2 criteria a status page can evidence, which it cannot, and the artifacts an auditor requests during Type II fieldwork.
- [Top Five Atlassian Statuspage Alternatives in 2026](https://www.openstatus.dev/guides/top-five-atlassian-statuspage-alternatives): Explore the best alternatives to Atlassian Statuspage including OpenStatus, Status-io, Datadog Status Page, Instatus, and Betterstack.
- [Top Five Instatus Alternatives in 2026](https://www.openstatus.dev/guides/top-five-instatus-alternatives): The honest guide to Instatus alternatives in 2026 — including openstatus, Atlassian Statuspage, Status.io, Datadog, and Betterstack — with pricing, monitoring depth, and who each is actually for.
- [Top Five Pingdom Alternatives in 2026](https://www.openstatus.dev/guides/top-five-pingdom-alternatives): The honest guide to Pingdom alternatives in 2026 — including openstatus, UptimeRobot, Better Stack, Checkly, and Uptime Kuma — with pricing, monitoring depth, free tiers, and who each is actually for.
- [What Is a Good Response Time?](https://www.openstatus.dev/guides/what-is-a-good-response-time): Target numbers for server response time and browser load time, why you should judge them at the 75th percentile rather than the average, and which metric to fix first when a page feels slow.
- [Status Page Terminology: Partial Outage, Degraded and Major Outage Explained](https://www.openstatus.dev/guides/what-is-a-status-page): What each status on a status page actually means — operational, degraded performance, partial outage, major outage and under maintenance — and how to choose the right one while an incident is running.
- [What Is Incident Management?](https://www.openstatus.dev/guides/what-is-incident-management): Incident management is the process teams use to detect, respond to, resolve, and learn from service disruptions. Here's the lifecycle, the roles, the severity model, and what separates teams that handle incidents well from those who don't.
- [What Is MTTR? (And the Other MTT-Whatevers)](https://www.openstatus.dev/guides/what-is-mttr): MTTR is the average time it takes to recover from an incident. But there are five different MTT- metrics that get confused regularly - including MTBF, which pairs with MTTR to give you availability. Here's what each one measures and how to move the numbers.
- [What Is Synthetic Monitoring?](https://www.openstatus.dev/guides/what-is-synthetic-monitoring): Synthetic monitoring uses scripted, automated checks to simulate user behavior against your service from external locations. Here's how it differs from real user monitoring, the types of synthetic checks, and when each is worth running.
- [What Is Uptime Monitoring?](https://www.openstatus.dev/guides/what-is-uptime-monitoring): Uptime monitoring is the practice of continuously checking whether your service is reachable and responding correctly from outside your own network. Here's how it works, how uptime percentages are actually calculated, and what to monitor.
- [Why Every SaaS Needs a Status Page](https://www.openstatus.dev/guides/why-every-saas-needs-a-status-page): Status pages aren't optional anymore. Learn why transparent service communication reduces support load, retains customers, and builds trust that marketing campaigns can't replicate.
- [Why Is My Monitor Failing? A Troubleshooting Guide](https://www.openstatus.dev/guides/why-is-my-monitor-failing): Your monitor says your site is down, but it loads fine in your browser. Here's how to tell a real outage from a false positive, the common causes, and how to fix each one.
- [Why Uptime Percentage Alone is Misleading](https://www.openstatus.dev/guides/why-uptime-percentage-is-misleading): 99.9% uptime sounds impressive until you realize it tells you nothing about user experience. What uptime and availability actually mean, why the percentage hides the real story, and what to measure instead.

## Use Cases

- [Status Page for AI Agent](https://www.openstatus.dev/use-case/agent): Let an AI agent run your status page. It receives openstatus webhooks, uses the openstatus MCP to investigate the failing monitor, files the status report, posts updates as it learns more, and resolves the report once the monitor recovers — all without waking anyone up.
- [Status Pages for API Infrastructure](https://www.openstatus.dev/use-case/api-providers): Your API consumers expect transparency. Give them a branded status page with real-time uptime data, incident history, and subscription channels — powered by monitoring from 28 regions.
- [SOC 2-Ready Status Page in 2 Minutes](https://www.openstatus.dev/use-case/compliance): SOC 2 auditors expect documented incident communication. Openstatus gives you a branded status page with incident history, subscriber notifications, and audit-ready evidence — set up in minutes.
- [Status Pages for Crypto Exchanges and DeFi Protocols](https://www.openstatus.dev/use-case/crypto): Keep your traders and users informed during outages. Monitor exchange APIs, wallet services, and blockchain nodes from 28 global regions with a branded, trustworthy status page.
- [Status Pages for Enterprise Sales](https://www.openstatus.dev/use-case/enterprise-sales): Enterprise prospects expect a status page. When their security team sends a vendor questionnaire, a branded status page with uptime history and incident communication turns a blocker into a checkbox.
- [Status Pages for Open-Source Projects](https://www.openstatus.dev/use-case/open-source): Give your open-source community a transparent view of service health. Free status page with uptime monitoring, incident history, and community-friendly subscriptions.
- [Status Pages for Reducing Support Tickets](https://www.openstatus.dev/use-case/reduce-support-tickets): Every minute of downtime floods your inbox. A status page deflects support tickets by giving users a single source of truth — with real-time incident updates and subscriber notifications.
- [Status Pages for Startups](https://www.openstatus.dev/use-case/startups): Early-stage startups need a status page before they think they do — for enterprise sales, SOC 2 audits, and SLA agreements. Openstatus gives you a branded, audit-ready status page in minutes with monitoring included.

## Comparisons

- [BetterStack vs openstatus](https://www.openstatus.dev/compare/betterstack): openstatus vs BetterStack compared side-by-side. 28 regions (parallel) vs 4 (round-robin), open-source vs closed-source, and transparent pricing with no add-on fees for status pages or subscribers.
- [Checkly vs openstatus](https://www.openstatus.dev/compare/checkly): Looking for a Checkly alternative focused on uptime monitoring and status pages? openstatus checks from 28 regions, includes public status pages, and is open source — starting free.
- [Datadog Synthetics vs openstatus](https://www.openstatus.dev/compare/datadog): Looking for a Datadog Synthetics alternative without the enterprise bill? openstatus does uptime and API monitoring from 28 regions with a built-in status page, open source, from $30/month — flat, no per-run fees.
- [Incident.io vs openstatus](https://www.openstatus.dev/compare/incidentio): Looking for an incident.io alternative that combines monitoring with status pages? openstatus detects outages from 28 regions and communicates them to users — open source and starting free.
- [Status.io vs openstatus](https://www.openstatus.dev/compare/statusio): Looking for a Status.io alternative with built-in monitoring? openstatus includes 28-region uptime checks, starts at $30/mo with unlimited team members, and is open source and self-hostable.
- [UptimeRobot vs openstatus](https://www.openstatus.dev/compare/uptime-robot): Looking for an UptimeRobot alternative that checks from 28 regions at once? openstatus is open source, includes status pages and CI/CD integration, and supports OpenTelemetry export.

## Playground

- [CDN Cache Checker](https://www.openstatus.dev/play/cdn-checker): Check if your CDN is actually caching from 28 regions worldwide. See cache HIT/MISS per region, which edge served you, and which CDN a website uses.
- [Global Speed Checker](https://www.openstatus.dev/play/checker): Free website speed test. Check your site's load time and response time from 28 regions worldwide in seconds - no signup, no install required.
- [cURL Builder](https://www.openstatus.dev/play/curl): An online curl command line builder. Generate curl commands to test your API endpoints.
- [MCP Server Health Check](https://www.openstatus.dev/play/mcp-health): Free online MCP server health check. Test JSON-RPC initialize, ping, and tools/list handshake from your browser — no install, no signup.
- [Incident Severity Matrix Builder](https://www.openstatus.dev/play/severity-matrix): Classify incidents with deterministic, auditable rules. Customize thresholds, test scenarios, and export a ready-to-use template for your runbook.
- [SLA Calculator](https://www.openstatus.dev/play/uptime-sla): Free SLA uptime calculator. Enter any target (99%, 99.9%, 99.99%) to see allowed downtime per day, month and year. Instant results, no signup.

## Pages

- [About openstatus](https://www.openstatus.dev/about): Openstatus is built by Thibault and Max — a bootstrapped, profitable two-person team building the open-source status page for teams who ship transparency.
- [Contact](https://www.openstatus.dev/contact): How to reach openstatus — support email, Discord, GitHub, a call with the founders, security disclosures, and our postal address.
- [Pricing](https://www.openstatus.dev/pricing): Start free with uptime monitoring and a status page. Upgrade to Starter ($30/mo), Pro ($100/mo), or Scale ($500/mo) for more monitors, team collaboration, and advanced features. No credit card required.
- [Privacy](https://www.openstatus.dev/privacy): The privacy conduct for openstatus
- [Component Registry](https://www.openstatus.dev/registry): Install beautiful, accessible React components for status pages. Pre-built, customizable components compatible with shadcn/ui.
- [Security](https://www.openstatus.dev/security): How openstatus protects your data, where it lives, and how to reach us if you find something.
- [Subprocessors](https://www.openstatus.dev/subprocessors): The list of subprocessors for openstatus
- [Terms of Service](https://www.openstatus.dev/terms): The terms and conditions for openstatus

## Blog

- [Our 2023 year in review.](https://www.openstatus.dev/blog/2023-year-review)
- [Openstatus 2025 Year in Review: Lessons Learned and What’s Next](https://www.openstatus.dev/blog/2026-roadmap)
- [A year of openstatus: what we learned](https://www.openstatus.dev/blog/a-year-of-openstatus-may-2026)
- [How we built an agent webhook for our status pages](https://www.openstatus.dev/blog/agent-webhook)
- [Audit humans and agents: don't leave them unobserved](https://www.openstatus.dev/blog/audit-humans-and-agents)
- [Building a CLI That Works for Humans and Machines](https://www.openstatus.dev/blog/building-cli-for-human-and-agents)
- [The React data-table I always wanted](https://www.openstatus.dev/blog/data-table-redesign)
- [Deploy private locations on a Raspberry Pi](https://www.openstatus.dev/blog/deploy-private-locations-raspberry-pi)
- [Dynamic Breadcrumb in Next.js with Parallel Routes](https://www.openstatus.dev/blog/dynamic-breadcrumb-nextjs)
- [How We Implemented Event Analytics with OpenPanel](https://www.openstatus.dev/blog/event-analytics-implementation)
- [From ClickOps to ChatOps](https://www.openstatus.dev/blog/from-clickops-to-chatops)
- [Global Latency Monitoring: Benchmarking a Hono App on Hetzner with openstatus](https://www.openstatus.dev/blog/global-latency-monitoring-benchmark-hono-hetzner)
- [Hono on Vercel: A Performance Deep Dive into Fluid Compute](https://www.openstatus.dev/blog/hono-vercel-fluid-compute)
- [How We Built our own GitHub Action](https://www.openstatus.dev/blog/how-we-build-our-github-action)
- [Migrate to openstatus from Atlassian Statuspage, Better Stack, or Instatus in Minutes](https://www.openstatus.dev/blog/import-from-statuspage-betterstack-instatus)
- [Introducing the GoaT stack](https://www.openstatus.dev/blog/introducing-goatstack)
- [Level Up Your Monitoring: Introducing the Openstatus CLI](https://www.openstatus.dev/blog/introducing-openstatus-cli)
- [Introducing: The Status Page Theme Explorer](https://www.openstatus.dev/blog/introducing-status-page-theme-explorer)
- [Live Mode](https://www.openstatus.dev/blog/live-mode-infinite-query)
- [One API to Rule Them All: Migrating from zod-openapi to ConnectRPC](https://www.openstatus.dev/blog/migrating-from-zod-openapi-to-connectrpc)
- [Why we migrated from Clerk to NextAuth (Auth.js).](https://www.openstatus.dev/blog/migration-auth-clerk-to-next-auth)
- [Why we migrated our backend from Vercel to Fly.io.](https://www.openstatus.dev/blog/migration-backend-from-vercel-to-fly)
- [Why we migrated from PlanetScale to Turso.](https://www.openstatus.dev/blog/migration-planetscale-to-turso)
- [Monitoring latency: Cloudflare Workers vs Fly vs Koyeb vs Railway vs Render](https://www.openstatus.dev/blog/monitoring-latency-cf-workers-fly-koyeb-raylway-render)
- [Monitoring latency: Vercel Serverless Function vs Vercel Edge Function](https://www.openstatus.dev/blog/monitoring-latency-vercel-edge-vs-serverless)
- [We Are So Back](https://www.openstatus.dev/blog/new-dashboard-we-are-so-back)
- [Nobody should hand-code a data table in 2026](https://www.openstatus.dev/blog/nobody-should-hand-code-a-data-table)
- [Building OpenStatus: A Deep Dive into Our Infrastructure Architecture](https://www.openstatus.dev/blog/openstatus-infra)
- [OpenStatus Light Viewer](https://www.openstatus.dev/blog/openstatus-light-viewer)
- [How We Built Our Slack Agent](https://www.openstatus.dev/blog/openstatus-slack-agent)
- [Our new pricing explained, and why pricing is hard](https://www.openstatus.dev/blog/our-new-pricing-explained)
- [Our Product Hunt Launch: The Brutal Reality](https://www.openstatus.dev/blog/our-producthunt-launch-brutal-reality)
- [Our latest pricing update: more value, cleaner numbers.](https://www.openstatus.dev/blog/pricing-update-july-2024)
- [Product Strategy - A Reality Check](https://www.openstatus.dev/blog/product-strategy-a-reality-check)
- [OpenStatus Q1 2024 Update](https://www.openstatus.dev/blog/q1-2024-update)
- [Our Journey Building OpenStatus: From Idea to Reality](https://www.openstatus.dev/blog/reflecting-1-year-building-openstatus)
- [RSS feed in your Slack channel](https://www.openstatus.dev/blog/rss-app-slack-feed)
- [Same Pricing. More Monitors.](https://www.openstatus.dev/blog/same-pricing-more-monitors)
- [How to secure your API with Unkey and Hono.js Middleware](https://www.openstatus.dev/blog/secure-api-with-unkey)
- [Self-hosting openstatus: The Hurdles Then, the Experience Now](https://www.openstatus.dev/blog/self-hosting-openstatus)
- [How We Built Our shadcn Component Registry](https://www.openstatus.dev/blog/shadcn-component-registry)
- [Status Page Add-ons](https://www.openstatus.dev/blog/status-page-addons)
- [Introducing Status Page Components](https://www.openstatus.dev/blog/status-page-components)
- [Tokenminning: a status page your agents can actually read](https://www.openstatus.dev/blog/status-page-markdown-for-agents)
- [Status Pages Are Politics](https://www.openstatus.dev/blog/status-pages-is-politics)
- [Connecting Telegram Groups Without a Webhook](https://www.openstatus.dev/blog/telegram-group-qr-integration)
- [48 hours of public OpenStatus](https://www.openstatus.dev/blog/the-first-48-hours)
- [Our plans in 2025](https://www.openstatus.dev/blog/vision-2025)
- [Your Monitoring Is Green. Your Customer Found Out First.](https://www.openstatus.dev/blog/your-customer-found-out-first)

## Changelog

- [API Key Scopes](https://www.openstatus.dev/changelog/api-key-scopes)
- [Audit Logs](https://www.openstatus.dev/changelog/audit-logs)
- [Auto Resolved Incidents](https://www.openstatus.dev/changelog/auto-resolved-incidents)
- [Binary payload](https://www.openstatus.dev/changelog/binary-payload)
- [Self-host the AI assistant with your own model](https://www.openstatus.dev/changelog/bring-your-own-ai-provider)
- [Chat Assistant](https://www.openstatus.dev/changelog/chat-assistant)
- [Run Check API](https://www.openstatus.dev/changelog/check-run-api)
- [Checker Playground](https://www.openstatus.dev/changelog/checker-playground)
- [CLI update: global check command and richer Terraform export](https://www.openstatus.dev/changelog/cli-check-terraform)
- [CLI: Import and manage monitors](https://www.openstatus.dev/changelog/cli-import-apply)
- [New CLI commands](https://www.openstatus.dev/changelog/cli-improvement)
- [CLI update: maintenance, Terraform export, and notifications](https://www.openstatus.dev/changelog/cli-maintenance-terraform-notifications)
- [CLI Monitor configuration template](https://www.openstatus.dev/changelog/cli-monitor-template)
- [CLI update: status pages and status reports](https://www.openstatus.dev/changelog/cli-skills)
- [Clone Monitor](https://www.openstatus.dev/changelog/clone-monitor)
- [cURL Builder](https://www.openstatus.dev/changelog/curl-builder-playground)
- [Dark mode support](https://www.openstatus.dev/changelog/dark-theme-support)
- [Command Menu for the Dashboard](https://www.openstatus.dev/changelog/dashboard-cmdk)
- [Dashboard Metrics Card](https://www.openstatus.dev/changelog/dashboard-metrics-card)
- [Dashboard Response Logs](https://www.openstatus.dev/changelog/dashboard-response-logs)
- [DNS Monitoring](https://www.openstatus.dev/changelog/dns-monitoring)
- [Docker Image Checker](https://www.openstatus.dev/changelog/docker-checker)
- [Follow Redirect](https://www.openstatus.dev/changelog/follow-redirect)
- [OpenStatus GitHub Actions](https://www.openstatus.dev/changelog/github-action)
- [Global Speed Checker Skill](https://www.openstatus.dev/changelog/global-speed-checker-skills)
- [Golang monitor checker](https://www.openstatus.dev/changelog/golang-monitor-checker)
- [Google Chat Notifications](https://www.openstatus.dev/changelog/google-chat-notifications)
- [Grafana OnCall Notifications](https://www.openstatus.dev/changelog/grafana-oncall-integration)
- [Grouped Monitors](https://www.openstatus.dev/changelog/grouped-monitors)
- [gRPC Monitoring](https://www.openstatus.dev/changelog/grpc-monitoring)
- [ICMP Monitoring](https://www.openstatus.dev/changelog/icmp-monitoring)
- [Invidivual Status Report Page](https://www.openstatus.dev/changelog/individual-status-report-page)
- [JSON Status Page](https://www.openstatus.dev/changelog/json-status-page)
- [Latency quantiles](https://www.openstatus.dev/changelog/latency-quantiles)
- [Maintenance status](https://www.openstatus.dev/changelog/maintenance-status)
- [OAuth for the MCP server](https://www.openstatus.dev/changelog/mcp-oauth)
- [MCP Server](https://www.openstatus.dev/changelog/mcp-server)
- [Microsoft Teams Notifications](https://www.openstatus.dev/changelog/microsoft-teams-notifications)
- [Monitor External Name](https://www.openstatus.dev/changelog/monitor-external-name)
- [Monitor Pack](https://www.openstatus.dev/changelog/monitor-pack)
- [Monitor Tags](https://www.openstatus.dev/changelog/monitor-tags)
- [Monitor Threshold](https://www.openstatus.dev/changelog/monitor-threshold)
- [More regions available 🌐](https://www.openstatus.dev/changelog/more-regions)
- [Multi-Cloud is here](https://www.openstatus.dev/changelog/multi-cloud-fly-railway-koyeb)
- [Multi regions monitoring by default](https://www.openstatus.dev/changelog/multi-region-monitoring)
- [ntfy.sh Integration](https://www.openstatus.dev/changelog/ntfy-sh-integration)
- [OpenStatus CLI](https://www.openstatus.dev/changelog/openstatus-cli)
- [openstatus PHP SDK](https://www.openstatus.dev/changelog/openstatus-sdk-php)
- [openstatus Python SDK](https://www.openstatus.dev/changelog/openstatus-sdk-python)
- [openstatus SDK](https://www.openstatus.dev/changelog/openstatus-sdk)
- [OpenTelemetry support](https://www.openstatus.dev/changelog/opentelemetry)
- [PagerDuty Integration](https://www.openstatus.dev/changelog/pagerduty-integration)
- [Password-protected status page](https://www.openstatus.dev/changelog/password-protected-status-page)
- [Speed Checker](https://www.openstatus.dev/changelog/play-checker-improvements)
- [Private Location is here (beta)](https://www.openstatus.dev/changelog/private-location)
- [Public Monitors](https://www.openstatus.dev/changelog/public-monitors)
- [Raycast Extension](https://www.openstatus.dev/changelog/raycast-integration)
- [Request assertions](https://www.openstatus.dev/changelog/request-assertions)
- [Response Time Charts](https://www.openstatus.dev/changelog/response-time-charts)
- [SAML single sign-on](https://www.openstatus.dev/changelog/saml-sso)
- [Website screenshots for incidents](https://www.openstatus.dev/changelog/screenshot-incident)
- [Slack Agent](https://www.openstatus.dev/changelog/slack-agent)
- [Slack and Discord Message Improvements](https://www.openstatus.dev/changelog/slack-discord-improvements)
- [Slack and Discord notifications](https://www.openstatus.dev/changelog/slack-discord-notification)
- [Get alerted on your cell phone](https://www.openstatus.dev/changelog/sms-notification)
- [Search Engine Indexing Control](https://www.openstatus.dev/changelog/status-page-allow-index)
- [Status Page Badge (v2)](https://www.openstatus.dev/changelog/status-page-badge-v2)
- [Status Page Badge](https://www.openstatus.dev/changelog/status-page-badge)
- [Status Page rework](https://www.openstatus.dev/changelog/status-page-colors-and-more)
- [Component Group Default Open](https://www.openstatus.dev/changelog/status-page-component-group-default-open)
- [Component Subscriptions](https://www.openstatus.dev/changelog/status-page-component-subscription)
- [Component impacts on status reports](https://www.openstatus.dev/changelog/status-page-components-impact)
- [Custom theme for status pages](https://www.openstatus.dev/changelog/status-page-custom-theme)
- [Status Page Email Authentication](https://www.openstatus.dev/changelog/status-page-email-authentification)
- [Embed your status page anywhere](https://www.openstatus.dev/changelog/status-page-embed-iframe)
- [Status Page Feeds](https://www.openstatus.dev/changelog/status-page-feed)
- [Configurable status page history](https://www.openstatus.dev/changelog/status-page-history-days-selector)
- [Status Page i18n](https://www.openstatus.dev/changelog/status-page-i18n)
- [Status Page Importer](https://www.openstatus.dev/changelog/status-page-importer)
- [Status Page IP Restriction](https://www.openstatus.dev/changelog/status-page-ip-restriction)
- [Status page monitor order](https://www.openstatus.dev/changelog/status-page-monitor-order)
- [Monitor values visibility](https://www.openstatus.dev/changelog/status-page-monitor-values-visibility)
- [Status page redesign (beta)](https://www.openstatus.dev/changelog/status-page-redesign-beta)
- [Status Page Skills for Agents](https://www.openstatus.dev/changelog/status-page-skills)
- [Slack feed subscribe on status page](https://www.openstatus.dev/changelog/status-page-slack-feed-subscribe)
- [Auto-post status updates to X and Bluesky](https://www.openstatus.dev/changelog/status-page-socials-notifier)
- [Status Page Subscribers](https://www.openstatus.dev/changelog/status-page-subscribers)
- [Status Page Unsubscribe](https://www.openstatus.dev/changelog/status-page-unsubscribe)
- [Status Page White Label](https://www.openstatus.dev/changelog/status-page-white-label)
- [Status Report location change](https://www.openstatus.dev/changelog/status-report-location-change)
- [Status Update Subscriber](https://www.openstatus.dev/changelog/status-update-subscriber)
- [Status Widget](https://www.openstatus.dev/changelog/status-widget)
- [TCP Monitoring](https://www.openstatus.dev/changelog/tcp-monitoring)
- [Team invites](https://www.openstatus.dev/changelog/team-invites)
- [Telegram Bot Integration](https://www.openstatus.dev/changelog/telegram-bot-integration)
- [Terraform Provider: status pages, notifications, and more](https://www.openstatus.dev/changelog/terraform-provider-update)
- [Terraform Provider](https://www.openstatus.dev/changelog/terraform-provider)
- [Webhook Integration](https://www.openstatus.dev/changelog/webhook-integration)
- [WhatsApp Notifications](https://www.openstatus.dev/changelog/whatsapp-notifications)

## Optional

- [API OpenAPI](https://api.openstatus.dev/openapi)
- [GitHub](https://github.com/openstatushq/openstatus)
- [SDK (JSR)](https://jsr.io/@openstatus/sdk-node)
- [Theme Store](https://themes.openstatus.dev)
- [Dashboard](https://app.openstatus.dev)