Spend time on your product, not workflow orchestration.
Run event-driven workflows with declarative infrastructure, operational control, and enterprise-grade scale.
The Difference
Keep workflow orchestration separate from business logic. Define workflows declaratively, stay zero-invasive to application code, and get a more capable alternative to cron without taking on Airflow-level complexity.
Deployment models
Run workflows where they belong.
Start local, self-host the full server, use Dagu Cloud as a full managed Dagu server, or run hybrid with private workers inside your infrastructure.
See deployment optionsLocal
Single server
Run the full Dagu server on one machine with local file-backed state. No external database, broker, or platform stack required.
Self-hosted
Your infrastructure
Keep the Dagu server, workers, secrets, logs, and execution inside your own environment, with enterprise controls when needed.
Dagu Cloud
Full managed server
Use a dedicated managed Dagu server operated by Dagu Cloud in an isolated gVisor instance on GKE, with the managed license included.
Hybrid
Managed server, private execution
Let Dagu Cloud operate the server while private workers run Docker steps, private-network jobs, and data-local work inside your infrastructure.
Hybrid execution
Hybrid keeps the server managed while execution that needs your network, runtime, or data stays under your control.
Built for enterprise workflow operations
Dagu helps teams move from fragile scripts and point integrations to event-driven workflow infrastructure with clear operational control.
Enterprise teams need a platform they can roll out carefully, operate with confidence, and adapt to existing infrastructure boundaries. Dagu is designed to support that path from evaluation to production.
What enterprise teams need
GitHub, webhook, and internal system triggers
Shared visibility for runs, failures, retries, and approvals
Execution on your infrastructure or isolated sandboxes
Migration support from scripts, cron, and legacy schedulers
Architecture guidance for production deployments
Security controls, auditability, and access governance
One place to coordinate workflows
Trigger workflows from GitHub pushes, pull requests, issues, webhooks, and internal systems, then operate them from one shared control plane.
Receive events in one place
Start workflows from GitHub pushes, pull requests, issues, webhooks, and internal systems without building a separate event layer.
Run steps where they belong
Keep execution on your infrastructure or in gVisor-powered sandboxes, based on what each workflow needs.
Operate from one shared view
Monitor runs, failures, retries, and approvals in one place so teams can respond without losing context.
Common patterns and use cases
DaguCloud fits workflows that start from events, run across systems, and still need clear operational visibility.
Agents and AI pipelines
Coordinate coding agents, AI tools, retries, and follow-up jobs in workflows that need more than a single agent loop.
Humans-in-the-loop
Add approvals, built-in Markdown preview for easier reviewing, and operator handoffs where automation still needs human judgment.
Infrastructure operations
Manage runbooks, run commands on remote hosts over SSH, orchestrate Docker containers, and coordinate Kubernetes jobs without stitching together scripts and cron.
Media conversion pipelines
Orchestrate FFmpeg execution and trigger encoding, rendering, and delivery workflows from uploads, webhooks, or internal events.
Data processing pipelines
Build plumbing between S3, PostgreSQL, SQLite, shell scripts, and other systems in data workflows that need validation, transformation, and delivery steps.
CI/CD automations
Connect GitHub events, build steps, checks, and deployment actions into reliable release workflows.
Need the self-hosted path? Dagu OSS stays available
DaguCloud is the managed cloud platform. Dagu OSS remains the self-hosted engine for teams that want to run the stack themselves and stay closer to the open-source experience.
The self-hosted engine stays available under its own brand
Install, self-host, and extend the open-source engine under /, with the current docs, examples, and community flow intact.
Ready to orchestrate with confidence?
Start with a managed instance or explore the open-source engine. Either way, your workflows deserve better operational visibility.