Know when your cron didn’t run.
Before your users do.
A dead-man’s switch for your cron jobs and background workers: they ping a URL when they finish; if koigrid stops hearing from them in time, you get alerted. The flat-rate, EU alternative to Healthchecks.io.
A cron that silently stops is the worst kind of outage
Uptime checks tell you when a URL is down — but they can’t see the backup that never ran, the queue worker that died, or the nightly sync that hung. koigrid Heartbeats watch from the inside: your job hits a ping URL on success, and if the ping doesn’t arrive within the window you set, you get an email and a webhook. One curl at the end of your script.
How koigrid compares
| koigrid | Healthchecks.io | |
|---|---|---|
| Pricing | Flat rate | Per check / tier |
| Ping URL + grace period | Yes | Yes |
| Alerts (email + webhook) | Built-in | Yes |
| Next to your Checks & Jobs | Yes (same platform) | No |
| Manage by API / AI agent | Native | API |
| EU data residency | Yes | Optional |
From public docs, 2026. koigrid marks a heartbeat down when no ping arrives within period + grace, and alerts once on the transition.
Catch the silent failures
Dead-man’s switch
Your job pings on success. No ping in time → it’s down, and you know within a minute.
Period + grace
Set how often you expect a ping and how much lateness to tolerate before alerting.
Email + webhook
Alerts on the transition (down, and recovery) — to the owner’s email and your webhook (Slack, PagerDuty…).
One curl
Add `curl <ping-url>` to the end of your cron or worker — nothing to install.
Next to your monitoring
Heartbeats sit beside Checks (external) and Jobs — inside monitoring and outside monitoring in one place.
Agent-native
Create and manage heartbeats from Claude Code or any LLM via the API.