A · leads
Metabase
87.7
50,382 stars · AGPL-3.0
Analytics
Metabase leads by 7.2 · clear
A · leads
87.7
50,382 stars · AGPL-3.0
B
80.5
1,223 stars · Apache-2.0
Metabase versus VisualHFT 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; VisualHFT is written mainly in C#. The composite score is 87.7 for Metabase and 80.5 for VisualHFT.
Metabase has 50,382 GitHub stars to VisualHFT's 1,223, a gap of 49,159 (41.20×). Forks are 7,016 for Metabase and 254 for VisualHFT. On the log scale used inside this pair, adoption is 100 versus 66, and the fork community is 100 versus 63.
Push history: Metabase was last pushed on 17 November 2026 (5 days ago), and VisualHFT was last pushed on 16 November 2026 (6 days ago). Open issues stand at 4,696 for Metabase (0.093 per star) and 2 for VisualHFT (0.002 per star). Issue-health scores are 52 and 96; activity scores are 92 and 92.
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. VisualHFT 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 VisualHFT. This is a procurement signal, not legal advice.
In Analytics, both Metabase (50,382 stars) and VisualHFT (1,223 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, VisualHFT is open source.
The lead is split. Metabase is furthest ahead on fork community (100 to 63), while VisualHFT is furthest ahead on issue health (96 to 52). Choose the dimension a rollout cannot compromise on.
Metabase finishes ahead at 87.7 against VisualHFT at 80.5, a 7.2 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 | Metabase | VisualHFT |
|---|---|---|
| GitHub stars | 50,382 | 1,223 |
| Forks | 7,016 | 254 |
| Open issues | 4,696 | 2 |
| Adoption | 100 | 66 |
| Activity | 92 | 92 |
| Community | 100 | 63 |
| Issue health | 52 | 96 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 87.7 | 80.5 |
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.
VisualHFT Terminal: open-source observability and decision terminal for electronic trading desks. Live Level 2 order books, microstructure analytics, and quantitative execution monitoring.
Metabase has more GitHub stars: 50,382 versus 1,223 for VisualHFT. The gap is 49,159 stars.
Metabase was pushed more recently: 17 November 2026 versus 16 November 2026 for VisualHFT. That is 1 days apart.
Yes. This catalog marks both Metabase and VisualHFT as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. VisualHFT 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.
Metabase scores 87.7 and VisualHFT scores 80.5. This page calls that a clear lead for Metabase.