Open-source Dotcom-Monitor alternatives

Uptime Kuma is a self-hosted tool that watches whether your services are up and tells you when they are not. You run it on your own server, point it at the endpoints you care about, and it records response times, certificate details and outages in a responsive web dashboard.

Supported monitor types include HTTP(S), TCP, keyword and JSON query checks, WebSocket, ping, DNS records, push-based heartbeats, Steam game servers and Docker containers, with checks as frequent as every 20 seconds. Alerts can go to Telegram, Discord, Gotify, Slack, Pushover, email over SMTP and more than 90 other notification services. You can publish several status pages and map them to your own domains.

It is MIT licensed and mainly distributed as a Docker image, with a Docker Compose setup and a non-Docker route that uses Node.js and pm2. Extras include proxy support, two-factor authentication, multiple UI languages and ping charts. Network file systems such as NFS are not supported for its data directory.

Upptime is an uptime monitor and status page that runs entirely on GitHub Actions, GitHub Issues and GitHub Pages, so no separate server is needed. Scheduled workflow runs check your endpoints as often as every five minutes and record response times by committing the data to git.

When downtime is detected, GitHub Issues are opened and closed automatically to track incidents. A status page built with Svelte is published through GitHub Pages and displays uptime, response times and incident history. Configuration lives in a single file, and every change and event leaves an audit trail in the git history.

The project is MIT licensed and was created by Anand Chowdhary as an affordable, flexible monitor that he could control himself. It costs nothing extra for anyone already using GitHub, because there is no subscription or external server. Deleting the repository also removes the data, since all history is stored in it.

Gatus is a developer-oriented health dashboard and status page for monitoring services. Each endpoint is checked using HTTP, ICMP, TCP or DNS queries, and the result is evaluated against a list of conditions covering values such as the status code, response time, certificate expiration and response body.

Checks can be paired with alerting through Slack, Microsoft Teams, PagerDuty, Discord, Twilio and many more providers, and the documentation lists dozens of alert integrations, from email and Matrix to Opsgenie and ntfy. Configuration is done in a file, with support for external endpoints, announcements, suites in alpha, storage options, tunneling and a web UI. Incident support is part of the pitch.

Gatus is written in Go and licensed under Apache-2.0, and it is easy to deploy with Docker or in Kubernetes. The author runs it in his own cluster to watch core applications. Anyone who prefers not to run it can use the managed offering at gatus.io.

Checkmate is an open-source, self-hosted monitoring application for uptime and infrastructure. It regularly checks whether a server or website is reachable and performing well, and it presents availability, downtime and response time in real-time visualizations with alerts and reports. The repository contains both the frontend and the backend.

An optional agent called Capture collects deeper server data, including CPU, RAM, disk and temperature readings, from remote machines. Capture is written in Go and runs on Linux, Windows, macOS, Raspberry Pi or any device that can run Go. Topics in the repository also mention incident handling and status pages, and the interface uses Material UI components.

Checkmate is written in TypeScript and licensed under AGPL-3.0, and the quickest installation route requires Docker and Git. The project offers a live demo, a user's guide, and translations of the README into many languages. It is positioned as a self-hosted option for teams that currently use hosted uptime services.

Openstatus is an uptime monitoring and status page platform, open source and built around infrastructure as code. Monitors, status pages and alert channels are written in YAML or Terraform and applied through the CLI or CI, and they can also be operated by AI assistants such as Claude, ChatGPT or Cursor through an MCP server.

The platform combines status pages and monitoring in one tool. Status pages can use custom domains and password protection, schedule maintenance windows, and notify subscribers by email, RSS or webhooks. Monitoring checks servers, websites and APIs from 28 regions across three cloud providers in parallel, with alerts through Slack, Discord, PagerDuty, email and more. Incident management lets teams open and manage incidents from the dashboard or Slack, with severity, a commander and a full timeline.

Openstatus is available as a managed service or can be self-hosted under the AGPL-3.0 licence, and private locations run in a very small Docker image. The README highlights flat pricing with unlimited members, with a JSON CLI, typed API and audit log for every change. It suits engineering teams that want monitoring configured in version control.

OneUptime is an open-source monitoring and observability platform that aims to replace a shelf of separate SaaS tools. It covers uptime monitoring, status pages, on-call and alerting, incident management, logs, traces, metrics, APM and error tracking in one application, and adds AI-assisted features such as helping find the root cause and proposing a fix.

Its README maps each module to the tools it can replace: Pingdom and UptimeRobot for uptime checks across websites, APIs, ports, SSL and DNS, StatusPage.io for branded public and private status pages, PagerDuty and Opsgenie for schedules, escalation policies and SMS, call, push or Slack alerts, Incident.io for declaring and triaging incidents with post-mortems, Datadog and New Relic for traces and dashboards, Loggly for logs, and Sentry for exceptions.

The Community Edition is open source under Apache 2.0 and free to self-host, and OneUptime Cloud offers a free-forever plan with no credit card. It is written in TypeScript. It suits small and mid-sized engineering teams that want one platform for reliability work rather than integrating many vendors.

sitespeed.io is open-source software for measuring web performance. You run it against a page or a set of pages, and it drives real browsers to measure how fast they load, producing an HTML report that includes Core Web Vitals and a video recording, so you can debug a slow page or compare changes over time.

It can be installed with Docker or Node.js, supports basic and advanced configuration, and includes guidance for mobile testing. Teams run it from CI or on a schedule to monitor performance continuously and catch regressions. The repository lists metrics, performance analysis and dashboards among its topics, and the project is active on Bluesky and Mastodon with a public changelog.

sitespeed.io is written in JavaScript and licensed under MIT. It runs on your own machines or servers, so no hosted account is needed. It suits front-end developers, performance engineers and operations teams that want self-controlled performance budgets and monitoring.

Tianji is an open-source project that combines website analytics, uptime monitoring, and server status reporting in one application. The authors built it because they were running separate tools for page views, network availability, and server health, and wanted a single place for all three. It is released under the Apache-2.0 license.

On the analytics side it covers page views and visits in the style of Google Analytics or Umami, the uptime monitor checks the availability and network quality of sites, and server status data is reported from your machines. The README also describes a telemetry use: developers of self-deployable applications can collect basic information about how others install their software.

Tianji is written in TypeScript and deployed with Docker, and its topics reference Umami and Uptime Kuma as comparable tools. It suits developers, indie hosts, and small teams who want to keep analytics and monitoring data under their own control instead of relying on separate hosted products.

CheckCle is an open-source, self-hosted monitoring platform for systems, applications and infrastructure. It gives developers, sysadmins and DevOps teams real-time uptime monitoring, distributed regional checks, incident tracking and alerts in one place, and can be deployed anywhere with Docker.

Service monitoring covers HTTP, DNS, ping and TCP-based services such as FTP and SMTP, with response times and incident history for up, down, warning and paused states. It also monitors SSL certificates and domain expiry, and tracks CPU, RAM, disk and network on Linux servers and, in beta, Windows through a one-line agent script. Other features include scheduled maintenance, public status pages, reports, user management, themes and notifications through email, Telegram, Discord, Slack, Matrix and more.

CheckCle is written in Go and TypeScript, uses PocketBase, and is licensed under MIT. A live demo is linked from the README, and the interface is available in several languages. It suits small teams and homelabs looking for a self-hosted alternative to uptime and status page services.

Peekaping is a modern uptime monitoring system written in Go with a React interface. It monitors websites, APIs and other services, publishes status pages and sends alert notifications when something fails. The README positions it as an alternative to Uptime Kuma for DevOps teams that want something more automatable. It is self-hosted, with a live demo and documentation available.

The README highlights an API-first architecture in which every function is available through a REST API, making it easy to integrate with CI/CD and infrastructure-as-code tools; a community Terraform provider exists. The server is modular, so new monitor types and notification channels can be added without changing the core. Storage can be SQLite, PostgreSQL or MongoDB, and the system includes API key management and access control.

The Go server is intended to use little memory and CPU. The project is MIT licensed, and the README says it is currently in beta. Teams moving from other monitors should check the documentation for the supported monitor types and notification channels before switching.