openstatushq/openstatus

🫖 Status page with uptime monitoring & API monitoring as code 🫖

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 18 minutes ago
Added to GitGenius on September 7th, 2026
Created on June 19th, 2023
Open Issues & Pull Requests: 67 (-2)
GitHub issues: Enabled
Number of forks: 765
Total Stargazers: 9,074 (+0)
Total Subscribers: 31 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Issue API getrepoissuespagesummary failed: 429 Rate limit exceeded. Please try again later.

Detailed Description

Openstatus is an open-source status page and uptime monitoring platform that combines incident communication and service health tracking in a single tool.

The platform solves the problem of managing service reliability and user communication by integrating status pages with uptime monitoring. Rather than wiring separate services together, openstatus provides both capabilities in one place. It monitors servers, websites, and APIs from 28 global regions across multiple cloud providers and notifies stakeholders through Slack, Discord, PagerDuty, email, and webhooks when services degrade or fail. Status pages are customizable with support for custom domains, password protection, maintenance windows, and subscriber notifications via email and RSS.

Teams should adopt this tool if they need a unified platform for both internal monitoring and external status communication without per-seat licensing constraints. It suits organizations that want to avoid vendor lock-in through self-hosting or prefer a managed service with flat pricing and unlimited team members. The platform distinguishes itself by supporting monitoring as code through YAML configuration, CLI tools, GitHub Actions, and Terraform, allowing infrastructure teams to manage monitoring alongside their other infrastructure definitions. Private monitoring locations run in a single lightweight Docker image, making self-hosted deployments straightforward.

The project maintains active development with regular commits across the codebase and responsive engagement in its community Discord channel. The maintainers actively incorporate user feedback and feature requests, as evidenced by the breadth of integrations and deployment options supported. Documentation is comprehensive and kept current alongside feature releases. The team demonstrates commitment to the open-source model by maintaining the AGPL-3.0 license and providing clear self-hosting paths alongside the managed offering.