ClapervsResume-Matcher
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| Claper | Resume-Matcher | |
|---|---|---|
| Score | 59/100 | 81/100 |
| Rank in category | #8 of 18 in Content Management | #1 of 12 in Document Processing |
| GitHub stars | 821 | 28 920 |
| Stars, last 30 days | +16 | +406 |
| Stable releases, 12 months | 8 | 5 |
| Latest release | v3.2.0 · 27 Oct 2026 | v1.4.0 · 21 Oct 2026 |
| Setup | Moderate | Easy |
| Official Docker image | Yes | Yes |
| License | AGPL-3.0 | Apache-2.0 |
| Main language | Elixir | Python |
Which one should you pick?
Resume-Matcher scores 81/100 against 59/100 for Claper, so it is the safer default.
Claper ships more often: 8 stable releases in the past year, against 5 for Resume-Matcher.
If you want the quickest setup, Resume-Matcher is easier to run; Claper needs more configuration.
Resume-Matcher is growing faster right now (+406 stars in 30 days).
Claper details →Resume-Matcher details →
Swap a project
Keep Claper, compare it with
Keep Resume-Matcher, compare it with