OpenStatus is an open-source status page and uptime monitoring platform designed for engineering teams who want to communicate incidents transparently and automate monitoring as part of their infrastructure-as-code workflow. It solves the problem of reactive user communication during outages by providing automated, audit-ready status pages and global synthetic monitoring that updates in real time.
Built with Next.js, Hono, and Turso, OpenStatus supports both managed SaaS and self-hosted deployments via Docker or Coolify. It integrates with 28 global monitoring locations across AWS, GCP, and Azure, and uses Drizzle ORM for database operations, Tinybird for analytics, and shadcn/ui for component-driven UIs. The platform is designed to be version-controlled, API-accessible, and SOC 2 compliant out of the box.
What You Get
- Branded Status Pages - Customizable, themeable status pages with password protection, custom domains, and support for status reports and maintenance windows to communicate incidents proactively.
- Global Synthetic Monitoring - Monitor HTTP endpoints, REST, and GraphQL APIs from 28 regions across AWS, GCP, and Azure to detect outages before users do.
- Monitoring as Code - Define and version your monitors using YAML files, enabling integration with CI/CD pipelines and infrastructure automation tools like Terraform.
- Multi-Channel Alerts - Receive incident alerts via Slack, Discord, PagerDuty, email, and webhooks with automatic status page updates upon detection.
- Audit-Ready Incident History - Every status update and incident is timestamped and logged automatically, satisfying SOC 2 CC2.3 compliance requirements without manual documentation.
- Self-Hostable Architecture - Deploy via Docker, Coolify, or manually using Bun, Turso, and Drizzle ORM with pre-built images for server, dashboard, checker, and status-page components.
Common Use Cases
- Running a public-facing SaaS status page - A SaaS company uses OpenStatus to host status.yourcompany.com with custom branding, showing real-time uptime and incident history to customers during outages.
- SOC 2 compliance automation - A compliance team deploys OpenStatus to automatically generate timestamped incident reports and subscriber logs required for SOC 2 audits without manual record-keeping.
- Monitoring internal APIs behind firewalls - A DevOps team uses the Docker-based private location to monitor internal microservices from within their VPC and push status updates to a public-facing page.
- Engineering teams managing monitoring as code - A team version-controls their 50+ HTTP endpoints in YAML, deploys them via GitHub Actions, and receives alerts on Slack when latency spikes or endpoints fail.
Under The Hood
Architecture
- Monorepo structure with Turbo orchestrating clearly separated workspaces for API, database, and notification systems, enforcing strict domain boundaries
- Domain-driven design with isolated layers for data access, HTTP endpoints, and alerting integrations, preventing cross-layer contamination
- Microservice-style deployment via Docker Compose with independent health checks and environment isolation for checker, server, and private-location services
- Event-driven orchestration using QStash and Redis to decouple health checks from ingestion pipelines, enabling scalable and resilient workflows
- Dependency injection achieved through workspace links and environment variables, avoiding runtime containers while maintaining configurability
Tech Stack
- Next.js 16+ with React 19 powering both dashboard and public status pages using server components and API routes
- TypeScript-first codebase with Biome and Oxlint enforcing strict type safety and consistent formatting across all packages
- Prisma and LibSQL as the primary data layer, managed via Bun and Dockerized migration workflows
- Turbo and pnpm coordinating builds and dependency management across the monorepo
- Go-based microservices handling background checks and ingestion, deployed via Docker and GitHub Packages
- Infrastructure-as-code using Docker Compose and Coolify-compatible YAML, supporting self-hosted deployments with optional integrations
Code Quality
- Extensive test coverage for HTTP APIs, RPC endpoints, and third-party integrations with comprehensive validation of schemas and authentication
- Zod-based schemas ensure runtime correctness of requests and responses, reducing malformed payload issues
- Mock-driven testing isolates external dependencies like databases and HTTP clients, enabling deterministic unit and integration tests
- Clear separation of concerns with dedicated test files per service, validating edge cases like invalid auth and malformed inputs
- Robust error handling returns structured, user-friendly responses with appropriate HTTP status codes instead of unhandled exceptions
- Comprehensive mocking and fixture-based testing for external providers ensures realistic validation of import and sync workflows
What Makes It Unique
- Native white-labeling for status pages allows full brand customization without external attribution
- Unified monitoring API supports HTTP, TCP, and DNS checks through a single endpoint with regional health probes
- Deep Next.js App Router integration enables server-side prefetching and zero-flash rendering with full SEO support
- Custom UI component library ensures visual consistency across dashboard and public status pages
- Real-time status updates via server components and TRPC subscriptions eliminate polling and third-party WebSocket dependencies
- Dynamic theme system with dark/light mode and workspace-aware UI states that persist across user sessions and embedded status pages