Choose an integration
Available framework integrations discover the scheduler's registry and report lifecycle automatically. Base SDKs cover other schedulers and explicit wrappers. When SDK setup is unavailable, use manual HTTP reporting; it does not provide automatic discovery.
Choose your library
HangfireAuto-discovery SDKQuartz.NETAuto-discovery SDKCeleryHTTP · SDK unavailable
LaravelHTTP · SDK unavailable
.NETSDK
Node.jsHTTP · SDK unavailable
PythonHTTP · SDK unavailable
PHPHTTP · SDK unavailableHTTP / cURLAny scheduled job
LaravelHTTP · SDK unavailable.NETSDKNode.jsHTTP · SDK unavailablePythonHTTP · SDK unavailablePHPHTTP · SDK unavailableHTTP / cURLAny scheduled jobEach guide includes installation, configuration, and verification. HTTP setup reports individual jobs; it does not discover your scheduler.
Let an assistant identify my stackPublished package availability
Checked 2026-09-20. Repository documentation can describe a release that is not yet published. Open the setup guide for current limitations.
| Scheduler or runtime | Published package | Setup available now |
|---|---|---|
| Hangfire | CronRadar.Hangfire 0.1.0 | SDK setup and release notes |
| Quartz.NET | CronRadar.Quartz 0.1.0 | SDK setup and release notes |
| Celery | cronradar-celery 0.1.0 | Manual HTTP; SDK unavailable |
| Laravel scheduler | cronradar/laravel not published | Manual HTTP; SDK unavailable |
| .NET base SDK | CronRadar 1.0.13 | SDK setup and release notes |
| Node.js base SDK | cronradar 0.0.6 | Manual HTTP; SDK unavailable |
| Python base SDK | cronradar 0.1.0 | Manual HTTP; SDK unavailable |
| PHP base SDK | cronradar/php not published | Manual HTTP; SDK unavailable |
For shell scripts, crontab, or another language, use the HTTP API contract. Bull/BullMQ auto-discovery is still in progress and is not a supported integration.