Skip to content
DevUtils Online

Analytics

Metabase vs uPlot

Too close to call · 89.4 to 88.8

A · level

Metabase

89.4

50,382 stars · AGPL-3.0

B · level

uPlot

88.8

10,650 stars · MIT

Metabase versus uPlot 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; uPlot is written mainly in JavaScript. The composite score is 89.4 for Metabase and 88.8 for uPlot.

Metabase has 50,382 GitHub stars to uPlot's 10,650, a gap of 39,732 (4.73×). Forks are 7,016 for Metabase and 472 for uPlot. On the log scale used inside this pair, adoption is 100 versus 86, and the fork community is 100 versus 70.

Push history: Metabase was last pushed on 17 November 2026 (0 days ago), and uPlot was last pushed on 17 November 2026 (0 days ago). Open issues stand at 4,696 for Metabase (0.093 per star) and 132 for uPlot (0.012 per star). Issue-health scores are 52 and 84; 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. uPlot 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 uPlot. This is a procurement signal, not legal advice.

In Analytics, both Metabase (50,382 stars) and uPlot (10,650 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, uPlot is open source.

The lead is split. Metabase is furthest ahead on fork community (100 to 70), while uPlot is furthest ahead on license flexibility (96 to 52). Choose the dimension a rollout cannot compromise on.

Composite score: Metabase 89.4, uPlot 88.8. 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.

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.

Metabase versus uPlot metrics
Signal Metabase uPlot
GitHub stars 50,382 10,650
Forks 7,016 472
Open issues 4,696 132
Adoption 100 86
Activity 100 100
Community 100 70
Issue health 52 84
License 52 96
Self-hosting 100 100
Composite 89.4 88.8

Metabase

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.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, Metabase or uPlot?

Metabase has more GitHub stars: 50,382 versus 10,650 for uPlot. The gap is 39,732 stars.

Which was updated more recently, Metabase or uPlot?

Both were last pushed on 17 November 2026.

Can I self-host both Metabase and uPlot?

Yes. This catalog marks both Metabase and uPlot as self-hostable. Confirm each project's deploy docs before you plan a migration.

Which license is easier to embed in a commercial product, Metabase or uPlot?

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. uPlot 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 Metabase vs uPlot score?

Neither tool clears a one-point margin. Metabase scores 89.4 and uPlot scores 88.8.

Related comparisons