A · leads
excelize
97.9
21,136 stars · BSD-3-Clause
Analytics
excelize leads by 8.0 · clear
A · leads
97.9
21,136 stars · BSD-3-Clause
B
89.9
10,891 stars · AGPL-3.0
excelize versus lago 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 Go. The composite score is 97.9 for excelize and 89.9 for lago.
excelize has 21,136 GitHub stars to lago's 10,891, a gap of 10,245 (1.94×). Forks are 2,004 for excelize and 798 for lago. On the log scale used inside this pair, adoption is 100 versus 93, and the fork community is 100 versus 88.
Push history: excelize was last pushed on 17 November 2026 (0 days ago), and lago was last pushed on 17 November 2026 (0 days ago). Open issues stand at 176 for excelize (0.008 per star) and 17 for lago (0.002 per star). Issue-health scores are 84 and 96; 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. lago 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 excelize and 52 for lago. This is a procurement signal, not legal advice.
In Analytics, both excelize (21,136 stars) and lago (10,891 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, lago is open source.
The lead is split. excelize is furthest ahead on license flexibility (96 to 52), while lago is furthest ahead on issue health (96 to 84). Choose the dimension a rollout cannot compromise on.
excelize finishes ahead at 97.9 against lago at 89.9, a 8.0 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 | excelize | lago |
|---|---|---|
| GitHub stars | 21,136 | 10,891 |
| Forks | 2,004 | 798 |
| Open issues | 176 | 17 |
| Adoption | 100 | 93 |
| Activity | 100 | 100 |
| Community | 100 | 88 |
| Issue health | 84 | 96 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 89.9 |
Go language library for reading and writing Microsoft Excel™ (XLAM / XLSM / XLSX / XLTM / XLTX) spreadsheets
Open Source Metering and Usage Based Billing API ⭐️ Consumption tracking, Subscription management, Pricing iterations, Payment orchestration & Revenue analytics
excelize has more GitHub stars: 21,136 versus 10,891 for lago. The gap is 10,245 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both excelize and lago 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. lago 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.
excelize scores 97.9 and lago scores 89.9. This page calls that a clear lead for excelize.