A
laravel-analytics
84.5
3,249 stars · MIT
Analytics
Metabase leads by 4.9 · narrow
A
84.5
3,249 stars · MIT
B · leads
89.4
50,382 stars · AGPL-3.0
laravel-analytics versus Metabase is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. laravel-analytics is written mainly in PHP; Metabase is written mainly in Clojure. The composite score is 84.5 for laravel-analytics and 89.4 for Metabase.
Metabase has 50,382 GitHub stars to laravel-analytics's 3,249, a gap of 47,133 (15.51×). Forks are 471 for laravel-analytics and 7,016 for Metabase. On the log scale used inside this pair, adoption is 75 versus 100, and the fork community is 70 versus 100.
Push history: laravel-analytics was last pushed on 05 November 2026 (12 days ago), and Metabase was last pushed on 17 November 2026 (0 days ago). Open issues stand at 0 for laravel-analytics (0.000 per star) and 4,696 for Metabase (0.093 per star). Issue-health scores are 96 and 52; activity scores are 92 and 100.
laravel-analytics 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 laravel-analytics and 52 for Metabase. This is a procurement signal, not legal advice.
In Analytics, both laravel-analytics (3,249 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: laravel-analytics is open source, Metabase is freemium.
The lead is split. laravel-analytics is furthest ahead on issue health (96 to 52), while Metabase is furthest ahead on fork community (100 to 70). Choose the dimension a rollout cannot compromise on.
Metabase finishes ahead at 89.4 against laravel-analytics at 84.5, a 4.9 point narrow 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 | laravel-analytics | Metabase |
|---|---|---|
| GitHub stars | 3,249 | 50,382 |
| Forks | 471 | 7,016 |
| Open issues | 0 | 4,696 |
| Adoption | 75 | 100 |
| Activity | 92 | 100 |
| Community | 70 | 100 |
| Issue health | 96 | 52 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 84.5 | 89.4 |
A Laravel package to retrieve pageviews and other data from Google 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 3,249 for laravel-analytics. The gap is 47,133 stars.
Metabase was pushed more recently: 17 November 2026 versus 05 November 2026 for laravel-analytics. That is 12 days apart.
Yes. This catalog marks both laravel-analytics and Metabase as self-hostable. Confirm each project's deploy docs before you plan a migration.
laravel-analytics 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 laravel-analytics scores 84.5. This page calls that a narrow lead for Metabase.