The Nimble alternative for residential proxies you can buy today

Nimble used to sell its residential proxy network under the name Nimble IP, and its docs still use the name. Today, the old residential proxy page now redirects to its Extract API product page. Its pricing page lists Agent, Search, Extract, Crawl, Map, Extract Template and Media APIs, plus managed Data Services plans. None of those is a proxy you plug into your own client.

From their side that is a reasonable decision. A data API is priced per request, and it hides the proxy behind a layer that renders pages, parses them and retries for you. That layer is worth paying for when it fits your work.

The proxy did not disappear with the page. Nimble's documentation still has a quickstart for it, and its price list still carries one proxy line, Residential Proxy, with no mobile, ISP or datacenter proxy on the price list. What changed is who can buy it: the residential proxy requires KYC verification and is not available to self-service accounts; access is by request to its team. There is a smaller sign of the same shift too: proxy credentials come from its legacy dashboard, with support in the new platform listed as coming soon.

If you do get access, the proxy is a conventional, well-documented backconnect service. It runs HTTP and HTTPS through one BackConnect gateway on port 7000; the proxy guides we read do not mention SOCKS5. It authenticates by username and password, or an IP allowlist on a custom port, and it covers residential IPs in 195+ countries. The allowlist option is a nice touch for fixed servers, because it keeps credentials out of your code.

Ours works the same way in principle: a host, a port and a username that carries your country, state and session. HTTP answers on port 7777 on every pool. SOCKS5 answers on port 1080 on Premium, Mobile and ISP, which matters if your tool speaks SOCKS5 and you would rather not wrap it in an adapter.

The difference is the front door. You can sign in to ResiFactory, top up from $0.50, and send traffic the same hour, with no application, identity review or sales call. See residential proxies for the pools and the username syntax.

Nimble's residential proxy is $5.30 per gigabyte, pay as you go. That is the published rate on its own price list, before any volume deal.

Ours are Essential at $1.50/GB and Premium at $3.00/GB, read live from our catalogue as this page loaded. Set the two side by side and judge the gap yourself.

The fair caveat is that Nimble's large customers are unlikely to pay the list rate. Its pricing page offers volume discounts, multi-year rate locks and bundles across its APIs. If you want one vendor for proxies, rendering and parsing at that scale, a negotiated Nimble contract may beat any per-gigabyte comparison here. If you are buying bandwidth and nothing else, the published rates are the honest comparison.

Nimble rotates to a new IP on every request by default, or timed rotation from 1 to 30 minutes on allowlisted pipelines. It also offers sticky sessions that keep one IP until 10 minutes pass with no request, which suits short flows that make requests steadily: a search, a few pages of results, then a new address.

Its most interesting session feature is one we do not match: geo-sessions that keep replacement IPs within 175 km and on the same ISP, in the US only. If your target compares the location of each request in a session, keeping replacements close and on the same network is a real advantage.

Our sticky sessions work differently. You set a session and its length in the username, and the exit stays put for that length. On Premium and Mobile a sticky exit holds up to 24 hours (120 minutes on Essential), so a long sign-in flow or a slow form keeps its address. Short, busy flows suit either of us; long ones with idle gaps are where the Premium and Mobile hold earns its place.

Nimble's proxy targets country, state (US and Canada only) and city. That is generous: city targeting runs globally on its network, and state targeting reaches into Canada as well as the US.

Every ResiFactory pool takes a country, a US state and a network (ASN) in the username, so you can test a specific carrier or network. Premium and Mobile add city. Our pools cover 150 countries, against Nimble's residential IPs in 195+ countries. On breadth, Nimble reaches further; choosing an ASN is the thing we offer that its proxy docs do not list.

Nimble's price list has one proxy line, Residential Proxy, with no mobile, ISP or datacenter proxy on the price list. If you need an exit on a carrier network, there is nothing on its side to compare.

ResiFactory Mobile is $3.00/GB, on real phones attached to carrier networks in 150 countries, with US state, city and ASN targeting. See mobile proxies for how the pool is built.

This is the part of Nimble that is genuinely for sale, and it is a different product from ours. Extract, Crawl and Map are $1 per 1,000 requests for Extract, Crawl and Map. Search is $1.10 per 1,000 requests for Search at its lightest depth. Each returns page content or structured results rather than a raw connection, and Extract comes with a built-in residential proxy with country, state and city targeting on Extract requests.

That changes the unit you pay for. With a proxy you pay for bandwidth and run your own browser, parser and retries. With Nimble's APIs you pay per request, and the rendering and parsing are theirs. A heavy page is expensive in gigabytes and cheap per request; a light one is the reverse.

We do not sell a scraping API, a search API or an agent platform. If you want clean data handed back and no scrapers to run, Nimble's APIs are the right shape and ours is not. If you already run your own scrapers, or need a proxy for a browser, the API layer is cost you would not use.

Nimble bills pay-as-you-go usage billed monthly by credit card, with only successful requests charged. Charging only for successful requests is a fair model. Above pay as you go it sells Data Services plans from $2,500 a month, billed annually, up to custom Enterprise contracts, and on those plans it lists plan credits that expire at the end of each month.

We use a prepaid wallet per pool instead. Load any amount from $0.50, spend it at your own pace, and it does not expire. Refunds are requests within 14 days of a top-up, under the refund policy.

On free use, Nimble is the more open of the two: its APIs come with 5,000 free requests a month across every API, with no credit card, though the proxy still sits behind its access review. Ours is 1 GB of Premium free when a new account links Google.

If you want a residential or mobile proxy you can buy this afternoon, the choice is made for you. Nimble's proxy is behind an identity review and a sales request, it has no mobile line, and its published rate is above ours. We sell both pools to anyone who signs in.

If you want web data rather than a proxy, Nimble is the better buy and we have said so throughout. Its APIs render, parse and retry for you, it has a free monthly allowance, and it can show your procurement team an audit report.

The overlap is narrow: an approved Nimble account using the residential proxy directly. There we would point to the published rate, SOCKS5 and the longer sticky hold on Premium and Mobile. Nimble would point to geo-sessions and global city targeting. Both are fair points.

Proxyway published a hands-on review of Nimble, first published in June 2024 and updated in February 2026. It is worth reading in full rather than through our summary, and the link goes straight to it.

We would rather you judged us on the network than on a badge. Every price of ours here is read live, every Nimble fact links to its source, and the trust page lists what we can prove.