Crontinel

Platforms: web dashboard at app.crontinel.com. Check-ins from curl, Node, Python, Sidekiq, and GitHub Actions. Laravel gets a dedicated Composer package.

Main benefit: you find silent failures before your users do.

Key Features

• Outcome rules. Set a minimum, such as 1 processed record. A zero count fails the check even with exit 0.

• Missing evidence fails. A receipt without a count is not healthy.

• Automatic recovery. A later receipt with a passing result closes the incident.

• One JSON body. Fields include request_key, command, status, exit_code, started_at, finished_at, and outcomes.metrics.

• Scheduler checks. Spot schedule:run arriving late or stopping after a deploy.

• Worker and queue views. Per-worker status, paused detection, queue depth trend, and failed job rate.

• Dashboard. Run history keeps exit 0. A separate outcome column shows the business result.

• Email alerts for failure and for recovery.

• Assistant access. Cursor, Claude Code, and Codex read the same incident. The packet states completion is not business success.

• Limits. The free plan covers one app. Queue depth and Horizon freshness appear only on Laravel, and only when the snapshot is reported.

Best For

• Laravel teams running scheduled tasks, queues, and Horizon.

• Developers with cron jobs in Node, Python, Ruby, or GitHub Actions.

• Small teams without a dedicated ops engineer.

• Teams using AI coding assistants for incident triage.

• Teams leaving thenping.me. Crontinel says thenping.me is no longer maintained.

Top Use Cases

• Catch a nightly report job with a clean exit and zero records.

• Detect a stopped scheduler after a deploy while the site returns 200.

• Find a crashed worker while the queue manager still shows running.

• Watch queue backlogs, such as an email queue with thousands of waiting jobs.

• Monitor webhook delivery failures and stalled callback queues.

• Check GitHub Actions scheduled workflows.

Integrations
Present:

• HTTP ingest endpoint. Auth uses a Bearer ingest key.

• curl for system cron.

• Node through fetch or node-cron.

• Python through a script or a Celery finally-block.

• Sidekiq through a Net::HTTP post.

• GitHub Actions with a secret plus curl or Python.

• Laravel through the crontinel/laravel Composer package.

• MCP server on GitHub. The MCP key differs from the ingest key.

• Email alerts.

Missing or not stated:

• No npm package, PyPI package, or Ruby gem. The site does not claim unowned language SDKs.

• Slack and webhook alerts are not on the public card.

• Export formats are not stated.

• A public read API, rate limits, data retention, SSO, and self-hosting are not stated.

• Paid plan limits and prices are not published.

Pros

• Separates process status from business result.

• Works with any runtime that sends an HTTP request.

• Needs no SDK.

• Free to start with no card.

• Reads the receipt after the process exits, so an alert does not die with the host.

• Email names the zero count and does not invent a cause.

• Laravel package and MCP server sit on GitHub.