Cron & Scheduler Monitoring
Give every scheduled task a heartbeat URL and know when it silently stops reporting.
Learn morePingBeacon monitors Laravel Scheduler, cron jobs and websites, then sends you a clear alert when something silently stops working.
A scheduled backup can stop. An invoice job can silently fail. A client website can go down at 2 AM. You don't want to discover it from a customer.
Start with the signals your applications already produce. No complicated infrastructure or noisy dashboards.
Give every scheduled task a heartbeat URL and know when it silently stops reporting.
Learn moreCheck uptime and response time automatically before your users report an outage.
Learn moreGet a clear alert when a monitor fails — and another when it comes back.
Learn moreKeep certificate expiry visible so an avoidable outage never becomes an emergency.
Learn moreCreate a cron, website or scheduled-task monitor from your dashboard.
Your job pings PingBeacon whenever it completes successfully.
If the expected signal doesn't arrive, PingBeacon lets you know.
PingBeacon only needs the signal you choose to send. No database passwords. No SSH access. No application credentials.
We're keeping the first version simple: enough monitoring for a small project, with room to grow when your infrastructure grows.
For basic cron monitoring, no. PingBeacon gives you a unique heartbeat URL that your job can call when it completes. A Laravel package can make this even simpler later.
PingBeacon waits through the monitor's configured grace period. If the expected heartbeat does not arrive, it creates an incident and sends an alert.
Yes. Website monitoring is a core part of PingBeacon. You can track availability, response time and SSL status.
Yes. The early-access plan starts with three monitors, five-minute checks, email alerts and seven days of incident history.
No. PingBeacon focuses on external health signals and scheduled-job failures. It complements application error monitoring rather than trying to replace it.