Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | ntfy | dsh-task-board | Backlog.md |
|---|---|---|---|
| Platforms | Universal | DeepSeek Harness | Universal, Codex, Claude Code, Cursor |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | Apache-2.0 / GPL-2.0 | Apache-2.0 | MIT |
| Stars | 35017 | 9384 | 7130 |
| Last activity | September 29, 2026 | — | — |
| Install complexity | سهل للتجربة، متوسط للاستضافة الآمنة / Easy to try, moderate to self-host securely | Intermediate | Easy — npm, Bun, Homebrew, or Nix |
| Category | Workflow, DevOps | Multi-Agent, Workflow | Multi-Agent, Git, Workflow |
| 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. | Best for a developer or small team using DSH for recurring or connected work and wanting task state and execution evidence in one record. It pins the project, agent preset, and permission, then runs manually or through Host cron with a human gate for elevated access. It is not a fit for a frequently sleeping machine or unreviewed sensitive automation. | Best for an individual developer or small team using coding agents and wanting to review the specification and plan before code. It keeps tasks, acceptance criteria, and decisions inside the project and exposes them through CLI, a local browser, or MCP. It is not a replacement for a centralized enterprise SaaS board with organization-wide permissions and reporting. |