Scheduled jobs fail silently: no error page, no failed request, nothing in the logs you'd think to check. CronAlive is a dead man's switch — your job pings a URL after each run, and when a ping doesn't arrive in time, the alert is already in your Telegram. Heartbeats, HTTP uptime checks from three regions and TLS expiry warnings live in one dashboard. Flat pricing: 10 checks free, 100 for $7/mo. The Laravel package creates checks straight from your scheduler.
Hi PH 👋
I built CronAlive after the oldest embarrassment in ops: a nightly backup that had been failing for weeks, discovered on the day we actually needed it. The job produced no error, no log line, no failed request — absence is invisible, and that's exactly what monitoring usually misses.
So it's a dead man's switch: your job curls a URL after every run, and silence becomes the alert. Around that I added the parts I kept wanting: /start signals so a hung job is visible before it overlaps the next one, HTTP checks confirmed from a second region before they page you, and TLS expiry warnings — because "certbot ran" and "the new certificate reached the edge" are different claims.
What's rough, honestly: I'm one person, SMS alerts aren't implemented, and the SDKs are pre-1.0. If you need self-hosting, Healthchecks.io is open source and better for that — I say so on my own comparison page.
Free plan is 10 checks, no card. I'd especially like to hear what you monitor that you're not monitoring yet.