A
pipelinedb
63.8
2,665 stars · Apache-2.0
Analytics
Umami leads by 35.3 · decisive
A
63.8
2,665 stars · Apache-2.0
B · leads
99.1
40,194 stars · MIT
pipelinedb versus Umami is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. pipelinedb is written mainly in C; Umami is written mainly in TypeScript. The composite score is 63.8 for pipelinedb and 99.1 for Umami.
Umami has 40,194 GitHub stars to pipelinedb's 2,665, a gap of 37,529 (15.08×). Forks are 243 for pipelinedb and 8,567 for Umami. On the log scale used inside this pair, adoption is 74 versus 100, and the fork community is 61 versus 100.
Push history: pipelinedb was last pushed on 20 February 2022 (1731 days ago), and Umami was last pushed on 17 November 2026 (0 days ago). Open issues stand at 133 for pipelinedb (0.050 per star) and 136 for Umami (0.003 per star). Issue-health scores are 70 and 96; activity scores are 16 and 100.
pipelinedb 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 pipelinedb and 96 for Umami. This is a procurement signal, not legal advice.
In Analytics, both pipelinedb (2,665 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: pipelinedb 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 recent activity at 84 points (16 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
Umami finishes ahead at 99.1 against pipelinedb at 63.8, a 35.3 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 | pipelinedb | Umami |
|---|---|---|
| GitHub stars | 2,665 | 40,194 |
| Forks | 243 | 8,567 |
| Open issues | 133 | 136 |
| Adoption | 74 | 100 |
| Activity | 16 | 100 |
| Community | 61 | 100 |
| Issue health | 70 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 63.8 | 99.1 |
High-performance time-series aggregation for PostgreSQL
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,665 for pipelinedb. The gap is 37,529 stars.
Umami was pushed more recently: 17 November 2026 versus 20 February 2022 for pipelinedb. That is 1731 days apart.
Yes. This catalog marks both pipelinedb and Umami as self-hostable. Confirm each project's deploy docs before you plan a migration.
pipelinedb 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 pipelinedb scores 63.8. This page calls that a decisive lead for Umami.