With 10,400 GitHub stars, 153 contributors, and no per-monitor pricing to worry about, Checkmate delivers comprehensive infrastructure monitoring from a single self-hosted dashboard — tracking uptime, page speed, server hardware, Docker containers, and even game servers without sending a byte of telemetry off your network. Ten monitor types cover HTTP, ping, TCP, gRPC, WebSocket, DNS, SSL certificate expiry, Docker container health, Lighthouse page speed with Core Web Vitals tracking, and game server status for over 100 server types including Minecraft and CS2. The Globalping integration enables geo-distributed monitoring from six continents, running ping and HTTP checks from Africa, Asia, Europe, North America, South America, and Oceania with results plotted on an interactive map. The optional Capture agent written in Go collects CPU, RAM, disk usage, temperature, and network metrics from any Linux, Windows, Mac, or Raspberry Pi host. Public status pages ship with four built-in themes and custom branding support, showing per-service uptime bars and incident history on a single shareable URL. Alert notifications reach teams through email, Discord, Slack, PagerDuty, Microsoft Teams, Telegram, Matrix, ntfy, Twilio SMS, and webhooks. Deploy via a single Docker Compose file requiring roughly 1 GB RAM — up and running in under five minutes on any Docker host. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPLv3 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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

GlitchTip speaks Sentry's protocol without Sentry's operational weight - open-source error tracking that your existing SDKs already understand. The pitch is pragmatic: instrument your application with the official Sentry SDKs you already know - any language they cover - and point the DSN at your own GlitchTip instance instead. Errors, exceptions, log messages, and Content Security Policy violations flow into one place for triage, grouped into issues with stack traces, with alerts delivered by email or webhook the moment things break. Where self-hosted Sentry has ballooned into a docker-compose stack of twenty-plus containers, GlitchTip is a deliberately lean Django and PostgreSQL application a small team can actually run. Beyond errors, it bundles three more monitoring concerns: performance monitoring takes a works-out-of-the-box approach - no dashboard building, just your slowest web requests, database queries, and transactions surfaced automatically; uptime monitoring pings your sites and alerts on failures, or runs in reverse as a dead-man's-switch heartbeat for cron jobs that must check in on schedule; and log search puts application logs alongside errors for faster debugging. Unlimited projects and team members, MIT-licensed, built by Burke Software - your event volume is limited only by your own hardware.

Production debugging slows to a crawl when logs, distributed traces, metrics, and session replays live in four disconnected dashboards, which is why Traceway consolidates every OpenTelemetry signal into a single self-hosted observability platform. Point any standard OTLP exporter directly at the ingestion endpoints without maintaining an intermediary collector or installing proprietary vendor SDKs. When an unhandled exception fires in production, automatic SHA-256 stack trace fingerprinting groups duplicates into prioritized issues complete with source-mapped frames and attached browser or Flutter session replays showing exact user clicks before the crash. Clicking any structured log entry jumps straight to its corresponding distributed span waterfall so engineers can trace slow database queries or failing downstream HTTP calls across microservices. Route performance bottlenecks surface immediately through per-endpoint P50, P95, and P99 latency percentiles ranked by Apdex and a five-factor impact score. Teams shipping AI features can also inspect LLM token consumption, model costs, tool calls, and multi-turn conversations grouped by customer identifier. Built-in on-call rotation schedules, escalation policies, and multi-channel alerts via Slack, Telegram, Pushover, email, and webhooks ensure incidents reach the right responder with one-click acknowledgment links. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Page views, funnels, session replays, error reports, Core Web Vitals, and uptime checks share one cookieless dashboard in Betterlytics, so teams stop stitching several tools together. The overview charts visitors, page views, bounce rate, and visit duration against the previous period, and annotations mark launches or campaigns right on the timeline. Breakdowns cover referrers, channels, UTM campaigns, browsers, devices, and operating systems, with visitor locations on a world map once an optional MaxMind key is added. Custom events, global properties such as plan or app version, and outbound link tracking show what visitors actually do, while user journey diagrams and funnels reveal where they drift away. Session replay is opt-in per tracking script, masks text and form inputs by default, and can keep recordings in your own S3-compatible bucket. Error tracking groups JavaScript errors with stack traces, a session trail, and a link to the matching replay. Uptime and SSL monitors alert through Slack, Discord, Teams, or webhooks and feed public status pages on your own domain. Teammates join by invitation, two-factor login is available, and a built-in MCP server lets Claude, Cursor, or Codex answer traffic questions. A script of about 3.5 KB or a WordPress plugin handles installation. 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.

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.

Monitoring everything from network switches to Kubernetes clusters since 2001 with over 6,200 GitHub stars and deployments exceeding 100,000 devices per installation, Zabbix has established itself as one of the most mature and feature-rich open-source monitoring platforms available, trusted by organizations including Dell, Salesforce, ICANN, and T-Mobile. The platform collects metrics from virtually any source using Zabbix Agent written in C, Zabbix Agent 2 written in Go with native plugin support, SNMP v1/v2c/v3 polling and trapping, IPMI for hardware health, JMX for Java applications, SSH and Telnet checks, HTTP/HTTPS polling, and ODBC database queries. Version 7.0 LTS introduced synthetic browser monitoring that executes user-defined JavaScript via WebDriver to simulate multi-step user interactions on websites, proxy load balancing with automatic host redistribution across proxy groups for high availability, in-memory proxy data buffering delivering up to 100x performance improvement, native multi-factor authentication with TOTP and Duo support, and just-in-time user provisioning from SAML and LDAP. Low-level discovery automatically detects file systems, network interfaces, SNMP OIDs, VMware resources, and Kubernetes pods, creating monitoring items and triggers dynamically. The alerting engine correlates events with configurable escalation chains, sending notifications through Slack, Microsoft Teams, PagerDuty, Jira, email, and SMS with customizable message templates. Over 1,000 official templates provide instant monitoring for Linux, Windows, VMware, AWS, Azure, Docker, PostgreSQL, MySQL, Apache, Nginx, and hundreds more. 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.