Cronwatch

Built for teams who can't afford a silent failure

Your cron jobs are
lying to you right now.

Backups that silently stopped three weeks ago. Billing jobs that quietly started taking 4x longer. Cronwatch catches what a dead-simple uptime check never will — with AI that actually understands what "normal" looks like for your jobs.

nightly-backup.sh
# add one line at the end of any job
pg_dump production > backup.sql
curl https://cronwatch.io/api/ping/your-token?status=success

How it works

1

Register a monitor

Tell Cronwatch how often your job should run. Takes 10 seconds.

2

Ping on success or failure

One curl call from the end of your script — no agents, no SDKs, no new dependencies.

3

Get alerted before it matters

Silent job? Abnormally slow run? You hear about it in seconds, with a summary you can actually act on.

AI anomaly detection

Cronwatch learns each job's normal run time and flags it the moment a 'successful' run quietly takes way longer than usual — the failures a timer-based monitor can't see.

Plain-English incident summaries

No more parsing log dumps at 2am. Get a summary and an auto-generated postmortem you can read in five seconds.

One-line integration

A single curl call at the end of any script, cron job, or worker. Live in under a minute, with zero new dependencies.

Pricing that scales with how much you rely on this

No surprise fees. Cancel anytime. No credit card required to start.

Starter

$39/mo

  • Up to 5 monitors
  • Email alerts
  • 1-minute check resolution
Get started
Most popular

Pro

$99/mo

  • Unlimited monitors
  • Email + Slack alerts
  • AI anomaly detection & incident summaries
  • 1-minute check resolution
Get started

Business

$249/mo

  • Everything in Pro
  • 30-second check resolution
  • Priority support
  • Multiple team members
Get started

Built by someone tired of dumb monitoring

Most monitoring tools only know how to ask "did you check in?" That catches the job that died outright. It misses the job that's still "succeeding" every night while quietly taking four times longer than it used to — which is usually the actual early warning sign, not the eventual crash. Cronwatch was built to catch that gap.

No card to start

The free tier needs only an email and password — no payment details collected until you choose to upgrade.

Minimal data, on purpose

We store pass/fail status and run duration. We never see your job's actual output, logs, or data.

Encrypted in transit

Every ping, alert, and dashboard request is served over HTTPS/TLS — including this status check below.

See our own live status →

Questions

How is this different from a basic uptime checker?

Uptime checkers verify a service responds. Cronwatch verifies your scheduled work actually ran — and on Pro and Business, flags runs that succeeded but took abnormally long, which is usually the first sign something is quietly breaking.

What happens if I forget to send a ping?

Cronwatch alerts you the moment your job misses its expected check-in window — by default within a minute, or 30 seconds on the Business plan.

Can I change plans later?

Yes — upgrade, downgrade, or cancel anytime from your dashboard. No contracts.