Better Status Page watches your services around the clock and turns outages into calm, branded status updates for your users instead of a flood of support tickets. Its monitors probe HTTPS endpoints with authentication flows and TLS expiry warnings, ping and TCP ports, DNS records, Docker containers, mail servers over SMTP, IMAP, and POP3, and databases from PostgreSQL and MySQL to Redis, MongoDB, SQL Server, and Oracle. A slower-than-usual alert fires when a monitor's p95 response time climbs against its own last seven days, and passive webhook heartbeats catch jobs that simply stop checking in. Alerts reach the team through email, Slack, Discord, Microsoft Teams, Telegram, ntfy, Pushover, webhooks, and Twilio SMS or voice calls, with failure thresholds, quiet hours, rate caps, and grouping keeping the noise down. Incidents carry severity levels, public updates, linked monitors, and recurring maintenance windows, and subscribers follow along by email, webhook, RSS or Atom feed, or a JSON status API. A drag-and-drop builder restyles the public page with your branding, dark mode, and translations, a static fallback keeps the page readable if the server itself falls over, and uptime reports export to CSV for SLA reviews. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

When a service you run goes down at 3 a.m., Upstat is the watcher that notices first and writes it down. Add any HTTP or HTTPS endpoint and it checks in every sixty seconds, building a living record of uptime, response latency, and ping times that you can read at a glance from status and latency charts. Certificate details sit alongside each monitor, so an expiring TLS certificate stops being a surprise outage waiting for a date. Each monitor can appear on public status pages, and you can run several of them, mapping different pages to different domains so customers, clients, or separate products each get their own honest view of what is up. When a check fails, a Discord notification heads to your channel with the news, and the dashboard keeps the incident in its history instead of letting it vanish into a chat scrollback. Install it as a progressive web app, keep its data in SQLite for a one-file setup or PostgreSQL when the deployment grows, and the whole thing stays on infrastructure you control. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

With 7,400+ GitHub stars and a feature set that replaces seven separate SaaS subscriptions — Pingdom for monitoring, StatusPage.io for status pages, PagerDuty for on-call, Incident.io for incident management, Datadog for APM, Loggly for logs, and Sentry for error tracking — OneUptime delivers every tool your reliability team needs in a single open-source platform that is genuinely 100% open source under Apache 2.0 (not open-core). Uptime monitoring runs synthetic checks against websites, APIs, ports, SSL certificates, and DNS records from distributed global probes with configurable intervals and thresholds. Branded status pages publish automatically when monitors detect issues, notifying subscribers via email, SMS, webhook, or RSS without manual intervention during an outage. On-call scheduling routes alerts through escalation policies to the right engineer via phone call, SMS, push notification, Slack, or Microsoft Teams. The incident management workflow handles declaration, triage, communication, resolution, and post-mortem generation in a unified timeline. APM collects traces and metrics via native OpenTelemetry integration — no proprietary agents required — while log management provides full-text search and alerting. An AI agent continuously monitors telemetry data, identifies root causes, and opens GitHub pull requests with proposed fixes for review. Deploy via Docker Compose or Kubernetes Helm charts with a Terraform provider for infrastructure-as-code configuration. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

Trusted by Cal.com, WhiteBIT, and Documenso and backed by 8,800+ GitHub stars, OpenStatus delivers the open-source status page and uptime monitoring platform that replaces Atlassian Statuspage, Better Stack, and Instatus with a single self-hosted deployment. The monitoring engine runs Go-based probes across 28 global regions on three cloud providers checking HTTP, TCP, and DNS endpoints in parallel with configurable intervals and multi-region consensus to eliminate false-positive alerts. Status pages ship with custom domain support, password and email-domain access controls, maintenance windows, grouped monitor components, and subscriber notifications via email and RSS. Incident management provides structured status reports with investigating, identified, monitoring, and resolved timeline phases that publish automatically to affected status pages. The monitoring-as-code workflow supports YAML configuration synced through the CLI, a GitHub Actions integration for CI/CD pipelines, and a Terraform provider for infrastructure-as-code deployments. The typed ConnectRPC JSON-over-HTTP API exposes a published OpenAPI specification with a Node SDK for programmatic access, while an MCP server connects AI assistants like Claude, ChatGPT, and Cursor directly to workspace data. The tech stack combines Next.js with shadcn/ui for the dashboard, Hono for the API server, Drizzle ORM over Turso for application data, and Tinybird for analytics. Private monitoring locations deploy as a single 8.5MB Docker image behind firewalls to check internal services. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.

Uptime checks, a customer-facing status page, and on-call paging arrive in one self-hosted package, so a failing check can open an incident, page the right person, and update the public page without a second tool. Monitors cover HTTP, TCP, ICMP ping, DNS, TLS certificate expiry, domain expiry, cron heartbeats, and scripted browser login flows with per-step timings. Probe agents run in any region you choose, and the dashboard shows latency by region. Incidents open on failure and close on recovery, with acknowledgement to silence paging and reminders per monitor. Escalation policies page channels and schedules level by level, and layered on-call rotations support daily, weekly, or custom shifts, calendar overrides, and an iCalendar feed. Alerts reach Slack, Discord, Teams, Telegram, PagerDuty, SMS, WhatsApp, ntfy, Gotify, email, and webhooks. The public status page shows 90 days of uptime per component, maintenance windows, incident updates, and RSS, JSON, and email subscriptions. Everything can be driven by REST API, scoped tokens, a Terraform provider, or an MCP server for AI assistants. Self-hosted installs have no monitor limits and no plan to buy. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.

Keep users ahead of outages by consolidating infrastructure monitoring into Peekaping, a unified uptime monitoring and incident communication platform that alerts engineering teams to network and application failures before customers experience disruptions. Users can configure automated synthetic checks across HTTP endpoints, database engines, message queues, and container runtimes to verify response latency, payload integrity, and SSL certificate expiration. When performance thresholds degrade or connections drop, the platform broadcasts structured incident notices across twenty-two notification channels including Slack, Discord, Telegram, PagerDuty, and custom webhooks. Visual dashboards display live heartbeat timelines, historical latency percentiles, and rolling availability scores for each monitored endpoint. System administrators can assemble custom public status pages with custom domains, branded color schemes, and component grouping to inform external stakeholders during planned maintenance or unforeseen service degradations. Teams can schedule recurring maintenance windows to pause alert notifications during routine deployments and generate API tokens to automate monitor creation directly from CI/CD deployment pipelines. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Sixty-thousand-plus GitHub stars make Uptime Kuma the most popular self-hosted monitoring tool - MIT-licensed, Node.js, and the standard replacement for UptimeRobot, Pingdom, and Freshping. It watches a dozen monitor types: HTTP(S) endpoints with keyword and JSON-query content validation, TCP ports, ICMP ping, DNS records, WebSockets, Docker containers via the socket, Steam game servers, MQTT brokers, gRPC services, and push-based heartbeats for cron jobs and internal workers. Checks run at intervals as tight as 20 seconds - versus UptimeRobot's 5-minute free tier - with unlimited monitors and unlimited data retention. When something fails, alerts fan out through 90+ notification channels: Slack, Discord, Telegram, email with LiquidJS templating, PagerDuty, OpsGenie, ntfy, Gotify, Matrix, and dozens more via native providers plus the Apprise library. Unlimited public or password-protected status pages - mappable to specific domains and organized into monitor groups - communicate health to customers, with maintenance windows that suppress alerts during planned work. The reactive dashboard graphs response times, tracks SSL certificate expiry with advance warnings, supports proxies and 2FA, and ships in dozens of languages. One Docker container with a SQLite volume covers an entire infrastructure.

Continuous infrastructure monitoring meets automated SSL expiration tracking in Kuvasz, a self-hosted uptime platform that alerts DevOps teams before outages disrupt production operations. Operators can configure granular health checks across HTTP endpoints, ICMP ping targets, and raw TCP ports with custom polling intervals down to seconds. Automated SSL inspectors track certificate validity, issuing early warning notices before cryptographic chains expire and disrupt production traffic. A push monitoring system receives incoming heartbeat signals from background cron jobs, database backups, and recurring automation scripts, triggering alerts whenever expected pings fail to arrive on schedule. Multi-channel dispatchers route incident notifications through Slack, Discord, Telegram, Microsoft Teams, PagerDuty, and custom webhook payloads with adjustable failure count thresholds to eliminate transient false alarms. Maintenance windows let teams schedule planned downtime through one-off intervals or recurring cron expressions, automatically muting notifications during deployment cycles. Public and private status pages publish categorized system health metrics, historical latency charts, and incident timelines to keep internal stakeholders and end users informed. An integrated Model Context Protocol server allows AI assistants to query monitoring states and toggle checks directly via conversational interfaces. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.

Lunalytics keeps watch over your websites, APIs, servers, and Docker containers, alerts your team the moment something goes down, and gives customers a branded status page to check instead of emailing you. Checks run over HTTP(S), TCP, ping, JSON query, push heartbeat, and Docker container status. Each monitor charts response time for the latest checks, one day, one week, or one month, next to uptime percentages and a certificate expiry countdown. Set a parent on a check and its dependents stop alerting when the parent is already down. The status page builder offers a block-based layout editor, custom colors, fonts, logos, favicons, and light or dark themes. Incident updates carry a timestamp and an impact level like Major Outage. Notifications reach Discord, Slack, Telegram, Pushover, Home Assistant, SMTP email, and webhooks with editable JSON payloads, and Apprise adds more than 100 further services. Teams get role-based access control, single sign-on through Authentik, Authelia, Keycloak, Discord, Google, GitHub, Slack, or Twitch, and personal API keys for scripting. Each user can pick a theme, accent color, time format, and timezone. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.

A polished public status page without Statuspage prices or a heavyweight observability suite: Kener is a status and uptime monitoring system built with SvelteKit and Node.js. It runs 11 monitor types - API, Ping, TCP, DNS, SSL certificate, SQL query, Heartbeat, gRPC, and GameDig game-server checks among them - each with configurable intervals and thresholds. Incident management covers the full lifecycle: structured timelines from investigation through resolution, acknowledgements, and subscriber-visible updates, plus maintenance windows with RRULE-based recurring schedules and automatic status transitions. Notifications reach email, Slack, Discord, and custom webhooks through trigger-based workflows with template-driven messaging. One instance can serve multiple branded status pages - per product, team, or region - with custom logos, colors, and CSS, localization into 21 languages, timezone-aware displays, and server-rendered pages that stay fast and SEO-friendly. Operations tooling includes role-based access for teams, API key management, a secrets vault, analytics integrations (Google Analytics, Plausible, Umami, and others), and a REST API with 17+ endpoints for automating incidents and monitors from CI/CD. MIT-licensed; Docker deployment with Redis, SQLite by default, PostgreSQL or MySQL for production.

CheckCle provides a complete uptime monitoring and infrastructure observability platform that deploys with a single Docker container and stores all data in embedded SQLite via PocketBase. The Go backend runs three microservices — a service operation engine handling HTTP, HTTPS, DNS, Ping, and TCP checks at configurable intervals, a distributed regional check agent for multi-location network testing, and a server monitoring agent collecting CPU, RAM, disk usage, and network metrics via gRPC. The React frontend built with Vite, TypeScript, Tailwind CSS, and shadcn-ui subscribes to PocketBase WebSocket endpoints for real-time dashboard updates without polling. SSL and domain monitoring tracks certificate issuers, expiration dates, days remaining, and validation status. The incident management system records UP, DOWN, WARNING, and PAUSE states with full history, while scheduled maintenance windows prevent false alerts during planned downtime. Public status pages provide external stakeholders with live service health information. Health heatmaps visualize uptime performance and outage patterns over time. Notification channels include email, Telegram, Discord, and Slack, with multiple alert targets per monitored service. The one-click agent installation script supports Debian, Ubuntu, CentOS, Red Hat, Alpine, and Windows in beta. Docker deployment runs on port 8090 with a single persistent volume at /mnt/pb_data, requiring minimum 1 vCPU and 500MB RAM. On RepoCloud, deploy CheckCle on a dedicated VPS with root SSH access, persistent storage for your monitoring database, and complete control over agent endpoints and notification configurations, all under the MIT license.

A status page and uptime monitor in one Go binary: Statping-ng - the actively maintained fork of Statping - replaces the UptimeRobot-plus-Statuspage combo with a ~20 MB Docker image using under 50 MB of RAM. It checks services over HTTP, TCP, UDP, ICMP ping, and gRPC health checks on configurable intervals, with per-service timeouts, expected status codes, POST requests with custom JSON bodies, SSL verification, and failure thresholds before alerting. The public status page is the differentiator against plain monitors: visitors see live status, uptime percentages, and latency charts grouped into service categories, with incident announcements and scheduled-maintenance messages you publish from the dashboard - and Sass-based custom styling matches the page to your brand rather than a vendor template. When something fails, notifiers fire immediately: Slack, Discord, Telegram, SMTP email, PagerDuty, Twilio SMS, Pushover, and custom webhooks, each testable before saving. Because notifiers are single Go files, the plugin system makes new channels straightforward. A RESTful API manages services and reads uptime data programmatically, and the free Statping mobile app connects to your server via QR code for on-the-go monitoring. Data persists to SQLite, MySQL, or PostgreSQL. Point it at internal services too - anything the container can reach is monitorable.

Monitor watches your servers the way a status page should: second by second, from one small binary you run yourself. A lightweight Linux agent on each machine reports CPU, memory, disks, network throughput, connections, and processes to your hub over a persistent connection, and the hub pushes a fresh snapshot to your browser every two seconds. History is kept for charting, so node pages show how load, traffic, and latency behaved over days. Ping tasks run from the hub's side too: define targets once and every agent measures latency to them on its own interval, drawing the curves next to the machine metrics. The public face is a status page you can reskin without touching the server: themes install from the panel, run as static pages against a small public API, and anonymous visitors see only the nodes you marked public, with addresses and hostnames stripped out. Node management stays practical: registration windows hand out tokens safely, installing an agent is one command, and replacing a token disconnects the old connection immediately. When a node goes offline, crosses its traffic allowance, approaches expiry, or someone signs in, alerts go out through Telegram or any webhook. The hub listens only on localhost behind your HTTPS proxy, signs in by password or GitHub OAuth allowlist, and lists revocable sessions. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

With 11,400+ GitHub stars and active development since 2019, Gatus is the developer-oriented status page and health monitoring tool that ships as a single statically-linked Go binary in a scratch Docker image under 20 MB — deploying in seconds while monitoring your entire infrastructure across 12 protocols from a single YAML configuration file. Define health checks for HTTP, ICMP, TCP, DNS, gRPC, WebSocket, SSH, UDP, SCTP, STARTTLS, and TLS endpoints with conditions that go far beyond simple ping: evaluate response status codes, body content with JSONPath expressions, response time thresholds, certificate expiration days, DNS record values, and IP address ranges. Each endpoint supports independent alerting through Slack, Microsoft Teams, PagerDuty, Discord, Telegram, Twilio, Mattermost, Google Chat, email, Gotify, Pushover, and custom webhook providers with configurable failure thresholds and descriptions. The built-in status page displays uptime badges, response time graphs, and incident timelines with maintenance window support for planned downtime communication. External endpoints accept push-based health reports from services behind firewalls. Prometheus metrics export via the /metrics endpoint enables integration with existing observability stacks. OIDC and Basic Authentication protect the dashboard. PostgreSQL persistence stores historical uptime data. The official Helm chart supports Kubernetes deployment with liveness probes and PVC storage, while a community sidecar auto-generates endpoint configurations from Kubernetes Ingress and HTTPRoute resources. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache 2.0 licensed.

Vigil monitors your entire distributed infrastructure and generates a public status page from a single Rust binary small enough to run on a Raspberry Pi, consuming minimal CPU and memory while providing crash-free reliability. Four distinct monitoring modes cover every topology: poll probes check HTTP, TCP, SSH, and ICMP endpoints for reachability with configurable intervals and thresholds; push probes receive health reports from Vigil Reporter libraries embedded in your application code across Node.js, Python, Golang, Rust, TypeScript, Dart, and C#; local probes delegate monitoring to Vigil Local slave daemons running behind firewalls on separate LANs; and script probes execute custom shell commands for specialized health checks. Each monitored service transitions through healthy, sick, and dead states based on consecutive probe failures, with configurable thresholds controlling state transition sensitivity. When services change state, Vigil dispatches notifications through twelve alert channels including Slack, Email, Twilio SMS, Telegram, Pushover, Gotify, XMPP, Matrix, Zulip, Cisco Webex, and generic webhooks. The generated status page displays service groups organized by category with real-time replica status, system load metrics from reporter probes, and a maintenance announcement system for communicating planned downtime through the Manager HTTP API. Configuration uses a single TOML file defining all probes, services, and notification channels with no database dependency. Docker deployment pulls the official image with volume-mounted configuration. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MPL-2.0 licensed.

Website analytics, uptime monitoring, and server status - three tools most teams run separately - combined in Tianji, an open-source observability platform. The analytics layer tracks page views, unique visitors, referrers, and UTM parameters with a lightweight cookie-less script, which keeps collection GDPR and CCPA friendly. The uptime monitor checks availability and latency on configurable intervals, accepts passively reported results, and publishes public status pages for incident communication. Server status agents report CPU, memory, disk, and network metrics with threshold-based alerts, and notifications route through webhooks, Slack, Telegram, and other channels with noise control. It also includes anonymous telemetry for tracking deployments of your own open-source projects, surveys, waitlists, team collaboration, and an OpenAPI interface for integrations and exports. The consolidation is the point: traffic analytics, uptime checks, and server metrics share one interface and one alerting layer, so diagnosing an incident does not mean hopping between Google Analytics, Uptime Kuma, and Prometheus - and the built-in public status pages replace a separate paid Statuspage-style subscription. Because collection uses no cookies with IP truncation and aggregation by default, basic traffic measurement requires no consent banner. Built in TypeScript under the Apache 2.0 license and inspired by Umami and Uptime Kuma, it is deliberately right-sized for independent developers and small SaaS teams whose monitoring needs are real but lightweight.

Browser tests, load tests, uptime checks, public status pages, and an AI incident investigator all live in one self-hosted dashboard called Supercheck. Write browser, API, database, custom, and k6 performance tests in a built-in code editor, or record a flow with the Chrome and Edge Recorder extension and save it as a Playwright script. Group tests into scheduled jobs, trigger them from CI with trigger keys, and review run logs, screenshots, traces, and reports. Five monitor types cover HTTP endpoints, website SSL expiry, ping, TCP and UDP ports, and scheduled synthetic browser journeys, with administrator-defined check locations and alerts to email, Slack, Discord, Telegram, Microsoft Teams, or webhooks. Status pages publish component health with 90-day uptime, incidents, scheduled maintenance, badges, and subscriber notifications under a subdomain or custom domain. When something breaks, the incident workspace collects evidence, drafts an evidence brief, and runs a read-only AI investigation across connectors such as GitHub, Prometheus, Grafana, and Kubernetes, while Copilot answers questions about that evidence. Requirements link expectations to tests and show coverage, and AI can extract them from a PRD. Organizations, projects, six roles, API keys, and audit trails keep teams in their lanes, and the CLI pulls, diffs, and deploys resources as code. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.

A single binary watches everything you care about and only bothers you when something breaks. EaseProbe is an open-source health and status checker that probes websites over HTTP, TCP ports, ping, TLS certificates, shell commands, SSH hosts, and native clients for MySQL, PostgreSQL, Redis, MongoDB, Kafka, Memcache, and ZooKeeper. Each target gets an interval, timeout, retry checks, and data validation, from HTTP status and XPath evaluation to a Redis key matching an expected value; SSH host probes also watch CPU, memory, and disk so slow saturation gets caught alongside hard failures. When a target flips state, edge-triggered notifications fan out to Slack, Discord, Telegram, Microsoft Teams, email, AWS SNS, WeCom, DingTalk, Lark, SMS providers, log files, syslog, or your own shell script, with repeat alerts and quiet recovery behavior under your control. Availability history accumulates into daily, weekly, or monthly SLA reports delivered through those same channels, plus a live SLA page and JSON endpoint served by the probe itself. Everything it measures also exits as Prometheus metrics with per-target status, latency, and uptime, ready for Grafana dashboards and alerting rules alongside the rest of your stack. Configuration is one YAML file, persistence is one local data file, and the same binary runs on a tiny VPS watching an entire fleet. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

With 10,100+ GitHub stars and 75 releases over a decade of continuous development, Healthchecks is the open-source cron job monitoring service that catches failures your other monitoring tools miss — the jobs that silently stop running, the backups that never completed, the nightly reports that disappeared without error. The dead man's switch architecture requires zero agent installation: your cron jobs, scripts, and services ping a unique URL via HTTP request or email, and Healthchecks alerts you only when a ping does not arrive within the configured Period and Grace Time window. Each check supports cron expression scheduling, optional start, success, and failure signals for measuring execution time, and HTTP body keyword filtering for intelligent alert routing. Twenty-five notification integrations cover every channel teams actually use: Slack, Discord, Microsoft Teams, PagerDuty, Opsgenie, Splunk On-Call, Telegram, Signal, WhatsApp, SMS, email, webhooks, GitHub Issues, Pushover, ntfy, Gotify, Matrix, Mattermost, Zulip, Pushbullet, PagerTree, Spike.sh, and Trello. The web dashboard provides a visual grid showing real-time status with color-coded badges and per-check integration toggles. Monthly, weekly, and daily email reports summarize uptime trends with checks sorted by downtime duration. Team management supports projects with member roles and read-only access. Prometheus metrics expose check health and grace state for Grafana dashboards. WebAuthn and TOTP two-factor authentication secure accounts. Deploy via Docker images available for amd64, arm/v7, and arm64 architectures. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. BSD 3-Clause licensed.

Aurora is an open-source AI SRE agent that investigates production incidents on its own, turning each incoming alert into a structured root cause analysis with evidence and a suggested fix. Alerts arrive from PagerDuty, Datadog, Grafana, New Relic, OpsGenie, incident.io, or CloudWatch, and every one triggers a background investigation without waiting for a human to pick it up. The agents choose from more than thirty tools, run cloud and cluster commands inside sandboxed pods, query logs, compare deployments, and search a knowledge base of past incidents for similar failures. An infrastructure dependency graph shows the blast radius across services and providers. When the root cause is found in code, Aurora can draft the remediation as a pull request instead of stopping at a diagnosis. Finished investigations become postmortems with a timeline, impact assessment, and remediation steps, exportable to Confluence, Notion, or SharePoint, and automated actions can open the fix, notify Slack, or update living documents as new evidence lands. Command policies and guardrails bound what the agents may run, and any major language model provider can power the reasoning, cloud-hosted or local. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.