Cronguard
v2.3 · Now with Slack & PagerDuty

Know in seconds when a cron job stops pinging.

Cronguard is dead-simple cron monitoring for SRE-minded teams. One curl call at the end of your job, alerts in your inbox the moment it goes quiet.

Start free · 5 monitors 30-second quickstart
No credit card · self-host on your own infra · open source on GitHub
cronguard.app/monitors
FreelyIT
Monitors10
Incidents1
Integrations
Team
Settings
Total
10
Healthy
8
Late
1
Down
1
Paused
1
1 incident active · Postgres nightly backup · 4h 12m
Postgres nightly backupDaily 02:00 UTC
4h 12m agodown
Invoice sync · StripeEvery 15 minutes
17m agolate
Ping retention cleanupDaily 03:00 UTC
6h 02m agohealthy
Sitemap rebuildHourly
12m agohealthy
Usage metering rollupEvery 5 minutes
1m agohealthy
Watching cron jobs at
LinearRAILWAYvercelSUPABASEresendneon.tech
Why teams switch to Cronguard

Quiet most days.
Loud the moment it matters.

Built by SREs who got tired of either learning a fault-tolerance framework just to ping a healthcheck, or having every paged alert come from a different tool.

Setup in 30 seconds
No SDK, no config file. One curl call in your job. Works with bash, python, k8s CronJob, Lambda — anything with HTTP.
Alerts that respect you
Configurable grace periods. Notifications go through email, Slack, PagerDuty or any webhook. Auto-recovery messages too.
Visual heartbeat
Every job has its own pulse line. You see flaky behaviour and long-running jobs at a glance, not in a wall of logs.
Maintenance windows
Pause a monitor before you ship. Set a "until" and it auto-resumes. Never get woken up by your own deploy.
Built for teams
Per-member access. Read-only for engineers, full control for SREs. SSO and audit log on the Team plan.
Self-host friendly
Docker image, Postgres, done. Keep your monitoring data on your own infrastructure — same UI, same alerts.
Drop-in integration

One line. Any language.
Any platform.

If it can make an HTTP request, it can talk to Cronguard. There's no SDK to keep up to date and nothing to break when you swap stacks.

Works with success, failure & duration payloads
11 ready-made snippets in the dashboard
Rate-limited & idempotent on the receiving end
# at the end of your cron job
curl -fsS https://cronguard.app/p/db-bk-x9k2
200 OK · < 60ms typical
Pricing

Simple. No usage anxiety.

Pick a plan in seconds. Change anytime. No per-ping charges, ever.

Free
€0forever
For personal projects and side jobs.
Start free
5 monitors
Email alerts
7 days history
Custom grace periods
Community support
Most popular
Pro
€9/month
For professionals & small startups.
Start 14-day trial
50 monitors
Email, Slack & webhook alerts
30 days history + CSV export
Pause & maintenance windows
Priority support
Team
€29/month
For teams running critical infra.
Start 14-day trial
Unlimited monitors
All alert channels + PagerDuty
90 days history + audit log
Per-member roles & SSO
Dedicated Slack channel
FAQ

The honest answers.

Cronguard re-checks every monitor every minute. Once a job misses its expected ping plus your grace period, alerts go out within one to two minutes.

Set up your first monitor.
It'll take 30 seconds.

Start free Read the docs