dkron-io/dkron

What it does

You run it as a cluster: server processes that hold the schedule and agent processes that do the work. The servers agree on the schedule using Raft, a protocol for keeping several machines consistent, and find each other using Serf, which spreads membership information between them by gossip. Each job can be pointed at any combination of machines, so a job can run on one, on all, or on everything with a particular label. A web screen built as a single-page application lists the jobs and their runs at /ui. Scaling is a single command: more server processes or more agents. It is written in Go and runs on Linux, macOS and Windows. The newest release is v4.2.1, from 7 October 2026. What the repository page does not do is explain the job types: it describes running scheduled commands on the cluster and leaves the list of executors to the documentation site. There is also a file named COMM-LICENSE in the repository alongside the LGPL-3.0 licence, and the page does not say what it covers.

Why it matters

Who it suits. Anyone whose scheduled jobs matter enough that a dead machine is an incident — nightly database dumps, billing runs, data imports that something downstream depends on. It is also the right answer when the jobs have to run on many machines at once, because targeting a group is built in rather than scripted. Skip it if one machine running one schedule has never let you down, because the clustering is the entire cost here and the entire benefit.

Verdict. A mature answer to a narrow problem, maintained since 2015, and the fourth-largest cost is understanding what you have built. Three machines agreeing about a schedule is more moving parts than most small setups need, and the honest question is whether a missed job would actually hurt. jhuckaby/Cronicle at 5,800 stars is the friendlier alternative with a much better interface and a single primary server, and Edition 45 covered it — note that its own page now announces a successor project while Cronicle itself continues to get bug and security fixes. kestra-io/kestra at 28,000 stars is the choice when the jobs form a pipeline with dependencies rather than a list of schedules, also covered in Edition 45. Two things to check before adopting it: the repository page gives no package-manager commands, so installation details live on the project's own site, and the COMM-LICENSE file sitting next to an LGPL-3.0 licence is worth reading if the plan is to build a product on this.