Crontinel
Crontinel provides outcome monitoring for background jobs and scheduled tasks, separating process exit status from business results so a job that exits 0 while processing zero records is flagged as unhealthy. It accepts check-ins via HTTP from curl, Node, Python, Sidekiq, and GitHub Actions, and offers a Laravel Composer package that automatically hooks into the scheduler, queue, and Horizon without per-task ping calls. The platform reads Horizon's Redis state directly to monitor supervisor status, queue depth, oldest job age, and failed-job rates.
- Developer Tools
- Software Only
Funding
Founders
Founder details are not available yet.
Product
Problem
Background job monitoring tools typically treat a process that exits with code 0 as healthy, even when the job performed no meaningful work. A scheduled task can finish cleanly while processing zero records, a scheduler can stop firing while the site remains up, and webhook delivery can fail silently—all without triggering traditional uptime or heartbeat alerts.
Solution
Crontinel provides outcome monitoring for background jobs and scheduled tasks by storing process status and business results as two separate states. It accepts check-ins via HTTP from curl, Node, Python, Sidekiq, and GitHub Actions, and offers a Laravel Composer package that hooks into the scheduler automatically without per-task ping calls. The platform reads Laravel Horizon's Redis state directly to monitor supervisor status, queue depth, oldest job age, and failed-job rates, alerting when a supervisor pauses or a queue backs up. When a job exits 0 but a rule required records and the receipt shows zero, Crontinel opens an incident and sends alerts via email, Slack, PagerDuty, or webhook. A later receipt with a passing result clears the incident, and multi-app support lets teams monitor polyglot stacks from one dashboard.
Target Audience
Primary users are development teams running Laravel applications, polyglot microservice stacks, or scheduled background jobs who need to detect when work silently stops happening. The platform serves both SaaS teams and self-hosted teams that want alerting without relying on generic URL-based heartbeat checks.
Features
- Separate tracking of process exit status and business outcome, so a missing record count is flagged as unhealthy even when exit code is 0
- HTTP check-in API with a single outcome body format shared across curl, Node, Python, Sidekiq, and GitHub Actions
- Laravel Composer package that auto-detects the scheduler, queue, and Horizon without adding thenPing calls per task
- Direct Redis-based Horizon monitoring for supervisor pauses, queue depth thresholds, oldest job age, and rolling failed-job rates
- Built-in status pages and an MCP server for AI agent integration
- Multi-app support with unified alerting across Laravel, Node, Python, Ruby, Go, .NET, and PHP runtimes