Skip to content
DevUtils Online

Analytics

spark vs Umami

Umami leads by 20.7 · decisive

A

spark

78.4

2,097 stars · MIT

B · leads

Umami

99.1

40,194 stars · MIT

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

Umami has 40,194 GitHub stars to spark's 2,097, a gap of 38,097 (19.17×). Forks are 332 for spark and 8,567 for Umami. On the log scale used inside this pair, adoption is 72 versus 100, and the fork community is 64 versus 100.

Push history: spark was last pushed on 05 November 2026 (12 days ago), and Umami was last pushed on 17 November 2026 (0 days ago). Open issues stand at 207 for spark (0.099 per star) and 136 for Umami (0.003 per star). Issue-health scores are 52 and 96; activity scores are 92 and 100.

Both spark and Umami are listed as MIT. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.

In Analytics, both spark (2,097 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: spark is open source, Umami is open source.

Umami is ahead on every scored dimension that is not level. Level dimensions: license flexibility, 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 spark 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.

spark versus Umami metrics
Signal spark Umami
GitHub stars 2,097 40,194
Forks 332 8,567
Open issues 207 136
Adoption 72 100
Activity 92 100
Community 64 100
Issue health 52 96
License 96 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, spark or Umami?

Umami has more GitHub stars: 40,194 versus 2,097 for spark. The gap is 38,097 stars.

Which was updated more recently, spark or Umami?

Umami was pushed more recently: 17 November 2026 versus 05 November 2026 for spark. That is 12 days apart.

Can I self-host both spark and Umami?

Yes. This catalog marks both spark 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, spark or Umami?

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

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

Related comparisons