Healthchecks.io Alternative for Teams That Want to Fix Jobs, Not Only Watch Them
Healthchecks.io is good. It’s open source, it’s self-hostable, and it tells you when a scheduled job stops checking in. If you want a heartbeat monitor you can run inside your own infrastructure and forget about, it’s probably the right answer, and you can stop reading here.
This article is for a narrower case: you’re happy with what Healthchecks.io tells you, but tired of what you have to do after it tells you.
What Healthchecks.io actually is
Healthchecks.io is a heartbeat pinger. Your cron job hits a unique URL when it finishes; if the ping doesn’t arrive within your configured grace period, Healthchecks.io fires an alert through whichever channel you’ve wired up. It’s minimal infrastructure that does one job:
- Free tier: 20 jobs
- Cheapest paid plan: $20/mo for 100 jobs
- Pricing model: per job
- Self-hosted: Yes, open source
If you want self-hosted heartbeat monitoring, Healthchecks.io is a strong answer. If self-hosting matters to you, stop here: norc has no self-hosted mode.
At $20/mo for 100 jobs, Healthchecks.io is cheap, and the free tier’s 20 jobs is enough for many small setups to never pay.
Why teams reach for Healthchecks.io in the first place
Besides the price, the integration is small: one curl call at the end of your script, one URL, no agent to install, and no account permissions to grant on the box the job runs on. Healthchecks.io has stayed a heartbeat pinger by design, and the open-source codebase is small enough to read if you want to know what it does with your ping data. That suits a team that wants monitoring it can audit and deploy inside a VPC.
The gap: a pinger doesn’t have a write path
Any heartbeat monitor, Healthchecks.io included, only observes. Your job pings a URL and the monitor watches for the ping. It has no connection to the machine the job runs on, so it can’t see the crontab, the script, or the logs, and it can’t change any of them.
When a job fails:
- Healthchecks.io doesn’t get the ping.
- You get an alert.
- You SSH into the box.
- You read logs, find the bug or the bad schedule, and fix it by hand.
- You edit the crontab directly, or push a deploy.
Steps 3 through 5 are the same with or without a monitoring tool. The monitor shortened the time between “it broke” and “you found out,” and did nothing for the time between “you found out” and “it’s fixed.”
What a control plane does differently
norc can act on the cron job as well as watch it. You pair a machine, local or remote, and from there norc can view the crontab, edit entries, deploy new jobs, and generate a schedule from a plain-English description. Run history and failure alerts are included, so you keep the monitoring half. The main difference is the write path: when something’s wrong, you fix it from the same place you found out about it, without dropping into a terminal.
| norc | Healthchecks.io | |
|---|---|---|
| Heartbeat / failure monitoring | Yes | Yes |
| Self-hosted | No | Yes, open source |
| Pricing model | flat tier by machines and jobs | per job |
| Free tier | Yes | Yes, 20 jobs |
| Edit & deploy jobs remotely | Yes | No |
| AI natural-language job creation | Yes | No |
| Multi-machine fleet management | Yes | No |
Who should pick which
Pick Healthchecks.io if:
- You need monitoring data to stay inside your own infrastructure.
- You’re comfortable being paged and then SSHing in yourself. For some teams that separation is a deliberate choice.
- Your job count is small enough that the free tier or a cheap paid tier covers you.
Pick norc if:
- You’re spending real time each incident on the SSH-and-fix loop, not just the alert.
- You manage more than one machine and want one place to see and edit schedules across all of them.
- You want AI-assisted schedule generation from plain English instead of hand-writing cron syntax.
- Self-hosting isn’t a requirement for you.
Healthchecks.io covers monitoring and norc covers the fix step, so the choice depends on which half hurts more.
What changes day to day
Instead of an alert landing in Slack with nothing to do but open a terminal, you open norc, see the machine and job that failed, and the crontab entry is right there and editable, with the run history that led up to the failure visible in the same view. If the fix is a schedule change (wrong hour, wrong day, a typo in the cron expression), you make it there and it deploys to the machine. If you manage the same job pattern across several servers, you’re not repeating the SSH-diagnose-edit loop per box.
This targets the fix step, which no heartbeat pinger, Healthchecks.io included, was built to touch. It doesn’t replace your monitoring stack.
See the full comparison for how norc stacks up against the rest of the field, or pricing for plan details.
FAQ
Is Healthchecks.io free? Yes, up to 20 jobs on the free tier. Paid plans start at $20/mo for 100 jobs.
Can I self-host norc like I can Healthchecks.io? No. norc has no self-hosted mode. It’s a hosted service. If self-hosting is a hard requirement, Healthchecks.io (or another OSS option) is the right choice, not norc.
Does norc do heartbeat monitoring too? Yes. Run history and failure detection are part of norc across every machine you manage. The difference is what happens after: norc lets you edit and redeploy the job, not just alert on it.
Can I use both? There’s nothing stopping you from running Healthchecks.io for monitoring and norc for editing and deploying jobs, though most teams that reach for norc are looking to consolidate rather than add a second tool.