Skip to content
DevUtils Online

Analytics

Metabase vs quary

Metabase leads by 8.6 · clear

A · leads

Metabase

89.4

50,382 stars · AGPL-3.0

B

quary

80.8

2,389 stars · Apache-2.0

Metabase versus quary 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; quary is written mainly in Rust. The composite score is 89.4 for Metabase and 80.8 for quary.

Metabase has 50,382 GitHub stars to quary's 2,389, a gap of 47,993 (21.09×). Forks are 7,016 for Metabase and 58 for quary. On the log scale used inside this pair, adoption is 100 versus 72, and the fork community is 100 versus 46.

Push history: Metabase was last pushed on 17 November 2026 (0 days ago), and quary was last pushed on 16 November 2026 (1 day ago). Open issues stand at 4,696 for Metabase (0.093 per star) and 45 for quary (0.019 per star). Issue-health scores are 52 and 84; activity scores are 100 and 100.

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

In Analytics, both Metabase (50,382 stars) and quary (2,389 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, quary is open source.

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

Metabase finishes ahead at 89.4 against quary at 80.8, a 8.6 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 quary metrics
Signal Metabase quary
GitHub stars 50,382 2,389
Forks 7,016 58
Open issues 4,696 45
Adoption 100 72
Activity 100 100
Community 100 46
Issue health 52 84
License 52 96
Self-hosting 100 100
Composite 89.4 80.8

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

Metabase has more GitHub stars: 50,382 versus 2,389 for quary. The gap is 47,993 stars.

Which was updated more recently, Metabase or quary?

Metabase was pushed more recently: 17 November 2026 versus 16 November 2026 for quary. That is 1 days apart.

Can I self-host both Metabase and quary?

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

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

Who wins the Metabase vs quary score?

Metabase scores 89.4 and quary scores 80.8. This page calls that a clear lead for Metabase.

Related comparisons