Gatus is a self-hosted service monitor that probes your endpoints on a schedule and publishes the results on a status page. It suits operators who are comfortable keeping a YAML file in version control and running one more container on their own infrastructure.[1][2]
Quick verdict
Small infrastructure teams that want a status page without a SaaS subscription get the most from Gatus: scheduled checks with pass/fail conditions, more than 40 alerting integrations, and badge-ready status pages in one Apache-2.0 licensed package. The capability behind that recommendation is config-as-code monitoring, where endpoints, conditions, and alert routing all live in a versioned YAML file. The material constraint is that you own hosting, upgrades, and the monitor's own availability, so teams with no one to run infrastructure or needs beyond uptime checks should choose a hosted SaaS monitor instead. If you have someone to run a container and like configuration in git, choose Gatus; if you need no-code simplicity, choose a hosted monitor.[1][2]
Key features
Scheduled checks with pass/fail conditions Scheduled checks with pass/fail conditions: endpoints are evaluated on a schedule against conditions on status, latency, and body content, so an HTTP 200 with the wrong payload still counts as down.[1][2]
More than 40 alerting integrations More than 40 alerting integrations: failures fan out to PagerDuty, Discord, Slack, email, and dozens of other providers, which lets Gatus drop into an existing on-call workflow without new tooling.[1]
Status pages with badges and tooltips Status pages with badges and tooltips: results publish to a developer-oriented status page with uptime badges and hover tooltips, giving customers and teammates one place to check health.[1][2]
YAML-file configuration YAML-file configuration: endpoints, conditions, and alert routing live in a versioned configuration file, so changes get review, diffing, and rollback through git.[1][2]
Docker, Helm, and Terraform distribution Docker, Helm, and Terraform distribution: the single Go binary ships as a Docker image and Helm chart with a Terraform module, fitting container hosts and Kubernetes clusters alike.[1][2]
SQLite or PostgreSQL persistence SQLite or PostgreSQL persistence: check history persists across restarts in embedded SQLite for small setups or PostgreSQL when retention and scale demand it.[1]
OIDC login and a programmatic API OIDC login and a programmatic API: the Security section documents OIDC alongside basic authentication, and a documented API supports programmatic interaction plus raw-data reads for checks.[1]
Apache-2.0 licensed core Apache-2.0 licensed core: the core carries an OSI-approved Apache-2.0 license with no paid tier verified, so self-hosting teams get the full monitor without license spend.[1]
Who will love it
Homelab and side-project owners Homelab and side-project owners: one container watches every service and produces a status page with badges, which covers personal infrastructure without a monitoring subscription.[1][2]
Small teams replacing a SaaS monitor subscription Small teams replacing a SaaS monitor subscription: scheduled checks, broad alerting, and bundled status pages remove a recurring bill wherever someone already runs infrastructure.[1][2]
Config-as-code teams Config-as-code teams: YAML endpoints in git plus Terraform distribution match teams that already review infrastructure changes as pull requests.[1][2]
Who should avoid it
Teams with nobody to host it Teams with nobody to host it: a self-hosted monitor needs patching, backups, and its own availability story, so the bill you remove becomes operational work you accept.[1][2]
Teams needing full observability Teams needing full observability: there is no APM, log analytics, or distributed tracing here, so metrics-and-traces platforms remain necessary alongside it.[1]
Buyers needing no-code setup Buyers needing no-code setup: endpoints are declared in YAML and the software runs on your infrastructure, so non-technical operators should pick a hosted monitor with a point-and-click setup.[1][2]
Alternatives and compatibility
Against hosted SaaS monitors Against hosted SaaS monitors: SaaS spares you hosting and carries the vendor's availability, while Gatus removes the subscription but needs someone to run it; choose by whether infrastructure ownership is staffed.[1][2]
Against Uptime Kuma Against Uptime Kuma: both are self-hosted monitors with status pages for the same workflow; Gatus leans config-as-code with YAML while Kuma leans dashboard-first, so pick by which operating style your team prefers.[1]
Sits alongside existing stacks Sits alongside existing stacks: because alerting covers 40-plus providers, Gatus drops into PagerDuty, Discord, Slack, or email workflows already in place, complementing rather than replacing observability tooling.[1]
Questions worth asking
What is the best Gatus alternative for non-technical users?
Is Gatus really no-code?
How much does Gatus cost per month?
The self-hosted core is Apache-2.0 licensed with no paid tier verified, so license cost is zero; checked October 2026. You still pay for whatever hosts it, and a managed Gatus.io offering exists with terms that were not verified in this pass.[1]
Sources and editorial review
Source research. Reviewed on October 10, 2026. Written by Sanjib Sah. AI assisted; reviewed by a human editor.
We have not run or tested this product.
- TwiN/gatus repository
official · Observed October 10, 2026
Official repository page: identity, Apache-2.0 license, Go/TypeScript, monitoring and status-page topics, Security/OIDC, API section, 40-plus alerting providers, Docker/Helm/Terraform distribution, creation date 2019-09-04.
- Gatus README
official · Observed October 5, 2026
Repository README: features, getting-started, conditions, alerting providers, storage tutorial, Docker Hub, Helm, and Terraform install channels.
- Gatus vs Upptime comparison
published measurement · Observed October 10, 2026
Independent comparison: YAML configuration, Docker/Helm/Terraform, SQLite/PostgreSQL, tooltips and badges, Uptime Kuma cross-link as related alternative.
Compared with these products
No explicit proprietary baseline is recorded.