Cronicle

Cronicle is a web-based task scheduler that replaces the scattered crontab files across your servers with a single dashboard. Schedule jobs, watch them run in real time, and see a history of every execution with timing, CPU usage, memory consumption, and the full log output. For anyone managing more than a handful of scheduled tasks, the visibility alone is worth the switch from raw cron.

The architecture separates a primary server from worker servers. The primary holds the schedule and assigns jobs; workers execute them. If you run a single machine it handles both roles. When you add a second server as a backup, Cronicle will automatically promote it to primary if the original goes down, keeping your schedule running without manual intervention. Additional worker servers distribute job execution across machines.

Plugins are the integration point. A plugin is any executable — a shell script, a Python file, a Node.js script, or a compiled binary. Cronicle passes job parameters as JSON via stdin and reads status updates and log output via stdout. This means any script you already have can become a scheduled Cronicle job with minimal changes. The HTTP plugin covers common API call and webhook scenarios without writing any code.

The live log viewer streams job output to the browser in real time over WebSockets. You can watch a long-running import or processing job complete without needing to SSH in and tail a log file. When a job fails, the output is preserved and accessible from the job history.

One thing worth noting before committing: the author announced xyOps as Cronicle’s successor in early 2026. Cronicle will continue to receive bug fixes and security patches, but active feature development is moving to the new project. For most scheduling use cases this does not matter immediately, but it is relevant context if you are building long-term infrastructure around it.

Cronicle: Pros & Cons