Crontinel is Laravel schedule and queue monitoring built to catch silent cron, queue, and agent failures before users do.
The problem it solves: many teams rely on uptime checks alone. An uptime check tells you that a server answered a request. It does not tell you whether the background work behind that server actually ran. Uptime can stay green while schedule:run is hours late, a Horizon worker has stalled, or a backup job never fired. Nothing breaks loudly, no error page appears, and the failure stays invisible until a customer asks why the thing they expected never arrived.
How Crontinel is different: instead of only asking whether a host responds, Crontinel watches the runs that should have happened and alerts when they do not. Every scheduled task, queue, worker, and agent run carries an expectation: it should run, and it should finish. When a run is late, missed, or fails quietly, you get notified instead of discovering it from customer reports.
What it monitors: Crontinel monitors the Laravel scheduler, Horizon queues, workers, backups, and agent runs. These are the parts of a Laravel application that keep working long after a deploy is finished, and they are usually the least observed. A cron entry that stops firing after a server change, a worker that dies without restarting, a backup that silently stops producing files, or an agent run that never completes are all failures that traditional monitoring can miss entirely.
Beyond Laravel: Crontinel also offers Node and Python SDKs, so the same monitoring approach can cover adjacent jobs and agents in a mixed stack. The goal is one place to see whether critical background work actually ran, regardless of which language started it.
Open core and free to start: Crontinel is open core, MIT licensed, with a free tier. You can start monitoring the jobs you already worry about without a large commitment, and expand coverage as your schedules and queues grow.
Who it is for: Laravel teams and developers who run scheduled tasks, queues, workers, backups, or agent workflows in production, and who would rather hear about a missed run from a monitor than from a user.
In short: if a silent schedule or queue failure would hurt your users, Crontinel is the watchdog for the jobs that are supposed to run, catching late, missed, and failed work before it becomes a production incident.
Crontinel is a side project built by a Laravel developer for other Laravel developers, and it is available to try today at https://crontinel.com. Questions and feedback are welcome at support@crontinel.com.
