dagucloud/dagu

Self-hostable workflow orchestrator for teams whose main work isn't orchestration. Declarative YAML over your scripts, SSH commands, containers, etc; keep...

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 1 hour ago
Added to GitGenius on September 17th, 2026
Created on April 22nd, 2022
Open Issues & Pull Requests: 77 (+0)
GitHub issues: Enabled
Number of forks: 339
Total Stargazers: 4,038 (+0)
Total Subscribers: 21 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.7 hours
Mean response time: 36.1 days
90th percentile: 31.2 days
Tracked items: 665

Most active contributors

Sign in to see contributor activity.

How this project is maintained

About 5% of issues opened in the past year have never received a reply. 66% of open issues come from outside the core team, a mix of external reports and the maintainers' own roadmap. 33% of tracked open issues have had no activity in three months. 87% of issues opened in the past year have been closed, leaving a working backlog. Three people close 90% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 71
New in 7 days: 31
Closed in 7 days: 20
Avg open age: 215 days
Stale 30+ days: 35
Stale 90+ days: 29

Recent activity

Opened in 7 days: 29
Closed in 7 days: 19
Comments in 7 days: 7
Events in 7 days: 24

Top labels

  • bug (73)
  • good first issue (28)
  • wishlist (24)
  • must-have (18)
  • help wanted (7)
  • discussion (5)
  • needs-docs (2)
  • needs-investigation (2)

Detailed Description

Dagu is a self-hostable workflow orchestrator designed for teams whose primary focus is not orchestration infrastructure itself.

The tool addresses the friction of managing complex workflows across scripts, SSH commands, and containers by letting you declare them in YAML while keeping orchestration logic separate from business logic. It runs as a single binary with no database requirement, making it lightweight enough to operate on constrained hardware. This approach eliminates the operational overhead of heavier orchestration platforms while still providing directed acyclic graph execution, scheduling, and monitoring capabilities.

Teams should consider Dagu if they need workflow automation without the complexity and resource demands of dedicated orchestration systems. It suits projects where workflows are relatively stable and teams want to avoid managing a separate database or complex infrastructure. The README positions it as an alternative to Airflow, Cron, and traditional job schedulers, making it particularly relevant for organizations that find those tools either oversized for their needs or too operationally demanding.

Development activity shows consistent engagement with regular commits across the codebase, indicating active maintenance. The project maintains a focused scope rather than pursuing rapid feature expansion, suggesting deliberate prioritization of stability and core functionality. Documentation and examples receive ongoing attention, reflecting a commitment to usability for new adopters. The tool incorporates support for modern workflow patterns including AI agents and human-in-the-loop execution, showing responsiveness to emerging use cases while preserving the lightweight design philosophy.