Skip to content

How we built it

We wrote our lean Go proxy engine to protect live execution.

Our custom Go software eliminates third-party proxy bloat. Built around a lean WireGuard philosophy, our proxy engine handles trading traffic directly. It routes packets over institutional backbone paths and recovers lost data inside your broker’s city.

From $9 a month · Stop renewal any time in your dashboard · First payment refunded if your platform can’t connect through us

  • Traffic shaping

    Live order packets take priority over ordinary web traffic

    Recognised trading sockets receive immediate dispatch on busy servers. High-frequency price updates stream continuously ahead of heavy background data.

  • Parallel routing

    Parallel broker address checks and rapid dead-socket termination

    When broker hostnames resolve to multiple IPs, our server checks them simultaneously. It connects through the first gateway that answers and drops dead sockets promptly.

  • Hardware isolation

    Separate server pools with private proxy passwords

    Free accounts remain confined to an isolated test node. Paid memberships run on separate server clusters with rotated proxy passwords.

Our Telegram proxy is the one exception, built on the open-source mtg project.

01 · The software

Our lean Go proxy engine passes orders without opening payloads.

You entrust our nodes with routing your trade executions. We built our proxy engine in Go following a lean WireGuard philosophy. Raw byte streams pass through the operating system kernel without intermediate memory buffers.

We never inspect order payloads, and we never decrypt trading streams. Your terminal TLS encryption stays untouched from your desk to your broker. Your broker credentials never touch our systems.

This optimisation applies strictly to the hop between our server and your broker. Lost packets between your computer and our node recover between those two points. We do not promise lower ping because physical distance sets the floor.

Our Telegram proxy is the one exception, built on the open-source mtg project.

Inside our proxy engineIllustrative
  1. Validates your separate proxy login

    Our node checks your proxy password while your actual broker credentials remain private. You never enter broker passwords into our systems.

  2. Terminates lost packets locally

    Our proxy engine establishes a clean socket to your broker trade server. Dropped packets on that broker leg retransmit locally within that city.

  3. Counts total bytes in place

    Our software tallies aggregate bandwidth usage for your live dashboard. Speed limits apply in place without dropping open trades.

02 · Your orders

Five ways our Go proxy engine protects live orders.

Default operating system networking is tuned for large file downloads and high-latency web browsing. Our custom Go proxy engine alters five specific transmission behaviours for live trading.

See how it works →
  1. 01

    Small packets leave our server as soon as they arrive, without waiting to bundle with other data.

    What it means for you. Your market order departs immediately instead of buffering behind artificial network delays.

  2. 02

    Unsent data is kept from piling up on both connections.

    What it means for you. Fresh price ticks and order fills never wait behind a backed-up queue of stale data.

  3. 03

    On a quiet connection, if a piece of data is lost again, the wait before the next try doesn’t double.

    What it means for you. Successive packet drops avoid exponential retry backoff, preventing temporary market hiccups from freezing your terminal.

  4. 04

    Multiple broker IP addresses are queried in parallel.

    What it means for you. Our engine resolves multi-homed broker gateways simultaneously and connects through the first endpoint that answers.

  5. 05

    Dead connections are discovered and terminated quickly.

    What it means for you. Dropped Wi-Fi sessions clear rapidly so your platform can reconnect immediately without hanging on ghost sockets.

These behaviours apply to our server connections only. Your local computer and your broker maintain their own network stacks. Physical distance sets baseline round-trip time.

03 · Keeping it running

Live trades stay protected during busy sessions and renewals.

When market volatility peaks or card billing retries occur, our infrastructure maintains connection stability.

Self-recovering services

Crashed services restart themselves automatically

If an internal daemon halts, supervisory monitors restart it automatically. System maintenance schedules during weekend windows to protect active trading hours.

Server pools

Paid plans never share hardware with free accounts

Free accounts operate on an isolated machine. Paid subscribers run on separate server pools with priority resource allocations.

Billing grace

Renewal failures grant a grace period before stopping access

If an automated subscription charge fails, proxy connectivity remains active while Stripe reattempts payment. Active positions avoid sudden disconnection.

Signed configuration

Dynamic configuration updates apply without dropped sockets

Our central controller cryptographically signs every rule push. Account parameters adjust dynamically without resetting active market connections.

04 · What we keep to ourselves

You see what it does. The exact settings stay private.

We openly explain our software architecture and its direct trading benefits. The proprietary kernel values and routing configurations remain private. Run your terminal with and without Traders Proxy to verify performance for yourself.

  • The exact numbers behind our settingsNot published
  • Any other settings we useNot published
  • Our source codeNot published

05 · Verified forum reports

Real queue, drop and timeout reports from forums, and what our software changes.

Every quote below links to the forum thread or vendor guide where it appeared. Underneath each quote, see which parts of our system work together on it and where our server stops.

MetaTrader 4 & 5Reduces one factor

'Ping failed' and drops with disconnects every few minutes, re-login loops and dropped sessions

“Is the chart freezing, or is it the terminal? If it is the terminal, then it is likely a broken indicator.”

What our system reduces. If your device drops off, our server notices quickly and frees its place, so your platform can reconnect instead of hanging.

  • Dead connections found and freedPrimary
  • Straight back in after a dropPrimary
  • Reconnect surges admitted in a steady streamSupporting
  • Own separate connection to your brokerSupporting

Where it stops. We do not prevent internet drops or fix broker faults. After a disconnect, your platform logs in again, so always use broker-side stop-loss orders.

cTraderReduces one factor

cTrader drops and re-logs in on a loop (Disconnected, Slow connection or Connection failed)

“Reconnections happen because cTrader cannot establish a good connection with the proxy. There are many reasons this can happen and they are usually temporary.”

What our system reduces. Traders Proxy gives your platform its own route to its servers, which can help when your provider's route is the weak stretch. It does not fix your own Wi-Fi or router.

  • Dead connections found and freedPrimary
  • Straight back in after a dropSupporting
  • Short send queuesSupporting
  • Built-in HTTP proxy loginPrimary

Where it stops. Helps only when your provider’s route is the weak stretch. It does not fix Wi-Fi, router drops or Spotware faults, and cTrader uses HTTP only.

MetaTrader 4 & 5When not to use a proxy

Shared server address where a broker block affects every account on that server

“I have a small VPS service in Thailand, where I share IP internet to save costs. Suddenly, all MT4 in the node started showing a "connection failed" error.”

Why a proxy can backfire here. Your broker sees one steady address, our server’s, shared by people on a Traders Proxy plan in that city.

  • One steady addressBoundary
  • City switchingSupporting

Where it stops. Our server address is shared by people on a Traders Proxy plan in that city. Switch city in your dashboard if a broker blocks that address.

MetaTrader 4 & 5Reduces one factor

'Ping failed' and drops with disconnects every few minutes, re-login loops and dropped sessions

“hey guys,..do you have any ideas why my MT4 often disconected in a several minute or sometime ping failed reported on journal tab. By the way my internet connection doesn,t have any problem or it's always connected.”

What our system reduces. If your device drops off, our server notices quickly and frees its place, so your platform can reconnect instead of hanging.

  • Dead connections found and freedPrimary
  • Straight back in after a dropPrimary
  • Reconnect surges admitted in a steady streamSupporting
  • Own separate connection to your brokerSupporting

Where it stops. We do not prevent internet drops or fix broker faults. After a disconnect, your platform logs in again, so always use broker-side stop-loss orders.

MetaTrader 4 & 5Avoids by design

Virtual hosting limits with one account per server and no custom DLLs

“If it requires DLL calls, it will not work on it, because they are prohibited.”

How local trading avoids it. Your platform runs on your own computer with your own charts and custom DLLs. Plans count connected devices, not trading accounts.

  • Platform stays on your own computerPrimary

Where it stops. We do not host Expert Advisors. If your computer sleeps or goes offline, your robot stops.

Windows VPS & RoutingAvoids by design

Remote-desktop session freezes, drops, or shows "connection has been lost"

“I added the dword `fClientDisableUDP` into HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Policies\\Microsoft\\Windows NT\\Terminal Services\\Client and set as 1. Logged in and out.....problem solved.”

How local trading avoids it. Your platform runs on your own computer, so there's no remote-desktop session to freeze or drop.

  • Platform stays on your own computerPrimary

Where it stops. Your platform's connection to our server can still drop. We notice quickly and your platform can reconnect, but we never promise it won't happen.

Get set up in under 5 minutes.

Setup requires four simple values and zero software installation. Time your platform with and without our route directly on your charts. If your broker prohibits proxies, do not use one.

From $9 a month · Stop renewal any time in your dashboard · First payment refunded if your platform can’t connect through us