Pleo vs Perk
Developer ecosystem comparison across GitHub activity, SDKs, documentation, community, reach and momentum.
Pleo and Perk (We're fixing business travel.) both appear on the Smoower Developer Ecosystem Index.
Perk (rank #372) holds a modest lead over Pleo (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 education (docs, guides and learning material for developers), Pleo is ahead of Perk. On community (issue response, PR reviews and discussion health), Perk is ahead of Pleo. On reach (how visible the ecosystem is beyond its own repos), Perk is ahead of Pleo. On momentum (release cadence and how fast the ecosystem moves), Pleo is clearly ahead of Perk.
Pleo carries 36 GitHub stars across 34 public repos, with 5 repositories active in the last 90 days and 8 external contributors on record. Perk shows 34 stars across 25 public repos, 5 active in the last 90 days and 6 external contributors.
Pleo 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.
Side-by-side metrics
| Metric | Pleo | Perk |
|---|---|---|
| Ranking | ||
| Overall rank | #625 | #372 |
| Pillars | ||
| Overall | 33 | 42 |
| Code | 44 | 44 |
| Education | 65 | 54 |
| Community | 20 | 38 |
| Reach | 11 | 30 |
| Momentum | 76 | 48 |
| Builder experience | 0 | 0 |
| Signals | ||
| Stars | 36 | 34 |
| Forks | 75 | 11 |
| Public repos | 34 | 25 |
| Active repos (90d) | 5 | 5 |
| External contributors | 8 | 6 |
| Avg polish | 45 | 33 |
| Avg AI-readiness | 26 | 38 |