Skip to content
DevUtils Online

Analytics

timescaledb vs Umami

Umami leads by 19.0 · decisive

B · leads

Umami

99.1

40,194 stars · MIT

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

Umami has 40,194 GitHub stars to timescaledb's 23,865, a gap of 16,329 (1.68×). Forks are 1,188 for timescaledb and 8,567 for Umami. On the log scale used inside this pair, adoption is 95 versus 100, and the fork community is 78 versus 100.

Push history: timescaledb 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 476 for timescaledb (0.020 per star) and 136 for Umami (0.003 per star). Issue-health scores are 84 and 96; activity scores are 100 and 100.

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

Umami is ahead on every scored dimension that is not level. Level dimensions: recent activity. The widest gap is license flexibility at 66 points (30 vs 96), and the tightest is recent activity at 0 points (100 vs 100).

Umami finishes ahead at 99.1 against timescaledb at 80.1, a 19.0 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.

timescaledb versus Umami metrics
Signal timescaledb Umami
GitHub stars 23,865 40,194
Forks 1,188 8,567
Open issues 476 136
Adoption 95 100
Activity 100 100
Community 78 100
Issue health 84 96
License 30 96
Self-hosting 35 100
Composite 80.1 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, timescaledb or Umami?

Umami has more GitHub stars: 40,194 versus 23,865 for timescaledb. The gap is 16,329 stars.

Which was updated more recently, timescaledb or Umami?

Both were last pushed on 17 November 2026.

Can I self-host both timescaledb and Umami?

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

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

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

Umami scores 99.1 and timescaledb scores 80.1. This page calls that a decisive lead for Umami.

Related comparisons