MT4/MT5 Liquidity Bridge Providers Compared (2026): PrimeXM, oneZero, Centroid and More

Brokers searching for an MT4 or MT5 liquidity bridge usually find two kinds of pages: vendors describing their own product, and "best bridge" lists written by other vendors. Neither tells you how the products differ on the questions that decide a setup: which platforms connect, where the bridge runs, how routing between A-book and B-book works, and what it costs.

This guide compares eight bridge providers that brokers commonly evaluate: PrimeXM, oneZero, Centroid Solutions, Gold-i, FXCubic, Tools for Brokers, Takeprofit Tech and Brokeree Solutions. It does not rank them. Every vendor fact below comes from that vendor's own website, checked in November 2026. Products, names and prices change, so confirm anything that matters with the vendor before you sign.

A note on where we stand: relioops is not a bridge vendor and not a liquidity provider. We set up, configure, monitor and support the bridge a broker has chosen, alongside the MT4 or MT5 server it connects to. We have deployed PrimeXM, oneZero, Centroid, Gold-i and FXCubic for broker clients, so this guide is written from the integration side.

The short answer

All eight connect MetaTrader 4 and MetaTrader 5 to liquidity providers, and all eight state some form of multi-provider aggregation. The real differences are elsewhere:

• Where it runs. PrimeXM, oneZero and Centroid run the bridge as a hosted instance in their own data centres. Gold-i, Tools for Brokers and Takeprofit offer either their hosting or your servers. FXCubic and Brokeree are deployed on the broker's own infrastructure.
• Which platforms beyond MetaTrader. Centroid, Gold-i, Tools for Brokers, Takeprofit and Brokeree name cTrader and other platforms on their sites. PrimeXM and oneZero describe MetaTrader plus other connections in general terms.
• How routing is described. Brokeree and Takeprofit use the words A-book, B-book and hybrid. Others describe the same ground as A/B-book switching, internalisation or warehousing.
• Price. Only PrimeXM publishes a fee schedule. The other seven quote on request.

What a liquidity bridge does

A liquidity bridge sits between your trade server and your liquidity providers. It takes orders from MT4 or MT5, routes them to one or more providers under your rules, and returns prices and fills. Most bridges also aggregate prices from several providers into one book, apply markups, and decide what happens when a provider is slow or unavailable.

On MT5 the connection to the bridge is usually an MT5 Gateway, a module on the trade server built on the MetaTrader Gateway API. On MT4 the bridge connects through a server plugin. More on how the two fit together on our liquidity bridge and gateway page.

Seven things to compare

1. Trading platforms, today and next year

List every platform you run and every one you may add in the next two years: MT4, MT5, cTrader, DXtrade, Match-Trader, TradeLocker. Ask whether each connection is in production at other brokers or still being built. A bridge that only covers MetaTrader is fine until you add a second platform.

2. Hosting model and data centre

There are three models in this group: hosted by the vendor as a dedicated instance, hosted by the vendor or on your servers as you choose, and installed on your infrastructure only. The vendor-hosted model puts the bridge next to the liquidity, usually in Equinix LD4 (London), NY4 (New York) or TY3 (Tokyo). Self-hosting gives you more control and shifts the operational work to your team. Ask where the bridge sits relative to your trade server, because the distance between them matters as much as the distance to your providers.

3. Liquidity provider connectivity and aggregation

Ask whether your current providers are already integrated, and how a new provider is added: an existing adapter, a FIX connection, or development work. Check which aggregation modes are available, how symbol mapping is handled across providers with different contract sizes, and what happens to a symbol when one feed stops.

4. A-book, B-book and hybrid routing

Routing rules decide which flow goes to the market and which stays on your book. Check whether rules can be set by symbol, group and account, whether positions can be moved between books after they open, and how every routing change is recorded. This has direct commercial impact, so it should be documented and changed deliberately.

5. Risk tools and reporting

Some bridges include exposure monitoring, toxic-flow detection and auto-hedging; others leave that to a separate risk system. Check what the bridge reports on its own (fill rates, slippage, rejections per provider) and whether regulatory reporting is built in or connected through a partner.

6. Pricing model

Bridge pricing usually combines a fixed monthly fee per instance or connection with a volume or transaction element. Model it at your current volume and at twice that volume. Ask what is included in the base fee: number of platform connections, provider connections, environments and support hours.

7. Who sets it up, and who runs it after go-live

Vendors typically state a setup time of a few days. The work that takes longer is on the broker's side: symbol mapping, session alignment with your providers, routing rules, failover testing and monitoring. Decide before you sign who does that work, and who answers when execution complaints arrive at 3 a.m.

A-book, B-book and hybrid: the short version

• A-book: client orders are passed to liquidity providers. The broker earns from markup and commission, and market risk sits with the provider.
• B-book: the broker takes the other side of client orders and keeps the market risk on its own book.
• Hybrid: a mix, set by rules. For example, larger or consistently profitable accounts are routed to the market while the rest stays on the book.

Every bridge in this guide states support for routing between external liquidity and internal execution in some form; the wording differs, the underlying question does not. What matters in practice is how granular the rules are, how fast they can change, and whether every change leaves a record.

Side by side

The providers: what each one states

PrimeXM (XCore)

• Product: XCore. MetaTrader connects through the PrimeXM MT4 Bridge and MT5 Gateway.
• Platforms: MT4 and MT5, plus other platforms and FIX API clients.
• Aggregation and routing: multi-tier best bid and offer aggregation; A-book, B-book and custom execution models, routed by client, group and instrument.
• Hosting: dedicated instance on PrimeXM's infrastructure, with hubs in Equinix LD4/LD7, NY4, TY3 and SG1.
• Pricing: the only vendor here with a public fee schedule. It lists a fixed monthly fee of $2,000 per XCore instance and $1,200 per MT4 or MT5 connection; volume and transaction fees also apply, and each instance is billed at the highest of these fee groups rather than their sum.
• Company: established in 2010.

oneZero (Hub)

• Product: the Hub, in Retail and Institutional versions, part of the oneZero EcoSystem.
• Platforms: connects to front-end platforms including MetaTrader 4 and 5.
• Aggregation and routing: custom liquidity pools and aggregation; describes book management as warehousing and warehouse controls.
• Hosting: each Hub is a dedicated hosted instance, co-located in NY4, LD4 and TY3.
• Assets: FX, CFDs, commodities, futures, cash equities and cryptocurrencies.
• Pricing: packages, not published.
• Company: founded in 2009, headquartered in Boston; states ISO 27001 certification.

Centroid Solutions (CS 360)

• Product: CS 360, the bridge and execution engine. The name "Centroid Bridge" now redirects to CS 360, and the risk product formerly called Centroid Risk is now C24.
• Platforms: MT4, MT5, cTrader, DXtrade, Match-Trader and TradeLocker among its integrations, plus FIX 4.4, WebSocket and REST APIs.
• Aggregation and routing: connects to any number of liquidity providers; exposure monitoring, A/B-book switching, internalisation and auto-hedging.
• Hosting: SaaS on a dedicated instance in Equinix LD4, NY4, TY3 and SG3.
• Pricing: not published.
• Company: headquartered in the UAE.

Gold-i (MatrixNET)

• Product: MatrixNET, described as an enhanced liquidity bridge, with a crypto version (MatrixNET Crypto) and a separate risk tool, Visual Edge.
• Platforms: MT4, MT5, DXtrade, cTrader, TradeLocker and Match-Trader, and any FIX or WebSocket-capable platform.
• Aggregation and routing: several smart-routing aggregation methods; internalisation and B-book management, with reports to identify unwanted trading patterns.
• Hosting: on Gold-i's servers at additional cost, or your own instance, cloud or dedicated.
• Pricing: model stated (flat monthly fee or transaction-based), figures on request.
• Company: founded in 2008, headquartered in the UK.

FXCubic (FXCubic Bridge)

• Product: FXCubic Bridge, a bridging and aggregation system.
• Platforms: MT4 and MT5, and other platforms through its own FIX API.
• Aggregation and routing: combines market depth from all providers into one table, with VWAP aggregation; A-book and B-book orders monitored on one interface, toxic-trader detection and a visual rule engine.
• Hosting: deployed on the broker's own infrastructure; each client gets a dedicated version of the full system. FXCubic does not offer hosting itself.
• Pricing: not published.

Tools for Brokers (Trade Processor)

• Product: Trade Processor, which TFB also calls its liquidity gateway.
• Platforms: MT4, MT5, cTrader, Match-Trader and DXtrade, with REST and FIX API for others.
• Aggregation and routing: six aggregation modes and private aggregation pools; an A/B-book switch and moving positions between books and providers.
• Hosting: cloud-hosted or installed on the client's site.
• Assets: Forex, CFDs and futures listed.
• Reporting: EMIR, MiFIR and ASIC reporting through a TRAction integration.
• Pricing: not published; trial on request.

Takeprofit Tech (Takeprofit Bridge)

• Product: Takeprofit Bridge. Some testimonials on the same page still use the older name Takeprofit Liquidity Hub.
• Platforms: MT4, MT5, cTrader, TradeLocker, DXtrade, or a custom platform via API.
• Aggregation and routing: simple and advanced aggregation modes; A-book, B-book and hybrid execution, with orders split between books; net open position limits with auto-hedging and toxic-flow filters.
• Hosting: your own server or Takeprofit's data centres.
• Assets: includes crypto exchanges among its providers.
• Pricing: not published; free trial offered.
• Company: based in Limassol, Cyprus.

Brokeree Solutions (Liquidity Bridge)

• Product: Liquidity Bridge, in versions for MetaTrader, cTrader and DXtrade.
• Platforms: MT4, MT5, cTrader and DXtrade.
• Aggregation and routing: aggregates quotes into a single feed with symbol mapping and combined depth of market; A-book, B-book and hybrid execution models.
• Hosting: deployed around the broker's existing infrastructure; no vendor hosting stated.
• Reporting: turnover, execution and slippage reports by symbol, account, group or provider.
• Pricing: not published.
• Company: founded in 2013, headquartered in Tallinn, Estonia, with an office in Limassol.

What the public information shows

• Hosting is the biggest structural difference. Choosing between a vendor-hosted instance and your own infrastructure decides who operates the bridge day to day, where it sits relative to your trade server, and what you need in-house.
• Pricing is mostly private. Only PrimeXM publishes figures. For the others, ask for a quote at your volume and at twice your volume, and ask what is included.
• Counts are not comparable. Vendors state numbers of liquidity providers, partners or clients in different ways, and some pages give two different figures for the same thing. Treat them as marketing, not as a ranking.
• Names change. Centroid Bridge is now CS 360, Gold-i's product is MatrixNET, and Takeprofit's bridge appears under two names. Search for the current product name before you rely on an older review.

Where relioops fits

We are not one of the vendors above, and we do not sell liquidity. When a broker chooses a bridge, we deploy and configure it, connect it to the MT4 or MT5 server and to the broker's liquidity providers, set up symbol mapping, routing and failover, and monitor it afterwards with an engineer behind every alert. We have deployed PrimeXM, oneZero, Centroid, Gold-i and FXCubic for broker clients, and the broker's LP relationships and commercials stay the broker's.

If you are choosing a bridge, or execution complaints point at the one you have, tell us what sits between your platform and your liquidity today. For the server side, see MT4 and MT5 server setup and management; for exposure and limits, see real-time risk management for brokers.

Frequently asked questions

Which liquidity bridge is best for MT5? There is no single answer. All eight in this guide connect to MT5. The choice depends on whether you want the bridge hosted by the vendor or on your own servers, which other platforms you run, how you route between A-book and B-book, and the price at your volume.

What is the difference between a liquidity bridge and an MT5 gateway? The MT5 Gateway is the connector on the trade server; the bridge is the system on the other side that aggregates providers and applies routing rules. Many setups use both.

Which bridges support A-book, B-book and hybrid routing? All eight state support for routing between external liquidity and internal execution. Brokeree and Takeprofit use the words A-book, B-book and hybrid; PrimeXM states A-book, B-book and custom models; Centroid and Tools for Brokers describe A/B-book switching; Gold-i describes internalisation and B-book management; oneZero uses the term warehousing; FXCubic monitors A-book and B-book orders on one interface.

Which bridge providers publish their prices? Of the eight, only PrimeXM publishes a fee schedule on its website. Gold-i describes its pricing model without figures. The others quote on request.

Can I host the bridge on my own servers? With FXCubic and Brokeree, the bridge is deployed on your infrastructure. Gold-i, Tools for Brokers and Takeprofit offer either option. PrimeXM, oneZero and Centroid run it as a hosted instance in their data centres.

All posts