Best free cron job monitoring tools (2026)
A dead-man's-switch monitor pings you when a cron job, backup, or scheduled script doesn't run. This page compares the four most commonly mentioned options — LastPing, Healthchecks.io, Cronitor, and Dead Man's Snitch — on the dimensions that matter: cron support, CI/CD integration, failure detail, free-tier caps, and alert channels. We write this page; take our objectivity with the appropriate grain of salt.
What matters in a cron monitor
The core feature is simple — alert when a job misses its window. But there are real differences in what "missing" means and what happens after the alert fires.
Absence detection
The job didn't run at all — scheduler crash, cron misconfiguration, host OOM. This is the dead-man's-switch case: silence is the alert.
Failure + detail
The job ran and reported an error. Does the monitor surface why it failed — log excerpt, exit code, error message — or just that it did?
CI/CD pipeline support
Beyond curl-in-job pings: can the monitor listen to platform events (GitHub webhooks, Jenkins notifications) to catch hung runs and never-started runs without touching the pipeline code?
Free-tier cap
How many monitors before you pay? A developer with 30 cron jobs across several projects should know if they'll hit a wall.
Feature comparison (as of July 2026)
Pricing and features change — check each provider's site before making a decision. Competitor data is based on public documentation and may not reflect recent updates.
| Feature | LastPing | Healthchecks.io | Cronitor | Dead Man's Snitch |
|---|---|---|---|---|
| Cron / heartbeat monitoring | ✓ | ✓ | ✓ | ✓ |
| Free tier | Free, no cap | Free, ~20 monitors | Free, ~5 monitors | Trial only; paid |
| Absence detection (never ran) | ✓ | ✓ | ✓ | ✓ |
| Failure detail (log excerpt on incident) | ✓ up to 64 KB | ✗ | Partial (paid) | ✗ |
| Hung run detection | ✓ | ✗ | Partial | ✗ |
| CI/CD native webhooks (GitHub/GitLab/Jenkins) | ✓ signed webhooks | ✗ | Partial (paid) | ✗ |
| Never-started CI/CD run detection | ✓ | ✗ | ✗ | ✗ |
| Email alerts | ✓ | ✓ | ✓ | ✓ |
| Slack alerts | ✓ free | ✓ | ✓ | ✓ |
| Telegram alerts | ✓ free | ✓ | ✗ | ✗ |
| Discord alerts | ✓ free | ✓ | ✗ | ✗ |
| Webhook / HTTP push alerts | ✓ free | ✓ | ✓ | ✓ |
| MCP server (AI agent self-registration) | ✓ mcp.lastping.dev | ✗ | ✗ | ✗ |
| Open source / self-hostable | ✓ MIT | ✓ BSD | ✗ SaaS only | ✗ SaaS only |
"Partial" means feature exists but is restricted to paid plans or has limited scope. Free-tier caps are approximate as of July 2026 — verify at each provider's pricing page. LastPing is this page's publisher; we have an obvious interest in its favour.
Each tool in context
What each tool actually does well and where it falls short.
What it is: Free, fully-hosted dead-man's-switch monitoring for cron jobs, CI/CD pipelines, and AI agents. No paid tier, no monitor cap.
Strengths: The broadest failure detection of the
four tools — catches absent, failed, and hung runs. Native CI/CD
webhook integrations for GitHub Actions, GitLab CI, and Jenkins
listen to platform events rather than curl steps inside the pipeline,
so they catch never-started runs (including GitHub's 60-day silent
schedule disable) without touching pipeline code. Failure log
excerpts (up to 64 KB) are stored on incidents. The MCP server at
mcp.lastping.dev
lets AI agents create and manage their own monitors without a
human in the loop. MIT-licensed and open-source.
Weaknesses: Newer product with a smaller community and ecosystem than Healthchecks.io. Feature set is broad but less battle-tested. No PagerDuty or Opsgenie routing on the free tier (these are enterprise channels). No SMS channel.
What it is: The most established open-source cron monitoring tool, with an active community and a self-hostable option. BSD-licensed.
Strengths: Mature and widely trusted. Self-hostable with the open-source version (unlimited monitors, no SaaS dependency). Strong integrations across many alert channels (email, Slack, Discord, Telegram, PagerDuty, Opsgenie, and many more). Good documentation and a large user community.
Weaknesses: Free hosted tier caps at approximately 20 monitors. No CI/CD native webhook integrations — monitoring a CI/CD pipeline requires adding curl steps inside the pipeline, which misses hung runs and never-started runs. No failure log excerpt feature — alerts say the job missed or failed, but not why.
healthchecks.io · Compare LastPing vs Healthchecks.io
What it is: A more enterprise-focused monitoring product covering cron jobs, CI/CD pipelines, and uptime. Primarily paid.
Strengths: Well-established product with polished UI, a CLI tool, and integrations for major alert platforms. Has some CI/CD monitoring capability on paid plans. Good documentation.
Weaknesses: The free tier is very limited (approximately 5 monitors as of 2026). Most meaningful features — CI/CD integration, team features, longer data retention — require a paid plan. More expensive than the alternatives for teams with many monitors.
cronitor.io · Compare LastPing vs Cronitor
What it is: A focused, simple cron monitoring tool that does one thing well: alerts you when a job doesn't check in. Paid-only as of 2026 (no permanent free tier, trial available).
Strengths: Simplicity is a genuine virtue here — zero configuration beyond a URL in your cron job. Good reliability and long track record. Email, Slack, and webhook integrations.
Weaknesses: No free tier. No CI/CD pipeline monitoring. No failure detail — alerts indicate absence, not cause. No open-source or self-hosted option. The pricing model (per-snitch) can add up quickly for teams with many cron jobs.
Which one should you use?
The right answer depends on what you're monitoring and whether you want to self-host.
Many cron jobs, free forever
LastPing or Healthchecks.io. LastPing has no monitor cap; Healthchecks.io caps at ~20 on the hosted free tier but is unlimited if self-hosted. Both are open-source.
Self-hosted, no SaaS dependency
Healthchecks.io has the most mature self-host experience with a large community. LastPing is also self-hostable but newer.
CI/CD pipelines (hung or never-started runs)
LastPing — the only tool here with native CI/CD webhook integrations that catch hung runs and never-started runs without modifying the pipeline.
AI agents self-registering their own monitors
LastPing — the only tool with an MCP server
that lets agents call create_monitor and
get_ping_instructions in one conversation.
Simple, single cron job, willing to pay
Dead Man's Snitch is the simplest option and has a long reliability track record. Cronitor is better if you want a polished UI and plan to grow.
Enterprise, team features, PagerDuty routing
Cronitor on a paid plan has the strongest enterprise feature set. Healthchecks.io also integrates with PagerDuty and Opsgenie.
Common questions
Straight answers to the questions people actually ask.
-
What is the best free cron job monitoring tool in 2026?
For no monitor cap and no paid tier, LastPing and Healthchecks.io are the strongest options. Healthchecks.io is more established; LastPing adds CI/CD webhook monitoring, failure log excerpts, and an MCP server for AI agents. If you need unlimited monitors and want to self-host, either tool works; Healthchecks.io has the larger community.
-
Does Healthchecks.io catch hung cron jobs?
Healthchecks.io detects absence (a job that doesn't ping in its window) but does not have a "started but hung" detection mechanism. If a job sends a start ping and then hangs, Healthchecks.io marks the check as "started" and waits — it will eventually alert when the window expires, but only on the basis of the overall window, not the start/complete pairing that makes hung detection fast. LastPing's
/startendpoint specifically arms overrun detection. -
What is Dead Man's Snitch and is it free?
Dead Man's Snitch is a simple, focused cron monitoring service that alerts when a job doesn't check in. As of 2026, it does not offer a permanent free tier — it's a paid product with a trial period. It does not support CI/CD pipeline monitoring or attach failure detail to alerts.
-
Which cron monitoring tools support AI agent self-registration?
As of July 2026, only LastPing offers an MCP server (at
mcp.lastping.dev) that lets an AI agent create its own monitor, configure alerts, and retrieve ping instructions in a single conversation without a human visiting a dashboard. See the LastPing MCP server page for details. -
Can I use a cron monitoring tool for CI/CD pipelines?
Yes, but not all tools are equal for CI/CD. The simplest approach works everywhere: add a
curlstep at the end of your pipeline job. This catches explicit failures but not hung runs (the step never executes) or never-started runs (the pipeline never queued). LastPing's native CI/CD webhook integrations for GitHub Actions, GitLab CI, and Jenkins listen to platform events and catch all three failure modes without touching pipeline code. See the guides for CircleCI, Bitbucket Pipelines, Drone CI, and TeamCity for the ping-step approach.
Try LastPing — free, no cap, no credit card.
Start monitoring your first cron job or CI pipeline in about two minutes. LastPing monitors itself with the same tools you'll use.