BTW we use OCaml
Ahrefs vs Clio
Developer ecosystem comparison across GitHub activity, SDKs, documentation, community, reach and momentum.
Ahrefs (BTW we use OCaml) and Clio both appear on the Smoower Developer Ecosystem Index.
Ahrefs (rank #401) holds a narrow lead over Clio (rank #625) on the overall Smoower ecosystem score (41 vs 33). The gap of 8 points reflects composite signals across code, docs, community and reach.
On code quality (the state of repositories, tests, releases and polish), Clio is slightly ahead of Ahrefs. On education (docs, guides and learning material for developers), Clio is clearly ahead of Ahrefs. On community (issue response, PR reviews and discussion health), Ahrefs is ahead of Clio. On reach (how visible the ecosystem is beyond its own repos), Ahrefs is clearly ahead of Clio. On momentum (release cadence and how fast the ecosystem moves), Ahrefs is clearly ahead of Clio.
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. Clio shows 518 stars across 19 public repos, 4 active in the last 90 days and 3 external contributors.
Ahrefs is the stronger read for anyone weighting momentum. Clio 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 | Clio |
|---|---|---|
| Ranking | ||
| Overall rank | #401 | #625 |
| Pillars | ||
| Overall | 41 | 33 |
| Code | 42 | 50 |
| Education | 57 | 84 |
| Community | 37 | 18 |
| Reach | 21 | 0 |
| Momentum | 65 | 42 |
| Builder experience | 0 | 0 |
| Signals | ||
| Stars | 1,303 | 518 |
| Forks | 261 | 163 |
| Public repos | 171 | 19 |
| Active repos (90d) | 28 | 4 |
| External contributors | 7 | 3 |
| Avg polish | 40 | 38 |
| Avg AI-readiness | 35 | 39 |