
Crontinel
Laravel schedule & queue monitoring — catch silent cron/queue/agent failures before users do.
About
Crontinel is Laravel schedule and queue monitoring built to catch silent cron, queue, and agent failures before users do.
Many teams rely on uptime checks alone. Uptime can stay green while schedule:run is hours late, a Horizon worker has stalled, or a backup job never fired. Crontinel watches the runs that should have happened and alerts when they do not.
Crontinel monitors the Laravel scheduler, Horizon queues, workers, backups, and agent runs. When a scheduled task is late, missed, or fails quietly, you get notified instead of discovering it from customer reports. That focus on expected runs—not just whether a host responds—is the core of the product.
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.
Crontinel is open core, MIT licensed, with a free tier. You can start monitoring without a large commitment and expand as your schedules and queues grow. Tags that fit the product include Laravel, DevTools, Monitoring, Cron, Queue, DevOps, Open Source, SaaS, and APM.
In short: if 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.
Ready to launch?
Submit your product and get discovered by builders and creators worldwide.
Launch NowFounderPlaybooks.
What other founders did to grow.
2722 dispatches from hundreds of founders, pulled from the week's best podcasts.
Initial MVP took around two to three months maybe… I use Cursor a lot, but I'm very specific which files to touch and don't let the AI just go rogue basically.
Ship the MVP in 2-3 months and keep the AI on a tight leash — specific files only
The first version shipped in two to three months by scoping tightly around a tracker plus a custom workout engine. AI coding tools accelerated the work, but only when pointed at specific files rather than allowed to roam — autonomy is what produces unmaintainable sprawl.
You want to make these offers highly targeted — you can tier them. Give a bigger discount if they were a subscriber for a longer period of time, consider a smaller discount if they were maybe only subscribing for a month or two. You don't want it to be a blanket discount because that's going to really cut into your bottom line.
Tier cancellation discounts by tenure — never blanket-discount
Tier cancellation save offers by subscription tenure. Blanket discounts train price-insensitive users to trigger the cancel flow just to grab the coupon, eroding margin on people who'd have stayed at full price. Long-tenure subscribers earn the bigger save offer; short-tenure churners get a small or no offer.
There's a play for whatever you're stuck on.
Read all 2722 playbooks