Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | D2 | act | Dagu |
|---|---|---|---|
| Platforms | Universal | GitHub | Universal, MCP |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | MPL-2.0 | MIT | GPL-3.0 |
| Stars | 25761 | 72485 | 4499 |
| Last activity | October 11, 2026 | — | October 28, 2026 |
| Install complexity | Easy with a supported package manager; Homebrew must already be installed for this command. Official binaries, Windows, Linux, and source options are documented. | — | سهل للبداية؛ يحتاج ضبط أمان قبل المشاركة / Easy to start; security configuration required before sharing |
| Category | Workflow, UI | Testing, Git, DevOps | Workflow, DevOps, Monitoring |
| Best use | For developers and small teams that want architecture and data-flow diagrams close to the repository and reviewable as text. Use it when relationships matter more than pixel-perfect placement; not for free-form marketing design or exact manual positioning. | Best for a developer or small team that repeatedly edits GitHub Actions workflows and wants to test a job before pushing. It provides a local run log, while a final GitHub check remains necessary. It is not suitable when exact hosted-runner parity is required. | Best for a developer or small team with connected scripts that need schedules, history, and a clear failure point. It adds dependencies, retries, and an operations UI without an external database in single-server mode. A simple independent command may not need it, and some team controls such as additional users, SSO, RBAC, and audit logging currently require a paid license. |