ClapervsReactive Resume
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| Claper | Reactive Resume | |
|---|---|---|
| Score | 59/100 | 87/100 |
| Rank in category | #8 of 18 in Content Management | #1 of 46 in Document Management |
| GitHub stars | 821 | 45 012 |
| Stars, last 30 days | +16 | +1 611 |
| Stable releases, 12 months | 8 | 34 |
| Latest release | v3.2.0 · 27 Oct 2026 | v6.0.7 · 26 Oct 2026 |
| Setup | Moderate | Moderate |
| Official Docker image | Yes | Yes |
| License | AGPL-3.0 | MIT |
| Main language | Elixir | Typescript |
Which one should you pick?
Reactive Resume scores 87/100 against 59/100 for Claper, so it is the safer default.
Reactive Resume ships more often: 34 stable releases in the past year, against 8 for Claper.
Reactive Resume is growing faster right now (+1 611 stars in 30 days).
Claper details →Reactive Resume details →
Swap a project
Keep Claper, compare it with
Keep Reactive Resume, compare it with