Copy TradeLocker trades
with zero headaches

All linked positions are stored in a local database. When you reboot, the engine automatically reconciles open positions, resolves any pending order links via TradeLocker's order history with exponential backoff retries, and resumes copying — no false positions, no manual intervention. Holding trades over the weekend? Shut down Friday, pick up Monday.

The History tab is a full performance analytics platform. It includes: 16 performance metrics (total trades, win rate, total/avg PnL, profit factor, max drawdown, Sharpe ratio, avg duration, avg win/loss, max win/loss, current/longest win/loss streaks, best/worst month), 5 interactive charts (equity curve, PnL by day of week, PnL by symbol, PnL distribution, trade duration distribution), slippage analytics (avg/worst/best per symbol, favourable vs. unfavourable fills, distribution histogram), a 12-week daily P&L calendar heatmap, per-pair performance breakdown, and a 13-column sortable closed trades table with time-range filtering, custom date ranges, account name search, pagination, and one-click CSV export of the current view or the entire history. Everything updates in real time over WebSocket.

When a new master position is detected, AlphaBridge builds order futures for every enabled slave simultaneously and fires them all at once using concurrent async execution. Every slave receives its order within the same millisecond window, regardless of how many slaves you have. This is fundamentally different from sequential copiers that process slaves one at a time.

Yes — this is one of AlphaBridge's most unique features. The engine builds proactive symbol translation maps between every pair of servers at startup. It uses exact matching first, then fuzzy matching that strips common suffixes (.e, X, PERP, SWAP, .c, etc.), so symbols like USDe ↔ USDX or BTCUSD.e ↔ BTCUSD are matched automatically. Both forward and reverse mappings are cached for instant lookup during copying.

The engine calculates a detection window based on your configuration: window = base delay + ⌈active slaves × 0.5s⌉. Any trade detected older than this window is skipped to protect you from excessive slippage. The window automatically scales with your slave count to ensure all copies are included. You can also disable it entirely if you prefer maximum coverage over slippage protection.

Absolutely. Your TradeLocker credentials are encrypted with AES-256-GCM using a key derived from your hardware fingerprint. Trade data never leaves your computer. Our backend only relays signed control commands and live telemetry over an encrypted WebSocket — we never store your API keys or trade history on our servers.

No. Your engine runs as a separate process on your machine or VPS, with a Windows system tray icon showing live status. The dashboard is purely for monitoring and configuration — close it anytime and copying continues uninterrupted.

Yes. AlphaBridge supports multi-master, multi-slave configurations with each pair handled independently and its own risk settings. On the Standard plan you can run up to 2 masters and 4 slaves, with up to 2 copy pairs per master. Accounts can even serve as both master and slave, supporting chained copying strategies.

Yes. The dashboard is fully responsive with a mobile-optimised layout: bottom navigation bar, bottom-sheet modals, sticky first column in tables, touch-friendly 44px+ tap targets, and dynamic viewport height support. Monitor your copies, check analytics, and manage settings from any phone or tablet.

Yes. AlphaBridge fully supports TradeLocker's native Trailing Stop Loss (TSL). The engine detects trailing SL orders, continuously monitors their movement, and synchronizes the updated stop-loss prices to all linked slave accounts in real-time. Your dynamic risk management is perfectly mirrored without any manual intervention.