Healthchecks

Unique ping URL per check Every monitored job gets its own URL, and any language or scheduler that can send an HTTP request can report in, from shell scripts to Arduino boards and GitHub Actions.[1]

Period and Grace states Each check moves through New, Up, Late, and Down based on time since the last ping, so brief overruns surface as Late before a Down notification fires.[1]

Cron-expression schedules Expected ping times can follow a cron expression or systemd OnCalendar syntax, with Grace time set slightly above the job's normal duration.[1]

Broad notification integrations Email, webhooks, Slack, Discord, Matrix, PagerDuty, Opsgenie, Gotify, ntfy, and GitHub Issues are covered, with SMS, WhatsApp, and phone-call credits on paid plans.[1][2]

Ping log and event history Each check keeps a log of received pings and sent down notifications, with 100 entries per job on free plans and 1000 on paid plans for auditing past runs.[1][2]

Public status badges Per-tag and account-wide badges with unguessable URLs drop into READMEs, dashboards, or status pages without exposing the account.[1]

Pinging API and Management API A pinging API covers heartbeat, start, failure, and log-carrying signals, while a management API plus slug URLs, cloning, and auto-provisioning support scripted fleet management.[1]

Self-hostable open-source core The BSD-3-Clause codebase runs from a documented Docker guide or a virtualenv source install, so cost-sensitive teams keep the data and alerting on their own infrastructure.[1][2]

Solo developers guarding backups One HTTP request per backup script plus a free tier covering 20 jobs covers nightly dumps and weekly reports without a paid plan.[1][2]

Self-hosting teams The open-source core with Docker and standard Python and Postgres building blocks fits shops that already run their own infrastructure and want monitoring data to stay in-house.[1]

Budget-conscious and nonprofit projects The free Hobbyist tier is usable without payment, and open-source projects and nonprofits can get the Business plan free, which removes cost as an objection for small footprints.[1]

Teams needing error and performance context Healthchecks knows a job missed its schedule, not why it failed; Sentry or a full observability stack pairs stack traces and profiling with its own cron monitoring.[1][2]

Non-technical operators working alone Every job must be edited to send pings, so someone with code or scheduler access has to do the wiring even though day-to-day use is a simple dashboard.[1]

Enterprises requiring SSO and support contracts No single-sign-on statement, no uptime SLA, and only email-based support were documented, so compliance-heavy buyers will find the packaging thin.[1][2]