Cylc is the workflow engine and meta scheduler built for cycling workflows, where one task graph repeats over an unbounded sequence of cycle points and each cycle can depend on the one before it.
Cylc is an open source workflow engine and meta scheduler designed for cycling workflows. Where a conventional pipeline tool runs a graph once per trigger, Cylc runs the same graph repeatedly over a sequence of cycle points, and lets a task in one cycle depend on a task in the previous cycle. Its scheduler keeps an unbounded cycling suite running continuously, handling retries, held and triggered tasks, and inter cycle dependencies without an operator having to restart anything between cycles.
That model is why Cylc is the engine behind operational numerical weather prediction and climate research at national meteorological services and academic computing centres. It suits any team running repeating, time indexed computation: forecast suites, rolling data assimilation, nightly or hourly reprocessing, long climate integrations, and research workflows that have to survive task failure and be resumed cleanly. Workflows are defined in a readable configuration file that describes the graph and the runtime for each task, validated before they run, and driven from either the command line or a live web interface that shows the state of every task in every cycle.
cloudimg ships both halves of Cylc, the scheduler and the web UI Server, installed together into one virtual environment, so the appliance is a working workflow host rather than a bare command line and the interface answers as soon as first boot finishes. A worked example workflow is included, so a new instance can run a real cycling task graph to completion within a minute of launch. Security is the reason to take this image rather than install it yourself: a Cylc UI can trigger workflow tasks, which means running code, so nothing is shipped that could serve it unauthenticated. No token, password or cookie secret is baked into the image, the UI Server refuses to start at all until first boot has minted a password unique to that VM into a root only file, and the engine and the interface both run as a dedicated unprivileged account with no sudo rights. The server itself is bound to the loopback interface and published only through a TLS reverse proxy that serves an explicit allowlist of the product's own paths, with a certificate minted for that VM. Run directories ride on a dedicated, independently resizable data disk, the base is fully patched with unattended security upgrades enabled, and every deployment is paired with a step by step deploy guide, backed by 24/7 cloudimg support.
Real screenshots taken while testing this image against its deployment guide.