PharosvsReactive Resume
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| Pharos | Reactive Resume | |
|---|---|---|
| Score | 44/100 | 87/100 |
| Rank in category | #80 of 125 in AI | #1 of 46 in Document Management |
| GitHub stars | 241 | 45 012 |
| Stars, last 30 days | +0 | +1 611 |
| Stable releases, 12 months | 0 | 34 |
| Latest release | — | v6.0.7 · 26 Oct 2026 |
| Setup | Advanced | Moderate |
| Official Docker image | No | Yes |
| License | MIT | MIT |
| Main language | Python | Typescript |
Which one should you pick?
Reactive Resume scores 87/100 against 44/100 for Pharos, so it is the safer default.
Reactive Resume ships more often: 34 stable releases in the past year, against 0 for Pharos.
If you want the quickest setup, Reactive Resume is easier to run; Pharos needs more configuration.
Reactive Resume is growing faster right now (+1 611 stars in 30 days).
Pharos details →Reactive Resume details →
Swap a project
Keep Pharos, compare it with
Keep Reactive Resume, compare it with