Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | Backlog.md | Beszel | dsh-git-graph |
|---|---|---|---|
| Platforms | Universal, Codex, Claude Code, Cursor | Universal | DeepSeek Harness |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | MIT | MIT | Apache-2.0 |
| Stars | 7131 | 26480 | 9384 |
| Last activity | — | October 20, 2026 | September 25, 2026 |
| Install complexity | Easy — npm, Bun, Homebrew, or Nix | متوسط / Medium | سهل / Easy |
| Category | Multi-Agent, Git, Workflow | DevOps, Monitoring | Git, Workflow, UI |
| Best use | 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. | Best for an individual developer or small team running a VPS, home server, or a few Docker hosts and needing a simple dashboard, history, and alerts. Its value is combining host and container metrics in a self-hosted hub. It is not a full logs-and-traces observability platform. | 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. |