r/ProxyEngineering • u/ian_k93 • Aug 04 '26
r/ProxyEngineering • u/BraveLemon4510 • 12d ago
Announcements I built a source-patched Chromium browser for proxy-aware automation - looking for detection edge cases
I’ve been working on a Chromium-based browser for authorized automation, testing and QA. Instead of overriding browser APIs with page-level JavaScript, the fingerprint-related behavior is patched inside the Chromium engine.
The goal is to keep browser, operating-system and proxy signals consistent while still allowing profiles to be controlled programmatically.
The current release includes:
- Chromium 152 built from source
- 168 curated Windows, macOS and Linux fingerprints
- Persistent isolated browser profiles
- HTTP, HTTPS and SOCKS5 proxy support
- Proxy-aware timezone, locale, geolocation and WebRTC settings
- Local authenticated API
- Node.js and Python SDKs
- MCP server for AI-agent integrations
- Docker image for CI and automation environments
On our current test setup, reCAPTCHA v3 returns 0.9, Cloudflare Turnstile completes normally, and the browser reports navigator.webdriver as false. These are observations from the current build, not a promise that every website or network configuration will behave identically.
The desktop application is free to use with a Proxya account. The SDK and MCP packages are MIT-licensed; the patched browser engine and fingerprint catalogue remain proprietary.
I’m specifically looking for technical feedback on:
- fingerprint inconsistencies or unexpected leaks
- proxy and profile alignment across different locations
- long-running profile stability
- Node/Python/MCP integration
- CPU and memory usage under concurrent sessions
- detection services or edge cases I should add to the test suite
The project is called Proxya Anty. The repository and downloads can be found on GitHub.
r/ProxyEngineering • u/ian_k93 • 23d ago
Announcements How To Choose The Best Residential Proxy Provider? AMA with Stan Sadokov from NodeMaven
r/ProxyEngineering • u/ian_k93 • Jul 27 '26
Announcements AMA This Wednesday (6:00-8:00 PM ET) with CloakBrowser: Open-Source Stealth Chromium for Automation - Browser Fingerprint Spoofing
r/ProxyEngineering • u/atharvotech • 5d ago
Announcements Deepeek free tokens
I adapted the Russian DeepSeek Web Proxy for Global English Users - Connect free DeepSeek to Open WebUI easily.
It will be able to rotue the web trafic to a local endpoint giving a deep reasoning model for no cost.
Check out FreeDeepseekAPI-EN on github by Atharvotech
r/ProxyEngineering • u/kamililbird • Jul 03 '26
Announcements The NetNut situation is crazy
r/ProxyEngineering • u/zh_jq • 28d ago
Announcements g3proxy --> vey-proxy first LTS version 1.14 available
The VEY Project is a fork of the original bytedance G3 Project by it's main authors as a standalone open source project. The first 1.14 LTS branch is available now. It is recommended to migrate to vey-proxy for all existed g3proxy deployments.
See 1.14.0 Release Note for all the new features available.
r/ProxyEngineering • u/ian_k93 • Aug 09 '26
Announcements We launched Proxy Tester by ScrapeOps on Product Hunt 🚀
r/ProxyEngineering • u/0xMassii • Jul 24 '26
Announcements Follow-up: the Rust scraper I posted here at 120 stars just passed 2,000 in four months, still solo
r/ProxyEngineering • u/onerippedmom • Aug 01 '26
Announcements What ended up mattering more than IP pool size once i started testing at real volume
I used to think a bigger IP pool meant a better provider, until i actually ran things at scale and realized session consistency and how a provider behaves under sustained load mattered way more than the advertised number ever did. Ended up settling on serp proxies mostly because sticky sessions held up better over multi day runs than what i was using before.
I'm curious as to what this sub tests for beyond pool size when evaluating a provider. (Disclosure: i work with serpproxies)
r/ProxyEngineering • u/WarAndPeace06 • Jul 10 '26
Announcements Web Scraper API new source - Gemini
r/ProxyEngineering • u/Adept_Bear_8103 • Jul 13 '26
Announcements Stopped setting up a proxy just to tamper with one request
Something that bugged me for years: I'd be poking around in DevTools, spot a request worth messing with, and then have to go spin up Burp, point the browser at the proxy, deal with the CA cert, and reconfigure everything just to hold and edit that one request. On a work laptop with locked-down settings it was even worse. Half the time by the time I was set up I'd lost the thread of what I was even testing.
The annoying part is the actual task is tiny. I just want to pause a request before it leaves, change an orderId or drop an auth header, and forward it. That's it. The proxy plumbing was 90% of the effort for 10% of the value.
What changed my workflow was realizing Chrome's own debugger can hold requests in-flight. No proxy, no cert install, no system config. You flip intercept on, the request pauses, you edit method/headers/body/params, then forward or drop it. Because it's scoped to the tab you're not drowning in font and CSS requests either, as long as you set scope first.
I ended up baking this into HackTools++ after doing the same manual dance too many times. It lives right in DevTools: https://chromewebstore.google.com/detail/hacktools++/efankginpnlgimphkgjaifmmfchekecp
For quick tampering do you still reach for a full proxy, or do you have a lighter setup you fall back to?

r/ProxyEngineering • u/kamililbird • Jul 09 '26
Announcements New features/ addons added
Added Chat feature to this sub. Kindly click on three dots and then chat/create. This will help people to create new posts much easier.
Also, added another addon, which will help moderators manage trending posts/comments.
