Decodo

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

Formerly Smartproxy. Offers both a username-parameter style and a port-per-session style, and the two do the same job.

1. Get the credentials

In your Decodo 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://user-<username>-country-us-session-randomstring123-sessionduration-30:<password>@gate.decodo.com:7000

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://user-<username>-country-us-session-randomstring123-sessionduration-30:<password>@gate.decodo.com:7000',
})

launch(
    profile="acc-01",
    proxy="http://user-<username>-country-us-session-randomstring123-sessionduration-30:<password>@gate.decodo.com:7000",
)

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

Parameters

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

Gateway	gate.decodo.com, plus a dedicated endpoint per country.
Ports	7000 and 10000 rotate. 10001-49999 are sticky, one session per port. Each location has its own range.
Protocols	Not published on the page above - see the provider docs
Options ride in	the username
Country targeting	country-<iso2>. city, state, zip, asn and continent work the same way.
Sticky session	session-<id> plus sessionduration-<minutes>. session_iplock-<id> holds one address instead of rotating when it drops.
Session length	1 to 1440 minutes (24 hours).
Source	https://help.decodo.com/docs/residential-proxy-endpoints-and-ports

Worth knowing

Sticky sessions can be had two ways: a port from the sticky range, or the session parameters in the username. Pick one - mixing them is where the confusing results come from.