Cronicle

A simple distributed task scheduler and runner with a web UI, written in Node.js, for cron-style jobs across one or many servers.

5.9k stars, 509 forks JavaScript On GitHub since January 2016

What is Cronicle?

Cronicle replaces scattered crontabs with a central web interface. You define events, schedule them, and run them on one server or across a group of workers, then follow live logs and real-time stats for every job. Plugins in any language do the actual work. Its author, Joseph Huckaby, now develops xyOps as its successor, which adds visual workflows, server monitoring and alerting, and can import Cronicle schedules.

Good fit if

  • You run many cron jobs on several servers and want one place to see them.
  • You want a mature scheduler, developed since 2016, that handles both scheduled and on-demand jobs.

Look elsewhere if

  • You need workflows with dependencies between steps: Dagu or Kestra.
  • You are starting fresh: its author points new users to xyOps.

Before you adopt it

Cronicle is MIT-licensed. One developer maintains it, and his attention is moving to xyOps, so expect maintenance rather than new features. It needs Node.js on every server; the repository has no Docker setup.

Drafted with AI from the project's README and repository data, then checked against that data on 30 October 2026. Report a correction

Cronicle health: is it still maintained?

65 of 100, actively developed

  • Activity
    46 commits in the last 90 days, the latest on 28 October 2026.
    20 / 30
  • Contributors
    1 person wrote the 46 commits of the last 90 days; the most active wrote 100% of them.
    2 / 20
  • Releases
    15 releases in the last 12 months; the latest, v0.9.140, on 28 October 2026.
    19 / 20
  • Replies to issues
    Maintainers answered 83% of recent issues, with a median first reply after 4 hours.
    19 / 20
  • Security practices
    OpenSSF Scorecard 4.5 of 10.
    5 / 10

Read from GitHub on 1 November 2026. How the score works

Cronicle license: is it open source?

Cronicle uses MIT, an open-source license approved by the OSI.

  1. January 2016First published on GitHub.
  2. TodayMIT.

How to run Cronicle yourself

Docker
No Docker files in the repository
Compose file
None in the repository
Setup effort
Not rated: no compose file to judge from
Kubernetes
No Helm chart in the repository
Desktop and mobile
No app builds in GitHub releases
Interface languages
English only

Install instructions: cronicle.net or the README on GitHub.

Alternatives to Cronicle

  • DaguSelf-hostable workflow orchestrator for teams whose main work isn't orchestration. Declarative YAML over… 77 health · GPL-3.0 · 4.5k stars
  • Apache AirflowApache Airflow - A platform to programmatically author, schedule, and monitor workflows 87 health · Apache-2.0 · 47.3k stars
  • KestraOrchestrate everything, everywhere. The open-source control plane for workflows across data, infrastructure,… 85 health · Apache-2.0 · 30.1k stars
  • Trigger.devTrigger.dev – build and deploy durable AI agents and workflows 84 health · Apache-2.0 · 16.7k stars
  • DagsterAn orchestration platform for the development, production, and observation of data assets. 68 health · Apache-2.0 · 16.4k stars

All 33 projects in Workflow automation

Questions about Cronicle

Is Cronicle open source?

Yes. Cronicle is published under MIT, an OSI-approved open-source license.

Is Cronicle still maintained?

Its health score is 65 of 100 (actively developed). It had 46 commits in the last 90 days, the latest on 28 October 2026, and its latest release came out on 28 October 2026.

How do I run Cronicle?

The repository has no Docker files or app builds, so you build it from source. The README on GitHub has the steps.

What are the alternatives to Cronicle?

Close alternatives in the Workflow automation category include Dagu, Apache Airflow, Kestra.