Dagu is a self-hosted workflow engine for teams whose real work is not orchestration. Workflows are declarative YAML files written next to the scripts they run, and a single Go binary executes them — with schedules, dependencies, retries, human approval steps and a built-in web UI — without a metadata database or a message broker. Steps can be shell commands, Docker containers, Kubernetes Jobs or remote commands over SSH, so the scripts you already have are not rewritten into framework code.
depends: edges, which gives parallel branches and fan-in without a Python DSL or an SDK import. Delete the file and the scripts still run exactly as before.One binary, and state lives in local files under a Dagu home directory — no external database and no broker to operate. Installer scripts cover Linux and macOS, with Homebrew, Windows Scoop, npm, a container image at ghcr.io/dagucloud/dagu and Helm charts as alternatives; the Docker quick start is docker run --rm -v ~/.dagu:/var/lib/dagu -p 8080:8080 ghcr.io/dagucloud/dagu:latest dagu start-all. That command runs the scheduler, the web server and the workers in one process, with the UI on port 8080. Scaling out is optional: additional workers can be pointed at the same home directory to spread execution across machines, and an experimental Go API allows embedding the engine in another application.
Dagu sits between cron and a full platform. Cron gives you schedules but no dependencies, retries or history; Airflow and Temporal give you those at the cost of operating an orchestration stack or moving business logic into an SDK. Dagu keeps the workflow as configuration and the engine as a single process, which suits ETL and data-operation scripts, media conversion with ffmpeg, legacy runbooks and internal automation on one machine or a small fleet. Development is active, with frequent releases and roughly 4.6k GitHub stars, and the project is GPL-3.0 with a separate note on commercial embedding of the Go API. The optional Dagu Console monitoring service is an opt-in, outbound-HTTPS, metadata-only extra; the engine itself runs fully self-hosted.