// the find
openstatusHQ/openstatus
🫖 Status page with uptime monitoring & API monitoring as code 🫖
OpenStatus is a self-hostable uptime monitoring and status page platform that covers HTTP, TCP, and DNS checks from 28 global regions across multiple cloud providers. It's a direct alternative to Statuspage.io or Betterstack for teams that want to own their monitoring stack. The managed SaaS exists alongside the open-source version.
The checker is written in Go with a clean separation from the TypeScript dashboard — the Go binary ships as an 8.5MB Docker image, which is the right call for something doing high-frequency network probes. Monitoring-as-code support (YAML, CLI, Terraform, GitHub Actions) means you can version-control your monitors alongside the infrastructure they watch. Private locations use gRPC (protobuf definitions are in the repo), so you're not punching holes in your firewall or trusting a cloud relay with your internal traffic. The tech stack choices are coherent: Drizzle + Turso for the DB layer keeps deployments lightweight, and Tinybird handles time-series analytics without you building a custom aggregation pipeline.
Turso (libSQL) is a significant lock-in choice — if you self-host and Turso's licensing or availability becomes a problem, migrating your monitoring history to Postgres is a real project. The dashboard pulls in the full AI chat feature (Claude-backed, with a tRPC router and session management) which is a lot of attack surface and complexity for teams that just want uptime graphs. Self-hosted setup requires Turso CLI, Bun, pnpm, and Node all at once before you can run a single app; the Docker path is better but the docs split across four separate markdown files (DOCKER.md, COOLIFY_DEPLOYMENT.md, COOLIFY_ENVIRONMENT_GUIDE.md, COOLIFY_SETUP.md) signal that nobody has consolidated the getting-started experience. AGPL-3.0 is the right license for keeping cloud providers honest, but it will block adoption in companies with legal policies against copyleft in internal tooling.