Skip to content
DevUtils Online

Analytics

lotus vs Metabase

Metabase leads by 8.1 · clear

A

lotus

81.3

1,844 stars · MIT

B · leads

Metabase

89.4

50,382 stars · AGPL-3.0

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

Metabase has 50,382 GitHub stars to lotus's 1,844, a gap of 48,538 (27.32×). Forks are 138 for lotus and 7,016 for Metabase. On the log scale used inside this pair, adoption is 70 versus 100, and the fork community is 56 versus 100.

Push history: lotus 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 36 for lotus (0.020 per star) and 4,696 for Metabase (0.093 per star). Issue-health scores are 84 and 52; activity scores are 100 and 100.

lotus 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. 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 lotus and 52 for Metabase. This is a procurement signal, not legal advice.

In Analytics, both lotus (1,844 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: lotus is open source, Metabase is freemium.

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

Metabase finishes ahead at 89.4 against lotus at 81.3, a 8.1 point clear 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.

lotus versus Metabase metrics
Signal lotus Metabase
GitHub stars 1,844 50,382
Forks 138 7,016
Open issues 36 4,696
Adoption 70 100
Activity 100 100
Community 56 100
Issue health 84 52
License 96 52
Self-hosting 100 100
Composite 81.3 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, lotus or Metabase?

Metabase has more GitHub stars: 50,382 versus 1,844 for lotus. The gap is 48,538 stars.

Which was updated more recently, lotus or Metabase?

Both were last pushed on 17 November 2026.

Can I self-host both lotus and Metabase?

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

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

Metabase scores 89.4 and lotus scores 81.3. This page calls that a clear lead for Metabase.

Related comparisons