# OpenStatus — Open-Source Monitoring and Status Page Platform

> OpenStatus is an open-source uptime monitoring and status page platform that checks endpoints from multiple regions, tracks latency and availability, and serves beautiful public status pages for your services.

## Install

Save as a script file and run:

# OpenStatus — Open-Source Monitoring and Status Page Platform

## Quick Use
```bash
git clone https://github.com/openstatusHQ/openstatus.git
cd openstatus
pnpm install
cp .env.example .env
pnpm dev
# Open http://localhost:3000
```

## Introduction
OpenStatus is an open-source synthetic monitoring and status page platform built with Next.js and Turso. It monitors HTTP endpoints from distributed global regions, measures response times and availability, and generates public status pages that keep users informed during incidents.

## What OpenStatus Does
- Monitors HTTP, TCP, and DNS endpoints at configurable intervals from 30+ global regions
- Generates public status pages with uptime graphs, incident timelines, and maintenance windows
- Sends alerts via email, Slack, Discord, PagerDuty, and webhooks when checks fail
- Tracks response time percentiles (p50, p95, p99) with historical graphs
- Provides an API for programmatic monitor management and status retrieval

## Architecture Overview
OpenStatus is built as a Next.js application using the App Router, backed by Turso (libSQL) for the database and Tinybird for analytics and time-series storage. Monitoring checks run on Cloudflare Workers deployed across global regions, sending results back to the central database. The status page is statically generated and served at the edge for fast load times worldwide.

## Self-Hosting & Configuration
- Clone the monorepo and run locally with pnpm; requires Node.js 18+ and a Turso database
- Environment variables configure database URL, Tinybird token, and notification endpoints
- Deploy to Vercel or any Node.js-compatible platform with edge function support
- Docker deployment available for self-contained setups without external platform dependencies
- Configure check regions, intervals, and alert thresholds through the web dashboard

## Key Features
- Multi-region monitoring from 30+ Cloudflare locations for accurate global availability data
- Beautiful auto-generated status pages with custom domains and branding
- Incident management with manual updates, status changes, and subscriber notifications
- Response time tracking with percentile breakdowns and trend analysis over time
- Cron-style scheduling with intervals as low as 30 seconds for critical endpoints

## Comparison with Similar Tools
- **Uptime Kuma** — Self-hosted monitoring with a rich UI; single-node checks without multi-region
- **Gatus** — Lightweight Go-based health dashboard; fewer notification integrations
- **Betteruptime** — SaaS monitoring with status pages; closed source and subscription-based
- **Cachet** — PHP-based status page; maintenance mode, lacks built-in monitoring checks
- **Instatus** — Hosted status page service; no self-host option and per-page pricing

## FAQ
**Q: Can I use my own domain for the status page?**
A: Yes. OpenStatus supports custom domains for status pages with automatic TLS via the hosting platform or a reverse proxy.

**Q: How does multi-region monitoring work?**
A: Checks run as Cloudflare Workers deployed in multiple global regions. Each region independently pings your endpoint, and results are aggregated to show per-region and overall availability.

**Q: Is there a free hosted version?**
A: OpenStatus offers a free tier on their hosted platform at openstatus.dev with limited monitors. Self-hosting removes all limits.

**Q: What database does OpenStatus use?**
A: OpenStatus uses Turso (a libSQL/SQLite fork) for its primary database and Tinybird for high-volume time-series analytics data from monitoring checks.

## Sources
- https://github.com/openstatusHQ/openstatus
- https://docs.openstatus.dev/

---
Source: https://tokrepo.com/en/workflows/ef13d2c6-3f0f-11f1-9bc6-00163e2b0d79
Author: Script Depot