A
litlyx
68.0
1,748 stars · Apache-2.0
Analytics
Metabase leads by 21.4 · decisive
A
68.0
1,748 stars · Apache-2.0
B · leads
89.4
50,382 stars · AGPL-3.0
litlyx versus Metabase is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. litlyx is written mainly in TypeScript; Metabase is written mainly in Clojure. The composite score is 68.0 for litlyx and 89.4 for Metabase.
Metabase has 50,382 GitHub stars to litlyx's 1,748, a gap of 48,634 (28.82×). Forks are 115 for litlyx and 7,016 for Metabase. On the log scale used inside this pair, adoption is 69 versus 100, and the fork community is 54 versus 100.
Push history: litlyx was last pushed on 03 December 2025 (349 days ago), and Metabase was last pushed on 17 November 2026 (0 days ago). Open issues stand at 7 for litlyx (0.004 per star) and 4,696 for Metabase (0.093 per star). Issue-health scores are 96 and 52; activity scores are 36 and 100.
litlyx 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. 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 litlyx and 52 for Metabase. This is a procurement signal, not legal advice.
In Analytics, both litlyx (1,748 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: litlyx is open source, Metabase is freemium.
The lead is split. litlyx 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 litlyx at 68.0, a 21.4 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 | litlyx | Metabase |
|---|---|---|
| GitHub stars | 1,748 | 50,382 |
| Forks | 115 | 7,016 |
| Open issues | 7 | 4,696 |
| Adoption | 69 | 100 |
| Activity | 36 | 100 |
| Community | 54 | 100 |
| Issue health | 96 | 52 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 68.0 | 89.4 |
Powerful Analytics Solution. Setup in 30 seconds. Display all your data on a Simple, AI-powered dashboard. Fully self-hostable and GDPR compliant. Alternative to Google Analytics, MixPanel, Plausible, Umami & Matomo.
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,748 for litlyx. The gap is 48,634 stars.
Metabase was pushed more recently: 17 November 2026 versus 03 December 2025 for litlyx. That is 349 days apart.
Yes. This catalog marks both litlyx and Metabase as self-hostable. Confirm each project's deploy docs before you plan a migration.
litlyx 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. 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 litlyx scores 68.0. This page calls that a decisive lead for Metabase.