Skip to content
DevUtils Online

Analytics

duckdb-wasm vs Umami

Umami leads by 19.2 · decisive

B · leads

Umami

99.1

40,194 stars · MIT

duckdb-wasm versus Umami is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in TypeScript. The composite score is 79.9 for duckdb-wasm and 99.1 for Umami.

Umami has 40,194 GitHub stars to duckdb-wasm's 2,172, a gap of 38,022 (18.51×). Forks are 244 for duckdb-wasm and 8,567 for Umami. On the log scale used inside this pair, adoption is 72 versus 100, and the fork community is 61 versus 100.

Push history: duckdb-wasm was last pushed on 16 November 2026 (1 day ago), and Umami was last pushed on 17 November 2026 (0 days ago). Open issues stand at 218 for duckdb-wasm (0.100 per star) and 136 for Umami (0.003 per star). Issue-health scores are 52 and 96; activity scores are 100 and 100.

Both duckdb-wasm 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 duckdb-wasm (2,172 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: duckdb-wasm is open source, Umami is open source.

Umami is ahead on every scored dimension that is not level. Level dimensions: recent activity, 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 duckdb-wasm at 79.9, a 19.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.

duckdb-wasm versus Umami metrics
Signal duckdb-wasm Umami
GitHub stars 2,172 40,194
Forks 244 8,567
Open issues 218 136
Adoption 72 100
Activity 100 100
Community 61 100
Issue health 52 96
License 96 96
Self-hosting 100 100
Composite 79.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, duckdb-wasm or Umami?

Umami has more GitHub stars: 40,194 versus 2,172 for duckdb-wasm. The gap is 38,022 stars.

Which was updated more recently, duckdb-wasm or Umami?

Umami was pushed more recently: 17 November 2026 versus 16 November 2026 for duckdb-wasm. That is 1 days apart.

Can I self-host both duckdb-wasm and Umami?

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

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

Umami scores 99.1 and duckdb-wasm scores 79.9. This page calls that a decisive lead for Umami.

Related comparisons