Compare › Healthchecks.io
RunVouch vs Healthchecks.io
Healthchecks.io is the reference dead man's switch for cron jobs. RunVouch starts where a ping ends: did the job do the work, and what did it cost?
| Healthchecks.io | RunVouch | |
|---|---|---|
| Missed / late run alerts | yes | yes |
| Failure with stderr excerpt | via /fail ping | yes, automatic with rv run |
| Evidence the task was actually done | no | yes — file / URL / assertion |
| Retry-storm (loop) detection | no | yes |
| Cost and token caps | no | per run and per day |
| Output/duration drift | no | yes |
| Claude Code plugin / MCP server | no | yes |
| Self-host | yes (BSD) | yes (MIT) |
| Price | free 20 checks; $17–85/mo | free 3 agents; $9 / $29 |
When to use which
Use Healthchecks.io for classic cron jobs where "it ran" is enough. Use RunVouch when the job is an agent or an LLM script: a green ping tells you nothing about whether the report was written or whether the agent spent $60 looping on a missing file. Many teams run both.