A
cube
77.0
21,239 stars · license n/a
Analytics
Metabase leads by 12.4 · clear
A
77.0
21,239 stars · license n/a
B · leads
89.4
50,382 stars · AGPL-3.0
cube versus Metabase is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. cube is written mainly in Rust; Metabase is written mainly in Clojure. The composite score is 77.0 for cube and 89.4 for Metabase.
Metabase has 50,382 GitHub stars to cube's 21,239, a gap of 29,143 (2.37×). Forks are 2,197 for cube and 7,016 for Metabase. On the log scale used inside this pair, adoption is 92 versus 100, and the fork community is 87 versus 100.
Push history: cube 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 1,189 for cube (0.056 per star) and 4,696 for Metabase (0.093 per star). Issue-health scores are 52 and 52; activity scores are 100 and 100.
cube 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 cube 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). cube is not (21,239 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: cube is unpriced in this catalog, Metabase is freemium.
Metabase is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health. The widest gap is self-hosting at 65 points (35 vs 100), and the tightest is issue health at 0 points (52 vs 52).
Metabase finishes ahead at 89.4 against cube at 77.0, a 12.4 point clear 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 | cube | Metabase |
|---|---|---|
| GitHub stars | 21,239 | 50,382 |
| Forks | 2,197 | 7,016 |
| Open issues | 1,189 | 4,696 |
| Adoption | 92 | 100 |
| Activity | 100 | 100 |
| Community | 87 | 100 |
| Issue health | 52 | 52 |
| License | 30 | 52 |
| Self-hosting | 35 | 100 |
| Composite | 77.0 | 89.4 |
📊 Cube Core is open-source semantic layer for AI, BI and embedded analytics
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 21,239 for cube. The gap is 29,143 stars.
Both were last pushed on 17 November 2026.
Only Metabase is marked self-hostable. cube is not.
cube 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 cube scores 77.0. This page calls that a clear lead for Metabase.