ClapervsTypesense
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| Claper | Typesense | |
|---|---|---|
| Score | 59/100 | 79/100 |
| Rank in category | #8 of 18 in Content Management | #6 of 41 in Search Engines |
| GitHub stars | 821 | 27 063 |
| Stars, last 30 days | +16 | +470 |
| Stable releases, 12 months | 8 | 4 |
| Latest release | v3.2.0 · 27 Oct 2026 | v30.2 · 19 Apr 2026 |
| Setup | Moderate | Easy |
| Official Docker image | Yes | Yes |
| License | AGPL-3.0 | GPL-3.0 |
| Main language | Elixir | C |
Which one should you pick?
Typesense scores 79/100 against 59/100 for Claper, so it is the safer default.
Claper ships more often: 8 stable releases in the past year, against 4 for Typesense.
If you want the quickest setup, Typesense is easier to run; Claper needs more configuration.
Typesense is growing faster right now (+470 stars in 30 days).
Claper details →Typesense details →
Swap a project
Keep Claper, compare it with
Keep Typesense, compare it with