A
fathom
74.7
8,035 stars · MIT
Analytics
Metabase leads by 14.7 · clear
A
74.7
8,035 stars · MIT
B · leads
89.4
50,382 stars · AGPL-3.0
fathom versus Metabase is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. fathom is written mainly in Go; Metabase is written mainly in Clojure. The composite score is 74.7 for fathom and 89.4 for Metabase.
Metabase has 50,382 GitHub stars to fathom's 8,035, a gap of 42,347 (6.27×). Forks are 388 for fathom and 7,016 for Metabase. On the log scale used inside this pair, adoption is 83 versus 100, and the fork community is 67 versus 100.
Push history: fathom was last pushed on 18 March 2026 (244 days ago), and Metabase was last pushed on 17 November 2026 (0 days ago). Open issues stand at 5 for fathom (0.001 per star) and 4,696 for Metabase (0.093 per star). Issue-health scores are 96 and 52; activity scores are 36 and 100.
fathom is listed as MIT, 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. 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 96 for fathom and 52 for Metabase. This is a procurement signal, not legal advice.
In Analytics, both fathom (8,035 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: fathom is open source, Metabase is freemium.
The lead is split. fathom is furthest ahead on issue health (96 to 52), while Metabase is furthest ahead on recent activity (100 to 36). Choose the dimension a rollout cannot compromise on.
Metabase finishes ahead at 89.4 against fathom at 74.7, a 14.7 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 | fathom | Metabase |
|---|---|---|
| GitHub stars | 8,035 | 50,382 |
| Forks | 388 | 7,016 |
| Open issues | 5 | 4,696 |
| Adoption | 83 | 100 |
| Activity | 36 | 100 |
| Community | 67 | 100 |
| Issue health | 96 | 52 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 74.7 | 89.4 |
Fathom Lite. Simple, privacy-focused website analytics. Built with Golang & Preact.
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 8,035 for fathom. The gap is 42,347 stars.
Metabase was pushed more recently: 17 November 2026 versus 18 March 2026 for fathom. That is 244 days apart.
Yes. This catalog marks both fathom and Metabase as self-hostable. Confirm each project's deploy docs before you plan a migration.
fathom is listed as MIT, 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. 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 fathom scores 74.7. This page calls that a clear lead for Metabase.