Skip to content
DevUtils Online

Analytics

rotki vs Umami

Umami leads by 20.7 · decisive

A

rotki

78.4

4,093 stars · AGPL-3.0

B · leads

Umami

99.1

40,194 stars · MIT

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

Umami has 40,194 GitHub stars to rotki's 4,093, a gap of 36,101 (9.82×). Forks are 791 for rotki and 8,567 for Umami. On the log scale used inside this pair, adoption is 78 versus 100, and the fork community is 74 versus 100.

Push history: rotki 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 353 for rotki (0.086 per star) and 136 for Umami (0.003 per star). Issue-health scores are 52 and 96; activity scores are 100 and 100.

rotki 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. 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 52 for rotki and 96 for Umami. This is a procurement signal, not legal advice.

In Analytics, both rotki (4,093 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: rotki is open source, Umami is open source.

Umami is ahead on every scored dimension that is not level. Level dimensions: recent activity, self-hosting. The widest gap is issue health at 44 points (52 vs 96), and the tightest is self-hosting at 0 points (100 vs 100).

Umami finishes ahead at 99.1 against rotki at 78.4, a 20.7 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.

rotki versus Umami metrics
Signal rotki Umami
GitHub stars 4,093 40,194
Forks 791 8,567
Open issues 353 136
Adoption 78 100
Activity 100 100
Community 74 100
Issue health 52 96
License 52 96
Self-hosting 100 100
Composite 78.4 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, rotki or Umami?

Umami has more GitHub stars: 40,194 versus 4,093 for rotki. The gap is 36,101 stars.

Which was updated more recently, rotki or Umami?

Both were last pushed on 17 November 2026.

Can I self-host both rotki and Umami?

Yes. This catalog marks both rotki and Umami as self-hostable. Confirm each project's deploy docs before you plan a migration.

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

rotki 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. 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 rotki vs Umami score?

Umami scores 99.1 and rotki scores 78.4. This page calls that a decisive lead for Umami.

Related comparisons