Cron jobs fail silently.
Now you'll know first.

A scheduled job doesn't send an error page when it stops running. It just stops — no exit code, no Slack message, no red X. Quietfail watches for that silence and tells you the moment it happens.

Free for up to 10 monitors. No credit card required.

Ping URL in under a minute
Email alerts on every plan
Cancel anytime
Monitors

nightly-db-backup

last ping 2m ago

Up

stripe-billing-sync

silent for 47m

Down

# alert sent
stripe-billing-sync hasn't pinged
in 47 minutes — expected every 30m

checked every 1 minute

The job doesn't crash. It just stops.

A cron job that errors out is easy — your process manager catches it, logs it, maybe pages you. The dangerous failure mode is the one with no error at all: a server got rebooted and the crontab never came back, a deploy silently dropped the scheduled task, an API key expired and the script has been exiting 0 on failure for a week. Nothing alerts you, because nothing broke loudly enough to alert on.

nightly-db-backup.sh

goes quiet, and your restore point is three weeks old before anyone notices.

stripe-billing-sync

goes quiet, and customers get charged the wrong plan for a month.

etl-warehouse-load

goes quiet, and every dashboard downstream is quietly wrong.

Three steps, no agent to install

1

Register a monitor

Name the job and tell Quietfail how often it should run. You get back a unique ping URL immediately.

2

Ping it on success

Add one line to the end of your script — a GET or POST to that URL. That's the entire integration.

3

Get alerted on silence

If the ping doesn't arrive within your interval plus grace period, we email you — Slack or Discord too, on Pro.

# Run at the end of your script
curl -fsS https://quietfail.kossh.in/api/ping/your-monitor-slug

# Or as a crontab entry (crontab -e) — adjust the schedule to match your job
*/5 * * * * curl -fsS https://quietfail.kossh.in/api/ping/your-monitor-slug > /dev/null 2>&1

Built for the two minutes you spend on this a month

Monitoring your cron jobs shouldn't be its own project. Quietfail is deliberately small in scope so there's nothing to maintain.

Set up in under a minute

Add a monitor, get a ping URL, paste one line into your script. No agents to install, no config files, no dashboards to configure before it's useful.

Alerts that reach you where you already are

Email on every plan. Slack or Discord webhooks on Pro, so a dead job shows up in the channel your team is already watching — not buried in an inbox.

A dashboard built to be scanned, not studied

Every monitor's status is color, icon, and label together — up, down, or never configured — so you can tell what's wrong from across the room.

Simpler than an observability platform, newer than a decade-old cron watcher

You don't need a full monitoring suite to know a backup script ran. Quietfail does one thing — dead-man's-switch monitoring for scheduled jobs — with a modern dashboard, no self-hosting, and a free tier that covers most side projects outright.

Simple pricing

Free while you're getting started. Upgrade when you need more.

Free

$0

forever

  • Up to 10 monitors
  • 5-minute minimum check interval
  • Email alerts
  • 7-day ping history
Get started
Most jobs outgrow free eventually

Pro

$9/mo

billed monthly, cancel anytime

  • Up to 100 monitors
  • 1-minute minimum check interval
  • Email + Slack/Discord alerts
  • 90-day ping history
Start free, upgrade anytime

Questions

What counts as a "monitor"?+

One monitor watches one scheduled job. It's the unique ping URL you call at the end of that job — a nightly backup, a sync script, a cron-triggered report. If you have five jobs you care about, that's five monitors.

What happens if I go over the free tier limit?+

You can't create an 11th monitor on the free plan until you upgrade or delete one. Monitors you already have keep running and alerting normally — nothing gets paused or deleted for you.

How fast are alerts actually sent?+

The background checker runs every minute. You'll be alerted within about a minute of your monitor's expected interval plus grace period running out — not minutes or hours later.

Can I self-host Quietfail?+

Not yet. Quietfail v1 is hosted-only — you sign up and use the dashboard we run. Self-hosting isn't supported at this time.

Find out about the failure before your users do.

Add your first monitor in under a minute. Free for up to 10 jobs.

Start monitoring — it's free