Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | dsh-agent-teams | Beszel | dsh-task-board |
|---|---|---|---|
| Platforms | DeepSeek Harness | Universal | DeepSeek Harness |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | MIT | MIT | Apache-2.0 |
| Stars | 2386 | 26480 | 9384 |
| Last activity | — | October 20, 2026 | — |
| Install complexity | يتطلب إصدار DSH متوافقًا وإعادة تشغيل | متوسط / Medium | Intermediate |
| Category | Multi-Agent, Workflow | DevOps, Monitoring | Multi-Agent, Workflow |
| Best use | For development work that can be divided into dependent tasks and reviewed as a plan before agents start. Monitor outputs and model costs; team state is not coordinated across separate processes. | 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 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. |