● Cron job & scheduled task monitoring

Know the moment your cron jobs stop running.

Backups that silently stopped. Reports that never sent. Heartbeat watches every scheduled job and alerts you by email, Slack or Discord the minute one misses its check-in.

Free for 5 checksNo credit cardSet up in 60 seconds

Monitoring that takes one line of code

No agents to install, no SDK, no config files. If it can make an HTTP request, it can be monitored.

1

Create a check

Tell us how often the job runs, like every hour or every night, and how much slack to allow.

Every 1 day · 1 hour grace
2

Ping when it finishes

Add a request to your unique URL at the end of the job. Works from bash, PowerShell, Python, Node and more.

backup.sh && curl …/ping/9f2c
3

Get alerted if it doesn't

If a ping is late, we alert you once, then again when the job recovers. No alert storms.

[DOWN] "backup" missed its check-in

Everything you need, nothing you don't

Built for developers, sysadmins and small teams who'd rather find out from us than from their customers.

Missed-run detection

Checked every minute. Late by even one grace period? You'll know.

Failure reporting

Jobs can report their own errors with /fail for an instant alert, with the error output attached.

Run time & slow-run alerts

Ping /start first to track how long runs take, with median and p95. Get alerted when a run is slow or hangs.

Email, Slack, Discord & webhooks

Send alerts where your team already is. Webhooks plug into anything else.

Status badges

Show live job status in your README or internal wiki with an embeddable SVG badge.

Ping history & logs

Every ping is logged. POST your job's output and read it right next to the failure.

Cron schedules & time zones

Use a real cron expression in any time zone, DST included, or a simple interval. Alert after N failures in a row to skip one-off flakes.

Scheduled HTTP jobs

No server to run cron on? Heartbeat calls your URL on schedule, with your own method, headers and body, and records every response.

GitHub & VS Code

Define checks in .heartbeat.yml and sync them from GitHub Actions. Trigger workflows on a schedule, or run jobs from VS Code with results reported automatically.

Free during the Pilot

Heartbeat is in an early Pilot. There's no paid plan and no credit card. Your feedback decides what gets built next.

Support the Pilot

Optional, and always appreciated

Heartbeat is built and run independently. If it's useful to you, a donation helps cover hosting and fund the features users ask for. Telling us what you'd like to see helps just as much. See where donations go →

Donations open soon.

Where donations go

Heartbeat is an independent project. Here is exactly what your support pays for, in order.

1

Keeping it running

Servers, database, email delivery and the domain. These come first, so monitoring stays reliable and free for everyone in the Pilot.

2

Features you ask for

Development time goes to what Pilot users request most: new integrations, longer history, team accounts and more. Your feedback sets the order.

3

Building it to last

Our goal is $100,000 in donations. Reaching it lets us set Heartbeat up as a proper business with dedicated support, so it's here for the long run. Paid plans will be shaped by Pilot feedback.

Donations are voluntary gifts. They aren't tax-deductible and don't buy equity or extra features, and Pilot accounts get the same features whether or not you donate. Payments are processed by Ko-fi.

Frequently asked questions

What can I monitor?

Anything that runs on a schedule and can make an HTTPS request: cron jobs, Windows Task Scheduler tasks, Kubernetes CronJobs, GitHub Actions schedules, backup scripts, ETL pipelines, serverless functions, and more. Every connection is encrypted: pings and the API are HTTPS only (plain HTTP is refused), and the URLs Heartbeat calls for you must be HTTPS too.

How fast will I be alerted?

We check every minute. You're alerted within about a minute of a check passing its expected time plus the grace period you chose, or immediately if your job pings /fail.

Will I get spammed if a job stays down?

No. You get one alert when a check goes down and one when it recovers. Nothing in between.

Is my ping URL a secret?

Yes. Treat it like a password: anyone with it can send pings for that check. Status badges use a separate read-only link, so they're safe to make public.

Do I need to install anything?

No. There's no agent or SDK. One curl, Invoke-RestMethod or HTTP call at the end of your job is all it takes.

Stop finding out from your customers.

Set up your first check in under a minute. Free during the Pilot.

Sign in or create an account

We'll email you a one-time sign-in link. No password needed.