This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
proxy-benchmark
Find out what's blocking your scraper: proxy, browser, host
An open-source harness that separates the causes of a scraping failure - exit IP, browser, TLS handshake, the machine you run it on, the target - by varying one at a time in the same hour. Every attempt is a JSONL row in the repo, and every table is generated from those rows. Built by Nodemaven for developers who are working in scraping, browser automation, anti-bot systems and others related fields.
We built this because a scraping failure gets blamed on the proxy first,
and usually nobody has checked.
Three layers can refuse you - the exit address, the browser, the TLS
handshake - plus the machine you are running on and the target itself.
Debugging fails when you inspect the one above whichever is actually
refusing you. So the harness varies one at a time, interleaved inside the
same hour, because the hour turned out to be the largest confound we
found.
Two results that surprised us:
- On Amazon the unmodified browser finished in the leading group. Stock
Chromium 96% (419/436) against 63% (288/457) for the lowest anti-detect
engine, over 3530 judged attempts. Six engines sit within four points at
the top, a Fisher exact separates none of them, and the control is one
of the six.
- Chrome spends 43 MB per fresh profile talking to Google before you ask
it for anything - 43.2 MB of a 43.4 MB window with the browser parked on
about:blank. On a metered residential exit that is billed traffic for a
file no target ever sees.
Some of our earlier conclusions did not survive re-measurement, and both
versions are in the notebook rather than the wrong one being quietly
edited. 18,763 attempt rows, run ids and the generated tables are all
committed, so any number here can be recomputed rather than taken.
Built at NodeMaven, who sell proxies. No account needed - a gateway is a
TOML file, so you point it at whatever you already have.
Would like feedback from people working on scraping, browser automation,
anti-bot or proxy infrastructure - especially anyone who can break the
Amazon result.
No comment highlights available yet. Please check back later!
About proxy-benchmark on Product Hunt
“Find out what's blocking your scraper: proxy, browser, host”
proxy-benchmark was submitted on Product Hunt and earned 0 upvotes and 1 comments, placing #126 on the daily leaderboard. An open-source harness that separates the causes of a scraping failure - exit IP, browser, TLS handshake, the machine you run it on, the target - by varying one at a time in the same hour. Every attempt is a JSONL row in the repo, and every table is generated from those rows. Built by Nodemaven for developers who are working in scraping, browser automation, anti-bot systems and others related fields.
proxy-benchmark was featured in Open Source (68.9k followers), Developer Tools (519.8k followers), GitHub (41.4k followers), Data (2.5k followers) and OpenAI Day (39 followers) on Product Hunt. Together, these topics include over 132.7k products, making this a competitive space to launch in.
Who hunted proxy-benchmark?
proxy-benchmark was hunted by Alexandr Kazmin. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how proxy-benchmark stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Alexandr Kazmin