A · leads
excelize
93.2
21,136 stars · BSD-3-Clause
Analytics
excelize leads by 3.8 · narrow
A · leads
93.2
21,136 stars · BSD-3-Clause
B
89.4
50,382 stars · AGPL-3.0
excelize versus Metabase 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; Metabase is written mainly in Clojure. The composite score is 93.2 for excelize and 89.4 for Metabase.
Metabase has 50,382 GitHub stars to excelize's 21,136, a gap of 29,246 (2.38×). Forks are 2,004 for excelize and 7,016 for Metabase. On the log scale used inside this pair, adoption is 92 versus 100, and the fork community is 86 versus 100.
Push history: excelize was last pushed on 17 November 2026 (0 days ago), and Metabase was last pushed on 17 November 2026 (0 days ago). Open issues stand at 176 for excelize (0.008 per star) and 4,696 for Metabase (0.093 per star). Issue-health scores are 84 and 52; 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. 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. License scores in this pair are 96 for excelize and 52 for Metabase. This is a procurement signal, not legal advice.
In Analytics, both excelize (21,136 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: excelize is open source, Metabase is freemium.
The lead is split. excelize is furthest ahead on license flexibility (96 to 52), while Metabase is furthest ahead on fork community (100 to 86). Choose the dimension a rollout cannot compromise on.
excelize finishes ahead at 93.2 against Metabase at 89.4, a 3.8 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 | Metabase |
|---|---|---|
| GitHub stars | 21,136 | 50,382 |
| Forks | 2,004 | 7,016 |
| Open issues | 176 | 4,696 |
| Adoption | 92 | 100 |
| Activity | 100 | 100 |
| Community | 86 | 100 |
| Issue health | 84 | 52 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 93.2 | 89.4 |
Go language library for reading and writing Microsoft Excel™ (XLAM / XLSM / XLSX / XLTM / XLTX) spreadsheets
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 21,136 for excelize. The gap is 29,246 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both excelize and Metabase 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. 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.
excelize scores 93.2 and Metabase scores 89.4. This page calls that a narrow lead for excelize.