A startup broker asks a vendor for “a liquidity solution” and receives a quote for a bridge. Six months later, with three liquidity providers connected, the dealing desk discovers that the bridge routes to whichever LP the rule file names — and nothing in the stack is choosing the best price across all three. That capability was never in scope, because it belongs to an aggregator.
The liquidity bridge vs aggregator distinction is the most consequential piece of terminology in broker infrastructure, and it is routinely blurred in sales material. Here is what each one actually does.
What a Bridge Does
A liquidity bridge connects your MT4 or MT5 server to an external execution venue. It translates between the platform’s internal protocol and the LP’s protocol — almost always FIX — in both directions: prices in, orders out, fills back.
Its responsibilities are:
- Receive the LP price feed and publish it into the platform as quotes
- Apply your markup, so the client sees your spread and not the raw feed
- Forward orders matching your routing rules to the LP
- Return fills, confirmations, and rejections to the platform
- Maintain the session, reconnect cleanly, and log everything for dispute resolution
A bridge with one LP is a straight pipe with markup and routing rules attached. That is a complete and correct architecture for most brokers in their first two years, and our introduction to liquidity bridges covers the basics.
What an Aggregator Adds
An aggregator sits in front of multiple LPs and constructs a single synthetic order book from all of them. Where the bridge asks “which LP does this order go to”, the aggregator asks “what is the best available price right now, and across how many venues do I need to fill this size”.
Its distinct responsibilities are:
- Book construction. Merge depth from every connected LP into one book per symbol, continuously.
- Best-price selection. Route each order to whichever venue is genuinely best at that instant.
- Order splitting. Fill 8 lots as 5 from LP A and 3 from LP B when no single venue has the depth at that price.
- Failover. If an LP drops or its prices go stale, exclude it from the book automatically rather than routing into a void.
- LP analytics. Fill ratio, rejection rate, average slippage, and last-look behaviour per provider — the data you need to renegotiate or drop a provider.
Liquidity Bridge vs Aggregator: Side by Side
| Bridge | Aggregator | |
|---|---|---|
| LP connections | One or several, routed by rule | Several, merged into one book |
| Price selection | Feed from the designated LP | Best bid/ask across all LPs |
| Order splitting | No | Yes |
| Automatic failover | Manual or rule-based | Built in |
| LP performance analytics | Basic logs | Core feature |
| Typical broker | Startup to mid-size | Multi-LP, higher volume |
Note the overlap: many commercial products marketed as bridges include light aggregation, and most aggregators include the bridge function. The label tells you less than the feature list, which is why the questions below matter more than the product name.
What Startup Brokers Get Wrong
Buying aggregation before it earns its keep
Aggregation is valuable when you have several LPs whose pricing genuinely differs and enough volume for those differences to matter. With one LP, an aggregator is an expensive bridge. Start with a bridge and a single well-chosen provider; add aggregation when your volume justifies a second and third relationship.
Assuming the bridge decides A-book versus B-book
It does not — your routing rules do, and the bridge only executes them. The decision of which flow goes to the market and which stays internal is a risk-management policy, covered in our guide to A-book versus B-book execution. Buying a bridge without a written routing policy means your risk profile is whatever the default configuration happened to be.
Ignoring the markup engine
Markup is where your revenue is made, and it needs to be far more granular than one number. Per symbol, per account group, per session, and ideally dynamic during high-volatility windows. A bridge with a single global markup field will cost you real money on exotics and during news.
Treating the LP agreement as included
Bridge software connects you to an LP. It does not get you the relationship, the credit line, or the collateral. Expect the LP to want a meaningful deposit and a look at your regulatory standing before turning on a FIX session. Our guide for startup brokers sets out realistic expectations.
No plan for stale prices
The dangerous failure is not an LP disconnecting — that is obvious and handled. It is an LP whose session stays up while its prices freeze. Your platform keeps quoting a stale price, clients trade against it, and you carry the loss. Ask any vendor explicitly how stale-price detection works and what the configured tolerance is.
A Simple Rule
The liquidity bridge vs aggregator decision comes down to provider count and volume. One LP, under roughly 50,000 lots a month: a bridge with a solid markup engine and stale-price protection is the right purchase. Two or more LPs, or a desk actively managing execution quality: aggregation pays for itself through better fills and the analytics that let you hold providers accountable.
Either way, the bridge must report into your broker CRM so that exposure, fills, and rejections are visible next to client data rather than in a separate terminal your risk manager has to alt-tab into.
The ForexPlatforms.Pro liquidity bridge ships with multi-LP aggregation, per-symbol and per-group markup, stale-price protection, configurable A-book/B-book routing, and per-provider execution analytics — connected to your MT4/MT5 server and your CRM as one system.
Frequently Asked Questions
Q: What is the difference between a liquidity bridge and an aggregator?
A: A bridge connects your MT4/MT5 server to an execution venue, translating prices in and orders out with your markup applied. An aggregator sits in front of multiple providers, merges their depth into one book, routes each order to the best price, and can split a single order across venues.
Q: Does a startup forex broker need an aggregator?
A: Usually not at first. Aggregation pays for itself when you have two or more providers whose pricing genuinely differs and enough volume for those differences to matter. With a single provider, an aggregator is an expensive bridge. Start with a bridge and add aggregation as volume grows.
Q: Does the liquidity bridge decide A-book or B-book?
A: No. The bridge executes your routing rules; the rules themselves are a risk-management policy you define. Buying a bridge without a written routing policy means your risk profile defaults to whatever the vendor configured, which is not a decision you want made for you.
Q: What is stale-price protection and why does it matter?
A: A provider whose session stays connected while its prices freeze is more dangerous than one that disconnects cleanly. Without stale-price detection, your platform keeps quoting a frozen price and clients trade against it at your expense. Ask any vendor how detection works and what the tolerance is.