A
quary
81.2
2,389 stars · Apache-2.0
Analytics
Umami leads by 17.9 · decisive
A
81.2
2,389 stars · Apache-2.0
B · leads
99.1
40,194 stars · MIT
quary versus Umami is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. quary is written mainly in Rust; Umami is written mainly in TypeScript. The composite score is 81.2 for quary and 99.1 for Umami.
Umami has 40,194 GitHub stars to quary's 2,389, a gap of 37,805 (16.82×). Forks are 58 for quary and 8,567 for Umami. On the log scale used inside this pair, adoption is 73 versus 100, and the fork community is 45 versus 100.
Push history: quary was last pushed on 16 November 2026 (1 day ago), and Umami was last pushed on 17 November 2026 (0 days ago). Open issues stand at 45 for quary (0.019 per star) and 136 for Umami (0.003 per star). Issue-health scores are 84 and 96; activity scores are 100 and 100.
quary 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 quary and 96 for Umami. This is a procurement signal, not legal advice.
In Analytics, both quary (2,389 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: quary 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 55 points (45 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
Umami finishes ahead at 99.1 against quary at 81.2, a 17.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 | quary | Umami |
|---|---|---|
| GitHub stars | 2,389 | 40,194 |
| Forks | 58 | 8,567 |
| Open issues | 45 | 136 |
| Adoption | 73 | 100 |
| Activity | 100 | 100 |
| Community | 45 | 100 |
| Issue health | 84 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 81.2 | 99.1 |
Open-source BI for engineers
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 2,389 for quary. The gap is 37,805 stars.
Umami was pushed more recently: 17 November 2026 versus 16 November 2026 for quary. That is 1 days apart.
Yes. This catalog marks both quary and Umami as self-hostable. Confirm each project's deploy docs before you plan a migration.
quary 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 quary scores 81.2. This page calls that a decisive lead for Umami.