The sentence we hear most often when selling a CRM to a broker is: "Ours connects to MT5 too." True, and incomplete. There are two ways to connect to MT5, and the difference between them is not a feature — it is architectural. Both open accounts. Both display balances. One of them still tells the truth when the system is under load. The other might not.
This is written for someone making a buying decision, not for an engineer. You do not need to know the internals; you need to know what to ask the vendor.
What a bridge is, and what it actually does
A bridge is a third piece of software sitting between MT5 and the CRM. Typically it pulls data from MT5's exposed interfaces on a timer — polling — and writes it into its own database. The CRM then reads that database.
The design has real appeal: it is easier to write, it needs no privileged access to the MT5 server, and at a small broker it can run for years without complaint. But it has three structural consequences, and they are arithmetic rather than choices.
1. The data is always slightly old
If your polling interval is five seconds, the balance you are looking at is on average 2.5 seconds stale. On a quiet day that does not matter. When news breaks and price gaps, the margin level on your support agent's screen is not the margin level in reality. The agent says "your account looks fine" and the client is margin-called five seconds later. That is not a bug — it is the design working as specified.
2. Under load, the polling interval stretches
This is the insidious part. Polling lags most exactly when the system is busiest — everyone is trading, MT5 is saturated, the bridge queues. So data freshness degrades precisely in the minute you most need it to hold. Testing on quiet days will never surface this behaviour.
3. You now have two sources of truth
The bridge keeps its own database. "Truth" now lives in two places: in MT5, and in the bridge's copy. Normally they agree. If the bridge loses connectivity for a while, they do not. And in most installations nobody has defined whose job reconciliation is — so when it breaks, an operations person compares by hand.
A practical symptom: if your support team says "the panel shows one thing but MT5 shows another" more than once a month, you have a bridge — and you are living with two sources of truth.
What the Manager API does
The MT5 Manager API is MetaQuotes' official server-side administration interface. It removes the intermediate layer: the CRM connects to the MT5 server at administrator level, performs the operation directly, and receives the result directly. There is no copy database and no polling loop.
Take a leverage change. With a bridge: the CRM tells the bridge → the bridge queues it → applies it to MT5 → reads the result on the next poll → reflects it back. With the Manager API: the CRM tells MT5, MT5 returns the result. Nothing to wait on — and if it fails, it fails immediately rather than sitting silently in a queue.
| Concern | Bridge | Manager API |
|---|---|---|
| Data freshness | Stale by the polling interval | State at the moment of the query |
| Behaviour under load | Lag grows exactly when it matters | Direct server response |
| Source of truth | Two: MT5 and the bridge copy | One: MT5 |
| Error visibility | Can sit silently in a queue | Returned on the call |
| Multiple MT5 servers | A separate bridge per server | Multiple connections from one install |
| Ease of setup | Easier, no privileged access | Requires server access and rights |
The last row deserves honesty: Manager API setup is more work. It needs server access, authorisation, and coordination with whoever hosts your platform. That is why a great many vendors choose a bridge — not because it is the better engineering decision, but because it shortens the sale and the onboarding.
When a bridge is genuinely fine
Not every broker needs the Manager API. A bridge is a reasonable choice when:
- You run one MT5 server and a few hundred active accounts
- Your book is not dominated by high-leverage, fast-moving instruments
- Your operations team already lives in the MT5 admin terminal anyway
- You are still validating the product and speed beats robustness
The moment you leave that description, the arithmetic changes. Three thresholds in particular:
- A second MT5 server. Usually it arrives with a second licence. Each server means another bridge, another reconciliation, another failure point.
- Automated risk rules. If the system is going to close positions or cut leverage on its own, that decision cannot be made on stale data.
- A supervised environment. When a regulator asks who changed this leverage and when, an answer produced from a copy database is an answer open to argument.
Concrete questions to put to a vendor
"Do you use the Manager API?" will be answered yes almost every time. These are the questions that actually discriminate:
- How many steps does a leverage change take to reach MT5? If the answer contains "queue" or "sync", there is a layer in between.
- How stale can the balance on my panel be? "Real-time" is not an answer. Ask for a number in seconds; if they cannot give one, they have not measured it.
- If MT5 stops responding for 30 seconds, what do I see? The right answer is "an error". The wrong answer is "the last known value" — because you cannot tell that it is old.
- How long does adding a second MT5 server take? If it is measured in weeks, they are performing another installation per server.
- Do you have an installation with several MT5 servers connected at once? Ask for the reference. This is where the architecture claim gets tested.
How we do it
Forex Pro CRM uses the Manager API at server level on the MT5 side, and the Open API on the cTrader side. Multiple MT5 servers connect from a single installation. Account opening, leverage and group changes, balance operations and trade history all speak directly to MT5 — there is no copy to keep in sync.
We write this as a trade-off rather than a boast: our setup takes longer and we ask you for server access. In exchange, we leave no place where the number on your support agent's screen and the number in MT5 can drift apart.
Not sure which one you are running today?
Put the five questions above to your current vendor. If you want a second opinion on the answers, 30 minutes is enough — we are happy to have that conversation without selling anything.