Run Dagu without giving up your execution boundary.
Run Dagu as a self-hosted server, with distributed workers where you need them. Workflows run where your network, secrets, and customer data already live, while Dagu keeps catalog, access, runs, logs, and approvals in one place.
Workflow control without moving the work
Dagu keeps orchestration, access, logs, and approvals in one place while your commands keep running inside your own execution boundary.
Deployment model
Run local, self-hosted, or distributed.
Start with one binary, add distributed workers when needed, and keep sensitive execution close to your private network and secrets.
View pricingLocal
Single binary
Run the server and scheduler together on a single node for internal tools and automation.
Self-hosted
Private control plane
Operate Dagu inside your own infrastructure with your own auth and storage.
Distributed
Private workers
Keep execution near private systems while centralizing catalog and visibility.
Execution boundary
Commands run where network and secrets already live.
Build the operational control plane around your workflows.
Work with the Dagu team on deployment, security, scale, and workflow design for production use cases.
Dagu is most useful when it wraps real operational work: scripts, containers, SQL, API calls, approvals, and Agent Harness workflows.
Solution partner focus
OIDC/SSO, RBAC, workspaces, and tenant isolation
MCP, distributed workers, queues, and high-volume run history
Persistence and backup strategy for production operations
Secrets, auditability, and least-privilege execution
Event routing, webhooks, notifications, and incident workflows
Container isolation and private worker deployment
A small runtime with explicit operational boundaries.
Dagu receives workflow intent, runs the declared commands, and leaves a reviewable record of status, logs, outputs, and approvals.
Receive
Accept workflow definitions, API calls, MCP requests, and manual operations.
Run
Execute shell, containers, SQL, HTTP, SSH, chat completion, and Agent Harness steps.
Operate
Track logs, artifacts, approvals, audit events, queues, and retry decisions.
Use cases
Wrap real operational work in workflows that are visible, repeatable, and governed.
Agent Harness workflows
Run 15 built-in agent CLIs—including Claude Code, Codex, Gemini CLI, Cursor, and DeepSeek Harness—or define a custom provider.
Human approvals
Pause sensitive operations for review before a workflow continues.
Infrastructure runbooks
Turn shell, SSH, Kubernetes, and HTTP procedures into controlled workflows.
Media and batch jobs
Run long-lived command workloads with logs, artifacts, and retries.
Data operations
Coordinate SQL, DuckDB, exports, imports, and reporting jobs.
CI/CD runbooks
Handle release, migration, rollback, and deployment dispatch workflows.
Open source foundation
Dagu remains open source and self-hostable.
Start with the project today
Use Dagu OSS when you want a self-contained workflow engine you can run anywhere with transparent YAML, logs, retries, and no external database requirement.
Put Dagu around the workflows you already run.
Keep execution close to your systems while centralizing control and visibility.