English
Gatus Hosting
Watch endpoints for uptime and latency and publish the results as a status page.
No setup fees-
One click deploy -
1 GB RAM Memory needed -
15 GB Disk Space Needed -
From 2 € Price
Official links
Gatus’s official links and original website
Gatus Website
More
Tech
- Docker image
- twinproduction/gatus:latest
- Default port
- 8080
How Gatus works
Gatus reads endpoint definitions that specify a target, protocol, interval, and conditions for deciding whether a check succeeds. Conditions can evaluate response status, latency, body content, certificates, and other properties supported by the selected endpoint type. Results feed a status page and history that help operators see current state and recent behaviour.
Alerting is configured per endpoint and provider. Upstream supports many provider integrations and custom webhooks, but the catalogue does not supply endpoint definitions, external service accounts, network allowlists, or provider credentials. Application email is disabled, so email alert delivery must not be promised from this package even though Gatus supports email when an SMTP service is configured elsewhere.
Key Gatus features
Configuration-driven monitoring makes the intended checks reviewable alongside infrastructure code. Endpoint groups, maintenance windows, conditions, client options, and alert thresholds can represent more than a basic HTTP ping. That flexibility also creates responsibility: a poorly chosen condition can report health while an important user path is failing, or generate noise for harmless variation.
The catalogue persists a /data volume, but Gatus configuration and integration setup still need to follow the package’s supported workflow. Monitoring from the same hosting environment cannot detect every regional, network, DNS, or platform-wide failure. Important public services often need checks from independent locations and a status page that remains reachable when the monitored environment is unavailable.
Gatus vs Better Stack
Gatus is a self-hosted, configuration-driven monitor and status page. Better Stack provides a managed service for uptime monitoring, incident management, hosted status pages, integrations, and on-call workflows. The commercial platform operates its checking infrastructure and team features, while Gatus leaves deployment, configuration, alert providers, access, and monitoring placement to the operator.
Better Stack may suit organisations that want managed multi-location checks, vendor-supported incident workflows, on-call scheduling, and a hosted status page without maintaining the monitoring application. Gatus is attractive for teams that prefer reviewable configuration and can operate the service, validate check coverage, configure providers, and account for correlated infrastructure failures.
Who uses Gatus
Development teams monitor APIs and dependencies, platform engineers define health conditions near their infrastructure code, and small operators publish a focused status view for selected services. Custom webhooks can connect failures to an existing automation or incident process when separately configured.
Gatus is not a full observability platform, synthetic browser suite, application performance profiler, log system, root-cause engine, or independent global monitoring network. A green check only demonstrates that the configured condition passed from the Gatus environment at that time.
Self-hosting Gatus: requirements and cost
Gatus resource use depends on endpoint count, check frequency, protocols, response size, conditions, history, alert volume, and dashboard traffic. PostgreSQL and MariaDB are Not required by the catalogue template; the persistent data volume stores application state. The software has no separate application fee, while short intervals and many endpoints can multiply outbound checks and retained results.
On AvaHost, Gatus uses Plan 1 at €2. The hosted Gatus package includes one-click deployment, a custom domain with automated HTTPS, automatic application updates, and scheduled backups. The package runs Gatus and persists data but does not create monitored endpoints, independent probe locations, provider accounts, API keys, network allowlists, incident staff, or application email. Customers must design conditions, configure non-email alert channels, and avoid relying on a monitor placed inside the same failure domain for complete coverage.
F.A.Q
Gatus starts at €2 on Plan 1. That plan suits a modest set of checks at reasonable intervals. Endpoint count, frequency, protocols, response size, conditions, history, alerting, and dashboard traffic determine when more resources are appropriate. Independent probe locations, provider accounts, and incident-response services are not included in the hosting price.
A custom domain can be assigned to Gatus, with automated HTTPS applied after DNS is configured. Use the final hostname for the status page and any callback references. Test public visibility, grouped endpoints, history, assets, and configured alert links before publishing it, and consider whether the page remains reachable during a failure of the monitored environment.
The package runs the application but does not define what to monitor, choose success conditions, supply provider credentials, create network allowlists, or build an incident process. Customers must configure each endpoint and alert channel. Application email is disabled, so use a separately configured non-email provider or custom webhook rather than expecting email notifications from this service.
A check reports what the configured condition observes from the Gatus hosting environment. It may miss failures limited to another region, provider, network path, identity flow, browser interaction, or the hosting platform itself. For critical services, combine well-designed conditions with independent monitoring locations and keep the public communication path outside the same likely failure domain.