A · leads
Metabase
89.4
50,382 stars · AGPL-3.0
Analytics
Metabase leads by 6.4 · narrow
A · leads
89.4
50,382 stars · AGPL-3.0
B
83.0
2,290 stars · MIT
Metabase versus talivia is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Metabase is written mainly in Clojure; talivia is written mainly in TypeScript. The composite score is 89.4 for Metabase and 83.0 for talivia.
Metabase has 50,382 GitHub stars to talivia's 2,290, a gap of 48,092 (22.00×). Forks are 7,016 for Metabase and 119 for talivia. On the log scale used inside this pair, adoption is 100 versus 72, and the fork community is 100 versus 54.
Push history: Metabase was last pushed on 17 November 2026 (0 days ago), and talivia was last pushed on 16 November 2026 (1 day ago). Open issues stand at 4,696 for Metabase (0.093 per star) and 3 for talivia (0.001 per star). Issue-health scores are 52 and 96; activity scores are 100 and 100.
Metabase 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. talivia 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 Metabase and 96 for talivia. This is a procurement signal, not legal advice.
In Analytics, both Metabase (50,382 stars) and talivia (2,290 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: Metabase is freemium, talivia is open source.
The lead is split. Metabase is furthest ahead on fork community (100 to 54), while talivia is furthest ahead on issue health (96 to 52). Choose the dimension a rollout cannot compromise on.
Metabase finishes ahead at 89.4 against talivia at 83.0, a 6.4 point narrow 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 | Metabase | talivia |
|---|---|---|
| GitHub stars | 50,382 | 2,290 |
| Forks | 7,016 | 119 |
| Open issues | 4,696 | 3 |
| Adoption | 100 | 72 |
| Activity | 100 | 100 |
| Community | 100 | 54 |
| Issue health | 52 | 96 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 89.4 | 83.0 |
Metabase is a business-intelligence tool that lets teams ask questions of a SQL database without writing a report from scratch. It is commonly self-hosted next to the warehouse it reads.
Open-source, self-hosted revenue-first analytics for founders: web analytics, Session Replay, revenue attribution, and customer revenue integrations. datafast alternative
Metabase has more GitHub stars: 50,382 versus 2,290 for talivia. The gap is 48,092 stars.
Metabase was pushed more recently: 17 November 2026 versus 16 November 2026 for talivia. That is 1 days apart.
Yes. This catalog marks both Metabase and talivia as self-hostable. Confirm each project's deploy docs before you plan a migration.
Metabase 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. talivia 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.
Metabase scores 89.4 and talivia scores 83.0. This page calls that a narrow lead for Metabase.