Executez Dagu sans abandonner votre frontiere d execution.

Utilisez Dagu comme plan de controle heberge, serveur self-hosted ou deployment hybride avec des workers private. Les workflows peuvent s executer la ou votre reseau, vos secrets et vos donnees client vivent deja, tandis que Dagu garde catalogue, acces, runs, logs et approvals au meme endroit.

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, managed, or hybrid.

Start with one binary, add distributed workers when needed, and keep sensitive execution close to your private network and secrets.

View pricing

Local

Single binary

Run server and scheduler together for small teams and internal tools.

Self-hosted

Private control plane

Operate Dagu inside your own infrastructure with your own auth and storage.

Managed

Hosted control plane

Use a managed Dagu instance while workers can stay in your environment.

Hybrid

Private workers

Keep execution near private systems while centralizing catalog and visibility.

Execution boundary

Managed server
Private worker
Your infrastructure

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.

Nous contacter

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.

Workflows Agent Harness

Exécutez Claude, Codex, OpenCode ou des CLI d’agents externes personnalisées via des étapes Agent Harness.

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.