A
beszel
93.9
27,434 stars · MIT
Self-Hosted
reactive-resume leads by 5.2 · narrow
A
93.9
27,434 stars · MIT
B · leads
99.1
45,854 stars · MIT
beszel versus reactive-resume 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; reactive-resume is written mainly in TypeScript. The composite score is 93.9 for beszel and 99.1 for reactive-resume.
reactive-resume has 45,854 GitHub stars to beszel's 27,434, a gap of 18,420 (1.67×). Forks are 1,188 for beszel and 4,959 for reactive-resume. On the log scale used inside this pair, adoption is 95 versus 100, and the fork community is 83 versus 100.
Push history: beszel was last pushed on 15 November 2026 (2 days ago), and reactive-resume was last pushed on 16 November 2026 (1 day ago). Open issues stand at 399 for beszel (0.015 per star) and 7 for reactive-resume (0.000 per star). Issue-health scores are 84 and 96; activity scores are 100 and 100.
Both beszel and reactive-resume 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 reactive-resume (45,854 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, reactive-resume is open source.
reactive-resume 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 17 points (83 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
reactive-resume finishes ahead at 99.1 against beszel at 93.9, a 5.2 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 | reactive-resume |
|---|---|---|
| GitHub stars | 27,434 | 45,854 |
| Forks | 1,188 | 4,959 |
| Open issues | 399 | 7 |
| Adoption | 95 | 100 |
| Activity | 100 | 100 |
| Community | 83 | 100 |
| Issue health | 84 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 93.9 | 99.1 |
Lightweight server monitoring with historical data, docker stats, and alerts.
A one-of-a-kind resume builder that keeps your privacy in mind. Completely secure, customizable, portable, open-source and free forever. Try it out today!
reactive-resume has more GitHub stars: 45,854 versus 27,434 for beszel. The gap is 18,420 stars.
reactive-resume was pushed more recently: 16 November 2026 versus 15 November 2026 for beszel. That is 1 days apart.
Yes. This catalog marks both beszel and reactive-resume 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. reactive-resume 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.
reactive-resume scores 99.1 and beszel scores 93.9. This page calls that a narrow lead for reactive-resume.