Every device exposes HTTP, SOCKS5 and OpenVPN, and all three are live at once. You don’t pick one at setup, so a customer whose tooling changes doesn’t need a new proxy.
HTTP
The default for anything that speaks the web. Scrapers, browser automation, antidetect browsers, and most off-the-shelf tools take an HTTP proxy without any configuration beyond host, port and credentials. If you’re not sure what a customer needs, this is the one to hand them first.
SOCKS5
Lower level, and it forwards traffic without trying to understand it. That makes it the right pick for anything that isn’t plain web traffic, and for tools that specifically ask for SOCKS. One gotcha worth knowing before you promise it to a customer: Chromium doesn’t support SOCKS5 with a username and password, so browser-driven setups on Chrome or Puppeteer usually want the HTTP endpoint instead.
OpenVPN
A full tunnel rather than a per-application proxy. Everything on the machine or device egresses through the phone’s carrier connection, including traffic from apps that have no proxy setting at all. It’s the answer when a customer says their software won’t take proxy credentials, and it’s what you want for a phone, a router, or a whole test machine.
Rotation works the same way whichever you use
The carrier IP can be rotated on demand, on a schedule, or through a rotation link the customer calls themselves. The protocol doesn’t change how rotation behaves, so you can mix protocols across customers on the same fleet without keeping track of which is which.