Open-source Instatus 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.

Cachet is an open-source status page system you host yourself. It gives teams a public page to show whether services are up, announce incidents and publish updates, which reduces support load when something breaks. It is built with PHP and the Laravel framework.

The project is in the middle of a rebuild: the README includes an announcement about Cachet 3.x and links to the plans, and a demo of the v3 dashboard is available that resets itself every 30 minutes. Requirements are PHP 8.3 or later, Composer and one of MariaDB, MySQL, PostgreSQL or SQLite. Documentation covers installing and upgrading, and vulnerabilities should be reported by email to the project.

Cachet's license is listed as 'Other' on GitHub, so check the repository terms. It is run on your own server and suits startups and larger organizations that want to control the hosting of their status communications instead of paying for a hosted status page service.

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.

Kener is a status page system built with SvelteKit and Node.js. It aims to give teams a simple, modern way to publish a good-looking status page with minimal effort, covering the essentials without extra complexity.

The project stresses minimal overhead, a clean interface and easy branding customization. Docker is the recommended way to run it, with published images on Docker Hub and the GitHub container registry, variants for deployment under a subpath such as /status, and a compose file for building from local source. The README warns to set a strong secret key and the public origin URL before the first start.

Kener is MIT-licensed and free. Its README is candid that it is not meant to replace large platforms like Datadog or Atlassian, but to offer a lighter option for communicating service status. The name comes from an Assamese word meaning how is it going.

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.

Vigil is an open-source status page and monitoring system you run on your own infrastructure. It watches your servers and apps, shows their health to users on a domain you choose, such as status.example.com, and notifies your team when a service goes down or recovers. It is particularly aimed at microservices setups where both backends and apps need monitoring.

Vigil can probe HTTP, TCP, SSH and ICMP targets for reachability, and applications can also report their own health through the Vigil Reporter library. Notification channels include email, Twilio SMS, Slack, Zulip, Telegram, Pushover, Gotify, XMPP, Matrix, Cisco Webex and generic webhooks. The generated status page can also carry announcements, for example to warn users about planned maintenance.

The software is written in Rust, licensed under MPL-2.0, and published as a crate on crates.io. Because you host it yourself, you control where checks run and how the public page looks, and you can place it on a separate domain from your main product. The README links a live demo on a public status page.

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.

Statping is a status page and monitoring server for websites and applications. It is aimed at teams and individuals who want a self-hosted alternative to hosted status-page services, automatically checking configured services and rendering a status page with graphs and history.

It is built in Go and ships as a single precompiled binary with no extra runtime dependencies, so it runs on Linux, macOS, Windows, or even a Raspberry Pi, and its Docker image is only about 16MB. The project recommends running the Statping instance on separate infrastructure from the services it monitors, so that a server crash does not also take down the status page. A free mobile app for iOS and Android lets users view services and receive offline notifications.

Statping supports MySQL, Postgres or SQLite as its database, and it exposes an API, a Docker image and installers for EC2, Mac, Linux and Windows. It is released under the GPL-3.0 license, with a live demo available for evaluation.

Statuspage is a command-line generator that creates a status page you can host for free on GitHub. It is aimed at teams or individuals who want a simple incident-communication page without paying for a dedicated status page service, by using a GitHub repository as both the backend and the hosting.

It uses GitHub issues to represent incidents and labels to indicate affected systems and severity levels, such as major outage, degraded performance or investigating. After generating a new repository with the statuspage CLI and a personal access token, users create issues to report problems and then run an update command the tool provides to reflect the incident on the public status page.

The README mentions the author is also alpha-testing a fully automated GitHub App version of the same idea at corestatus.io. Statuspage is installed via pip, with prebuilt binaries for macOS and Linux also available, and is released under the MIT license.

This project is a status page generator built to run entirely on Cloudflare's edge platform. It is aimed at developers who want a lightweight, serverless status page for their websites and APIs without managing a traditional backend server or database.

It periodically checks configured websites and APIs using Cloudflare Workers CRON Triggers, stores status history in Workers KV storage, and displays daily history on a public status page served from the same Worker. When a monitored site's status changes, it can send notifications to Slack, Telegram or Discord through configured webhooks.

Deployment uses a Cloudflare Workers account, optionally through GitHub Actions and a one-click Cloudflare Deploy Button, or manually by editing the project's config.yaml and wrangler.toml files. The project notes it works on both the paid Workers Bundled plan and the free Workers plan with some adjustments. It is written in JavaScript and released under the MIT license.