Pre-launchThe spec on this site is committed; the gateway is not yet in service.Ask for early access →
ProxyNomad

proxynomad.com / Aboutsmall, senior, reachable

We were the customer.

ProxyNomad was built by people who spent years running data collection and buying proxies to do it: writing scrapers, watching success rates, reading invoices that needed a translator. We crossed to the proxy side recently, to build the vendor we kept wishing existed.

§ 01 The origin every feature
here is a scar

Every feature here is a scar.

If you have run collection infrastructure, you already know the catalog.

  • Scar 01

    The pool that was "residential" until you looked up the ASNs.

  • Scar 02

    The credit system that quietly zeroed a balance at renewal.

  • Scar 03

    The city targeting that cost an enterprise sales call.

  • Scar 04

    The support chat that asked, eight hours into an outage, whether you had tried turning it off and on again.

  • Scar 05

    The pricing page that was a lead form wearing a costume.

None of that is fixed by a bigger pool. It is fixed by decisions: bill so the invoice computes, publish the numbers, answer with an engineer, refuse the customers who burn the pool for everyone else. Those decisions are the company. The proxies are the easy part.

§ 02 What we believe three positions
we will not trade

Three positions we will not trade.

A proxy is infrastructure, not magic.

A vendor who promises a success rate is billing you for their retries.

No exit unblocks every site, and nobody can promise a number against a target they do not control. What we promise instead: clean supply, honest routing, exact billing, and help tuning the part nobody can promise.

Pricing is a respect issue.

If you cannot compute the bill from the public page in one minute, the obscurity is the product.

Our rates fit on one page, include the targeting, and the fine print says things like "does not expire" instead of hiding the opposite.

The network answers for its traffic.

A policed pool is a clean pool.

Our exits sit on real people's connections, and that is a responsibility before it is a product. So we vet every customer, publish a real acceptable use policy, and cut abuse instead of warning it twice.

§ 03 Proof falsifiable
beats decorated

What you will not find on this site.

The marketing convention of this industry is decoration, and decoration is what we were trying to get away from.

Not on this site

  • A live counter of IPsyou cannot verify it
  • An uptime badgea badge is not a measurement you took
  • Testimonials with first names and stock photos
  • A logo wall of free trials from 2024

Run the trial, measure cost per thousand successful requests, and compare us to anyone. That is the only proof that was ever real.

§ 04 How we work small, senior,
reachable

Small, senior, reachable.

Every person who answers a support thread can read a packet capture. Setup is hands-on, because thirty minutes of tuning at the start prevents the three-week slow bleed that kills most proxy deployments. Advice is honest even when it shrinks the invoice: the customers who stay for years are worth more than the quarter we could have overcharged.

  • 4hrsbusiness hours to a reply, written by an engineer
  • 6daysa week, Monday through Saturday
  • EUbased and remote, close to your working day

The person writing back has spent years running the kind of data-collection job you are asking about. That is the whole org chart.

§ 05 Start

Judge us the empirical way.

A trial and one afternoon will tell you whether we are what this page claims.

Put a real route under your next job.

Start pay as you go, or send us the target first and we will tell you honestly what it needs. Trials: enough traffic to test against production, no card required.