BTW we use OCaml
Ahrefs vs Customer IO
Developer ecosystem comparison across GitHub activity, SDKs, documentation, community, reach and momentum.
Ahrefs (BTW we use OCaml) and Customer IO both appear on the Smoower Developer Ecosystem Index.
Customer IO (rank #165) holds a modest lead over Ahrefs (rank #401) on the overall Smoower ecosystem score (51 vs 41). The gap of 10 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 Ahrefs. On education (docs, guides and learning material for developers), Customer IO is clearly ahead of Ahrefs. On community (issue response, PR reviews and discussion health), Ahrefs is slightly ahead of Customer IO. On reach (how visible the ecosystem is beyond its own repos), Customer IO is ahead of Ahrefs. On momentum (release cadence and how fast the ecosystem moves), Ahrefs is ahead of Customer IO.
Ahrefs carries 1,303 GitHub stars across 171 public repos, with 28 repositories active in the last 90 days and 7 external contributors on record. Customer IO shows 684 stars across 107 public repos, 42 active in the last 90 days and 26 external contributors.
Ahrefs is the stronger read for anyone weighting momentum. Customer IO looks better where education 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 | Ahrefs | Customer IO |
|---|---|---|
| Ranking | ||
| Overall rank | #401 | #165 |
| Pillars | ||
| Overall | 41 | 51 |
| Code | 42 | 54 |
| Education | 57 | 80 |
| Community | 37 | 35 |
| Reach | 21 | 40 |
| Momentum | 65 | 45 |
| Builder experience | 0 | 0 |
| Signals | ||
| Stars | 1,303 | 684 |
| Forks | 261 | 346 |
| Public repos | 171 | 107 |
| Active repos (90d) | 28 | 42 |
| External contributors | 7 | 26 |
| Avg polish | 40 | 54 |
| Avg AI-readiness | 35 | 46 |