Proxyware

Proxyware is the consumer-facing software that supplies residential proxy pools. It covers passive-income apps that pay people to share idle bandwidth, and bandwidth-sharing SDKs embedded in free VPNs, mobile games and utility apps. In every case the end user's device becomes a peer, and commercial traffic exits through their home connection. This is where residential IPs come from. There is no other source, because the addresses have to belong to real ISP subscribers to look like real ISP subscribers.

Three sourcing models sit under that label and they differ sharply in consent quality. The first is explicit paid opt-in: someone installs an app whose entire purpose is selling bandwidth. PacketStream is the plain version, describing users as "Packeters" who run a desktop app, earn "$0.10 for every GB of customer traffic", and can "stop or uninstall the app at any time" (read 2026-07-27). The second is an SDK bundled into a free app behind a disclosed toggle, where the user traded bandwidth for a free tier and may or may not have registered what they agreed to. The third is undisclosed inclusion, where the SDK ships without meaningful notice. Security vendors have published reports of that third category over the years; treat it as the reason to ask questions rather than as an allegation about any particular supplier.

The exposure lands on the buyer, not only the vendor. Your requests arrive at a target from a private household connection, and if the person behind it never knowingly agreed, that is a consent defect in your data supply chain. Regulators and plaintiffs look at who benefited. Vendors know this, which is why access is increasingly gated: Bright Data's residential proxy documentation covers KYC verification requirements and access policy before a customer can use the network at all (read 2026-07-27). Gating on the buyer side is evidence a vendor takes the risk seriously; it says nothing on its own about how the peers were recruited.

So put the sourcing questions in writing during diligence. Which apps supply the pool, what the consent flow looks like on the peer's screen, how opt-out is handled and how fast it propagates, whether peers are compensated, and what KYC the vendor runs on its own customers. Ask for the artifacts, not the assurances. When a vendor will not name its supply apps, or answers a consent question with an ethics statement, that is the point to price ISP or datacenter supply instead and accept the lower success rate as the cost of a clean chain.