Home / Playbooks / VPS bandwidth farm

Build a Bandwidth Farm on Cheap VPS Instances

How to deploy bandwidth-sharing containers across multiple $5 VPS boxes safely — provider selection, ToS compliance, and realistic datacenter-IP earnings.

Intermediate⏱ ~45 minutes per VPS·$5–12/VPS/month·Updated 2026-08-24
Contents
  1. Reality check: datacenter economics
  2. Provider selection criteria
  3. Server baseline setup
  4. Datacenter-friendly app selection
  5. Deploy the standard node template
  6. Fleet management without tears
  7. When the farm makes sense

1. Reality check: datacenter economics

Before spending money: datacenter IPs earn 3–10x less than residential IPs on every bandwidth platform. A VPS farm is a volume game — many cheap machines, each earning modest amounts, automated heavily. It works, but the math must include the VPS rental cost itself.

SetupTypical gross/moVPS costNet
1 budget VPS$3–8$5≈ break-even to small profit
5 VPS, mixed providers$18–35$25thin positive
Residential Pi/N100 (comparison)$25–45$0best ROI by far

Strategy: treat VPS nodes as satellite earners around a residential core, and prioritize platforms with explicit datacenter support and crypto payouts.

2. Provider selection criteria

Not all VPS hosts tolerate proxy traffic. Requirements for this job:

CriterionWhy
Crypto payment acceptedPrivacy + no chargeback risk on disposable boxes
Unmetered or 5TB+ trafficBandwidth apps consume modestly but continuously
ToS permitting proxy/VPN usageAvoids mid-month terminations
Cheap hourly billingKill underperforming nodes without annual lock-in
Locations: US/EU mixDifferent buyer demand pools per region

Categories that historically fit: budget crypto-friendly hosts (check current community consensus — this changes quarterly). Avoid AWS/GCP/Oracle free tiers for this purpose: against ToS, accounts die.

3. Server baseline setup

Per VPS, minimal Debian 12/Ubuntu 24.04 baseline:

ssh root@SERVER_IP
apt update && apt full-upgrade -y
apt install -y curl ufw
adduser operator && usermod -aG sudo operator
ufw allow OpenSSH && ufw --force enable

# Docker
curl -fsSL https://get.docker.com | sh
usermod -aG docker operator
One account per platform, period. Multiple VPS nodes under ONE account = fine on most platforms. Multiple accounts from one person = ban. The farm scales via devices, never via duplicate identities.

4. Datacenter-friendly app selection

Apps ranked by datacenter-IP friendliness (from our testing):

AppDC earningsNotes
GrassLow but realWorks on DC IPs; expect ~$1–3/node
TraffMonetizerModerateExplicitly supports servers
PacketShareModerateDC traffic allocated reasonably
RepocketLowRun last; see review caveats
Honeygain/EarnAppSkipResidential-focused; DC allocation near-zero

5. Deploy the standard node template

Identical compose file on every VPS — only credentials differ:

services:
  grass:
    image: gogol/grass-node:latest
    restart: unless-stopped
    environment:
      - USER_EMAIL=YOU@example.com
      - USER_PASSWORD=PASS
    mem_limit: 400m

  traffmonetizer:
    image: traffmonetizer/cli_v2:latest
    restart: unless-stopped
    command: "start accept --token YOUR_TOKEN --device-name vps1"
    mem_limit: 150m
docker compose up -d
sleep 60 && docker compose logs --tail 20

6. Fleet management without tears

Three-plus servers demand automation. Minimum viable fleet tooling:

ToolPurpose
SSH config file (~/.ssh/config)Aliases: ssh vps1, ssh vps2...
Ansible (optional)Push compose updates to all nodes in one command
Uptime Kuma central monitorOne dashboard watching every node's health
Shared spreadsheetNode, provider, cost, monthly earnings — the P&L

Kill-switch discipline: any node whose monthly gross falls below its rental cost for two consecutive months gets destroyed. Sentimentality is the margin killer in VPS farming. The spreadsheet decides, not hope.

7. When the farm makes sense

Honest summary of who should do this:

- ✅ You already run a residential node and want incremental scale

- ✅ You enjoy infrastructure and treat $5 experiments as entertainment-plus

- ✅ You have specific needs for geo-distributed IPs anyway

- ❌ You expect VPS farms to beat a single residential box (they won't)

- ❌ You'd violate platform terms to squeeze margins (bans erase everything)

Start with ONE VPS for a month. Measure honestly. The spreadsheet will tell you whether to build the fleet or pour that budget into an N100 instead.

Tools used in this playbook

This guide contains referral links to some of the services mentioned. They cost you nothing and fund more testing. See disclosure.