Monitor your infrastructure.

Healthchecks

Healthchecks — monitor your cron jobs, backups and scheduled tasks: get alerted the moment a job does not run, fails or runs too long.

1 GB minimum RAM 1 vCPU Port 8102 In validation

In validation

Automatic installation for this solution is ready and currently going through our tests on a real server. Ordering will open as soon as validation is complete.

Tech stack

DockerPython (Django)SQLite
Minimum RAM1 GB minimum
Minimum CPU1 vCPU
Default port8102
Compatible OSChoice of Linux distributions

Healthchecks is an open-source (BSD-3 licensed) service for monitoring scheduled tasks. It turns classic monitoring around: instead of polling a server, Healthchecks waits for a signal. Every job — a crontab line, a systemd timer, a backup, a CI job — calls a ping URL when it finishes. If the ping does not arrive within the expected period plus the grace time, Healthchecks notifies you.

This is exactly the gap an uptime monitor leaves open: a website can return 200 while the nightly backup has not run for three weeks. Healthchecks also measures job duration, receives exit codes and the last lines of output, and sends alerts by email, webhook, Slack, Discord, Matrix, ntfy, Telegram and some twenty other integrations.

Key features

Ping-based monitoring — each job calls a unique URL; a missing ping triggers the alert.
Cron or period schedules — a cron expression with time zone, or a simple interval, plus a grace time.
Start, end and duration — /start and /fail pings measure run time and report explicit failures.
Exit codes and logs — send the exit code and the tail of the command output, viewable from the dashboard.
More than twenty alert channels — email, webhook, Slack, Discord, Matrix, ntfy, Telegram, Gotify, PagerDuty, Opsgenie…
Projects, team and API — separate projects, invited members, status badges and a REST API to create checks from your scripts.

When to use this solution?

1

Never lose a backup silently

Add a ping at the end of your nightly backup script: the day it stops running — full disk, expired credentials, rebooted server — you hear about it that morning, not the day you need the backup.

2

Monitor an application's background jobs

Invoice sending, session cleanup, supplier sync: every scheduled command of your SaaS gets its own check, with its normal duration and an alert channel to the team.

3

Track machines you cannot reach

A workstation behind NAT, a router, a Raspberry Pi at a customer site: as long as it can call an HTTPS URL, it can report that it is alive, without opening any inbound port.

Deploy Healthchecks on your VPS

Guide optimized for ServOrbit Cloud VPS.

01

Create the VPS and choose the address

Order an Ubuntu 24.04 VPS with 1 GB of RAM. Healthchecks requires a domain: ping URLs and alert links are built on that address. It opens over HTTPS on a subdomain of one of your domains, or on the VPS's free subdomain (healthchecks.{dns_slug}.servorbit-dns.com), HTTPS included. No need to buy a domain name.

02

Install Healthchecks from the Marketplace

In your client area, select Healthchecks, choose the address and click Install. The script deploys the container, runs the SQLite database migrations, creates the administrator account and sets up the nginx reverse proxy over HTTPS. Public sign-up is closed.

03

Log in for the first time

Open https://your-domain and log in with the address [email protected] and the generated password shown in your client area. Then change the email address and password from the account settings.

04

Create a check and add the ping

Click Add Check, choose a cron schedule or a period, then copy the ping URL. Append it to your job, for example && curl -fsS -m 10 --retry 5 https://your-domain/ping/<uuid>.

05

Connect an alert channel

Under Integrations, add at least one channel you actually read: webhook, Slack (incoming webhook), Mattermost, ntfy or Gotify work without any server configuration. For email alerts, set an SMTP server in the application's .env file.

Frequently asked questions

Uptime Kuma polls your services from outside and checks that they respond. Healthchecks does the opposite: it waits for your scheduled jobs to call it, and alerts when the call does not come. The two complement each other — one watches what must be reachable, the other what must run.

Monitor your infrastructure.

Healthchecks isn't orderable yet.

Automatic installation for this solution is ready and currently going through our tests on a real server. Ordering will open as soon as validation is complete.

Need help?

Browse our help center and FAQ, or reach our team — callback, WhatsApp or email. Support in French, English and Arabic.

Message us on WhatsAppopens in a new tab