Cronicle is a free, open-source task scheduler and job runner created by developer Joseph Huckaby and released under the MIT license. Written in Node.js, it acts as a modern replacement for traditional Unix cron, adding a web-based dashboard, distributed job execution, and real-time monitoring.
The project requires no external database — job definitions, schedules, and logs are stored as JSON files on disk — which keeps deployment and backups simple compared to schedulers that depend on a separate database server.
Key Features
Cronicle handles scheduled recurring jobs, one-time on-demand jobs, and event-driven jobs, with schedules configured through a visual multi-select time picker rather than raw cron syntax.
Jobs can be distributed across any number of worker servers, with automatic discovery of nearby nodes, automatic failover to backup servers, and automatic retries for transient failures.
The web dashboard provides live log streaming, graphical progress bars with estimated completion times, and historical CPU and memory usage graphs for each job.
Pricing
Cronicle is completely free and open source under the MIT license, with no paid tiers, vendor, or subscription of any kind. Users self-host it on their own servers or infrastructure and are responsible for their own hosting costs.
There is no commercial company behind Cronicle; it is a community-maintained project accepting contributions through its public GitHub repository.
Key Features
Visual job scheduling — Configure recurring jobs through a multi-select time picker for years, months, days, weekdays, hours, and minutes instead of raw cron syntax.
Distributed worker execution — Distribute job execution across any number of worker servers with automatic discovery and load balancing.
Automatic failover and retries — Jobs automatically fail over to backup servers and retry on transient failures without manual intervention.
Live log streaming — Real-time log viewer for running jobs, with graphical progress bars and estimated time remaining.
Historical performance graphs — Tracks average CPU and memory usage per job over time to help detect performance regressions early.
No database required — All job data, schedules, and logs are stored as JSON files on disk, simplifying deployment and backup.
API keys and webhooks — Authenticate external applications with API keys and trigger custom webhooks on job success, failure, or completion.
Pros & Cons
Pros
Completely free and open source under the MIT license with no paid tiers
No external database dependency makes deployment and backups straightforward
Distributed, multi-server job execution with automatic failover goes well beyond plain cron
Real-time web UI with live logs and historical performance graphs improves visibility over standard cron
Cons
Requires self-hosting and ongoing maintenance since there is no managed/hosted version
No dedicated commercial support; help comes from documentation and community channels
Less suited to complex, dependency-graph-based workflows compared to dedicated orchestration tools like Airflow
Smaller ecosystem and integration library than commercial scheduling and monitoring platforms
Frequently Asked Questions
Is Cronicle free to use?
Yes. Cronicle is fully free and open source under the MIT license, with no paid tiers or subscription required.
Does Cronicle need a database?
No. Cronicle stores all job definitions, schedules, and logs as JSON files on disk, so no external database server is required to run it.
Can Cronicle run jobs across multiple servers?
Yes. Cronicle supports distributing jobs across any number of worker servers, with automatic discovery of nearby nodes and automatic failover to backups.
Who maintains Cronicle?
Cronicle was created by developer Joseph Huckaby and is maintained as an open-source project on GitHub, with contributions from the community.
How is Cronicle different from regular cron?
Unlike plain Unix cron, Cronicle adds a web-based UI, visual scheduling, multi-server job distribution with failover, live log streaming, and historical performance tracking.