A · level
Metabase
89.4
50,382 stars · AGPL-3.0
Analytics
Too close to call · 89.4 to 89.0
A · level
89.4
50,382 stars · AGPL-3.0
B · level
89.0
13,817 stars · MIT
Metabase versus partytown 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; partytown is written mainly in TypeScript. The composite score is 89.4 for Metabase and 89.0 for partytown.
Metabase has 50,382 GitHub stars to partytown's 13,817, a gap of 36,565 (3.65×). Forks are 7,016 for Metabase and 460 for partytown. On the log scale used inside this pair, adoption is 100 versus 88, and the fork community is 100 versus 69.
Push history: Metabase was last pushed on 17 November 2026 (0 days ago), and partytown was last pushed on 09 November 2026 (8 days ago). Open issues stand at 4,696 for Metabase (0.093 per star) and 1 for partytown (0.000 per star). Issue-health scores are 52 and 96; activity scores are 100 and 92.
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. partytown 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 partytown. This is a procurement signal, not legal advice.
In Analytics, both Metabase (50,382 stars) and partytown (13,817 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, partytown is open source.
The lead is split. Metabase is furthest ahead on fork community (100 to 69), while partytown is furthest ahead on issue health (96 to 52). Choose the dimension a rollout cannot compromise on.
Composite score: Metabase 89.4, partytown 89.0. The margin is under one point, so this page calls a tie. Use the dimension breakdown rather than the headline number.
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 | partytown |
|---|---|---|
| GitHub stars | 50,382 | 13,817 |
| Forks | 7,016 | 460 |
| Open issues | 4,696 | 1 |
| Adoption | 100 | 88 |
| Activity | 100 | 92 |
| Community | 100 | 69 |
| Issue health | 52 | 96 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 89.4 | 89.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.
Relocate resource intensive third-party scripts off of the main thread and into a web worker. 🎉
Metabase has more GitHub stars: 50,382 versus 13,817 for partytown. The gap is 36,565 stars.
Metabase was pushed more recently: 17 November 2026 versus 09 November 2026 for partytown. That is 8 days apart.
Yes. This catalog marks both Metabase and partytown 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. partytown 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.
Neither tool clears a one-point margin. Metabase scores 89.4 and partytown scores 89.0.