Skip to content
DevUtils Online

Analytics

eventql vs Metabase

Metabase leads by 43.0 · decisive

A

eventql

44.7

1,176 stars · license n/a

B · leads

Metabase

87.7

50,382 stars · AGPL-3.0

eventql versus Metabase is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. eventql is written mainly in C++; Metabase is written mainly in Clojure. The composite score is 44.7 for eventql and 87.7 for Metabase.

Metabase has 50,382 GitHub stars to eventql's 1,176, a gap of 49,206 (42.84×). Forks are 104 for eventql and 7,016 for Metabase. On the log scale used inside this pair, adoption is 65 versus 100, and the fork community is 53 versus 100.

Push history: eventql was last pushed on 06 May 2017 (3487 days ago), and Metabase was last pushed on 17 November 2026 (5 days ago). Open issues stand at 113 for eventql (0.096 per star) and 4,696 for Metabase (0.093 per star). Issue-health scores are 52 and 52; activity scores are 16 and 92.

eventql is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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 30 for eventql and 52 for Metabase. This is a procurement signal, not legal advice.

Only Metabase is marked self-hostable here (50,382 stars, deploy score 100). eventql is not (1,176 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: eventql is unpriced in this catalog, Metabase is freemium.

Metabase is ahead on every scored dimension that is not level. Level dimensions: issue health. The widest gap is recent activity at 76 points (16 vs 92), and the tightest is issue health at 0 points (52 vs 52).

Metabase finishes ahead at 87.7 against eventql at 44.7, a 43.0 point decisive 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.

eventql versus Metabase metrics
Signal eventql Metabase
GitHub stars 1,176 50,382
Forks 104 7,016
Open issues 113 4,696
Adoption 65 100
Activity 16 92
Community 53 100
Issue health 52 52
License 30 52
Self-hosting 35 100
Composite 44.7 87.7

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

Metabase has more GitHub stars: 50,382 versus 1,176 for eventql. The gap is 49,206 stars.

Which was updated more recently, eventql or Metabase?

Metabase was pushed more recently: 17 November 2026 versus 06 May 2017 for eventql. That is 3482 days apart.

Can I self-host both eventql and Metabase?

Only Metabase is marked self-hostable. eventql is not.

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

eventql is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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 eventql vs Metabase score?

Metabase scores 87.7 and eventql scores 44.7. This page calls that a decisive lead for Metabase.

Related comparisons