Helodata

Point a browser profile at Helodata residential proxies. Three steps, no plugin, no proxy-auth extension.

Helodata residential proxies: one gateway, with the sub-user, product, geo and sticky session all encoded in a single username that starts with helo_. Measured on a live trial account, not read off a docs page - and three of the documented targeting forms did not work as written, so the forms below are the ones that did.

https://helodata.com/products/residential-proxies

1. Get the credentials

In your Helodata dashboard, open the residential product and copy the gateway host, the port, and the username and password. Everything below assumes those four values.

2. Build the proxy URL

One string, credentials included. Targeting and session options go in whichever half this provider puts them in - the table below says which.

http://helo_<sub-user>-type-res-region-us-session-<id>-sesstime-30:<sub-user password>@gate.helodata.io:7777

3. Launch

Timezone, locale and WebRTC are derived from the exit address, so a US exit does not arrive with your own timezone attached.

await ab.launch({
  profile: 'acc-01',
  proxy: 'http://helo_<sub-user>-type-res-region-us-session-<id>-sesstime-30:<sub-user password>@gate.helodata.io:7777',
})

launch(
    profile="acc-01",
    proxy="http://helo_<sub-user>-type-res-region-us-session-<id>-sesstime-30:<sub-user password>@gate.helodata.io:7777",
)

Prefer not to run an account at all? Managed residential proxies are included on paid plans.

Parameters

Read off Helodata's own documentation on 2026-09-23. Ports and endpoints differ by plan and by zone, so where this table and your dashboard disagree, the dashboard is right.

Gateway	gate.helodata.io. The regional entries that resolve are na.helodata.io, eu.helodata.io and as.helodata.io - the na.gate / eu.gate / ap.gate names on the docs page returned NXDOMAIN on 2026-09-23. A German exit through eu.helodata.io was measured and worked.
Ports	7777 for every protocol. The gateway detects HTTP, HTTPS and SOCKS5 from the handshake.
Protocols	HTTP and SOCKS5, same host and port. Both were measured in AntiBrow with the same credential.
Options ride in	the username
Country targeting	-region-<iso2>, lowercase. Narrower targets follow it: -state- takes the full state name, not the 2-letter code the docs show (state-california and state-newyork worked; state-ca, state-ny and state-tx never did). -city- takes the full slug: city-losangeles worked and landed in Garden Grove, the docs' city-la did not. city-berlin came out in Berlin, and -asn-7922 came out on Comcast.
Sticky session	-session-<id>-sesstime-<minutes>, both or neither. Measured: one session id returned 100.14.135.117 in an AntiBrow profile and again in two separate requests minutes later, so the session is held at the gateway, not by the browser. Leave the session segment out and every new connection gets a new exit.
Session length	1 to 30 minutes on residential, 1 to 60 on mobile, per the docs. Session ids are [a-z0-9], up to 32 characters.
Source	https://docs.helodata.com/getting-started/username-format

Worth knowing

The helo_ prefix is not optional, and leaving it off fails badly: the gateway closes the CONNECT tunnel without any status code. A wrong password, by contrast, comes back as a clean 407. If a page fails with a closed connection rather than an auth error, check the prefix first.
Measured on 2026-09-23 with AntiBrow, one profile per case: the US exit was Comcast in Pennsylvania, the German one Vodafone in Giessen, the Japanese ones QTnet in Oita and SoftBank in Tokyo. Every exit that was looked up sat on a consumer ISP. In rotating mode the exit changes per connection - two pages loaded one after the other in the same profile saw two different addresses - so add a session whenever the site has to see one IP.
One sticky session got stuck: its id stayed pinned to an exit that accepted the tunnel and then dropped every TLS handshake, five attempts over about seven minutes - two browser launches and three plain requests - where the docs say a dead exit gets re-pinned. A new session id fixed it at once. If a sticky profile suddenly fails with a closed connection, change the id before anything else.
The first connection through the gateway is slow - the first page load took 2.6 to 18.7 seconds, SOCKS5 being the slowest - and that matters for the timezone. The timezone followed the exit on the US and German runs (America/New_York, Europe/Berlin), but on the Japanese runs the launch-time geo lookup through this gateway took 2.8 to 20 seconds and ran out of time, so the profile kept its configured timezone. For distant exits, set the timezone on the profile yourself, or check browser.timezone after launch.
No WebRTC leak on any run: the only ICE candidates were mDNS .local host names, and no local address appeared. Unlike most vendors on this page, no srflx candidate came back at all - the STUN request did not return through this gateway - so a WebRTC check sees no public address rather than the exit.
Helodata supports sub-users: add them in the dashboard under Proxy Generator - Account Management, and each sub-user's name and password is the proxy credential. The dashboard sits behind a Cloudflare check. The API key from the dashboard's API page reads balance, quotas and usage at api.helodata.com/v1; it has no sub-user endpoint, so take the credential from the dashboard, not the API. The trial tested was 1 GB of residential, valid for seven days.