Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | dsh-agent-teams | Beszel | dsh-session-archive |
|---|---|---|---|
| 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 | September 26, 2026 |
| Install complexity | يتطلب إصدار DSH متوافقًا وإعادة تشغيل | متوسط / Medium | Easy |
| Category | Multi-Agent, Workflow | DevOps, Monitoring | Memory, Security, 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. | Use it when DSH sessions pile up and you need to identify old work, archive it first, then safely remove what is no longer needed while protecting running sessions. It fits recurring cleanup and finished projects; do not enable automatic deletion before previewing the policy and checking backups. |