Proxy Server VPS — Run Your Own Anonymous Proxy

Match the proxy software to your use case:

• Squid (HTTP/HTTPS proxy with caching): Best for browsing, bulk web scraping, or shared corporate internet routing. Caches static content, reduces bandwidth, supports auth and ACLs. Default port 3128. Comes pre-configured with optional basic auth.
• 3proxy (SOCKS5 + HTTP combo): Best for applications that speak SOCKS5 (Telegram, qBittorrent, browser extensions like FoxyProxy). Lighter than Squid, no caching, supports per-user auth and IP whitelist. Default ports 1080 (SOCKS) and 3128 (HTTP).
• MTProto Proxy (Telegram-specific): Custom protocol that disguises Telegram traffic as TLS to a major site (Google/Cloudflare). Required for Telegram users in countries where Telegram itself is throttled or blocked at the protocol level. Uses 'fake-tls' mode by default. Generates a t.me/proxy?... share link.

Proxy servers are network-bound, not CPU-bound. The right sizing question is bandwidth, not cores:

• Personal proxy (1-3 users) — $4.99/mo: Offshore VPS Starter. 2 vCPU, 2 GB RAM, 40 GB NVMe, 1 Gbps unmetered. Easily handles 50-100 concurrent connections. Fine for individual browsing, Telegram, light scraping.
• Small team / family proxy — $9.99/mo: Offshore VPS Plus. 4 vCPU, 4 GB RAM, 80 GB NVMe, 1 Gbps unmetered. Up to 500 concurrent connections. Good for a small team or shared household.
• Heavy scraping / proxy farm node — $24.99/mo: Offshore VPS Pro. 8 vCPU, 16 GB RAM, 200 GB NVMe, 1 Gbps unmetered. Sustained ~1000+ concurrent. For aggressive web scraping or running multiple proxy types on one host.

All plans include a unique IPv4 (no shared IPs), full root access, and your choice of location: Iceland, Finland, Netherlands, or Romania.

If your use case is legitimate (research, accessing your own services from a restrictive network, family members in censored countries, security testing your own systems), some configuration tweaks reduce false-positive detection:

• Don't use cloud-provider IP ranges: Sites maintain blocklists for AWS/GCP/Azure/DigitalOcean. Our IPs come from independent network blocks announced from our own ASN where possible — significantly less likely to be on commercial blocklists.
• Set rDNS to something believable: Default rDNS often gives away the host. We let you set custom rDNS via panel — pick something residential-looking like 'pool-cust-XX.lab.example.net'.
• Match proxy port to expected traffic: Squid on 3128 is a fingerprint. Move HTTPS proxy to 443 and use TLS so it looks like normal HTTPS traffic. 3proxy supports this with the 'auth strong' + TLS wrapper combo.
• Use MTProto for Telegram specifically: Default Telegram doesn't tunnel — RKN/GFW DPI sees it. MTProto fake-tls mode is currently effective.

None of this defeats sophisticated state-level censorship. For that, layer Tor (obfs4 bridges) on top.

You can either deploy from a clean Debian/Ubuntu image and install your proxy yourself, or pick one of our pre-configured templates at checkout:

• 'Squid Proxy' template: Debian 12 + Squid 5 + sample auth config + iptables rules. After provisioning, edit /etc/squid/squid.conf to set your auth and ACLs, then 'systemctl restart squid'.
• 'SOCKS5 Proxy (3proxy)' template: Debian 12 + 3proxy + minimal config in /etc/3proxy/3proxy.cfg. Add users with the 'users' directive, restart with 'systemctl restart 3proxy'.
• 'Telegram MTProto' template: Debian 12 + mtg (Telegram MTProto v2 proxy) + auto-generated secret + Telegram share URL printed on first SSH login.

All templates start running immediately on first boot. No web panel required. SSH in, edit configs, restart services. Anything you change persists across reboots.