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