A
hexclave
77.9
6,893 stars · license n/a
Analytics
Metabase leads by 11.5 · clear
A
77.9
6,893 stars · license n/a
B · leads
89.4
50,382 stars · AGPL-3.0
hexclave versus Metabase is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. hexclave is written mainly in TypeScript; Metabase is written mainly in Clojure. The composite score is 77.9 for hexclave and 89.4 for Metabase.
Metabase has 50,382 GitHub stars to hexclave's 6,893, a gap of 43,489 (7.31×). Forks are 525 for hexclave and 7,016 for Metabase. On the log scale used inside this pair, adoption is 82 versus 100, and the fork community is 71 versus 100.
Push history: hexclave was last pushed on 13 November 2026 (4 days ago), and Metabase was last pushed on 17 November 2026 (0 days ago). Open issues stand at 116 for hexclave (0.017 per star) and 4,696 for Metabase (0.093 per star). Issue-health scores are 84 and 52; activity scores are 92 and 100.
hexclave 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 hexclave and 52 for Metabase. This is a procurement signal, not legal advice.
In Analytics, both hexclave (6,893 stars) and Metabase (50,382 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: hexclave is unpriced in this catalog, Metabase is freemium.
The lead is split. hexclave is furthest ahead on issue health (84 to 52), while Metabase is furthest ahead on fork community (100 to 71). Choose the dimension a rollout cannot compromise on.
Metabase finishes ahead at 89.4 against hexclave at 77.9, a 11.5 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 | hexclave | Metabase |
|---|---|---|
| GitHub stars | 6,893 | 50,382 |
| Forks | 525 | 7,016 |
| Open issues | 116 | 4,696 |
| Adoption | 82 | 100 |
| Activity | 92 | 100 |
| Community | 71 | 100 |
| Issue health | 84 | 52 |
| License | 30 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 77.9 | 89.4 |
The user infrastructure platform. You choose the frontend, backend, and database. Hexclave handles everything else.
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 6,893 for hexclave. The gap is 43,489 stars.
Metabase was pushed more recently: 17 November 2026 versus 13 November 2026 for hexclave. That is 4 days apart.
Yes. This catalog marks both hexclave and Metabase as self-hostable. Confirm each project's deploy docs before you plan a migration.
hexclave 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 hexclave scores 77.9. This page calls that a clear lead for Metabase.