A
age
81.7
4,948 stars · Apache-2.0
Analytics
Metabase leads by 7.7 · clear
A
81.7
4,948 stars · Apache-2.0
B · leads
89.4
50,382 stars · AGPL-3.0
age versus Metabase is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. age is written mainly in C; Metabase is written mainly in Clojure. The composite score is 81.7 for age and 89.4 for Metabase.
Metabase has 50,382 GitHub stars to age's 4,948, a gap of 45,434 (10.18×). Forks are 547 for age and 7,016 for Metabase. On the log scale used inside this pair, adoption is 79 versus 100, and the fork community is 71 versus 100.
Push history: age was last pushed on 04 November 2026 (12 days ago), and Metabase was last pushed on 17 November 2026 (0 days ago). Open issues stand at 269 for age (0.054 per star) and 4,696 for Metabase (0.093 per star). Issue-health scores are 52 and 52; activity scores are 92 and 100.
age is listed as Apache-2.0, 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 age and 52 for Metabase. This is a procurement signal, not legal advice.
In Analytics, both age (4,948 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: age is open source, Metabase is freemium.
The lead is split. age is furthest ahead on license flexibility (96 to 52), while Metabase is furthest ahead on fork community (100 to 71). Choose the dimension a rollout cannot compromise on.
Metabase finishes ahead at 89.4 against age at 81.7, a 7.7 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 | age | Metabase |
|---|---|---|
| GitHub stars | 4,948 | 50,382 |
| Forks | 547 | 7,016 |
| Open issues | 269 | 4,696 |
| Adoption | 79 | 100 |
| Activity | 92 | 100 |
| Community | 71 | 100 |
| Issue health | 52 | 52 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 81.7 | 89.4 |
Graph database optimized for fast analysis and real-time data processing. It is provided as an extension to PostgreSQL.
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 4,948 for age. The gap is 45,434 stars.
Metabase was pushed more recently: 17 November 2026 versus 04 November 2026 for age. That is 12 days apart.
Yes. This catalog marks both age and Metabase as self-hostable. Confirm each project's deploy docs before you plan a migration.
age is listed as Apache-2.0, 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.
Metabase scores 89.4 and age scores 81.7. This page calls that a clear lead for Metabase.