Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | ntfy | Miller | dsh-git-graph |
|---|---|---|---|
| Platforms | Universal | Universal, MCP, Claude Code, Codex, Cursor | DeepSeek Harness |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | Apache-2.0 / GPL-2.0 | BSD-2-Clause | Apache-2.0 |
| Stars | 35017 | 10049 | 9384 |
| Last activity | September 29, 2026 | October 21, 2026 | September 25, 2026 |
| Install complexity | سهل للتجربة، متوسط للاستضافة الآمنة / Easy to try, moderate to self-host securely | EASY | سهل / Easy |
| Category | Workflow, DevOps | Workflow, Data | Git, Workflow, UI |
| Best use | Best for an individual developer or small team that wants backup, deployment, and scheduled-job alerts without building a notification app. It starts with one HTTP request and can be self-hosted with users and ACLs. It is not a complete incident-management or log-retention system. | Ideal for developers, data analysts, and operators who need to clean a CSV export, inspect JSON Lines, or summarize a large file from the terminal without starting a Python project. Use it for quick, repeatable file processing; concurrent transactions and advanced visual analysis still call for a database or complementary analytics tool. | Best for a developer running several DSH sessions against one repository who wants visible branch context, history, and worktree creation in the UI. It adds session isolation and readable branch-switch guards. It may be excessive for one small change on one branch or for environments that prohibit outbound telemetry. |