Iterable vs Perk

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

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

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

Iterable carries 269 GitHub stars across 100 public repos, with 16 repositories active in the last 90 days and 10 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 Iterable's footprint is roughly 7.9x larger, which usually shows up in downstream signals like inbound issues and third party integrations.

Iterable is the stronger read for anyone weighting momentum. Perk looks better where reach 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.