Best LP: bridge architecture, routing and testing.
The best liquidity provider is the one that performs for your flow, measured. Evaluate coverage, connectivity and behaviour under stress with repeatable tests.
Architecture
A bridge sits between MT5 and one or more providers, handling price feeds, order routing and fill reports. Decide whether you aggregate sources and where routing rules live. Document each hop.
Routing rules
Hybrid A-book and B-book routing is a policy encoded in software. Write the rules in plain terms first, including thresholds and exceptions, and get risk and compliance sign-off before implementation.
Test plan
Compare providers on the same instruments, dates and hours: spreads, fills, slippage, rejects and latency. Test failover and feed loss. Record results in a shared sheet. See hosting topology.
Ongoing quality metrics
Track spread, fill ratio, slippage, rejects and latency per instrument and per hour. Compare against baselines and alert on deviations. Share monthly reports with the provider and use them in commercial discussions.
Example test matrix
Instruments: EURUSD, XAUUSD, an index. Sessions: Asian, London, New York. Metrics: spread, fill rate, slippage, rejects, latency. Collect per session for two weeks and compare providers. Use the same order sizes for fairness.
Questions we hear
Is one provider enough?
Resilience and pricing often argue for two. Weigh against complexity.
Who operates the bridge?
Agree operator, monitoring and change process in writing.