Hi, I’m Jonathan.
I built TradersProxy because I got tired of the answer “get a VPS” every time my broker connection wobbled.
Why this exists
The standard answers to a bad broker connection are: get a VPS, use a VPN, or just accept it. I tried all three. None of them were the right shape for the problem.
A VPS works if you want to run an EA unattended. I didn’t. I was trading with my hands on the keyboard, reading charts on my own machine, making decisions in real time. Moving my entire trading environment to a remote machine to solve what was fundamentally a routing problem felt like building a new house to fix a leaky pipe.
A VPN made things worse. It tunnelled everything on the machine through a single encrypted pipe, added encryption overhead, and handed the routing problem to a different provider who was also not thinking about trading traffic.
The actual problem was simpler: the path from my machine to my broker’s server was bad. Not always — on quiet days it was fine. On news events, during high-traffic windows, when my ISP decided to route packets the long way around — it fell apart. And there was no tool that just fixed the route and left everything else alone.
That’s the insight that became TradersProxy. Execution is a network problem, not a platform problem. The platform — MT4, MT5, cTrader — is fine. The broker is fine. The route between the two is the variable. A proxy that sits between your existing platform and your broker, routes only trading traffic, and is engineered specifically for the pattern of a long-lived TCP broker session — that’s the tool that was missing.
TradersProxy is bootstrapped. No outside capital. No VC pressure. No board timeline. I built it with a small team, the product pays for the infrastructure it runs on, and every decision gets made on the basis of what’s right for the traders using it — not what makes a deck slide look good.
Engineering principles
These are not marketing claims. They are descriptions of specific decisions made in the production build.
- The relay runs at TCP layer — no trade content inspection The proxy forwards raw TCP streams. It does not parse your order payloads, inspect your account balance, or read your broker protocol messages. It moves bytes. That’s the whole job.
- Active health checks every 15 seconds Route quality is measured continuously, not assumed. Every 15 seconds the node checks the path to the broker endpoint. If something degrades, the system knows before you do.
- EWMA-based failover to backup node Failover decisions use an exponential weighted moving average over a 15-minute window. Short-term jitter spikes don’t trigger unnecessary failovers. Sustained degradation does. You get a stable primary until the primary genuinely needs replacing — then the backup takes over automatically.
- No trade logs, no account data stored The relay does not log what you trade, when you trade, how much you trade, or which account you’re using. Operational logs cover connection counts, bandwidth totals, and session timing. Nothing else.
- No credential sharing, one account per person Proxy credentials are issued to one individual at provisioning. The acceptable-use policy is one person, one seat. Not a team tool. Not a reseller product. One trader, one connection.
Who I am outside TradersProxy
I’m Australian. I walked away from a licensed career in traditional financial planning to document and prove the mathematical cycles that govern markets. Trading has been part of my life for decades, and through my work in cyclical market forecasting, I understand why execution quality matters on a visceral level. It’s not an abstract metric. It’s the difference between a trade that fills exactly where you expected it and one that doesn’t.
I am not a professional fund manager. I am not a prop firm champion. I am a person who trades with real money, noticed a structural problem in how retail execution works, and solved it by building a disciplined, purpose-built infrastructure.
If you want to know more about me outside this product, my personal site is JonathanEvans.com.au. That’s where I write about the intersection of cyclical market forecasting, finite luxury assets, and trading infrastructure.
The reason I built TradersProxy as a product and not just a personal tool: the problem was too common to keep the solution private. Every community I was in — trading Discord servers, prop firm forums, signal groups — had the same complaint running in the background. Bad fills. Disconnects at news events. Slow logins. The answer everyone gave was “get a VPS.” The right answer was “fix the route without dismantling your setup.” TradersProxy is that answer.
How to reach me
Support goes through the portal. That keeps the conversation attached to your account, which means I can actually help instead of guessing your setup.
Support email via the portal
Open a ticket from the client portal. I read every support email. If something is broken, wrong, or not what you expected — say so. I’d rather know than not.
For everything else — general questions, partnership enquiries, feedback — the portal contact form reaches me directly. I don’t have a support team that filters mail before I see it. It comes to me.