A
anyquery
64.5
1,793 stars · license n/a
Analytics
Metabase leads by 24.9 · decisive
A
64.5
1,793 stars · license n/a
B · leads
89.4
50,382 stars · AGPL-3.0
anyquery versus Metabase is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. anyquery is written mainly in Go; Metabase is written mainly in Clojure. The composite score is 64.5 for anyquery and 89.4 for Metabase.
Metabase has 50,382 GitHub stars to anyquery's 1,793, a gap of 48,589 (28.10×). Forks are 142 for anyquery and 7,016 for Metabase. On the log scale used inside this pair, adoption is 69 versus 100, and the fork community is 56 versus 100.
Push history: anyquery was last pushed on 08 October 2026 (40 days ago), and Metabase was last pushed on 17 November 2026 (0 days ago). Open issues stand at 4 for anyquery (0.002 per star) and 4,696 for Metabase (0.093 per star). Issue-health scores are 96 and 52; activity scores are 78 and 100.
anyquery 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 anyquery 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). anyquery is not (1,793 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: anyquery is unpriced in this catalog, Metabase is freemium.
The lead is split. anyquery is furthest ahead on issue health (96 to 52), while Metabase is furthest ahead on self-hosting (100 to 35). Choose the dimension a rollout cannot compromise on.
Metabase finishes ahead at 89.4 against anyquery at 64.5, a 24.9 point decisive margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | anyquery | Metabase |
|---|---|---|
| GitHub stars | 1,793 | 50,382 |
| Forks | 142 | 7,016 |
| Open issues | 4 | 4,696 |
| Adoption | 69 | 100 |
| Activity | 78 | 100 |
| Community | 56 | 100 |
| Issue health | 96 | 52 |
| License | 30 | 52 |
| Self-hosting | 35 | 100 |
| Composite | 64.5 | 89.4 |
One SQL interface for 60+ tools (e.g., GitHub, Notion, Airtable). Plug into any LLM through MCP.
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.
Metabase has more GitHub stars: 50,382 versus 1,793 for anyquery. The gap is 48,589 stars.
Metabase was pushed more recently: 17 November 2026 versus 08 October 2026 for anyquery. That is 40 days apart.
Only Metabase is marked self-hostable. anyquery is not.
anyquery 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.
Metabase scores 89.4 and anyquery scores 64.5. This page calls that a decisive lead for Metabase.