Backups, scrapers, billing scripts, and nightly reports break without a sound — and you find out when a customer does. Pulsewatch pings you the moment a scheduled job misses its check-in.
Pulsewatch monitors cron jobs and scheduled tasks. Add one ping URL to your job, and Pulsewatch alerts you by email or Slack if it stops checking in.
No credit card · 3 monitors free · Setup in one line
Add that one line to the end of any job. Silence = we alert you.
Uptime monitors watch your website. Almost nothing watches the invisible work happening on a schedule.
You assume last night's dump ran. It's been failing since the disk filled up. You learn this during a restore.
A source changed, the cron exited non-zero, dashboards quietly went stale. No error reached a human.
The monthly invoice run didn't fire. Finance notices on the 5th. Now it's a customer trust problem.
A "dead man's switch" for anything on a schedule. If the check-in doesn't arrive on time, you hear about it.
Cron example — one extra step:
Only pings on success (&&). If the backup fails or the box is down, no ping arrives — and we tell you.
Want duration & failure signals too?
A background clock checks every monitor continuously. Late = down, no polling your servers required.
One alert when it breaks, one when it recovers. We only notify on real state changes — never spam.
Know when it's fixed, not just when it broke. Full incident history per monitor.
Every monitor gets its own 144-bit URL. Isolated per account. Rotate anytime.
Cron, systemd timers, GitHub Actions, Kubernetes CronJobs, Lambda, Windows Task Scheduler, bots.
Create a monitor, copy one curl line, done. No agent to install, no SDK required.
Set up your first monitor in the next two minutes — free.
Create your first monitor →Public monthly pricing. Free forever for personal jobs — upgrade as you add more monitors.
3 monitors
Good for testing and personal jobs
25 monitors
For solo developers and small projects
100 monitors
For indie SaaS founders and small teams
500 monitors
For agencies and production teams
Taxes may apply and will be calculated at checkout.
Uptime tools ping your server from outside. Pulsewatch works the opposite way: your job pings us. That's the only way to catch a job that silently didn't run at all — there's nothing to poll.
A single outbound HTTPS call is almost always allowed. It's one request; if even that can't get out, that itself usually signals a bigger problem worth an alert.
No. We alert once on the transition to "down" and once on recovery. A job that stays down does not re-notify.
Yes — ping /start then / to measure run time, or /fail to report an explicit failure and trigger an immediate alert.
Every monitor belongs to one account and is only reachable via its unguessable token. Passwords are salted & hashed (scrypt).
Yes. Pulsewatch is a single Node process with an embedded database — no external services required to run the core product.