Secure ping URLs
Every monitor gets an unguessable ping URL. Add it to cron jobs, scripts, scheduled commands, containers, or GitHub Actions.
MVP features for early access
Focused features for monitoring critical automations.
CronHealth starts with the essentials: secure ping URLs, expected schedules, grace periods, clear statuses, recent history, and email alerts when jobs stop checking in.
Monitor details
Nightly Backup
Ping URL
https://cronhealth.io/ping/your-monitor-token
Last ping
03:00 today
Next expected
03:00 tomorrow
Schedule
0 3 * * *
Grace
30 minutes
curl -fsS -m 10 --retry 3 \
https://cronhealth.io/ping/your-monitor-token
https://cronhealth.io/ping/your-monitor-token
Core features
Everything needed for the first useful version.
No teams, billing, SMS, Slack, or complex outcome metrics in the first MVP. Just the foundation developers can actually use.
Intervals and cron expressions
Use simple intervals like every 15 minutes or custom cron expressions like 0 3 * * *.
Grace periods
Avoid noisy alerts when a job runs a little late. CronHealth waits until the expected time plus grace period before marking it late.
Simple statuses
See whether each monitor is pending, healthy, late, or paused. No need to scan server logs to know what stopped checking in.
Recent ping history
Review recent executions, last ping time, next expected ping, and basic alert history from the monitor detail page.
Email alerts
Get one email when a monitor becomes late and one recovery email when the next successful ping arrives.
Status logic
Status changes are intentionally predictable.
CronHealth is built around simple state transitions. It only alerts when something changes, so one missed job does not create hundreds of emails.
Pending
The monitor was created but has not received its first ping yet.
Healthy
The latest ping arrived and the next expected deadline has not been missed.
Late
The expected ping did not arrive after the configured grace period.
Paused
The monitor is temporarily disabled and will not trigger late alerts.
alert behavior
# Normal flow pending → healthy # If expected ping is missed healthy → late send missed-ping email once # If the job checks in again late → healthy send recovery email once # No email spam while still late late → late no repeated alert every minute
Built for practical developer workflows.
CronHealth works anywhere that can make an HTTP request. Keep your existing cron jobs, scripts, commands, and scheduled workers.
Linux cron
Add curl after your command.
Docker
Ping from inside container jobs.
Symfony / Laravel
Monitor scheduled commands.
GitHub Actions
Ping from scheduled workflows.
setup pattern
# Ping CronHealth only after the real task succeeds. 0 3 * * * /app/bin/backup.sh \ && curl -fsS -m 10 --retry 3 \ https://cronhealth.io/ping/your-monitor-token
Early access limits
Free MVP, intentionally constrained.
The first version is free while the product is validated. Limits keep the service simple, stable, and focused.
5
Monitors
Enough to test CronHealth on your most important automations.
5m
Minimum interval
Avoids unnecessary load and keeps free early access sustainable.
50
Alert emails/day
A safety limit to prevent notification abuse or accidental loops.
Not included in the first MVP
CronHealth has a broader vision around automation health and future outcome checks, but the first version avoids scope creep.
Slack, Discord, Telegram, SMS alerts
Teams, organizations, roles, audit logs
Billing and paid subscriptions
Business outcome metrics and custom payload rules
Public status pages and incident timelines
AI summaries, workflow orchestration, or job scheduling
Start with one important job.
Create a free monitor, add the ping URL, and see whether your critical automation keeps checking in.
Start free