FloodvsReactive Resume
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| Flood | Reactive Resume | |
|---|---|---|
| Score | 65/100 | 87/100 |
| Rank in category | #2 of 7 in Torrent | #1 of 46 in Document Management |
| GitHub stars | 2 860 | 45 045 |
| Stars, last 30 days | +17 | +1 644 |
| Stable releases, 12 months | 13 | 35 |
| Latest release | v4.16.3 · 17 Oct 2026 | v6.0.8 · 29 Oct 2026 |
| Setup | Easy | Moderate |
| Official Docker image | Yes | Yes |
| License | GPL-3.0 | MIT |
| Main language | Typescript | Typescript |
Which one should you pick?
Reactive Resume scores 87/100 against 65/100 for Flood, so it is the safer default.
Reactive Resume ships more often: 35 stable releases in the past year, against 13 for Flood.
If you want the quickest setup, Flood is easier to run; Reactive Resume needs more configuration.
Reactive Resume is growing faster right now (+1 644 stars in 30 days).
Flood details →Reactive Resume details →
Swap a project
Keep Flood, compare it with
Keep Reactive Resume, compare it with