# ChronoFrame vs socks5-proxy-server

> Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.

| | ChronoFrame | socks5-proxy-server |
|---|---|---|
| Score | 63/100 ✓ | 43/100 |
| Rank in category | #8 of 41 in Photo Management | #5 of 10 in Network |
| GitHub stars | 1 964 ✓ | 145 |
| Stars, last 30 days | +32 | — |
| Stable releases, 12 months | 3 ✓ | 1 |
| Latest release | v1.0.2 · 21 Oct 2026 ✓ | v1.20.0 · 29 Nov 2025 |
| Setup | Easy ✓ | Moderate |
| Official Docker image | Yes ✓ | No |
| License | AGPL-3.0 | Apache-2.0 |
| Main language | Typescript | JavaScript |

## Which one should you pick?

ChronoFrame scores 63/100 against 43/100 for socks5-proxy-server, so it is the safer default.

ChronoFrame ships more often: 3 stable releases in the past year, against 1 for socks5-proxy-server.

If you want the quickest setup, ChronoFrame is easier to run; socks5-proxy-server needs more configuration.

ChronoFrame is growing faster right now (+32 stars in 30 days).

## Details

- [ChronoFrame](https://selfhost.directory/project/chronoframe) (markdown: https://selfhost.directory/project/chronoframe.md)
- [socks5-proxy-server](https://selfhost.directory/project/socks5-proxy-server) (markdown: https://selfhost.directory/project/socks5-proxy-server.md)

---
Source: https://selfhost.directory/compare/chronoframe-vs-socks5-proxy-server