A · leads
beszel
97.9
27,434 stars · MIT
Self-Hosted
beszel leads by 9.1 · clear
A · leads
97.9
27,434 stars · MIT
B
88.8
23,827 stars · license n/a
beszel versus pangolin is a Self-Hosted comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. beszel is written mainly in Go; pangolin is written mainly in TypeScript. The composite score is 97.9 for beszel and 88.8 for pangolin.
beszel has 27,434 GitHub stars to pangolin's 23,827, a gap of 3,607 (1.15×). Forks are 1,188 for beszel and 840 for pangolin. On the log scale used inside this pair, adoption is 100 versus 99, and the fork community is 100 versus 95.
Push history: beszel was last pushed on 15 November 2026 (2 days ago), and pangolin was last pushed on 17 November 2026 (0 days ago). Open issues stand at 399 for beszel (0.015 per star) and 135 for pangolin (0.006 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.
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. pangolin is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. License scores in this pair are 96 for beszel and 30 for pangolin. This is a procurement signal, not legal advice.
In Self-Hosted, both beszel (27,434 stars) and pangolin (23,827 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, pangolin is unpriced in this catalog.
beszel is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, self-hosting. The widest gap is license flexibility at 66 points (96 vs 30), and the tightest is self-hosting at 0 points (100 vs 100).
beszel finishes ahead at 97.9 against pangolin at 88.8, a 9.1 point clear 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 | pangolin |
|---|---|---|
| GitHub stars | 27,434 | 23,827 |
| Forks | 1,188 | 840 |
| Open issues | 399 | 135 |
| Adoption | 100 | 99 |
| Activity | 100 | 100 |
| Community | 100 | 95 |
| Issue health | 84 | 84 |
| License | 96 | 30 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 88.8 |
Lightweight server monitoring with historical data, docker stats, and alerts.
Modern networking and security platform providing secure access and connectivity to apps, infrastructure, and AI workloads. Connect and protect your users.
beszel has more GitHub stars: 27,434 versus 23,827 for pangolin. The gap is 3,607 stars.
pangolin was pushed more recently: 17 November 2026 versus 15 November 2026 for beszel. That is 2 days apart.
Yes. This catalog marks both beszel and pangolin 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. pangolin is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
beszel scores 97.9 and pangolin scores 88.8. This page calls that a clear lead for beszel.