A
chat-analytics
55.5
1,198 stars · AGPL-3.0
Analytics
redash leads by 39.3 · decisive
A
55.5
1,198 stars · AGPL-3.0
B · leads
94.8
28,887 stars · BSD-2-Clause
chat-analytics versus redash is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in TypeScript. The composite score is 55.5 for chat-analytics and 94.8 for redash.
redash has 28,887 GitHub stars to chat-analytics's 1,198, a gap of 27,689 (24.11×). Forks are 81 for chat-analytics and 4,645 for redash. On the log scale used inside this pair, adoption is 69 versus 100, and the fork community is 52 versus 100.
Push history: chat-analytics was last pushed on 19 October 2025 (398 days ago), and redash was last pushed on 14 November 2026 (8 days ago). Open issues stand at 31 for chat-analytics (0.026 per star) and 780 for redash (0.027 per star). Issue-health scores are 70 and 70; activity scores are 16 and 92.
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. redash is listed as BSD-2-Clause, 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 chat-analytics and 96 for redash. This is a procurement signal, not legal advice.
In Analytics, both chat-analytics (1,198 stars) and redash (28,887 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, redash is open source.
redash is ahead on every scored dimension that is not level. Level dimensions: issue health, self-hosting. The widest gap is recent activity at 76 points (16 vs 92), and the tightest is self-hosting at 0 points (100 vs 100).
redash finishes ahead at 94.8 against chat-analytics at 55.5, a 39.3 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 | redash |
|---|---|---|
| GitHub stars | 1,198 | 28,887 |
| Forks | 81 | 4,645 |
| Open issues | 31 | 780 |
| Adoption | 69 | 100 |
| Activity | 16 | 92 |
| Community | 52 | 100 |
| Issue health | 70 | 70 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 55.5 | 94.8 |
Generate interactive, beautiful and insightful chat analysis reports
Make Your Company Data Driven. Connect to any data source, easily visualize, dashboard and share your data.
redash has more GitHub stars: 28,887 versus 1,198 for chat-analytics. The gap is 27,689 stars.
redash was pushed more recently: 14 November 2026 versus 19 October 2025 for chat-analytics. That is 390 days apart.
Yes. This catalog marks both chat-analytics and redash 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. redash is listed as BSD-2-Clause, 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.
redash scores 94.8 and chat-analytics scores 55.5. This page calls that a decisive lead for redash.