Helm
Helm runs two release trains in lockstep while v3 walks toward end-of-life.
Comparison · Infra & APIs
Cronicle vs rush
A side-by-side editorial comparison of Cronicle and rush — release velocity, themes, recent moves, and the top alternatives to consider.
Cronicle vs rush: at a glance
What is Cronicle?
The job scheduler's release stream is now almost entirely vulnerability patching and authorization hardening.
Cronicle is a self-hosted distributed job scheduler with a web UI, plugin-defined job types, and a multi-server cluster model. Its 0.9.11x-0.9.12x releases are dominated by two threads: dependency bumps closing published vulnerabilities in sanitize-html, nanoid, shell-quote, ws, and nodemailer, and a sustained authorization review of its own. Version 0.9.125 restored cluster authentication clock validation, aligned job log access checks with job details, moved event filtering server-side, and hardened authorization for event placement and manual run targets; 0.9.124 restricted event and job parameters to those a plugin actually defines.
What is rush?
Rush spent 2026 making distributed task ownership correct, starting with a breaking 1.0.
rush is the Redis-backed distributed computing backend behind mlr3's parallel tuning: workers pull tasks, push results and are tracked through heartbeats. Since 1.0.0 in March 2026 it has shipped five releases in four months, almost all correcting how tasks and workers are owned and identified under failure. The most recent lets each worker start in its own mirai call so it can spawn local daemons.
Cronicle vs rush: editorial side-by-side
Cronicle
5.0INFRA · APIS
The job scheduler's release stream is now almost entirely vulnerability patching and authorization hardening.
◆ Current state
Cronicle is a self-hosted distributed job scheduler with a web UI, plugin-defined job types, and a multi-server cluster model. Its 0.9.11x-0.9.12x releases are dominated by two threads: dependency bumps closing published vulnerabilities in sanitize-html, nanoid, shell-quote, ws, and nodemailer, and a sustained authorization review of its own. Version 0.9.125 restored cluster authentication clock validation, aligned job log access checks with job details, moved event filtering server-side, and hardened authorization for event placement and manual run targets; 0.9.124 restricted event and job parameters to those a plugin actually defines.
◆ Where it's heading
The pattern in 0.9.124 and 0.9.125 is not incidental fixes but a systematic pass over where the server trusted client input — parameters, filters, targets, and log access were each independently tightened, and password hashing moved from the unmaintained bcrypt-node to bcryptjs in 0.9.123. Feature work is essentially absent from this window; what is not security is dependency maintenance or narrow platform compatibility, like FreeBSD process monitoring in 0.9.126. For a scheduler that executes arbitrary commands across a cluster, that allocation is defensible.
◆ Prediction
Given that each recent release closes another category of over-trusted input, expect the hardening sweep to continue through the remaining API surface before feature work resumes.
rush
2.5INFRA · APIS
Rush spent 2026 making distributed task ownership correct, starting with a breaking 1.0.
◆ Current state
rush is the Redis-backed distributed computing backend behind mlr3's parallel tuning: workers pull tasks, push results and are tracked through heartbeats. Since 1.0.0 in March 2026 it has shipped five releases in four months, almost all correcting how tasks and workers are owned and identified under failure. The most recent lets each worker start in its own mirai call so it can spawn local daemons.
◆ Where it's heading
The through-line is moving responsibility from the controller to the worker. 1.0.0 rewrote the task lifecycle and dropped the seed mechanism; 1.2.0 moved fail_tasks(), finish_tasks(), pop_task() and push_running_tasks() from Rush onto RushWorker so only the worker that ran a task can mark it done, and gave worker ids random suffixes so they cannot collide. 1.1.0 had already removed phantom failed tasks when a worker crashes between evaluations.
◆ Prediction
With ownership and identity settled, the remaining pressure points are heartbeat and lost-worker detection; expect the next releases to tighten failure recovery rather than add API surface.
Alternatives to Cronicle and rush
Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Cronicle or rush.
goodpractice
The R package-quality checker returns from CRAN limbo with checks you can select by category.
quarto
Quarto's editor extension is quietly becoming Positron-first while keeping VS Code parity.
q2
Ten releases in six days, methodically porting Quarto's surface into a Rust binary.
pkgcache
The metadata cache under pak now speaks to authenticated and corporate repositories.
packrat
R's old dependency manager now runs on a vendored copy of its own successor.
See all Cronicle alternatives → · See all rush alternatives →
Recent activity from Cronicle and rush
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 21h agoCroniclenanoid vulnerability bump, pixl-server-user to v2
- 1d agoCroniclesanitize-html and nanoid vulnerability fixes
- 8d agoCronicleFreeBSD compatibility for process monitoring
- 14d agoCronicleCluster auth clock validation restored, five authorization gaps closed
- 21d agorushWorkers start in their own mirai call so they can create local daemons
- 28d agoCronicleEvent and job parameters restricted to plugin-defined ones
- 1mo agorushTask lifecycle moves onto the worker; worker ids can no longer collide
- 1mo agoCroniclePassword hashing moved from bcrypt-node to bcryptjs
- 3mo agorushPhantom failed tasks and missed results fixed
- 4mo agorushSmaller Redis payloads and vector-valued task parameters
- 4mo agorushRush 1.0 rewrites the task lifecycle and drops the seed mechanism ⚡
- 9mo agorushwait_for_workers() can target a count or specific ids
Frequently asked questions
What is the difference between Cronicle and rush?
They serve adjacent needs but don't currently overlap on shipped themes. Cronicle is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is Cronicle better than rush?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Cronicle is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
What are the best alternatives to Cronicle?
Top Cronicle alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Cronicle alternatives" section above for the current picks, or visit /alternatives/cronicle for the full list with editorial commentary on each.
What are the best alternatives to rush?
Top rush alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "rush alternatives" section above for the current picks, or visit /alternatives/rush for the full list with editorial commentary on each.