Integrations for agencies and business teams

Undetectable.io

Undetectable.io is the antidetect browser we point agencies to first. It runs on Windows and macOS, and every profile carries its own fingerprint and its own proxy, so one client's accounts never borrow another client's network. Profiles can live locally on the workstation or in the cloud, where a colleague on a different machine can open them, and larger plans let you share profiles across the team. The free plan covers up to five cloud profiles, which is enough to pilot one client before rolling it out agency-wide.

1. Install Undetectable.io on a Windows or macOS workstation and register; the free plan is enough for a pilot.
2. Create a profile for the client account and decide whether it should be local or cloud, depending on who needs to open it.
3. In the profile's proxy settings choose HTTP or SOCKS5, then enter the GlobalProxies host, the port for that protocol and the line's username and password.
4. Run the proxy check and confirm a US address on AT&T, T-Mobile or Verizon.
5. Let timezone, language and geolocation follow the proxy IP, point WebRTC at the proxy's address, and save.
6. Open the profile once and load a client dashboard to confirm everything renders normally.

• Name profiles by client, metro and carrier, and label the proxy entry the same way, so account managers never open the wrong one.
• On paid plans, proxy import lets an operations lead load every client line in one pass instead of typing them profile by profile.
• After rotating a line from the dashboard, close and reopen the profile so the session starts on the new address.

Full Undetectable.io setup guide →

GoLogin

GoLogin is our alternative pick, and the one to choose when part of the team works on Linux or reviews accounts from a phone: it ships for Windows, macOS and Linux, with Android and iOS apps alongside. Profiles run in its own Orbita browser, each with a proxy of its own, and the free plan gives you three profiles with no card required. A 7-day trial of the paid plans unlocks team sharing, and the API and SDKs suit agencies that already drive client QA with Selenium, Puppeteer or Playwright.

1. Sign up on the free plan, or start the 7-day trial if you want team sharing from the first day.
2. Create a profile per client account and open its proxy settings.
3. Pick HTTP or SOCKS5 to match the port you copied; GoLogin also offers SOCKS4, which our lines do not use.
4. Paste the line as host:port:user:pass into the paste field, or fill in the four fields one by one.
5. Press check proxy and read back the US carrier address before anyone signs in.
6. Keep timezone, language and geolocation tied to the proxy IP and save the profile.

• Hand client profiles to account managers through team sharing instead of passing line credentials around in chat.
• If you launch profiles through the API, call the line's rotation link from the same job and relaunch the profile afterwards.

Full GoLogin setup guide →

GeeLark

GeeLark runs virtual Android devices in the cloud, each with its own apps, storage and device identity, and lets you set a proxy per cloud phone. Because the whole device routes through that proxy, it is the natural choice when a client's presence lives inside a mobile app rather than a browser. A carrier line keeps the app's network consistent with the handset it appears to be.

1. Open the cloud phone you want to configure and find its proxy settings.
2. Select HTTP, or SOCKS5 if apps on the device use voice or video.
3. Enter host, port, username and password for the line.
4. Run the proxy check and confirm a US carrier address.
5. Let the device align region and timezone with the exit IP, then start it.

• Keep one cloud phone per line when handling separate client apps so each device has a clean history.
• With 15 GB per day included on every line, app updates and media uploads fit comfortably; schedule big updates outside working hours anyway.

Selenium

Selenium drives Chrome, Firefox and other browsers from code and is the backbone of many regression suites and monitoring jobs. It does not handle proxies itself; the browser does, through launch options, and an authenticated proxy usually needs a small extension or a local forwarder. A carrier line helps when compliance or QA checks must confirm how a site behaves for US mobile visitors.

1. Decide between the HTTP and SOCKS5 port for the line.
2. Pass the proxy host and port through the browser options when creating the driver.
3. Supply the username and password with a proxy-auth extension or a local forwarder, since launch flags have no credential field.
4. Open an IP lookup page in the first test and assert the carrier and country.
5. Run the rest of the suite and call the rotation link between suites if you want a fresh address.

• Give each parallel driver its own line; sharing one line across drivers makes results hard to attribute.

Playwright

Playwright automates Chromium, Firefox and WebKit with a single API and accepts a proxy object containing server, username and password when a browser or context is launched. That built-in credential support makes it simpler than Selenium for authenticated proxies. Agencies use it for scheduled screenshots of client landing pages as seen from specific US metros.

1. Copy the host, port and credentials for the line.
2. Build a proxy setting with the server address and scheme, http or socks5, plus username and password.
3. Pass it at browser launch, or per context if different contexts need different lines.
4. Load an IP lookup page and confirm the carrier before the real job runs.
5. Save outputs with the metro and carrier in the file name for later review.

• Per-context proxies let one script compare New York and Los Angeles lines side by side.
• Browsers differ in how they handle authenticated SOCKS5; test your chosen engine first and fall back to the HTTP port if it rejects credentials.

Puppeteer

Puppeteer is a Node library for controlling Chromium, and agency developers reach for it when they need scheduled screenshots of client ads or PDF snapshots of landing pages for monthly reports. Chromium takes the proxy as a launch argument and Puppeteer answers the credential prompt per page, so an authenticated GlobalProxies line works without any extension.

1. Launch Chromium with the proxy-server argument set to the line's host and HTTP port.
2. Call page.authenticate with the line's username and password before the first navigation.
3. Visit an IP lookup page and check that it reports a US mobile carrier.
4. Capture the client pages you need, saving files with the metro in the name.
5. Close the browser when the job ends, and call the rotation link only between runs.

• Chromium will not send a username and password to a SOCKS5 proxy, so stay on the HTTP port with Puppeteer.
• Keep line credentials in environment variables on the build server, never inside a shared script.

Proxifier

Proxifier pushes desktop software that has no proxy setting of its own through a proxy you pick, with rules per application. Agencies use it for a client's desktop messenger or a reporting tool that must reach a US-only service. It moves traffic only; fingerprints and accounts are left as they are.

1. Add a proxy server in Proxifier with the line's host and port.
2. Choose HTTPS when you use the HTTP port, or SOCKS Version 5 for the SOCKS5 port, and enable authentication with the line's credentials.
3. Run the built-in check to confirm Proxifier can reach the line.
4. Write a rule that sends only the chosen application through it and leaves everything else direct.
5. Launch the app and watch the connection log to see its traffic leave through the proxy.

• Resolve hostnames through the proxy so the app's lookups agree with its US exit.

FoxyProxy and SwitchyOmega

FoxyProxy and SwitchyOmega are free extensions that move your everyday browser onto a proxy from the toolbar. They change the route, not the fingerprint, so they suit quick jobs: a planner checking how a client's US landing page or local search results appear on a phone network, without opening a full profile.

1. Install either extension in Chrome or Firefox and open its options page.
2. Create an entry labelled with the client or metro.
3. Choose HTTP with the HTTP port, or SOCKS5 with the SOCKS5 port, and fill in the host.
4. Add the username and password and save.
5. Switch the entry on, open an IP lookup page and confirm the US carrier before reviewing the client page.

• Use pattern rules so only the client's domains travel over the line while the rest of your browsing stays local.