Skip to content
DevUtils Online

Analytics

lmnr vs Metabase

Metabase leads by 6.4 · narrow

A

lmnr

83.0

3,501 stars · Apache-2.0

B · leads

Metabase

89.4

50,382 stars · AGPL-3.0

lmnr versus Metabase is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. lmnr is written mainly in TypeScript; Metabase is written mainly in Clojure. The composite score is 83.0 for lmnr and 89.4 for Metabase.

Metabase has 50,382 GitHub stars to lmnr's 3,501, a gap of 46,881 (14.39×). Forks are 263 for lmnr and 7,016 for Metabase. On the log scale used inside this pair, adoption is 75 versus 100, and the fork community is 63 versus 100.

Push history: lmnr was last pushed on 17 November 2026 (0 days ago), and Metabase was last pushed on 17 November 2026 (0 days ago). Open issues stand at 173 for lmnr (0.049 per star) and 4,696 for Metabase (0.093 per star). Issue-health scores are 70 and 52; activity scores are 100 and 100.

lmnr 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. 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. License scores in this pair are 96 for lmnr and 52 for Metabase. This is a procurement signal, not legal advice.

In Analytics, both lmnr (3,501 stars) and Metabase (50,382 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: lmnr is open source, Metabase is freemium.

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

Metabase finishes ahead at 89.4 against lmnr at 83.0, a 6.4 point narrow 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.

lmnr versus Metabase metrics
Signal lmnr Metabase
GitHub stars 3,501 50,382
Forks 263 7,016
Open issues 173 4,696
Adoption 75 100
Activity 100 100
Community 63 100
Issue health 70 52
License 96 52
Self-hosting 100 100
Composite 83.0 89.4

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, lmnr or Metabase?

Metabase has more GitHub stars: 50,382 versus 3,501 for lmnr. The gap is 46,881 stars.

Which was updated more recently, lmnr or Metabase?

Both were last pushed on 17 November 2026.

Can I self-host both lmnr and Metabase?

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

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

lmnr 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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.

Who wins the lmnr vs Metabase score?

Metabase scores 89.4 and lmnr scores 83.0. This page calls that a narrow lead for Metabase.

Related comparisons