Skip to content
DevUtils Online

Analytics

anyquery vs Umami

Umami leads by 34.2 · decisive

A

anyquery

64.9

1,793 stars · license n/a

B · leads

Umami

99.1

40,194 stars · MIT

anyquery versus Umami is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. anyquery is written mainly in Go; Umami is written mainly in TypeScript. The composite score is 64.9 for anyquery and 99.1 for Umami.

Umami has 40,194 GitHub stars to anyquery's 1,793, a gap of 38,401 (22.42×). Forks are 142 for anyquery and 8,567 for Umami. On the log scale used inside this pair, adoption is 71 versus 100, and the fork community is 55 versus 100.

Push history: anyquery was last pushed on 08 October 2026 (40 days ago), and Umami was last pushed on 17 November 2026 (0 days ago). Open issues stand at 4 for anyquery (0.002 per star) and 136 for Umami (0.003 per star). Issue-health scores are 96 and 96; activity scores are 78 and 100.

anyquery 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 anyquery 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). anyquery is not (1,793 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: anyquery is unpriced in this catalog, Umami is open source.

Umami is ahead on every scored dimension that is not level. Level dimensions: 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 anyquery at 64.9, a 34.2 point decisive margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

anyquery versus Umami metrics
Signal anyquery Umami
GitHub stars 1,793 40,194
Forks 142 8,567
Open issues 4 136
Adoption 71 100
Activity 78 100
Community 55 100
Issue health 96 96
License 30 96
Self-hosting 35 100
Composite 64.9 99.1

Umami

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.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, anyquery or Umami?

Umami has more GitHub stars: 40,194 versus 1,793 for anyquery. The gap is 38,401 stars.

Which was updated more recently, anyquery or Umami?

Umami was pushed more recently: 17 November 2026 versus 08 October 2026 for anyquery. That is 40 days apart.

Can I self-host both anyquery and Umami?

Only Umami is marked self-hostable. anyquery is not.

Which license is easier to embed in a commercial product, anyquery or Umami?

anyquery 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.

Who wins the anyquery vs Umami score?

Umami scores 99.1 and anyquery scores 64.9. This page calls that a decisive lead for Umami.

Related comparisons