A
chartbrew
74.2
4,097 stars · license n/a
Analytics
Umami leads by 24.9 · decisive
A
74.2
4,097 stars · license n/a
B · leads
99.1
40,194 stars · MIT
chartbrew versus Umami is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. chartbrew is written mainly in JavaScript; Umami is written mainly in TypeScript. The composite score is 74.2 for chartbrew and 99.1 for Umami.
Umami has 40,194 GitHub stars to chartbrew's 4,097, a gap of 36,097 (9.81×). Forks are 458 for chartbrew and 8,567 for Umami. On the log scale used inside this pair, adoption is 78 versus 100, and the fork community is 68 versus 100.
Push history: chartbrew was last pushed on 14 November 2026 (3 days ago), and Umami was last pushed on 17 November 2026 (0 days ago). Open issues stand at 2 for chartbrew (0.000 per star) and 136 for Umami (0.003 per star). Issue-health scores are 96 and 96; activity scores are 100 and 100.
chartbrew 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. 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 30 for chartbrew and 96 for Umami. This is a procurement signal, not legal advice.
Only Umami is marked self-hostable here (40,194 stars, deploy score 100). chartbrew is not (4,097 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: chartbrew is unpriced in this catalog, Umami is open source.
Umami is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health. The widest gap is license flexibility at 66 points (30 vs 96), and the tightest is issue health at 0 points (96 vs 96).
Umami finishes ahead at 99.1 against chartbrew at 74.2, a 24.9 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 | chartbrew | Umami |
|---|---|---|
| GitHub stars | 4,097 | 40,194 |
| Forks | 458 | 8,567 |
| Open issues | 2 | 136 |
| Adoption | 78 | 100 |
| Activity | 100 | 100 |
| Community | 68 | 100 |
| Issue health | 96 | 96 |
| License | 30 | 96 |
| Self-hosting | 35 | 100 |
| Composite | 74.2 | 99.1 |
Open-source reporting platform to build and share live dashboards from APIs, SQL and NoSQL databases, with powerful AI assistant, scheduling, and embeddable charts 📈📊
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 4,097 for chartbrew. The gap is 36,097 stars.
Umami was pushed more recently: 17 November 2026 versus 14 November 2026 for chartbrew. That is 3 days apart.
Only Umami is marked self-hostable. chartbrew is not.
chartbrew 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. 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 chartbrew scores 74.2. This page calls that a decisive lead for Umami.