A
chat-analytics
54.0
1,198 stars · AGPL-3.0
Analytics
Metabase leads by 33.7 · decisive
A
54.0
1,198 stars · AGPL-3.0
B · leads
87.7
50,382 stars · AGPL-3.0
chat-analytics versus Metabase is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. chat-analytics is written mainly in TypeScript; Metabase is written mainly in Clojure. The composite score is 54.0 for chat-analytics and 87.7 for Metabase.
Metabase has 50,382 GitHub stars to chat-analytics's 1,198, a gap of 49,184 (42.06×). Forks are 81 for chat-analytics and 7,016 for Metabase. On the log scale used inside this pair, adoption is 66 versus 100, and the fork community is 50 versus 100.
Push history: chat-analytics was last pushed on 19 October 2025 (398 days ago), and Metabase was last pushed on 17 November 2026 (5 days ago). Open issues stand at 31 for chat-analytics (0.026 per star) and 4,696 for Metabase (0.093 per star). Issue-health scores are 70 and 52; activity scores are 16 and 92.
Both chat-analytics and Metabase are listed as AGPL-3.0. A network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. The license score is therefore level at 52 versus 52, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In Analytics, both chat-analytics (1,198 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: chat-analytics is open source, Metabase is freemium.
The lead is split. chat-analytics is furthest ahead on issue health (70 to 52), while Metabase is furthest ahead on recent activity (92 to 16). Choose the dimension a rollout cannot compromise on.
Metabase finishes ahead at 87.7 against chat-analytics at 54.0, a 33.7 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 | chat-analytics | Metabase |
|---|---|---|
| GitHub stars | 1,198 | 50,382 |
| Forks | 81 | 7,016 |
| Open issues | 31 | 4,696 |
| Adoption | 66 | 100 |
| Activity | 16 | 92 |
| Community | 50 | 100 |
| Issue health | 70 | 52 |
| License | 52 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 54.0 | 87.7 |
Generate interactive, beautiful and insightful chat analysis reports
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,198 for chat-analytics. The gap is 49,184 stars.
Metabase was pushed more recently: 17 November 2026 versus 19 October 2025 for chat-analytics. That is 393 days apart.
Yes. This catalog marks both chat-analytics and Metabase as self-hostable. Confirm each project's deploy docs before you plan a migration.
chat-analytics 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. 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 87.7 and chat-analytics scores 54.0. This page calls that a decisive lead for Metabase.