Skip to content
DevUtils Online

Analytics

Metabase vs rotki

Metabase leads by 11.3 · clear

A · leads

Metabase

89.4

50,382 stars · AGPL-3.0

B

rotki

78.1

4,093 stars · AGPL-3.0

Metabase versus rotki 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; rotki is written mainly in Python. The composite score is 89.4 for Metabase and 78.1 for rotki.

Metabase has 50,382 GitHub stars to rotki's 4,093, a gap of 46,289 (12.31×). Forks are 7,016 for Metabase and 791 for rotki. On the log scale used inside this pair, adoption is 100 versus 77, and the fork community is 100 versus 75.

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

Both Metabase and rotki 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 Metabase (50,382 stars) and rotki (4,093 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, rotki is open source.

Metabase is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, license flexibility, self-hosting. The widest gap is fork community at 25 points (100 vs 75), and the tightest is self-hosting at 0 points (100 vs 100).

Metabase finishes ahead at 89.4 against rotki at 78.1, a 11.3 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.

Metabase versus rotki metrics
Signal Metabase rotki
GitHub stars 50,382 4,093
Forks 7,016 791
Open issues 4,696 353
Adoption 100 77
Activity 100 100
Community 100 75
Issue health 52 52
License 52 52
Self-hosting 100 100
Composite 89.4 78.1

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 rotki?

Metabase has more GitHub stars: 50,382 versus 4,093 for rotki. The gap is 46,289 stars.

Which was updated more recently, Metabase or rotki?

Both were last pushed on 17 November 2026.

Can I self-host both Metabase and rotki?

Yes. This catalog marks both Metabase and rotki 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 rotki?

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

Metabase scores 89.4 and rotki scores 78.1. This page calls that a clear lead for Metabase.

Related comparisons