imgproxyvsnocodb
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| imgproxy | nocodb | |
|---|---|---|
| Score | 72/100 | 81/100 |
| Rank in category | #2 of 13 in Image Processing | #1 of 4 in No-code Platforms |
| GitHub stars | 11 161 | 65 374 |
| Stars, last 30 days | +69 | +320 |
| Stable releases, 12 months | 23 | 15 |
| Latest release | v4.0.20 · 26 Oct 2026 | 2026.10.0 · 23 Oct 2026 |
| Setup | Easy | Moderate |
| Official Docker image | Yes | Yes |
| License | Apache-2.0 | Other |
| Main language | Go | Typescript |
Which one should you pick?
nocodb scores 81/100 against 72/100 for imgproxy, so it is the safer default.
imgproxy ships more often: 23 stable releases in the past year, against 15 for nocodb.
If you want the quickest setup, imgproxy is easier to run; nocodb needs more configuration.
nocodb is growing faster right now (+320 stars in 30 days).
imgproxy details →nocodb details →
Swap a project
Keep imgproxy, compare it with
Keep nocodb, compare it with