Declare
A framework extension reads Hangfire, Quartz.NET, Celery, or Laravel schedules. Base SDKs and raw HTTP can declare other recurring work.
Product overview
The reliability layer for work that runs without an audience.
CronRadar turns recurring jobs into a current inventory, watches their expected lifecycle, and tells the responsible team when a run is missed, failed, stuck, or disappears.
- No per-job dashboard setup with native extensions
- Five alert channels
- Fixed capacity plans
The product
Operational truth before another dashboard.
CronRadar shows the health of automated work by application. It does not replace the scheduler, logs, or on-call system you already use.
How it works
From code to alert in three contracts.
Observe
Start, completion, failure, and expected schedule signals establish whether the latest run is healthy, late, failed, or timed out.
Notify
An incident is recorded and dispatched to the configured email, Slack, webhook, Discord, or PagerDuty destination.
Evidence, not promises
Behavior bounded by the working system.
30-second evaluation cadence
The monitoring worker checks expected schedules every 30 seconds. Alert delivery time is not guaranteed.
Constants.Monitoring.CheckIntervalSeconds
5-second SDK request timeout
Official SDK HTTP calls are bounded and monitoring errors are caught.
Constants.Sdk.RequestTimeoutSeconds
Schedule reconciliation
Framework integrations synchronize declared jobs so the inventory can follow code and scheduler changes.
Five live failure modes
Detect missed, failed, stuck, disappeared, and completed runs that violate a bounded outcome expectation.
Five supported channels
Email, Slack, webhook, Discord, and PagerDuty are included on every plan.
Bounded history
Ping history is retained for 30 days and alert history for 90 days.
30 days / 90 days
Choose your path
Framework depth when it exists. A small API when it doesn't.
Reference path
Hangfire
Startup and periodic registry synchronization plus execution filtering.
Native .NET
Quartz.NET
Trigger discovery, schedule translation, and a scheduler-wide job listener.
Universal path
Base SDKs and raw HTTP
Wrap .NET, Node.js, Python, or PHP work, or report a complete lifecycle with curl.
Product boundaries
What CronRadar does not try to become.
A scheduler replacement?
No. Hangfire, Quartz, cron, Celery, or Laravel still schedules and executes the work.
A log or tracing platform?
No. CronRadar records bounded lifecycle evidence and links the incident back to the team’s investigation tools.
An on-call scheduler?
No. Route to PagerDuty or another destination; CronRadar does not build escalation calendars.
A website uptime or status-page product?
No. The product is scoped to scheduled and recurring automation reliability.
Start with the automation customers would notice first.
Use the card-free Team trial, then stay on Free or explicitly choose a fixed paid plan.