Customer IO vs Perk

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

Customer IO (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), Customer IO is ahead of Perk. On education (docs, guides and learning material for developers), Customer IO is clearly ahead of Perk. On community (issue response, PR reviews and discussion health), Perk is slightly ahead of Customer IO. On reach (how visible the ecosystem is beyond its own repos), Customer IO is ahead of Perk. On momentum (release cadence and how fast the ecosystem moves), Perk is slightly ahead of Customer IO.

Customer IO carries 684 GitHub stars across 107 public repos, with 42 repositories active in the last 90 days and 26 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 Customer IO's footprint is roughly 20.1x larger, which usually shows up in downstream signals like inbound issues and third party integrations.

Customer IO is the stronger read for anyone weighting education. Perk looks better where community 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.