Skip to content
DevUtils Online

AI Agents

deepseek-harness vs OpenBot

deepseek-harness leads by 12.0 · clear

B

OpenBot

85.4

12,716 stars · MIT

deepseek-harness versus OpenBot is a AI Agents comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in TypeScript. The composite score is 97.4 for deepseek-harness and 85.4 for OpenBot.

deepseek-harness has 282,805 GitHub stars to OpenBot's 12,716, a gap of 270,089 (22.24×). Forks are 35,041 for deepseek-harness and 1,578 for OpenBot. On the log scale used inside this pair, adoption is 100 versus 75, and the fork community is 100 versus 70.

Push history: deepseek-harness was last pushed on 13 November 2026 (4 days ago), and OpenBot was last pushed on 17 November 2026 (0 days ago). Open issues stand at 0 for deepseek-harness (0.000 per star) and 121 for OpenBot (0.010 per star). Issue-health scores are 96 and 84; activity scores are 92 and 100.

Both deepseek-harness and OpenBot are listed as MIT. A permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.

In AI Agents, both deepseek-harness (282,805 stars) and OpenBot (12,716 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: deepseek-harness is open source, OpenBot is open source.

The lead is split. deepseek-harness is furthest ahead on fork community (100 to 70), while OpenBot is furthest ahead on recent activity (100 to 92). Choose the dimension a rollout cannot compromise on.

deepseek-harness finishes ahead at 97.4 against OpenBot at 85.4, a 12.0 point clear margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

deepseek-harness versus OpenBot metrics
Signal deepseek-harness OpenBot
GitHub stars 282,805 12,716
Forks 35,041 1,578
Open issues 0 121
Adoption 100 75
Activity 92 100
Community 100 70
Issue health 96 84
License 96 96
Self-hosting 100 100
Composite 97.4 85.4

OpenBot

The open, self-hostable alternative to closed AI bots. Production-ready, fully customizable, and plugs into every stack: any agent, any model, any tool.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, deepseek-harness or OpenBot?

deepseek-harness has more GitHub stars: 282,805 versus 12,716 for OpenBot. The gap is 270,089 stars.

Which was updated more recently, deepseek-harness or OpenBot?

OpenBot was pushed more recently: 17 November 2026 versus 13 November 2026 for deepseek-harness. That is 4 days apart.

Can I self-host both deepseek-harness and OpenBot?

Yes. This catalog marks both deepseek-harness and OpenBot as self-hostable. Confirm each project's deploy docs before you plan a migration.

Which license is easier to embed in a commercial product, deepseek-harness or OpenBot?

deepseek-harness is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. OpenBot is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. Read both grants before you embed either codebase in a hosted product. This is not legal advice.

Who wins the deepseek-harness vs OpenBot score?

deepseek-harness scores 97.4 and OpenBot scores 85.4. This page calls that a clear lead for deepseek-harness.

Related comparisons