Dead Man's Snitch Alternative for Teams That Outgrew Ping-and-Pray
Dead Man’s Snitch does one thing: you curl a unique URL at the end of a cron job, and if that curl doesn’t show up on schedule, it alerts you. There’s no agent and no dashboard to configure beyond naming the snitch. For a handful of jobs where “did this run” is the whole question, that’s very little overhead, and $5/mo for three snitches is cheap.
This article is for the point where “did this run” stops being the whole question, when you spend more time SSHing in to fix what the snitch reported than the snitch saved you by reporting it.
What Dead Man’s Snitch actually is
- Free tier: 1 snitch
- Cheapest paid plan: $5/mo for 3 snitches
- Pricing model: per snitch
- Self-hosted: No
- Native app: iOS only
It’s a ping-and-alert service. There’s no crontab view, no remote editing, and no fleet dashboard. A snitch doesn’t know what command it’s attached to, only whether a curl call arrived.
Why teams start with it
The integration is one line at the end of a script:
/opt/scripts/nightly-export.sh && curl https://nosnch.in/abc123There’s nothing to install and no API key to manage beyond the snitch URL. For a side project, a single cron job protecting a backup script, or a small team’s first pass at “we should probably know if this stops running,” that’s enough tooling.
Where it stops helping
Every pure heartbeat pinger, Dead Man’s Snitch included, observes but doesn’t act. When a snitch goes silent:
- Dead Man’s Snitch doesn’t get the ping.
- You get an alert.
- You SSH into the box the job runs on.
- You read logs or re-run the command by hand to find out why.
- You edit the crontab or push a fix, then wait for the next run to confirm it worked.
The snitch shortened the gap between “it broke” and “you found out.” It did nothing for steps 3 through 5, which look identical whether or not you’re paying for monitoring at all. Per-snitch pricing also means the gap grows as you add jobs, and so does the bill. Three snitches at $5/mo is cheap. Thirty jobs across a handful of servers, each with its own snitch URL and its own manual SSH-and-fix loop, costs more than the price tag suggests.
What a control plane adds
norc can reach the job itself instead of waiting on a curl call. You pair a machine, local or remote, and from there norc sees the crontab and run history and lets you edit and redeploy an entry directly. Failure alerting is still there. When a job breaks, the crontab line and the run history leading up to the failure are in the same place you got the alert, and a fix like a bad schedule or a typo in a path happens without opening a terminal.
| norc | Dead Man’s Snitch | |
|---|---|---|
| Heartbeat / failure monitoring | Yes | Yes |
| Self-hosted | No | No |
| Pricing model | flat tier by machines and jobs | per snitch |
| Free tier | Yes | Yes, 1 snitch |
| Edit & deploy jobs remotely | Yes | No |
| AI natural-language job creation | Yes | No |
| Multi-machine fleet management | Yes | No |
Who should pick which
Pick Dead Man’s Snitch if:
- You have a handful of jobs and the only question you need answered is “did it run.”
- You’re fine being the one who SSHes in and fixes it by hand. For a small setup, that’s a reasonable tradeoff.
- An iOS app for alerts covers how you want to be notified.
Pick norc if:
- Per-job monitoring pricing is starting to scale worse than your actual job count.
- The SSH-diagnose-edit loop after an alert is eating real time, not just occasional attention.
- You manage more than one machine and want the crontab, not just the alert, in one place.
- You want a schedule generated from plain English instead of hand-writing cron syntax.
Dead Man’s Snitch answers “did it run” cheaply. norc starts one step later, at what to do about a failure.
See the full comparison for how norc stacks up against the rest of the field, or pricing for plan details.
FAQ
Is Dead Man’s Snitch free? Yes, for 1 snitch. Paid plans start at $5/mo for 3 snitches.
Can I self-host norc like some alternatives? No. norc has no self-hosted mode. Dead Man’s Snitch is hosted-only too, so this doesn’t separate the two. If self-hosting is a hard requirement, neither fits.
Does norc replace Dead Man’s Snitch’s alerting? Yes. Failure detection and run history are part of norc for every job on every machine you manage. The difference is what happens next: norc lets you open the crontab entry and fix it, not just get told something’s wrong.
Can I use both? Nothing stops you from keeping a Dead Man’s Snitch on a handful of critical jobs while using norc for management, but most teams reaching for norc are trying to consolidate onto one tool, not run two.