Metabase vs Perk

Metabase and Perk (We're fixing business travel.) both appear on the Smoower Developer Ecosystem Index.

Metabase (rank #165) holds a modest lead over Perk (rank #372) on the overall Smoower ecosystem score (51 vs 42). The gap of 9 points reflects composite signals across code, docs, community and reach.

On code quality (the state of repositories, tests, releases and polish), Metabase is slightly ahead of Perk. On education (docs, guides and learning material for developers), Metabase is clearly ahead of Perk. On community (issue response, PR reviews and discussion health), Metabase is slightly ahead of Perk. On reach (how visible the ecosystem is beyond its own repos), Metabase is ahead of Perk. On momentum (release cadence and how fast the ecosystem moves), Metabase is ahead of Perk.

Metabase carries 50,225 GitHub stars across 100 public repos, with 21 repositories active in the last 90 days and 49 external contributors on record. Perk shows 34 stars across 25 public repos, 5 active in the last 90 days and 6 external contributors. The star gap on its own does not decide the comparison, but Metabase's footprint is roughly 1477.2x larger, which usually shows up in downstream signals like inbound issues and third party integrations.

Metabase is the stronger read for anyone weighting education. Perk makes more sense for teams already using its adjacent tools. The table below breaks the scores down pillar by pillar; the linked profiles cover the underlying repos, docs and community signals in full.