23/07/2026
We just launched PingArk, and it solves a problem almost every developer has been burned by at least once.
Scheduled jobs fail silently. The nightly backup, the billing run, the report that goes out every Monday morning. They run quietly in the background until one day they just stop. A server reboots, a path changes, an update breaks something. And because a cron job is not a website, no uptime monitor will ever catch it. Nothing tells you. Weeks later you need that backup, and you discover the last good copy is from a month ago.
PingArk fixes this with a simple idea called a dead man's switch. Every job sends a tiny check-in when it runs. If the check-in does not arrive on schedule, PingArk assumes the worst and alerts you on email, Slack, Discord, Telegram, or wherever your team actually looks.
For and apps, it goes a step further. Install one package and every scheduled job is monitored automatically, including how long it ran, its exit code, and the actual error when something fails. So instead of "the backup did not run," you see exactly what broke and why. And any other stack, in any language, can check in with a single line added to the job.
It is live now and free for 20 monitored jobs, no card required. That is enough to cover a project or two end to end. Paid plans are coming soon, and founding users who join now get early access to the Pro plan plus a founding perk when upgrades open.
If you or your team run scheduled tasks anywhere, this is worth two minutes of setup:
Monitor Laravel scheduled tasks and Node.js cron jobs. One package auto-registers your jobs and captures duration, exit codes, and the actual exception. Free for 20 checks, and any language can ping over plain HTTP.
