A
bruin
79.7
1,813 stars · Apache-2.0
Analytics
Umami leads by 19.4 · decisive
A
79.7
1,813 stars · Apache-2.0
B · leads
99.1
40,194 stars · MIT
bruin versus Umami is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. bruin is written mainly in Go; Umami is written mainly in TypeScript. The composite score is 79.7 for bruin and 99.1 for Umami.
Umami has 40,194 GitHub stars to bruin's 1,813, a gap of 38,381 (22.17×). Forks are 101 for bruin and 8,567 for Umami. On the log scale used inside this pair, adoption is 71 versus 100, and the fork community is 51 versus 100.
Push history: bruin was last pushed on 17 November 2026 (0 days ago), and Umami was last pushed on 17 November 2026 (0 days ago). Open issues stand at 69 for bruin (0.038 per star) and 136 for Umami (0.003 per star). Issue-health scores are 70 and 96; activity scores are 100 and 100.
bruin is listed as Apache-2.0, 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. Umami 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. License scores in this pair are 96 for bruin and 96 for Umami. This is a procurement signal, not legal advice.
In Analytics, both bruin (1,813 stars) and Umami (40,194 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: bruin is open source, Umami is open source.
Umami 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 49 points (51 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
Umami finishes ahead at 99.1 against bruin at 79.7, a 19.4 point decisive 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 | bruin | Umami |
|---|---|---|
| GitHub stars | 1,813 | 40,194 |
| Forks | 101 | 8,567 |
| Open issues | 69 | 136 |
| Adoption | 71 | 100 |
| Activity | 100 | 100 |
| Community | 51 | 100 |
| Issue health | 70 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 79.7 | 99.1 |
Build data pipelines with SQL and Python, ingest data from different sources, add quality checks, and build end-to-end flows.
Umami is a small web analytics product with a simple dashboard over page and event data. It is MIT-licensed and is usually chosen when a team wants a short self-hosted setup.
Umami has more GitHub stars: 40,194 versus 1,813 for bruin. The gap is 38,381 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both bruin and Umami as self-hostable. Confirm each project's deploy docs before you plan a migration.
bruin is listed as Apache-2.0, 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. Umami 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.
Umami scores 99.1 and bruin scores 79.7. This page calls that a decisive lead for Umami.