dagucloud /dagu
Self-hostable workflow orchestrator for teams whose main work isn't orchestration. Declarative YAML over your scripts, SSH commands, containers, etc; keep workflows separate from business logic. One binary, no database, runs on limited H/W resources. Alternative to Airflow / Cron / Job Scheduler.
★ 4,624⑂ 404👁 18⑃ 2,719● 1,192▤ 332
4,624
stars
404
forks
18
watchers
2,719
prs
1,192
issues
332
releases
README
Docs ·
CLI ·
API ·
Examples ·
Live demo
(username/password: demouser) ·
Discord
Dagu
Dagu is a local-first workflow engine for operations and internal automation. It is open source and self-hostable: a single binary with a built-in Web UI, no external database or message broker, running on Linux, macOS, and Windows. Define DAGs in a declarative YAML format. It natively supports shell commands, Docker containers, Kubernetes Jobs, remote commands via SSH, and more through Dagu Actions.
Dagu turns existing scripts and runbooks into production workflows with scheduling, retries, human tasks, and run history. It runs where your data and credentials live: on-prem, air-gapped, edge, or cloud, and scales from a single node to a fleet of workers.
Highlights:
- Single binary installation.
- Self-contained: no external DBMS or message broker required.
- Runs on Linux, macOS, and Windows.
- Declarative YAML format for defining DAGs.
- Run existing shell commands, Docker containers, Kubernetes Jobs, and remote commands over SSH without modifications.
- Compose reusable Sub-DAGs and run work in parallel with concurrency controls.
- Schedule workflows with cron syntax, timezones, overlap policies, and catch-up windows.
- Keep logs, run history, retries, notifications, and webhook triggers in one place.
- Built-in MCP server for inspecting workflows and runs, maintaining Wiki pages, applying changes, and controlling runs.
- Optional monitoring in Dagu Console: every server's runs and trends in one place, and an email when a workflow fails or a server stops reporting. Opt-in, outbound HTTPS only, metadata only.
Quick Look
For a quick look at how workflows are defined, see the examples.
| Run Details | Step Logs | Wiki |
|---|---|---|
| !Run details in dark mode | !Workflow logs in dark mode | !Workflow Wiki in dark mode |
Try it live: Live Demo (credentials: demouser / demouser)
Why Dagu?
Orchestration is not your main work. You have scripts and containers that already work. You want a schedule, retries, dependencies, and a place to see logs. The usual options each have a cost:
- cron runs commands, but gives you no dependencies, no retries, no history.
- Airflow orchestrates, but you operate a platform for it (scheduler, metadata database, workers, a Python environment), and your jobs get rewritten as @dag/@task framework code.
- Temporal gives durable execution, but your business logic moves into its SDK and programming model.
You wanted to schedule some jobs. Now you operate a second system, and the orchestrator lives inside the code it was supposed to serve.
Dagu treats workflow structure as configuration, not code. Order, dependencies, retries, schedules, and human tasks go in one YAML file next to your scripts; the engine that runs them is a single process:
sh
Traditional Orchestrator Dagu
┌────────────────────────┐ ┌──────────────────┐
│ Web Server │ │ Top issues
#1814let dagu connect to codex / antrophics agents sdk13 comments · 2026-03-20#1452[FEAT] Add webhook callback after task completion15 comments · 2025-12-06#1181Add file triggers to run DAGs on file events10 comments · 2025-08-10#2047Queues are not used when DAG is called as sub dag9 comments · 2026-04-28#3288Feedback: replacing workspaces with projects in v3.07 comments · 2026-10-22#2024Enabe/disable dag regardless of schedule7 comments · 2026-04-21#1016feat: Support for operators to enhance pre conditions6 comments · 2025-06-15#3043xlsx.update_rows fails when rows is empty5 comments · 2026-10-07
Latest release
v2.27.0 v2.27.0 2026-11-16Summary
This release adds schedule slots, run dates, and backfills, so you can run a DAG for past or missed schedule slots and track each run.
- Backfills: Plan, start, and watch backfills over a range of schedule slots from the CLI, API, MCP, or the Run menu in the UI. Dagu records the slots a DAG missed while paused or down and offers to backfill them.
- Schedule slots and dates: Start a run for a specific slot with --scheduled-at or the run dialog. A new dates block resolves the dates each run loads, readable as ${dates.NAME}, and you can preview them before the run starts.
- Upgrades and