Choose how to run Dagu.
Dagu is the open-source workflow engine. Hosted Dagu runs a dedicated Dagu server for you; private workers can keep Docker, private-network, and data-heavy execution in your infrastructure; self-host licenses add enterprise controls when you run the server yourself.
Self-hosted on your own infrastructure
Dagu is GPLv3 and free forever. Please consider purchasing licenses to support open source sustainability. Paid license enables useful features for using in a team.
- Full workflow automation and monitoring
- Web UI with DAG visualization
- Docker, SSH, and HTTP executors
- Cron scheduling & retries
- Up to 2 API keys for automation
3 self-host Dagu server licenses
15 self-host Dagu server licenses
For teams building event-driven workflow infrastructure in complex environments
- Architecture consulting for distributed setup
- Custom implementation
- MCP OIDC/SSO setup guidance
- Initial migration support
- Dedicated meetings
Custom Solutions
Building tailored features for specific company needs.
Turnkey Solutions
Creating ready-to-go setups to help teams scale Dagu easily without burning massive technical or server resources.
Create a 14-day self-host license trial in minutes β 14 days, No credit card required. Start free license trial
Building this together
As the project grows, managing it requires more time and resources. To ensure Dagu thrives long-term, we are slowly exploring ways to make the project financially sustainable.
Our goal is to build a business model that funds core development without restricting the features you already love.
We want to build this future with you. If you have ideas, feedback, or want to share what features your team would pay for, please drop them in the #feedback channel. Thank you for being an amazing community! π
Managed control plane
Start with a dedicated Dagu server isolated from other tenants and operated by Dagu. Minimum and Starter are self-serve; Medium or larger hosted instances are available by request.
Hosted Instance (Minimum)
A low-cost hosted control plane for evaluation, light orchestration, and workflows that mostly run on private workers.
Best fit: trials, lightweight schedules, and coordination. Not intended for sustained local execution, heavy logs, Docker jobs, or data-heavy processing on the hosted server.
Monthly billing. Dedicated instance.
- Dedicated GKE + gVisor instance isolated from other tenants
- CPU: 50m request / 100m limit
- Memory: 128Mi request / 2Gi limit
- Storage: 1Gi persistent volume + 1Gi temporary storage
- Private/on-prem workers authenticate with mTLS
Hosted Instance (Starter)
A larger self-serve hosted control plane with more storage and runtime headroom for small production teams.
Best fit: light production orchestration and moderate logs. Move Docker, private-network, CPU-heavy, memory-heavy, or data-heavy work to private workers.
Monthly billing. Dedicated instance.
- Dedicated GKE + gVisor instance isolated from other tenants
- CPU: 250m request / 1 vCPU limit
- Memory: 1Gi request / 1Gi limit
- Storage: 20Gi persistent volume + 1Gi temporary storage
- Private/on-prem workers authenticate with mTLS
Hosted Instance (Medium or Larger)
For sustained local execution, larger logs, higher queue pressure, or capacity beyond Starter, contact us and we will size the hosted instance around your workload.
- Capacity beyond Starter
- Direct sizing review with the Dagu team
- Provisioning plan matched to your workload
Capacity settings
Queues, concurrency, and workload placement are configurable
Use the web terminal on the hosted server to edit the Dagu config file when your workload needs different queue names or max concurrency.
- Max concurrency controls how many runs Dagu starts; it is not a resource guarantee. Set it according to the selected server type and actual workflow behavior.
- Runs executed on the hosted server consume that server's CPU, memory, temporary storage, and persistent volume; excessive logs can fill the volume.
- Private/on-prem workers authenticate with mTLS and are the right place for Docker, private-network, custom-runtime, CPU-heavy, memory-heavy, or data-local work.
- If concurrency, logs, or local execution need more capacity than Starter, use Medium or larger by request instead of overloading the selected tier.
Dedicated runtime
Your instance is provisioned separately instead of being packed into a shared multi-tenant runtime, and includes managed enterprise controls and incident routing without a separate self-host license. Notification routing is included across deployments.
gVisor isolation
Hosted workloads run on GKE inside a gVisor sandbox boundary. The managed instance does not expose a Docker daemon or Docker socket; private workers authenticate with mTLS when you need Docker actions, private networks, or custom runtimes.
Persistent workspace
Instance storage stays attached until you delete the instance.
Web terminal access
Open the browser terminal to inspect files, adjust config, and operate Dagu directly.
How billing cycles work
Self-host licenses and managed instances are billed as separate Stripe subscriptions. The billing portal shows the exact renewal dates for each subscription.
Self-host licenses
Minimum is $50/month for 3 licensed Dagu servers. Pro is $150/month for 15. Workers are included. Plan and interval changes are handled through Stripe and prorated when they affect the current billing period.
Managed instances
Hosted Minimum and Starter are billed monthly per instance. Saving a payment method does not start billing. Failed instances are not kept on billing; added instances and shutdowns are prorated during the month. Stopped instances continue billing because storage is retained. Any prorated credit is a Stripe invoice credit for future Dagu invoices in the same billing account and currency, not a transferable credit or automatic refund.
Deployment models
Choose where the Dagu server runs and where your workflows execute.
Community self-host
- Control plane
- Your infrastructure, using the open-source Dagu server.
- Execution
- Local execution and workers run on machines you operate.
- Best for
- Teams that want the free GPLv3 engine with no managed control plane.
Enterprise self-host
- Control plane
- Your infrastructure, with licensed Dagu servers for SSO, RBAC, audit logging, and incident routing. Notification routing is available without a license.
- Execution
- Workers run in your infrastructure and are not licensed separately.
- Best for
- Teams that need enterprise controls while keeping Dagu inside their own security boundary.
Managed Dagu server + private workers
- Control plane
- A full Dagu server running in a dedicated, isolated gVisor instance on GKE, operated by Dagu with the managed license and incident routing included. Notification routing is included across deployments.
- Execution
- Run workflows directly in the managed Dagu server, or attach mTLS-authenticated private workers for Docker, private networks, and custom runtimes.
- Best for
- Teams that want Dagu to run the full server while selected execution can stay close to their systems.
Managed Dagu is a full Dagu server. Private workers authenticate with mTLS and let Docker steps, private network access, secrets, and data-heavy work stay inside your infrastructure.
Which deployment model fits your team?
Hosted Dagu and Self-Host solve different problems. Pick the model that matches your operational preference.
| Β | Hosted Dagu | Self-Hosted Dagu |
|---|---|---|
| Billing unit | $20 for Minimum or $50 for Starter, billed monthly per hosted instance | Community is free; self-host plans start at $50/month for 3 server licenses |
| Isolation model | Dedicated instance isolated from other tenants, with gVisor sandboxing | Isolation is defined by the infrastructure and controls you operate |
| Who operates it | Dagu manages the platform, networking, and runtime environment | Your team operates the servers, upgrades, and surrounding infrastructure |
| Scaling path | Start with Minimum or Starter, place heavy execution on private workers, tune Dagu config, or request Medium or larger capacity | Move from Minimum with 3 licensed servers to Pro with 15, or ask for a custom Enterprise allotment; workers do not require separate licenses |
| Security features | Managed GKE + gVisor isolation, controlled network policy, browser access, no Docker socket exposure, notification routing, and incident routing | SSO, RBAC, audit logging, and incident routing via the self-host license; notification routing is included without a license |
| Best for | Teams that want Dagu running quickly without owning platform operations | Teams that need Dagu inside their own environment and security boundary |
Frequently Asked Questions
What is a hosted instance?
A hosted instance is a dedicated Dagu environment managed by Dagu. It is isolated from other tenants, includes enterprise security features for that instance, and is billed separately from self-host licenses.
How much is a self-host license?
Community remains free and open source. Notification routing and up to 2 API keys are available without a license. Minimum is $50/month for 3 self-host Dagu server licenses. Pro is $150/month for 15. Paid licenses remove the Community API key cap and add SSO, RBAC, audit logging, incident routing, and support. Workers are included and are not licensed separately. This helps fund ongoing development and maintenance while keeping Community free.
What do Hosted Minimum and Starter include?
Hosted Minimum is a dedicated GKE + gVisor Dagu server for $20 per month with 50m CPU request / 100m CPU limit, 128Mi memory request / 2Gi memory limit, 1Gi persistent storage, and 1Gi temporary storage. It is best for trials, light orchestration, and workflows that mostly run on private workers. Hosted Starter is $50 per month with 250m CPU request / 1 vCPU limit, 1Gi memory request / 1Gi memory limit, 20Gi persistent storage, and 1Gi temporary storage. It is best for light production orchestration and moderate logs. Queue names and max concurrency are configured in the Dagu config file on the hosted server and should match the selected server resources and workload.
How do larger hosted instances work?
Larger hosted instances beyond Starter are request-based. Contact the Dagu team and we will size the instance around your workload.
Can hosted deployments run Docker steps?
Not inside the managed instance. Managed instances run on GKE with gVisor isolation and do not expose a Docker daemon or Docker socket. Docker actions can run on a private worker in your infrastructure, attached to the managed Dagu server with the worker mTLS bundle.
Does hosted have annual billing?
Not yet. Hosted Minimum and Starter are currently billed monthly. Self-host plans support monthly and yearly billing: Minimum is $50/month or $500/year for 3 licenses; Pro is $150/month or $1,500/year for 15 licenses.
How does the license trial work?
Create a free trial license from the Dagu console, enable the paid self-host features on your self-hosted deployment, and evaluate them for 14 days. No credit card is required to start.
What happens if provisioning fails, or if I stop or shut down a hosted instance?
Failed instances are not kept on billing. Stop keeps persistent storage and monthly billing. Shutdown removes retained resources and stops future billing after cleanup; unused monthly time is handled as a Stripe invoice credit or adjustment for your Dagu billing customer. It applies automatically to future Dagu invoices in the same account and currency, not to other merchants or separate Stripe accounts, and it is not an automatic card refund.