A · leads
beszel
95.4
27,434 stars · MIT
Self-Hosted
beszel leads by 2.8 · narrow
A · leads
95.4
27,434 stars · MIT
B
92.6
38,974 stars · AGPL-3.0
beszel versus Trilium 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; Trilium is written mainly in TypeScript. The composite score is 95.4 for beszel and 92.6 for Trilium.
Trilium has 38,974 GitHub stars to beszel's 27,434, a gap of 11,540 (1.42×). Forks are 1,188 for beszel and 2,630 for Trilium. On the log scale used inside this pair, adoption is 97 versus 100, and the fork community is 90 versus 100.
Push history: beszel was last pushed on 15 November 2026 (2 days ago), and Trilium was last pushed on 17 November 2026 (0 days ago). Open issues stand at 399 for beszel (0.015 per star) and 574 for Trilium (0.015 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. Trilium is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. License scores in this pair are 96 for beszel and 52 for Trilium. This is a procurement signal, not legal advice.
In Self-Hosted, both beszel (27,434 stars) and Trilium (38,974 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, Trilium is open source.
The lead is split. beszel is furthest ahead on license flexibility (96 to 52), while Trilium is furthest ahead on fork community (100 to 90). Choose the dimension a rollout cannot compromise on.
beszel finishes ahead at 95.4 against Trilium at 92.6, a 2.8 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 | Trilium |
|---|---|---|
| GitHub stars | 27,434 | 38,974 |
| Forks | 1,188 | 2,630 |
| Open issues | 399 | 574 |
| Adoption | 97 | 100 |
| Activity | 100 | 100 |
| Community | 90 | 100 |
| Issue health | 84 | 84 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 95.4 | 92.6 |
Lightweight server monitoring with historical data, docker stats, and alerts.
Build your personal knowledge base with Trilium Notes
Trilium has more GitHub stars: 38,974 versus 27,434 for beszel. The gap is 11,540 stars.
Trilium 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 Trilium 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. Trilium is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
beszel scores 95.4 and Trilium scores 92.6. This page calls that a narrow lead for beszel.