ImageFlowvsrimgo
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| ImageFlow | rimgo | |
|---|---|---|
| Score | 50/100 | 57/100 |
| Rank in category | #3 of 9 in Image Management | #2 of 6 in Media |
| GitHub stars | 607 | — |
| Stars, last 30 days | +1 | — |
| Stable releases, 12 months | 1 | 0 |
| Latest release | v3.0 · 12 Dec 2025 | — |
| Setup | Moderate | Easy |
| Official Docker image | Yes | Yes |
| License | MIT | AGPL-3.0 |
| Main language | Typescript | — |
Which one should you pick?
rimgo scores 57/100 against 50/100 for ImageFlow, so it is the safer default.
ImageFlow ships more often: 1 stable releases in the past year, against 0 for rimgo.
If you want the quickest setup, rimgo is easier to run; ImageFlow needs more configuration.
ImageFlow is growing faster right now (+1 stars in 30 days).
Key differences
- License: ImageFlow is MIT, rimgo is AGPL-3.0.
- Features only ImageFlow lists: Animated GIF preservation, API Key Authentication, Async background processing, Automatic WebP/AVIF conversion and 11 more.
- Features only rimgo lists: Bandwidth-efficient image formats, HTTP/SOCKS proxy support, Instance privacy disclosures, No ads or tracking and 5 more.
ImageFlow details →rimgo details →