Ashby vs Perk

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

Perk (rank #372) holds a narrow lead over Ashby (rank #536) on the overall Smoower ecosystem score (42 vs 36). The gap of 6 points reflects composite signals across code, docs, community and reach.

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

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

Ashby is the stronger read for anyone weighting education. 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.