MT4 and MT5 Liquidity Bridge Solutions for Brokers
A vendor-neutral guide to choosing, setting up and running a liquidity bridge for MetaTrader 4 and MetaTrader 5: how it differs from an MT5 gateway and MetaQuotes Ultency, what to ask vendors, and how to test and monitor it.
MT4 and MT5 liquidity bridge guide for brokers: bridge vs MT5 gateway vs Ultency, vendor types, a selection checklist, setup steps, testing and monitoring.
What is a liquidity bridge for MT4 and MT5?
A liquidity bridge (also called an MT4 bridge, MT5 bridge or forex bridge) is the layer between a broker's MetaTrader server and its liquidity providers (LPs). It does two jobs: it brings external prices into MetaTrader, and it carries client orders out to the market and execution reports back.
Most commercial bridges also:
- Aggregate prices from several LPs into one book and build a best bid and offer per symbol.
- Apply markups per symbol, group or client segment before prices reach MetaTrader.
- Route orders by rules: to an LP (A-book), into the broker's own book (B-book), or partly to each (hybrid).
- Map symbols between the names your LP uses and the names your clients see.
- Record and report fills, rejections, slippage and exposure.
Brokeree, one of the vendors in this market, summarises the job in a single sentence that fits most products:
"Brokeree's Liquidity Bridge connects trading servers with multiple liquidity providers, aggregates their quotes into a single feed, and routes every order according to broker-defined execution rules."— Brokeree Solutions, Liquidity Bridge page (accessed October 2026)
A bridge is not a liquidity provider: you still need agreements and FIX sessions with each LP. If you are still choosing LPs, start with liquidity provider integration.
How a bridge connects MetaTrader to liquidity providers
A bridge connects to MetaTrader through a server-side component and to LPs, usually over FIX. On MT4 the component is a server plugin built on MetaQuotes' Server API; on MT5 it is a gateway built on the Gateway API.
Clients (desktop / web / mobile)
|
MT4 or MT5 trade server
|
MT4 plugin / MT5 gateway <-- installed on the MetaTrader side
|
Bridge / hub engine <-- symbol map, markups, routing, risk, logs
| | |
LP 1 LP 2 LP 3 <-- FIX 4.4 or vendor API sessions
MetaQuotes documents both connection points. For MT4, the Server API supports server plugins for "processing trade requests". For MT5, MetaQuotes states:
"Gateway API is used for MetaTrader 5 integration with other trading systems and creation of custom data feeds."— MetaQuotes, MetaTrader 5 for brokers (accessed October 2026)
Vendors use the same model. PrimeXM describes its product as follows: "PrimeXM's MT4 Bridge and MT5 Gateway is a powerful yet light-weight server side plugin which connects MT4 and MT5 platforms to the client's XCore order management and reporting engine." Integral says its MT4/MT5 connection deploys "with a single plugin file (MT4) or executable (MT5) – everything else runs in the cloud."
Every hop on that path, from MetaTrader to plugin, engine and FIX session, is a place where configuration can break, so testing and monitoring matter as much as the product.
Liquidity bridge vs MT5 gateway vs Ultency
On MT5 you have three ways to reach liquidity: a single gateway to one LP, MetaQuotes' own Ultency matching engine, or a third-party bridge or hub. On MT4 a third-party bridge or plugin is the normal route.
MetaQuotes defines a gateway in technical terms: "From a technical point of view, a gateway is a small plug-in for MetaTrader 5." Ultency is MetaQuotes' native aggregation and matching engine. MetaQuotes says that "Ultency is a native solution for the MetaTrader 5 platform" and that it gives "access to more than 30 liquidity providers."
| Question | MT5 gateway (single LP) | MetaQuotes Ultency | Third-party bridge / hub |
|---|---|---|---|
| Platforms | MT5 only | MT5 only | MT4 and MT5; many also cTrader, DXtrade, Match-Trader or FIX clients |
| Liquidity aggregation | No; one LP per gateway | Yes; LPs chosen per instrument | Yes; depth and rules vary by vendor |
| A-book / B-book routing | Routing rules in MT5 | A-Book, B-Book and C-Book (partial hedge, overhedge, reverse hedge) | Yes; group, symbol, size and client rules |
| Where it runs | Inside the MT5 cluster | Dedicated platform per broker, hosting locations chosen by the broker | Vendor-hosted instance or broker server, depending on vendor |
| Symbol setup | Map MT5 symbols to the LP list | Instrument and session settings configured once in MT5 | Three lists to link: LP, bridge and platform |
| Several MT servers | One gateway can serve the cluster | MT5 only | Usually yes, including mixed MT4/MT5 |
| Fits best | One LP, one MT5 server, STP | MT5-only broker wanting native aggregation | Multi-LP, multi-platform, hybrid risk models |
Brokeree's own comparison offers a simple test: if you use one LP, run one MetaTrader server and offer stock trading, a gateway "will be sufficient". That is a vendor's view, but it matches what we see in practice: a bridge earns its cost when you aggregate several LPs, run hybrid execution or connect more than one platform.
For an MT5-only broker, Ultency is worth testing first: MetaQuotes advertises a "free 90-day Ultency trial", and its LP list includes LMAX Group, Swissquote Bank and StoneX Financial Ltd.
Do MT4 bridges still make sense in 2026?
Yes for brokers that already run MT4, but MT4 is not a platform you can start on today. MetaQuotes states on its MT4 broker page:
"The MetaTrader 4 trading platform licenses are no longer available for purchase."— MetaQuotes, MetaTrader 4 API page (accessed October 2026)
An existing MT4 broker still needs a bridge to reach LPs, because MT4 has no native aggregation engine. When you choose or renew an MT4 bridge, check that the same vendor supports MT5, so that you can keep your LP sessions, symbol maps and routing rules when you move. A bridge that runs MT4 and MT5 side by side also makes a staged MT4 to MT5 migration easier: clients move group by group while hedging stays in one place.
New brokers buy MT5. MetaQuotes sells three licence tiers by number of real accounts: Entry (1,000), Standard (25,000) and Enterprise (200,000). The bridge decision then becomes the gateway, Ultency or third-party question above.
Types of bridge vendors
Bridge vendors fall into a few practical groups, from hosted hubs to the native MetaQuotes route. Compare like with like; the facts below come from each vendor's own site.
| Category | Example and what the vendor states | Typical buyer |
|---|---|---|
| Hosted aggregation and risk hub | oneZero Hub: "Each Hub is a dedicated, hosted instance." PrimeXM XCore: MT4 Bridge and MT5 Gateway plugins connect to a hosted XCore engine. | Multi-LP brokers who want the vendor to run the engine |
| Bridge engine (SaaS or self-hosted) | Centroid CS 360: "offered as a SaaS solution", dedicated instance, "over 300 LPs and 17 trading platforms". Brokeree Liquidity Bridge: MT4, MT5, cTrader and DXtrade CFD. | Brokers wanting flexible routing across several platforms |
| Cloud plugin connectivity | Integral: plugin file on MT4 or executable on MT5, "everything else runs in the cloud"; Best and VWAP depth aggregation. | Brokers wanting a light footprint on the MT server |
| Platform vendor with bridge | Match-Trade Bridge MT4/MT5 with RMS: "No plugin installation on MT4 Server needed"; free with Match-Trade's recommended LPs. | Brokers also running Match-Trader or wanting LP-bundled pricing |
| Native MetaQuotes | Ultency (MT5 only), 30+ LPs listed by MetaQuotes; MT5 gateways for single-LP STP. | MT5-only brokers keeping everything inside the platform |
If you buy through a reseller that bundles bridge, hosting and liquidity, ask who owns the licence, the FIX sessions and the configuration export.
We have integration pages for the products we configure most often: PrimeXM XCore, oneZero Hub, Match-Trade and direct FIX API sessions.
A-book, B-book and hybrid routing in a bridge
All mainstream bridges and hubs support A-book, B-book and hybrid routing; the difference is how precise the rules can be. A-book sends client orders to an LP. B-book keeps the client's risk in-house. Hybrid splits flow by group, symbol, trade size, client profile or a percentage of each order.
Vendor documentation shows the range. MetaQuotes lists A-Book, B-Book and C-Book in Ultency, where C-Book covers "partial hedge, overhedge, reverse hedge". oneZero's Portfolios feature lets a broker internalise one group while hedging others. Brokeree says each request "can be sent to the best-priced provider, executed in-house, or split between both".
When you compare products, ask for a live demo of these four cases rather than a feature list:
- Move one client from B-book to A-book in real time without restarting MetaTrader.
- Hedge 50% of a symbol's flow and keep the rest in-house.
- Route orders above a set size to a different LP.
- Show net exposure per symbol across MT4 and MT5 on one screen.
Routing rules are risk policy: sign them off with your risk management team and log every change.
How to choose a liquidity bridge: selection checklist
Choose a bridge on fit with your platforms, LPs and risk model, then on operations and exit terms. Price matters, but a cheap bridge that cannot route your flow the way your dealers need it costs more over time. Score each shortlisted vendor against this list.
| Area | Question to ask the vendor | Why it matters |
|---|---|---|
| Platforms | Which MT4 and MT5 builds do you support, and how fast after a new MetaQuotes build? | An outdated plugin can block server updates. |
| LP coverage | Are my LPs already integrated? What does a new LP cost and take? | New FIX integrations need LP certification time. |
| Hosting | Hosted, self-hosted or both? Which data centres? | Distance between MT server, engine and LP affects latency. |
| Routing | Can rules change in real time per group, symbol, size and client? | Dealers need to react during news without restarts. |
| Symbols | How are suffixes, contract sizes and digits mapped? Is there bulk import? | Mapping errors cause wrong fills and wrong P&L. |
| Failover | What happens when an LP session drops, or when MetaTrader switches to its backup server? | Brokeree warns that a bridge may stay connected to the live server after MetaTrader fails over. |
| Reporting | Can I export fills, slippage, rejections and markups per LP and group? | Needed for LP reviews and best-execution evidence. |
| Support | Support hours, emergency contact, update policy? | Markets open on Sunday evening; problems do too. |
| Commercials and exit | Fee model, minimum term, configuration export on exit? | Switching bridges later should not mean rebuilding everything. |
Two common mistakes: choosing the bridge before the LPs (agree LP terms first, then confirm they are integrated), and buying a multi-LP hub for a single-LP STP setup that an MT5 gateway would handle.
Not sure if you need a bridge, a gateway or Ultency?
Tell us your platforms, server count, LPs and routing model. We will compare the options for your setup and send a written recommendation.
Request a free technical review WhatsApp TelegramBridge setup step by step
A bridge setup runs from preparation to a staged go-live. The vendor runs its engine; the broker or its support team handles MetaTrader and the LP side.
- Collect inputs. MT4/MT5 server details and builds, symbol list with contract specifications, client groups, LP agreements and FIX session parameters (host, port, SenderCompID, TargetCompID, session times).
- Prepare servers. Firewall rules, IP whitelisting with each LP, time sync and backups.
- Install the MetaTrader component. Install the MT4 plugin or MT5 gateway in a demo or test environment first, never straight on the live server.
- Connect LP sessions. Log on to each LP's UAT environment, confirm heartbeats, market data subscriptions and order acknowledgements.
- Map symbols. Link LP symbols, bridge symbols and MetaTrader symbols, including suffixes, digits, contract size and trading sessions.
- Configure pricing. Set aggregation depth, markups per group and stale-quote or spike filters.
- Configure routing. Build A-book, B-book and hybrid rules from the signed-off routing policy.
- Test. Run the test plan below on demo, then with small live volume.
- Go live in stages. Move one group or a few symbols first, then widen, with a rollback plan ready.
- Hand over. Document the configuration and alerts, and export a backup.
Timelines depend most on LP onboarding and certification, so ask each LP for its UAT steps at the start.
Testing a bridge before go-live
Test every order type, symbol class and failure you can simulate before real client money goes through the bridge.
- Order types: market, limit, stop, stop-limit (MT5), partial fills, and the fill policies your LP supports (for example fill-or-kill and immediate-or-cancel).
- Prices: quotes arrive for every mapped symbol, markups match the group, and stale or off-market prices are filtered.
- Routing: each rule sends orders where the policy says; switching a client between books works without a restart.
- Sessions: trading hours, weekend close and Sunday open, holidays and DST changes match between LP, bridge and MetaTrader.
- Failures: drop an LP session, restart the bridge, fail MetaTrader over to its backup server, and check that positions and orders reconcile afterwards.
- Reconciliation: positions in MetaTrader coverage accounts, in the bridge and in the LP's statement agree at end of day.
Keep the test log as your execution-quality baseline.
Monitoring a bridge after go-live
Monitor connectivity, execution quality and reconciliation every trading day. Our monitoring for bridge clients alerts on connection drops, latency spikes and rising rejection rates, and we review execution quality per LP on a regular schedule.
| Metric | What to watch | Typical cause when it moves |
|---|---|---|
| LP session status | Logons, disconnects, sequence resets | Network, LP maintenance, expired credentials |
| Quote freshness | Time since last tick per symbol and LP | Stale feed, wrong session times, filter too strict |
| Rejection rate | Rejects per LP, symbol and reason | Price moved, credit limit, symbol not enabled at LP |
| Fill latency | Order sent to execution report, per LP | LP load, route through a distant data centre |
| Slippage | Positive and negative, per LP and group | Volatility, last look, markup or routing rule |
| Exposure | Net position per symbol vs limits | Routing rule gap, hedge not sent |
| Reconciliation breaks | Differences between MT, bridge and LP positions | Missed execution report, manual dealer action |
Pair it with daily risk reports and toxic-flow lists. For MetaTrader-side faults, see forex server troubleshooting.
What does a forex bridge cost?
Bridge cost is driven by hosting model, number of LP and platform connections, traded volume and support level. Few vendors publish prices, so expect a quote.
- Published example: PrimeXM publishes its XCore fee as the maximum of instance, connectivity, volume and transaction fees, with an instance fee of $2,000 per month and an MT4/5 taker connection of $1,200 per month (PrimeXM pricing page, accessed 8 October 2026). See our XCore page for how the formula works.
- Bundled with liquidity: Match-Trade says its MT4/MT5 bridge can be used "for free if connected to recommended Liquidity Providers".
- Native trial: MetaQuotes offers a free 90-day Ultency trial for MT5.
Around the bridge sit LP minimums, hosting near the LP, the MetaTrader licence and the team that runs it. FXSUPPORT quotes after reviewing your setup.
What FXSUPPORT does in a bridge project
FXSUPPORT is an independent MT4/MT5 support company. We install, configure and run bridges for brokers; we do not sell a bridge of our own, so we can recommend the product that fits your setup.
Selection and design
Compare gateway, Ultency and third-party bridges for your platforms, LPs and routing model, and write the routing policy with your dealers.
Installation and configuration
Server preparation, plugin or gateway installation, LP session setup, symbol mapping, markups and routing rules, tested before live order flow.
Monitoring and alerts
24/7 monitoring of bridge health and LP connectivity, with alerts for connection drops, latency spikes and rising rejections, on a 99.9% uptime target.
Optimisation and changes
Execution-quality reviews per LP, routing refinements, new LPs and symbols, MetaTrader updates and bridge migrations.
You can use us for the full managed service, for installation plus ongoing support, or as consultants to an in-house team that runs its own bridge. Related services include MetaTrader support, MetaTrader server hosting and plugin development when a bridge needs a custom MetaTrader component.
Frequently asked questions
What is a liquidity bridge in forex?
What is the difference between an MT4 bridge and an MT5 gateway?
Do I need a bridge if I use MT5?
Can I still buy an MT4 bridge?
Which MT4/MT5 bridges support A-book and B-book routing?
Is Integral or oneZero better for MT4/MT5 bridge connectivity?
What is an MT4 FIX API bridge?
Should the bridge be hosted by the vendor or on my own server?
How much does a forex bridge cost?
What happens if an LP disconnects?
Does FXSUPPORT sell its own bridge?
Sources
- MetaTrader 5 for brokers: APIs and gateways — MetaQuotes (accessed 8 October 2026)
- MetaTrader 5 on global exchanges: gateways — MetaQuotes (accessed 8 October 2026)
- Ultency Matching Engine — MetaQuotes (accessed 8 October 2026)
- Liquidity Providers for MetaTrader 5 — MetaQuotes (accessed 8 October 2026)
- MetaTrader 4 API — MetaQuotes (accessed 8 October 2026)
- Buy MetaTrader 5 — MetaQuotes (accessed 8 October 2026)
- XCore solutions — PrimeXM (accessed 8 October 2026)
- XCore pricing — PrimeXM (accessed 8 October 2026)
- Hub technology — oneZero (accessed 8 October 2026)
- Portfolios — oneZero (accessed 8 October 2026)
- CS 360 Liquidity Bridge & Execution Engine — Centroid Solutions (accessed 8 October 2026)
- MT4/MT5 Bridge Connectivity — Integral (accessed 8 October 2026)
- Liquidity Bridge — Brokeree Solutions (accessed 8 October 2026)
- MetaTrader Bridge and MT5 Gateway: a head-to-head comparison — Brokeree Solutions (accessed 8 October 2026)
- Bridge MT4/MT5 with RMS — Match-Trade Technologies (accessed 8 October 2026)
- FIX Protocol — FIX Trading Community (accessed 8 October 2026)
FXSUPPORT is not affiliated with MetaQuotes Ltd. or the vendors named on this page. General information, not legal or investment advice.
Choosing, replacing or fixing a liquidity bridge?
Send us your MetaTrader version, server count, LP list and routing model. We will review the setup and reply with a written recommendation and a quote.