Cronicle is a self-hosted task scheduler and job runner with a web front end — a distributed replacement for cron. Instead of a crontab on every machine, you define events in a browser UI, point them at shell commands or plugins, and let a primary server dispatch the work to as many worker servers as you need. Every run streams its log live, and each job keeps its own CPU and memory history. It is written in Node.js and released under the MIT licence.
The vocabulary is worth knowing before you install it. A server group is a set of machines that events can target; each server is the primary (keeps time and assigns jobs), a backup (promoted if the primary fails) or a worker (idle until given work). An event is a schedule entry pointing at a plugin and a target; a job is one running instance of an event. Everything — events, categories, plugins, users, API keys, server groups — can be exported and imported through the built-in command line tool.
Cronicle runs on Linux and macOS and is installed with the project’s own installer, which fetches a release tarball and can install Node.js for you; there is no distribution package and no officially maintained container image, so the supported path is the installer on each server you want in the cluster. It keeps its data in local files under its install directory rather than in an external database, which makes a single-server install very light but means backup is a directory copy. The web UI listens on port 3012 by default. Windows is not a supported host.
Cronicle still works and is still maintained, but the author has moved new development to xyOps, a successor built by the same person that carries the scheduling and plugin model forward into visual workflows, server monitoring, alerting and incident response. Cronicle itself is now in maintenance mode — bug fixes and security patches rather than new features — and there is a documented migration path: export the Cronicle data, import it into xyOps, and pause Cronicle’s scheduler before switching over. Choose Cronicle when you want a small, stable, well-understood cron replacement that you can run today; choose xyOps when you want the newer platform the author is actively building. Do not run both schedulers against the same jobs at once.