Crontinel
Cron and background-job monitoring that separates process completion from business outcomes and alerts when finished jobs do no work.
About Crontinel
Crontinel is a monitoring tool for cron jobs, scheduled tasks, workers, and background processes. It separates a process exit status from the business result, so a job that exits with code 0 can still be marked failed when it processed no records or missed a required outcome.
Applications send Crontinel one JSON HTTP receipt containing fields such as status, exit code, timestamps, and outcome metrics. Crontinel compares those values with configured rules, treats zero or missing counts as failures when required, and clears an incident when a later receipt passes.
The service supports check-ins from curl, Node, Python, Sidekiq, and GitHub Actions. An optional Laravel package can attach receipts from the scheduler and report queue depth and Horizon freshness. The dashboard shows run history, schedule lateness, worker status, queue depth, and failed-job rates.
Crontinel sends email alerts for zero-work incidents and later recovery, including when the monitored application or assistant is offline. Its incident packet can be read by coding assistants such as Cursor, Claude Code, or Codex. A free plan supports one app, while Starter, Pro, and Max paid plans are still being prepared.
Features
- Monitors Laravel scheduler, Horizon queues, workers, and agents
- Routes alerts to Slack, PagerDuty, email, or webhook
- Provides a dashboard showing job run times, exit codes, and queue depth
- Track worker status, queue depth, failed-job rate, schedule lateness, and run history
- Connect from curl, Node, Python, Sidekiq, GitHub Actions, or the optional Laravel package
Use cases
- Detecting silent failures in cron jobs not visible in uptime monitors
- Tracking queue backlogs and worker crashes before they impact customers
- Verifying scheduler and queue health after deploys with CLI checks
- Review late or missed invoice, notification, ETL, and webhook jobs
- Give coding assistants structured incident packets for debugging
Screenshots
Frequently asked questions
Does Crontinel support languages other than Laravel PHP?
Yes, Crontinel offers SDKs for Node.js, Python, Go, Rust, Ruby, and .NET besides Laravel PHP.
How does Crontinel alert me when a job fails or queue backs up?
It sends routed alerts to your chosen channel such as Slack, PagerDuty, email, or webhook with quiet hours and auto-resolve features.
Can Crontinel be self-hosted?
Yes, the open-source packages are MIT licensed and can be self-hosted, offering full queue and cron visibility without requiring the cloud dashboard.
Are Slack and webhooks available for alerts?
They are not listed on the current public alert card. Email is the documented alert channel.
Which credential is used for check-ins?
Applications use the CRONTINEL_INGEST_KEY; the site states that this is separate from the MCP key.
What we verified
- Public API?
- Yes, an HTTP JSON receipt endpoint is documented
- Self-hostable?
- Not stated
- Free tier without a credit card?
- Yes, one app at $0 per month and no card required
- Pricing model?
- Free single-app plan with paid plans planned
- Price?
- $0 per month for one app; paid pricing not published
- Data region / hosting location?
- The dashboard preview shows eu-west-1; overall hosting scope is not stated
- Named integrations?
- curl, Node, Python, Sidekiq, GitHub Actions, and an optional Laravel package
Could not be verified
- Self-hosting instructions, paid-plan pricing, detailed usage limits, data retention, complete integration availability, and the exact hosting region for customer data were not stated.
0 comments
Sign in to leave a comment.
No comments yet. Say something useful and be the first.