Proxies

Proxies are essential: every account goes out through a dedicated IP, stable for life.

Adding a proxy

In the Proxies tab, fill in one line per proxy:

Field	Example	Note
Type	SOCKS5	SOCKS5 required
Host / IP	198.51.100.10	host or IP
Port	1080
User / Password	user / ••••	if the proxy requires auth

SOCKS5 only

Botify only works with SOCKS5 proxies. Account creation and verification run over strict SOCKS5 (no HTTP fallback). An HTTP/HTTPS proxy will be rejected.

SOCKS5 with authentication

Chrome cannot authenticate natively over SOCKS5. Botify launches a small local relay that handles the auth → Chrome connects without any issue. This is automatic.

Capacity per proxy

A proxy can host several accounts (the Comptes max / proxy (Max accounts / proxy) setting) and a limited number of concurrent workers per proxy (realistic density: few accounts per IP, like a household).

Account → proxy affinity

An account is bound for life to the proxy it was created with. This is crucial: changing an account’s IP can get its session revoked on the platform side. Distribution respects this rule (the account is created through the exact proxy the streaming machine requested).

Role in distribution

Botify continuously computes the empty slots (capacity − assigned accounts) per proxy and declares the need to the server. When a proxy is full, the need drops to 0 and creation stops for that proxy. See Distribution.