A
excelize
95.5
21,136 stars · BSD-3-Clause
Analytics
redash leads by 1.0 · narrow
A
95.5
21,136 stars · BSD-3-Clause
B · leads
96.5
28,887 stars · BSD-2-Clause
excelize versus redash is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. excelize is written mainly in Go; redash is written mainly in TypeScript. The composite score is 95.5 for excelize and 96.5 for redash.
redash has 28,887 GitHub stars to excelize's 21,136, a gap of 7,751 (1.37×). Forks are 2,004 for excelize and 4,645 for redash. On the log scale used inside this pair, adoption is 97 versus 100, and the fork community is 90 versus 100.
Push history: excelize was last pushed on 17 November 2026 (0 days ago), and redash was last pushed on 14 November 2026 (3 days ago). Open issues stand at 176 for excelize (0.008 per star) and 780 for redash (0.027 per star). Issue-health scores are 84 and 70; activity scores are 100 and 100.
excelize is listed as BSD-3-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. 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 96 for excelize and 96 for redash. This is a procurement signal, not legal advice.
In Analytics, both excelize (21,136 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: excelize is open source, redash is open source.
The lead is split. excelize is furthest ahead on issue health (84 to 70), while redash is furthest ahead on fork community (100 to 90). Choose the dimension a rollout cannot compromise on.
redash finishes ahead at 96.5 against excelize at 95.5, a 1.0 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 | excelize | redash |
|---|---|---|
| GitHub stars | 21,136 | 28,887 |
| Forks | 2,004 | 4,645 |
| Open issues | 176 | 780 |
| Adoption | 97 | 100 |
| Activity | 100 | 100 |
| Community | 90 | 100 |
| Issue health | 84 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 95.5 | 96.5 |
Go language library for reading and writing Microsoft Excel™ (XLAM / XLSM / XLSX / XLTM / XLTX) spreadsheets
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 21,136 for excelize. The gap is 7,751 stars.
excelize was pushed more recently: 17 November 2026 versus 14 November 2026 for redash. That is 3 days apart.
Yes. This catalog marks both excelize and redash as self-hostable. Confirm each project's deploy docs before you plan a migration.
excelize is listed as BSD-3-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. 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 96.5 and excelize scores 95.5. This page calls that a narrow lead for redash.