Skip to content
DevUtils Online

Analytics

lago vs Metabase

Metabase leads by 3.8 · narrow

A

lago

85.6

10,891 stars · AGPL-3.0

B · leads

Metabase

89.4

50,382 stars · AGPL-3.0

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

Metabase has 50,382 GitHub stars to lago's 10,891, a gap of 39,491 (4.63×). Forks are 798 for lago and 7,016 for Metabase. On the log scale used inside this pair, adoption is 86 versus 100, and the fork community is 76 versus 100.

Push history: lago 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 17 for lago (0.002 per star) and 4,696 for Metabase (0.093 per star). Issue-health scores are 96 and 52; activity scores are 100 and 100.

Both lago and Metabase are listed as AGPL-3.0. A network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. The license score is therefore level at 52 versus 52, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.

In Analytics, both lago (10,891 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: lago is open source, Metabase is freemium.

The lead is split. lago is furthest ahead on issue health (96 to 52), while Metabase is furthest ahead on fork community (100 to 76). Choose the dimension a rollout cannot compromise on.

Metabase finishes ahead at 89.4 against lago at 85.6, a 3.8 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.

lago versus Metabase metrics
Signal lago Metabase
GitHub stars 10,891 50,382
Forks 798 7,016
Open issues 17 4,696
Adoption 86 100
Activity 100 100
Community 76 100
Issue health 96 52
License 52 52
Self-hosting 100 100
Composite 85.6 89.4

lago

Open Source Metering and Usage Based Billing API ⭐️ Consumption tracking, Subscription management, Pricing iterations, Payment orchestration & Revenue analytics

Project site · GitHub · Full profile

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

Metabase has more GitHub stars: 50,382 versus 10,891 for lago. The gap is 39,491 stars.

Which was updated more recently, lago or Metabase?

Both were last pushed on 17 November 2026.

Can I self-host both lago and Metabase?

Yes. This catalog marks both lago 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, lago or Metabase?

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

Metabase scores 89.4 and lago scores 85.6. This page calls that a narrow lead for Metabase.

Related comparisons