Gatus

github.com ↗

Define endpoint health checks and alert conditions in a lightweight self-hosted status dashboard.

SI Score
80/100
Pricing
Open Source AI reading, not confirmed
Free plan
Not confirmed
Sign-up required
Not confirmed

Ask SI about Gatus

Answers use saved listing facts and recorded sources.
Homepage screenshot
Screenshot of the Gatus homepage

What it does

Gatus is a developer-oriented health dashboard for monitoring services over HTTP, ICMP, TCP, and DNS. A YAML configuration defines endpoints and conditions for status codes, response time, certificate expiration, or response bodies; checks can be paired with notifications such as Slack, Teams, PagerDuty, Discord, and Twilio. The self-hosted project is Apache-2.0 licensed.

The official repository README shows a configuration file at config/config.yaml and a YAML example with a named URL, check interval, and conditions. A first endpoint might require a 200 response and a response time below a chosen threshold; add a body check when the service exposes a health document. The README also provides a Docker example that publishes the dashboard on port 8080. These are illustrative setup details from the README, not commands run for this record.

Gatus is useful when the question is whether a set of endpoints still meets explicit health conditions. It reports check results and can alert on failures, but it is not a general system-metrics, log, or trace analysis platform. The repository README links Gatus.io as a managed option; that site's fetched page contained only its title, so this entry covers the self-hosted project and makes no claim about hosted pricing or behavior.

Strengths

  • Checks HTTP, ICMP, TCP, and DNS endpoints with conditions for status, latency, certificate expiry, and response content.
  • The README documents YAML configuration and Docker deployment, and supports several alert destinations.
  • The official repository provides the Apache License, version 2.0.

Watch out for

  • Operators must deploy the service and configure the endpoints and conditions they want checked.
  • The product focuses on endpoint health checks rather than collecting logs, traces, or host metrics.

Best for

  • Developers who want a self-hosted status view for HTTP and network endpoint checks.
  • Small teams that prefer to keep monitoring targets and alert conditions in configuration files.

Sources