A
beszel
94.7
27,434 stars · MIT
Self-Hosted
pentagi leads by 4.4 · narrow
A
94.7
27,434 stars · MIT
B · leads
99.1
34,396 stars · MIT
beszel versus pentagi is a Self-Hosted comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in Go. The composite score is 94.7 for beszel and 99.1 for pentagi.
pentagi has 34,396 GitHub stars to beszel's 27,434, a gap of 6,962 (1.25×). Forks are 1,188 for beszel and 5,447 for pentagi. On the log scale used inside this pair, adoption is 98 versus 100, and the fork community is 82 versus 100.
Push history: beszel was last pushed on 15 November 2026 (2 days ago), and pentagi was last pushed on 13 November 2026 (3 days ago). Open issues stand at 399 for beszel (0.015 per star) and 76 for pentagi (0.002 per star). Issue-health scores are 84 and 96; activity scores are 100 and 100.
Both beszel and pentagi 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 Self-Hosted, both beszel (27,434 stars) and pentagi (34,396 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: beszel is open source, pentagi is open source.
pentagi is ahead on every scored dimension that is not level. Level dimensions: recent activity, license flexibility, self-hosting. The widest gap is fork community at 18 points (82 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
pentagi finishes ahead at 99.1 against beszel at 94.7, a 4.4 point narrow margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | beszel | pentagi |
|---|---|---|
| GitHub stars | 27,434 | 34,396 |
| Forks | 1,188 | 5,447 |
| Open issues | 399 | 76 |
| Adoption | 98 | 100 |
| Activity | 100 | 100 |
| Community | 82 | 100 |
| Issue health | 84 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 94.7 | 99.1 |
Lightweight server monitoring with historical data, docker stats, and alerts.
Fully autonomous AI Agents system capable of performing complex penetration testing tasks
pentagi has more GitHub stars: 34,396 versus 27,434 for beszel. The gap is 6,962 stars.
beszel was pushed more recently: 15 November 2026 versus 13 November 2026 for pentagi. That is 1 days apart.
Yes. This catalog marks both beszel and pentagi as self-hostable. Confirm each project's deploy docs before you plan a migration.
beszel 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. pentagi 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.
pentagi scores 99.1 and beszel scores 94.7. This page calls that a narrow lead for pentagi.