jhuckaby /Cronicle

A simple, distributed task scheduler and runner with a web based UI.

★ 5,878⑂ 510👁 63⑃ 63● 727▤ 268
JavaScriptNOASSERTIONCreated 2016-01-08cronicle.net
Download: Version 0.9.146Version-0.9.146 ↓0.9.1462026-11-13
+1
Daily
5,878
stars
510
forks
63
watchers
63
prs
727
issues
268
releases

README

xyOps™: The Future of Cronicle

Meet xyOps, the next generation of Cronicle, built by the same creator.  It carries Cronicle's scheduling and plugin philosophy forward into a complete, self-hosted platform for job scheduling, visual workflows, server monitoring, alerting, and incident response.

Explore xyOps | Migration Guide | Install | GitHub



Fully open source. Self-hosted. No telemetry. No feature gates.  Every xyOps application feature is free, including SSO.  Paid plans provide optional human support and hands-on assistance.

 Why move to xyOps?

Keep the scheduling concepts you know, and give your automation room to grow:

- Build visual workflows: Connect jobs with branching, parallel execution, human approval, and reusable sub-workflows.
- Watch jobs and servers together: See live metrics, processes, network connections, and historical performance in one place.
- Investigate failures with context: Capture server snapshots when alerts fire, open tickets, and launch automated remediation.
- Simplify your workers: Run jobs through lightweight xySat agents without installing Node.js on every worker server.
- Bring your existing automation: Import Cronicle schedules and configuration, keep compatible plugins, and automatically convert multiplexed events into workflows.

 Bring your Cronicle schedules forward

You don't have to rebuild your schedule from scratch.  xyOps includes a Cronicle data importer and a plugin compatibility mode to help you get started:

1. Set up xyOps using the Self-Hosting Guide, then add your worker servers before importing so event targets can be matched correctly.
2. Export your Cronicle data using the built-in export command.  This includes events, categories, plugins, users, API keys, and server groups.  Job history and logs are not included.
3. Import through the xyOps interface: Sign in as an administrator, open System, click Import Data..., and select Cronicle Data Format to upload your export.
4. Review and test your setup: Check the import report, event settings, and user privileges.  Enable Cronicle plugin compatibility mode for existing plugins that need it.  When you're ready to switch, pause Cronicle's scheduler before enabling scheduling in xyOps to avoid duplicate runs.

Start with a fresh xyOps installation for your migration trial.  Importing replaces conflicting data in xyOps, aborts its running jobs, clears its queues, and pauses its scheduler.  xyOps is a separate application, so plan to test your imported jobs before switching production over.

Prefer a familiar look?  You can even restore the Cronicle name and logo in the xyOps interface.

Read the full Cronicle migration guide for compatibility details and step-by-step instructions, or try xyOps in one Docker command to explore it first.

 What about Cronicle?

Cronicle will continue to receive maintenance, primarily bug fixes and security patches.  xyOps is the path forward for new features and capabilities.  The Cronicle documentation and 

Top issues

Discussions

Latest release

Version 0.9.146 v0.9.146 2026-11-13
- Dep: Bump basic-ftp override to v6.2.6 for vuln fixes.
- Dep: Bump pixl-server-user to v2.0.5 for improved email and full name field hardening.

Snapshot: 2026-11-16T09:23:14Z · Data license Apache-2.0 · JSON