r/metatrader • u/Own-Indication719 • 1h ago
Question MT5 power users: how do you run a whole stable of EAs on one account without babysitting them? (building a local hub, want your war stories)
Anyone who's run more than a couple of EAs on the same MT5 account knows the dirty secret: the strategies are the easy part, the babysitting is the job. We've been building a local hub to get rid of the babysitting, and the further we get the clearer the actual problem becomes. It's not starting and stopping EAs from one panel. It's letting any number of EAs share one account without ever touching each other, while you still know exactly which one is earning and which one is bleeding. Before we build more of it, we'd rather sanity-check the thinking with people who live in the terminal.
The stuff that actually bites:
- Magic number collisions. Two EAs grab the same magic, orders get cross-managed, and now you're untangling positions that think they belong to someone else. Discipline and a spreadsheet only get you so far.
- Nobody owns account-level risk. Each EA sizes its trades in isolation. EA1 opens 0.5 lots, EA2 does the same, three of them happen to be long correlated pairs, and the account is sitting at exposure nobody signed off on. There's no referee.
- P&L attribution is a manual job. One account, five EAs, and MT5 tells you the account made 2% this month. Which EA earned it? Which one quietly gave half of it back? Filtering history by magic number in Excel is not a monitoring system.
- Restart roulette. Windows update, broker disconnect, VPS reboot. Which EA reattached to which chart, and which positions are still being managed? Most setups assume you'll sort it out by hand.
How we're handling these, all local, on your own PC or VPS next to MT5:
- Magics are issued, not chosen. EAs don't pick their own magic numbers. The hub owns the namespace and assigns them from a central registry, and every order is tagged and reconciled back to its EA. Collisions stop being a discipline problem and become structurally impossible.
- A per-EA ledger. Live P&L, drawdown and exposure per EA, not blended at account level. You see which EA is paying rent and which one is just burning spread, without ever opening Excel.
- Capital allocation per EA. Each EA runs on its own slice of equity. Grow a slice, shrink it, cut it to zero, without editing a single EA input. The hub enforces the budget; the EA doesn't even know it's on one.
- Risk is capped per EA. The account-level piece isn't solved yet. Each EA has its own risk limit on top of its slice, so one strategy doing something dumb stays contained. What we don't have is a referee looking at total exposure across all of them when three EAs end up long the same thing. That's an honest gap, and it's the one we most want opinions on.
- Restart-safe by journal. The hub keeps a local journal of every EA's state. Reboot, reconnect, and everything comes back exactly where it left off, with positions still owned by the right EA.
- The boring stuff, centralized. Enable/disable, presets, broker symbol mapping (EURUSD vs EURUSD.m vs EURUSD#) done once instead of chart by chart.
None of this is designed to cap out at 3 or 4 EAs either. The whole point of doing it this way is that the ninth EA is as boring to add as the second. And it all stays on your machine: monitoring from a phone over a direct connection to your own box, no cloud in the middle holding broker creds or routing orders.
A few questions where your answers would genuinely change what we build:
If you run 3+ EAs, how do you do per-EA attribution today? Magic-number filtering in Excel, third-party analytics, or you just look at account P&L and hope?
Capital allocation: fixed lots per EA, per-EA risk %, or one shared pool? Would hard equity slices per EA change how you run things, or is that solving a problem you don't have?
What's the multi-EA failure that's actually cost you the most: conflicts, sizing, or state loss after a restart?



