Sage vs Perk

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

Perk (rank #372) holds a modest lead over Sage (rank #625) on the overall Smoower ecosystem score (42 vs 33). 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), Sage is ahead of Perk. On education (docs, guides and learning material for developers), Perk is slightly ahead of Sage. On community (issue response, PR reviews and discussion health), Perk is slightly ahead of Sage. On reach (how visible the ecosystem is beyond its own repos), Perk is slightly ahead of Sage. On momentum (release cadence and how fast the ecosystem moves), Perk is clearly ahead of Sage.

Sage carries 2,180 GitHub stars across 122 public repos, with 6 repositories active in the last 90 days and 22 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 Sage's footprint is roughly 64.1x larger, which usually shows up in downstream signals like inbound issues and third party integrations.

Sage is the stronger read for anyone weighting code quality. Perk looks better where momentum is the deciding factor. The table below breaks the scores down pillar by pillar; the linked profiles cover the underlying repos, docs and community signals in full.