A · leads
redash
96.3
28,887 stars · BSD-2-Clause
Analytics
redash leads by 11.9 · clear
A · leads
96.3
28,887 stars · BSD-2-Clause
B
84.4
7,285 stars · AGPL-3.0
redash versus Sink 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 96.3 for redash and 84.4 for Sink.
redash has 28,887 GitHub stars to Sink's 7,285, a gap of 21,602 (3.97×). Forks are 4,645 for redash and 5,404 for Sink. On the log scale used inside this pair, adoption is 100 versus 87, and the fork community is 98 versus 100.
Push history: redash was last pushed on 14 November 2026 (3 days ago), and Sink was last pushed on 27 October 2026 (21 days ago). Open issues stand at 780 for redash (0.027 per star) and 34 for Sink (0.005 per star). Issue-health scores are 70 and 96; activity scores are 100 and 78.
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. Sink 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 redash and 52 for Sink. This is a procurement signal, not legal advice.
In Analytics, both redash (28,887 stars) and Sink (7,285 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: redash is open source, Sink is open source.
The lead is split. redash is furthest ahead on license flexibility (96 to 52), while Sink is furthest ahead on issue health (96 to 70). Choose the dimension a rollout cannot compromise on.
redash finishes ahead at 96.3 against Sink at 84.4, a 11.9 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 | redash | Sink |
|---|---|---|
| GitHub stars | 28,887 | 7,285 |
| Forks | 4,645 | 5,404 |
| Open issues | 780 | 34 |
| Adoption | 100 | 87 |
| Activity | 100 | 78 |
| Community | 98 | 100 |
| Issue health | 70 | 96 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 96.3 | 84.4 |
Make Your Company Data Driven. Connect to any data source, easily visualize, dashboard and share your data.
⚡ A Simple, Speedy, Secure, and Serverless Link Shortener with Analytics, Running Entirely on Cloudflare.
redash has more GitHub stars: 28,887 versus 7,285 for Sink. The gap is 21,602 stars.
redash was pushed more recently: 14 November 2026 versus 27 October 2026 for Sink. That is 18 days apart.
Yes. This catalog marks both redash and Sink as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. Sink 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.
redash scores 96.3 and Sink scores 84.4. This page calls that a clear lead for redash.