dkron-io/dkron

Dkron - Distributed, fault tolerant job scheduling system https://dkron.io

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 54 minutes ago
Added to GitGenius on September 14th, 2026
Created on June 10th, 2015
Open Issues & Pull Requests: 35 (+0)
GitHub issues: Enabled
Number of forks: 418
Total Stargazers: 4,736 (+0)
Total Subscribers: 90 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 14.1 days
Mean response time: 156.1 days
90th percentile: 174.6 days
Tracked items: 84

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 14
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,253 days
Stale 30+ days: 14
Stale 90+ days: 12

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • enhancement (23)
  • triage (14)
  • bug (10)
  • 4.x (5)
  • help wanted (4)
  • question (4)
  • 3.x (2)
  • invalid (2)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Dkron is a distributed, fault-tolerant job scheduling system for cloud native environments.

Dkron solves the problem of reliably scheduling and executing cron jobs across a cluster of servers without single points of failure. It uses the Raft protocol and Serf gossip protocol to maintain consistency and fault tolerance across distributed nodes. Jobs can be configured to run on any combination of servers in the cluster, and the system automatically handles node failures and recovery.

Dkron suits teams running scheduled workloads in cloud or on-premises clusters who need high availability and don't want to manage cron jobs on individual machines. It provides a web UI for job management and an API for programmatic access. The tool is designed to be simple to install and operate, running on Linux, OSX, and Windows. It draws inspiration from Google's distributed cron research and Airbnb's Chronos, incorporating similar reliability patterns.

The project maintains active development with comprehensive documentation and a focus on developer experience. The codebase includes tooling for local testing via Docker Compose, with integrated email testing support through Mailpit for validating notification features during development. The project provides scripts for running the full CI test suite locally before pushing changes, enabling developers to catch issues early. Frontend development uses React Admin as a single-page application for the dashboard interface.