A Healthchecks.io alternative that also watches your website and API
Healthchecks.io is a focused, well-regarded cron job monitor, and a good choice if scheduled jobs are all you need to watch. Asniher covers the same heartbeat job (cron schedules, start and fail signals, exit statuses and job output) and adds active uptime checks and public status pages, so the jobs and the services they feed are monitored in one place.
What Asniher does differently
Cron jobs and the services they feed, together
Heartbeat monitors sit next to HTTP(S), keyword and SSL monitors that Asniher runs itself. A failed backup and a slow API show up in the same dashboard, alert channels and status page.
One outage, one alert
Make a job depend on the API it calls. While the API is down, the job's alerts are held back and its incident notes why, so one outage does not page you once per job.
Why it failed, in the alert
Send the exit status and output with each run, or wrap the job with the asniher-run script. Failure alerts include the exit status and the end of the output, so you can often see the cause without opening a terminal.
Status pages in every plan
Show jobs and endpoints on a public status page with 90-day uptime bars. Pro and Team add a custom domain with automatic TLS.
Side by side
A summary of how each product approaches the same job. Details about Healthchecks.io are phrased cautiously because they change; confirm on their website.
| Capability | Asniher | Healthchecks.io |
|---|---|---|
| Heartbeat (cron job) monitoring | Yes | Yes |
| Cron schedules with time zones | Yes, five-field cron | Yes; see their documentation for supported formats |
| Start, fail and exit-status signals | Yes | Yes |
| Job output in failure alerts | Last 1,500 characters in chat and email, full 10 KB in webhooks | See their documentation |
| Active HTTP(S), keyword and SSL monitoring | Yes, with re-checks and multi-region confirmation | Not offered; it monitors incoming pings |
| Alert dependencies between monitors | Yes | See their documentation |
| Public status page | Included in every plan | Status badges; see their documentation |
| Heartbeat monitors on the free plan | 20, plus 5 uptime monitors | Check their pricing page |
| SMS and phone call alerts | Not offered | Offered on paid plans; check their pricing page |
| Open source and self-hosting | No, hosted only | Yes; see their documentation |
| Import from Healthchecks.io | Yes, schedules, time zones and grace periods carry over | Not applicable |
| Data hosting | EU (Germany) | See their privacy policy |
Which one fits your team?
Choose Asniher if
- You also need to monitor websites, APIs or certificates, not only scheduled jobs.
- You want a public status page that includes your jobs and endpoints.
- You want one alert when a shared dependency breaks, not one per job.
- You want failure alerts to say why a job failed.
Healthchecks.io may be a better fit if
- Scheduled jobs are the only thing you need to monitor.
- You want to self-host an open-source monitor.
- You need SMS or phone call alerts, or integrations beyond email, Slack, Discord, Telegram and webhooks.
- You use systemd OnCalendar schedules, which Asniher does not support.
Product details change often. Information about third-party products reflects our understanding at the time of writing; check their website and pricing page for current features and limits. Trademarks belong to their respective owners.
Try Asniher alongside Healthchecks.io
Run both in parallel on the Free plan for a week and compare alerts. No card required.