A broker with one liquidity provider and a platform that already splits A-book and B-book flow does not need to buy a bridge. A broker aggregating six liquidity providers, running algo execution across venues and needing minute-by-minute risk reporting almost certainly does. The two setups get confused because both are called "routing," and vendors on both sides have reasons to blur the line. Here is the actual difference.
What a dedicated liquidity bridge does
A liquidity bridge sits between a broker's trading platform and its liquidity providers, and its job is to aggregate more than one source of price and depth into a single feed the platform can trade against, then route each order to whichever provider or combination of providers the broker's rules point to. PrimeXM describes its XCore product as an aggregation and execution engine connecting a broker to a large network of liquidity partners over an MT4 / MT5 bridge. oneZero calls its core technology a hub, serving retail brokers, institutional brokers and banks, and liquidity providers from one platform. Gold-i names its own liquidity bridge directly, paired with MAM tools and risk management for firms connecting a trading platform to multiple providers. Centroid Solutions offers a modular platform spanning liquidity access, risk intelligence and hosting, with bridge products referenced in its own client case studies. Tools For Brokers, sold as TFB, centres its stack on the Trade Processor, which it describes as an execution engine, risk manager and liquidity hub together.
What these vendors share is depth: many liquidity connections at once, algorithmic execution logic that can split, delay or reprice an order across providers, and risk dashboards built for a dealing team managing dozens of feeds rather than one or two.
What built-in routing does instead
The eTrader Dealing Desk is routing built into the platform rather than sold separately. A broker connects its own liquidity provider over FIX, and the desk sends new client orders to the B-book in house, to the A-book at the provider, or by hybrid rules based on a client's trading history, win rate, net profit, profit factor, volume, balance or open lots. Split routing goes further: a set percentage of every order is sent to the liquidity provider as the A-book share, and the rest is filled in house as the B-book share, with the split set per server, per hybrid rule or per account, and a coverage multiplier from 0.5 to 2 scaling how much hedge is sent to the provider relative to the in-house exposure.
The desk also carries exposure limits that cap the house position per symbol, automations that alert staff or move a client between books when a position, a loss or a client's win rate crosses a threshold, and execution data on every order: quote age, slippage in points and money, and the price move after the fill. All of it is visible on the broker dashboard and available to the firm's own CRM through the eTrader CRM API. What it does not do is aggregate several liquidity providers into one book. It is built to run one connected provider, or the built-in eTrader price feed, well.
| Dedicated liquidity bridge | Built-in routing (eTrader Dealing Desk) | |
|---|---|---|
| Number of liquidity providers | Aggregates several at once | One connected provider, or the eTrader price feed |
| Execution logic | Algorithmic splitting and repricing across venues | A-book, B-book, hybrid and percentage split routing |
| Risk tooling | Dedicated risk dashboards from the bridge vendor | Exposure limits, toxic flow scoring, automations, built in |
| Vendor count | Platform, CRM and bridge are separate contracts | Routing ships inside the platform, no extra vendor |
| Best fit | Multiple LPs, high volume, dedicated dealing desk staff | One or two LPs, newer or leaner broker operations |
When a firm needs a dedicated bridge
A broker aggregating liquidity from several providers to get the best price and depth at any moment needs a bridge built for that job, because splitting and re-routing across many venues in real time is exactly what PrimeXM, oneZero, Gold-i, Centroid Solutions and TFB are built around. A broker running complex algo execution strategies, needing detailed slippage and rejection reporting across each individual provider, or already running MetaTrader with its own separate liquidity setup, is also better served by a dedicated bridge than by asking a platform's built-in routing to do a job it was not designed for.
When built-in routing is enough
A new broker connecting one liquidity provider, or a prop firm running evaluation accounts on a platform's own price feed with no external liquidity provider at all, gets little from a bridge beyond an extra vendor relationship and an extra monthly cost. For that firm, what matters is whether the platform's own routing covers the basics: A-book and B-book separation, hybrid rules based on client behaviour, exposure caps, and visibility into execution quality. The eTrader Dealing Desk covers all of that without a firm connecting a second vendor, and split routing with a coverage multiplier gives a broker a middle ground between pure A-book and pure B-book without needing bridge-level aggregation to do it.
The honest limit on the built-in side: if a broker later wants to aggregate five or six liquidity providers with algorithmic best-execution logic, that is a job for a dedicated bridge, not for any single platform's native routing, eTrader included. A broker in that position pairs a bridge with whichever platform it already runs, since a bridge connects to a platform through the same FIX handoff regardless of which one it is.
Deciding which one you need
Count your liquidity providers first. One or two providers with straightforward hybrid rules point toward a platform's built-in routing. Three or more, or a dealing desk that wants algorithmic execution across all of them, points toward a dedicated bridge from a vendor like the ones above. Either way, ask for execution data during a live test: quote age, slippage and rejection rates tell you more in a week than a vendor's own description will. Brokers running eTrader can test the built-in Dealing Desk against a demo before deciding whether a bridge is worth adding on top, on a live demo call.
"We built split routing and a coverage multiplier into the Dealing Desk because most brokers we talk to do not need a five-provider bridge on day one. When they do, they add one on top of eTrader rather than instead of it."
— The SGHK Team
Key Takeaways
- A dedicated liquidity bridge, such as PrimeXM, oneZero, Gold-i, Centroid Solutions or TFB, aggregates several liquidity providers and runs algorithmic execution across them.
- Built-in routing, such as the eTrader Dealing Desk, handles A-book, B-book, hybrid and split routing with one connected provider, no extra vendor needed.
- Split routing with a coverage multiplier from 0.5 to 2 lets a broker blend A-book and B-book without bridge-level aggregation.
- Three or more liquidity providers, or a need for algorithmic best execution across venues, is the signal to add a dedicated bridge.
Frequently Asked Questions
What does a liquidity bridge actually do that built-in routing does not?
It aggregates prices and depth from several liquidity providers into one feed and runs algorithmic execution logic across them. Built-in routing like the eTrader Dealing Desk handles A-book, B-book, hybrid and split routing well for one connected provider, but it is not built to aggregate several providers into one book.
Can a broker use both a bridge and eTrader's Dealing Desk?
Yes. A bridge connects to a platform over FIX the same way a single liquidity provider does, so a broker can run a dedicated bridge upstream and still use the Dealing Desk's A-book, B-book and hybrid rules on top of it.
How many liquidity providers before a bridge makes sense?
There is no fixed number, but most brokers who add a dedicated bridge are aggregating three or more providers, or want algorithmic best-execution logic that a single platform's native routing was not built to do.
What is split routing and the coverage multiplier?
Split routing sends a set percentage of every order to the liquidity provider as the A-book share, filling the rest in house as the B-book share. The coverage multiplier, from 0.5 to 2, scales how much hedge goes to the provider relative to the in-house exposure, and both are set per server, per hybrid rule or per account.
Does a prop firm need a liquidity bridge at all?
Usually not. A prop firm running evaluation accounts on a platform's own demo price feed, such as the eTrader price feed, needs no external liquidity provider and therefore no bridge. A bridge matters once a firm is routing real client flow to outside liquidity.
About SGHK
SGHK is a FinTech company that designs and builds its own software for the trading industry: the eTrader trading platform, Launch your Broker and Launch your Prop Firm. Every product is written, hosted and supported in-house and licensed to trading firms, with the CRMs branded to them, all hosted by us in the cloud, managed by each firm and built to scale across clustered servers as our clients grow. Everything is encrypted, and each firm is the only one with access to its data and its clients' data.