What Is Status Page Software?
Mix (16 tools)
- License: 6 open source · 10 proprietary
- Hosting: 4 self-hosted · 11 SaaS · 1 both
Status page software provides a public or internal web page that communicates the real-time operational status of services, infrastructure, and applications. It is the primary channel for incident communication between service providers and their users.
Status pages replace ad-hoc emails and social media posts with a structured, branded communication channel that builds trust during outages. They serve both external customers and internal teams with consistent, timely updates.
Core capabilities that define status page software:
- Component status – display operational state of individual services, APIs, regions, or infrastructure components (operational, degraded, partial outage, major outage)
- Incident updates – create and update incident timelines with investigating, identified, monitoring, and resolved states
- Scheduled maintenance – announce planned maintenance windows with start/end times and affected components
- Uptime history – show historical availability as percentage uptime and incident timeline over 30/60/90 days
- Subscriber notifications – email, SMS, webhook, Slack, and RSS notifications when status changes or incidents are created/updated
- Metrics display – show real-time or historical performance metrics (response time, latency, throughput) on the status page
- Automation – integrate with monitoring tools to automatically create incidents and update component status based on alerts
- Branding – custom domain, logo, colors, and favicon to match the organization’s identity
About this data & disclaimer
The information on these pages was researched by a combination of human review and large language models. This catalogue serves as a reference for the resources, applications, devices, deployment payloads, and other components that the ResorsIT platform integrates, deploys, and manages. To suggest an addition or correction, please contact us. Prepared by Rhodium Systems Inc., author of the ResorsIT platform — a unified IT operations management platform for IT teams and MSPs that integrates a curated suite of open-source, commercial, and SaaS applications into a single system with shared identity, single sign-on, access control, and a common audit trail. This information is compiled on a best-effort basis: it may be incomplete, contain errors, and become out of date as tools, vendors, licences, and features change. Use this catalogue only as a starting point for your own research, and independently verify and review any tool carefully against your own requirements before relying on it.
Comparison
Feature Matrix – Open Source / Self-Hosted
| Feature | Cachet | Upptime | Gatus | Statping-ng | cState | UptimeKit |
|---|---|---|---|---|---|---|
| Components | Yes | Yes | Yes | Yes | Yes | Yes |
| Manual incidents | Yes | Yes* | No | Yes | Yes** | Yes |
| Incident updates | Yes | Yes* | No | Yes | Yes** | Yes |
| Sched. maint. | Yes | No | No | No | Yes | No |
| Subscribers | No | No | No | No | Yes | |
| Built-in monitor | No | Yes | Yes | Yes | No | Yes |
| Uptime history | Yes | Yes | Yes | Yes | No | Yes |
| Metrics display | Yes | Yes | Yes | Yes | No | Yes |
| Postmortems | No | No | No | No | No | No |
| Custom branding | Yes | Yes | Limited | Yes | Yes | Yes |
* = via GitHub Issues ** = via Markdown files in Git repository
Feature Matrix – Commercial / SaaS
| Feature | Statuspage | Instatus | Sorry | BetterStack | Hyperping |
|---|---|---|---|---|---|
| Components | Yes | Yes | Yes | Yes | Yes |
| Manual incidents | Yes | Yes | Yes | Yes | Yes |
| Incident updates | Yes | Yes | Yes | Yes | Yes |
| Sched. maint. | Yes | Yes | Yes | Yes | Yes |
| Email subs | Yes | Yes | Yes | Yes | Yes |
| SMS subs | Paid | Paid | No | Yes | Paid |
| Built-in monitor | No | No | No | Yes | Yes |
| Uptime history | Yes | Yes | Yes | Yes | Yes |
| Metrics display | Yes | No | No | Yes | Yes |
| Postmortems | Yes | Yes | No | Yes | No |
| Custom branding | Yes | Yes | Yes | Yes | Yes |
| Private pages | Biz+ | Pro+ | No | Yes | Yes |
Feature Matrix – Incident Platforms
| Feature | PagerDuty SP | Rootly | incident.io | FireHydrant | StatusHub |
|---|---|---|---|---|---|
| Components | Yes | Yes | Yes | Yes | Yes |
| Manual incidents | Yes | Yes | Yes | Yes | Yes |
| Incident updates | Yes | Yes | Yes | Yes | Yes |
| Sched. maint. | Yes | Yes | Yes | Yes | Yes |
| Email subs | Yes | Yes | Yes | Yes | Yes |
| SMS subs | No* | No | No | No | Yes |
| Built-in monitor | No | No | No | No | No |
| On-call/escalation | Yes | Via PD | Via PD | Via PD | No |
| Postmortems | Yes | Yes | Yes | Yes | No |
| Runbooks | Yes | Yes | Yes | Yes | No |
| Private pages | Yes | Yes | Yes | Yes | Yes |
| Per-user pages | No | No | No | No | Yes |
* = SMS for responder alerting, not subscriber notifications
Deployment Comparison
| Tool | Type | Self-Hosted | SaaS | Tech |
|---|---|---|---|---|
| Cachet | Status page | Yes | No | PHP/Laravel |
| Upptime | Monitor+page | GitHub* | No | TypeScript |
| Gatus | Monitor+page | Yes | No | Go |
| Statping-ng | Monitor+page | Yes | No | Go |
| cState | Status page | Static | No | Hugo |
| UptimeKit | Monitor+page | Yes | No | TypeScript |
| Statuspage | Status page | No | Yes | – |
| Instatus | Status page | No | Yes | – |
| Sorry | Status page | No | Yes | – |
| BetterStack | All-in-one | No | Yes | – |
| Hyperping | Monitor+page | No | Yes | – |
| PagerDuty SP | Incident+page | No | Yes | – |
| Rootly | Incident+page | No | Yes | – |
| incident.io | Incident+page | No | Yes | – |
| FireHydrant | Incident+page | No | Yes | – |
| StatusHub | Status page | No | Yes | – |
* = GitHub Pages + GitHub Actions; not fully self-contained
Licensing Comparison
| Tool | License | Cost Model |
|---|---|---|
| Cachet | BSD-3-Clause | Free |
| Upptime | MIT | Free |
| Gatus | Apache-2.0 | Free |
| Statping-ng | GPL-3.0 | Free |
| cState | MIT | Free |
| UptimeKit | MIT | Free |
| Statuspage | Proprietary | $0–399+/mo |
| Instatus | Proprietary | $0–80+/mo |
| Sorry | Proprietary | $29–499/mo |
| BetterStack | Proprietary | $0–170+/mo |
| Hyperping | Proprietary | $0–99+/mo |
| PagerDuty SP | Proprietary | $41+/user/mo* |
| Rootly | Proprietary | $0–21+/user/mo |
| incident.io | Proprietary | $0–21+/user/mo |
| FireHydrant | Proprietary | Free–custom |
| StatusHub | Proprietary | $49–299+/mo |
* = requires PagerDuty Business plan
SSO / OIDC Comparison
OIDC is the preferred SSO protocol. The table notes each tool’s behaviour with Authentik as the IdP.
| Tool | OIDC | SAML | Authentik Notes |
|---|---|---|---|
| Cachet | No | No | Reverse proxy auth |
| Upptime | N/A | N/A | GitHub repo access |
| Gatus | Yes | No | Direct OIDC |
| Statping-ng | No | No | Reverse proxy auth |
| cState | N/A | N/A | Git repo access |
| UptimeKit | No | No | Reverse proxy auth |
| Statuspage | No | Yes* | SAML via Atlassian Access |
| Instatus | No | Ent | SAML Enterprise only |
| Sorry | No | Ent | SAML Enterprise only |
| BetterStack | No | Ent | SAML Enterprise only |
| Hyperping | No | Ent | SAML Enterprise only |
| PagerDuty SP | No | Yes | SAML via PagerDuty |
| Rootly | Ent | Ent | OIDC/SAML Enterprise |
| incident.io | Yes | Yes | Direct OIDC |
| FireHydrant | Yes | Yes | Direct OIDC |
| StatusHub | No | Ent | SAML Enterprise only |
* = requires Atlassian Access add-on
Best OIDC support: Gatus, incident.io, and FireHydrant offer native OIDC that integrates directly with Authentik. Rootly offers OIDC on Enterprise plans.
Best self-hosted SSO: Gatus is the only self-hosted tool with native OIDC support.
Monitoring Integration Comparison
| Tool | AlertManager | Prometheus | Webhook In | Built-in |
|---|---|---|---|---|
| Cachet | Via API | Community | API | No |
| Upptime | No | No | No | Yes |
| Gatus | Prom export | Yes | No | Yes |
| Statping-ng | Prom export | Yes | No | Yes |
| cState | No | No | No | No |
| UptimeKit | No | No | No | Yes |
| Statuspage | Webhook | Via tools | Yes | No |
| Instatus | Webhook | Via tools | Yes | No |
| Sorry | No | No | Webhook | No |
| BetterStack | Webhook | Import | Yes | Yes |
| Hyperping | No | No | No | Yes |
| PagerDuty SP | Via PD | Via PD | Via PD | No |
| Rootly | Webhook | Via tools | Yes | No |
| incident.io | Webhook | Via tools | Yes | No |
| FireHydrant | Webhook | Via tools | Yes | No |
| StatusHub | Webhook | Via tools | Yes | No |
Best monitoring integration: Gatus (Prometheus metrics endpoint + alerting) and tools with incoming webhooks (Statuspage, Instatus, BetterStack, incident platforms) that can receive AlertManager notifications.
Tools
16 tools.
Atlassian Statuspage
Atlassian Statuspage (formerly StatusPage.io) is the dominant status page SaaS product. Acquired by Atlassian in 2016, it is used by thousands of companies including GitHub, Twilio, Datadog, Cloudflare, and Dropbox.
License: Proprietary (proprietary) · Kind: web · Deploy: saas · SSO: OIDC, SAML
ResorsIT usage: Web App with SSO
Access & Identity: Single sign-on
BetterStack
BetterStack (formerly Better Uptime) is a modern observability platform that combines uptime monitoring, status pages, incident management, and log management into a single SaaS product.
License: Proprietary (proprietary) · Kind: web · Deploy: saas · SSO: SAML
ResorsIT usage: Web App with SSO
Access & Identity: Single sign-on
Cachet
Cachet is the original open-source status page application. Built on PHP/Laravel, it provides a full-featured status page with component management, incident tracking, metrics display, and subscriber notifications.
License: BSD-3-Clause (OSS) · Kind: web · Deploy: direct · SSO: none
ResorsIT usage: Web App without SSO
Access & Identity: Forward-auth · Vaulted credential
cState
cState is a Hugo-based open-source status page that generates a fast, static website from Markdown and YAML files. It requires no database, no backend server, and no JavaScript framework – the entire status page is pre-rendered HTML.
License: MIT (OSS) · Kind: web · Deploy: saas · SSO: none
ResorsIT usage: Web App without SSO
Access & Identity: Vaulted credential
FireHydrant
FireHydrant is an incident management platform that provides automated incident response, status pages, and reliability tracking. It focuses on the full incident lifecycle from detection through resolution and learning.
License: Proprietary (proprietary) · Kind: web · Deploy: saas · SSO: OIDC, SAML
ResorsIT usage: Web App with SSO
Access & Identity: Single sign-on
Gatus
Gatus is an open-source health dashboard and automated status page written in Go, monitoring HTTP, TCP, DNS, ICMP, and SSH endpoints from a single YAML config with many alerting integrations.
License: Apache-2.0 (OSS) · Kind: web · Deploy: direct · SSO: OIDC
ResorsIT usage: Web App with SSO
Access & Identity: Single sign-on
Hyperping
Hyperping is a lightweight SaaS uptime monitoring and status page tool. It combines HTTP/TCP/ping monitoring with a branded public status page, targeting developers and small teams who want a simple, affordable solution.
License: Proprietary (proprietary) · Kind: web · Deploy: saas · SSO: SAML
ResorsIT usage: Web App with SSO
Access & Identity: Single sign-on
incident.io
incident.io is an incident management platform built around Slack integration with a strong focus on developer experience.
License: Proprietary (proprietary) · Kind: web · Deploy: saas · SSO: OIDC, SAML
ResorsIT usage: Web App with SSO
Access & Identity: Single sign-on
Instatus
Instatus is a modern SaaS status page platform that positions itself as a faster, cheaper, and simpler alternative to Atlassian Statuspage. It emphasizes speed (static-site-like performance), generous free tier, and clean design.
License: Proprietary (proprietary) · Kind: web · Deploy: saas · SSO: SAML
ResorsIT usage: Web App with SSO
Access & Identity: Single sign-on
PagerDuty Status Page
PagerDuty Status Page is a status page module within the PagerDuty Operations Cloud, providing customer-facing and internal pages that update automatically from PagerDuty incidents and service health.
License: Proprietary (proprietary) · Kind: web · Deploy: saas · SSO: OIDC, SAML
ResorsIT usage: Web App with SSO
Access & Identity: Single sign-on
Rootly
Rootly is an incident management platform that automates incident response workflows, primarily through Slack integration. Status pages are one module within Rootly’s broader incident response platform.
License: Proprietary (proprietary) · Kind: web · Deploy: saas · SSO: OIDC, SAML
ResorsIT usage: Web App with SSO
Access & Identity: Single sign-on
Sorry (StatusPage.io)
Sorry (formerly known as Sorry, sometimes confused with StatusPage.io before Atlassian acquired that brand) is a SaaS status page and incident communication platform.
License: Proprietary (proprietary) · Kind: web · Deploy: saas · SSO: SAML
ResorsIT usage: Web App with SSO
Access & Identity: Single sign-on
Statping-ng
Statping-ng is a community fork of the original Statping (Statup) project. It provides an uptime monitoring and status page application with a web admin panel, REST API, and public status page.
License: GPL-3.0-only (OSS) · Kind: web · Deploy: direct, docker · SSO: none
ResorsIT usage: Web App without SSO
Access & Identity: Forward-auth · Vaulted credential
StatusHub
StatusHub is a dedicated status page and incident communication platform focused on IT service providers and MSPs.
License: Proprietary (proprietary) · Kind: web · Deploy: saas · SSO: SAML
ResorsIT usage: Web App with SSO
Access & Identity: Single sign-on
Upptime
Upptime is a GitHub-powered open-source uptime monitor and status page. It uses GitHub Actions as the monitoring engine, GitHub Issues for incident management, and GitHub Pages for the status page – requiring no server infrastructure at al…
License: MIT (OSS) · Kind: web · Deploy: saas, direct · SSO: none
ResorsIT usage: Web App without SSO
Access & Identity: Forward-auth · Vaulted credential
UptimeKit
UptimeKit is an open-source, self-hosted status page and uptime monitoring platform with multi-tenant orgs.
License: MIT (OSS) · Kind: web · Deploy: docker · SSO: none
ResorsIT usage: Web App without SSO
Access & Identity: Forward-auth · Vaulted credential
