Evidence-led broker guideLiquidity, execution, and connectivity

Liquidity Bridge: Definition, Routing and Evaluation

A liquidity bridge links an MT4 or MT5 broker server to liquidity providers. Learn how it routes prices and orders, and how to evaluate one before go-live.

By Orrnn Traders2,723 words
Broker order-routing architecture with risk checks, internal and external execution paths, exception handling, and reconciliation
Execution design is a controlled workflow: intake, validation, routing, exception handling, counterparty processing, and reconciliation.

Direct answer

A liquidity bridge is connectivity software that links a broker's trading server to liquidity providers. It passes prices in, routes client orders out and returns executions. It does not create liquidity or guarantee fills, best execution or compliance. Evaluate one by documenting its counterparties, routing rules, order lifecycle, failover and reconciliation, then testing each flow against the provider's protocol.

Key takeaways

  • A liquidity bridge connects a broker's trading server to liquidity providers. It moves prices in and orders and executions back out.
  • MetaQuotes announced a Gateway API in 2013 that lets brokers build their own gateways to other systems. Check current MetaQuotes documentation before relying on it.
  • A bridge does not create liquidity, guarantee fills or make execution compliant on its own.
  • Bridge, aggregator and gateway are different roles. Ask each vendor which role it performs and where each decision is made.
  • Test every order state, price feed and failure path against the counterparty's protocol before launch.
  • The RTX5 roadmap lists its liquidity bridge as build not published (checked 9 November 2026), so confirm scope and accepted build in writing.

What is a liquidity bridge?

A bridge sits between the trading server and the providers that supply prices and fill orders.

A liquidity bridge is the software layer that connects a broker's trading server to external liquidity. In a typical MetaTrader deployment, the bridge receives quotes or depth from one or more providers and passes them to the server, so clients can trade against those prices. When the broker chooses to hedge or route a client order, the bridge forwards it to a provider. Executions come back along the same path, and the server books them against client accounts. The exact job depends on the deployment, so write it down before comparing vendors.

A MetaQuotes news item dated 21 August 2013 announced a Gateway API that lets brokers develop a gateway to any system or exchange, and said some brokers had already done so. That is a dated announcement, so check current MetaQuotes documentation before relying on it. The MetaQuotes brokers page separately describes built-in liquidity aggregation and order matching, and direct connectivity to global exchanges through dedicated gateways. Those are vendor statements about what the platform supports. They do not show that a particular bridge, provider or server build will behave as your brokerage needs, so each connection still requires its own specification and test evidence.

The same role exists in MT4 deployments, but the server interfaces, supported versions and vendor tooling differ. Confirm the server version and the bridge's supported interface before assuming an MT5 design carries across. Keep the failure modes in view. A stale price feed, a dropped session or a timed-out order can leave the server and the provider with different views of the same trade. The sections that follow cover how to evaluate each point.

Diagram of a liquidity bridge. Quotes flow from liquidity providers LP A and LP B through the primary bridge into the MT5 trading server, and orders flow back out along the same route. Dashed failover paths run from LP A to LP B and from the primary bridge to a standby bridge.
Illustrative flow only. Quote, order and execution paths run through the bridge. Failover paths must be defined and tested with each counterparty rather than assumed from the diagram. Open full-size diagram

Bridge, aggregator and gateway compared

The three terms overlap in vendor material. The proposal should name the role the vendor actually performs.

Vendors use these words loosely. A gateway is a connection layer that speaks one counterparty's protocol or API. An aggregator combines quotes or depth from several sources into one consolidated price. A bridge can include either or both, and often adds mapping, routing, risk and reporting functions. A bridge is not automatically an aggregator, and an aggregator does not provide order execution by itself.

The practical risk of a vague label is an ownership gap. The price feed may work while nobody owns the order state after a counterparty timeout. Ask which component stores the order, which component decides the route, and which record proves the outcome. Those answers matter more than the marketing category.

Role, typical job and vendor question by term
TermTypical jobQuestion to ask the vendor
Liquidity bridgeCarries prices and orders between the trading server and one or more providers, often with mapping and routingWhich counterparties, sessions and message types are supported, and who owns each mapping?
Liquidity aggregatorCombines quotes or depth from several sources into a consolidated price, with markup and priority rulesWhich aggregation, staleness and priority rules apply, and can the outcome be reproduced later?
Gateway or connectorImplements one protocol or venue connection, such as FIX or a vendor APIWhich versions, dialects and certification records apply to this exact connection?

Define the bridge's job in the operating model

Start with the business flow rather than a latency claim. A bridge may receive prices, normalize symbols, aggregate books, apply markups, publish prices to a trading platform, receive orders, apply risk or routing logic, send messages to counterparties, process executions, and feed reporting. Another deployment may perform only connectivity. List every required function and identify whether it belongs in the bridge, trading server, separate risk engine, liquidity provider, or brokerage procedure.

Document products, venues, account types, legal entities, client classifications, expected concurrency, order and quote rates, peak scenarios, sessions, currencies, and geographic deployment. Define which flows are matched externally, internalized, manually handled, or rejected. Have compliance and counsel review how execution arrangements, conflicts, disclosures, and client outcomes apply; a technical diagram does not decide the legal characterization.

Identify each system of record. The trading platform, bridge, counterparty, and ledger can disagree about order state, execution, position, price, fee, or timestamp. Define authoritative records for each purpose, cross-system identifiers, reconciliation frequency, tolerances, corrections, and escalation. The architecture is incomplete until operations can explain and resolve a break without editing databases or relying on a vendor's informal message.

Evaluate market-data construction separately from execution

List every price source, data right, instrument mapping, precision, trading session, time zone, subscription, depth level, and redistribution condition. Establish how quotes are normalized, filtered, timestamped, aggregated, marked up, and published. Ask how the system identifies stale, crossed, inverted, outlier, duplicate, or missing data and what safe behavior follows. A displayed quote can remain technically available while being economically unusable.

Define aggregation rules in measurable terms. If a consolidated book is required, specify price-time or other priority, depth construction, minimum quantity, source eligibility, locked or crossed handling, quote lifetime, and whether indicative and executable prices are distinguished. Record what information dealers and surveillance teams can retrieve afterward. A diagram labelled "smart aggregation" does not explain reproducible behavior.

Keep data and execution entitlements explicit. Permission to receive prices does not necessarily permit display, derived data, storage, or redistribution to all clients and territories. Market-data agreements and exchange rules can affect architecture and cost. Require the vendor and brokerage to identify contractual owners and technical controls, while qualified counsel reviews the rights for the intended use.

Specify the complete order and execution lifecycle

Write state diagrams for market, limit, stop, stop-limit, and other approved order types. Cover validation, acknowledgement, routing, pending status, partial fill, full fill, rejection, cancellation, replacement, expiry, disconnection, correction, and bust where applicable. Define client and counterparty identifiers, allowed transitions, timeout behavior, and how late or contradictory events are handled. Include position and ledger effects at each stage.

For every liquidity connection, obtain its protocol specification or FIX rules of engagement. Record application and session versions, message types, mandatory and optional fields, symbol identifiers, quantities, prices, time-in-force, execution instructions, custom tags, throttles, sequence and resend policy, sessions, certificates, test environments, and certification. FIX compatibility is bilateral; the word FIX does not make two systems plug-and-play.

Test duplicate, delayed, out-of-order, and lost events. Network recovery can replay messages, while a timeout can occur after a counterparty accepted an order. The design must avoid double execution and retain uncertainty for investigation rather than inventing a final state. Match drop-copy or independent records where available and surface gaps immediately to operations.

Bridge acceptance scenarios that reveal operational risk
ScenarioExpected controlEvidence
Price source goes staleSource is excluded or safely degraded under an approved ruleAlert, decision trace, client output
Order timeout after sendState remains controlled until counterparty status is reconciledMessage log and operator workflow
Partial fill then disconnectFilled quantity is preserved and remainder follows defined recoveryOrder, execution, position, and ledger trace
Sequence gapSession recovery follows bilateral rules without silent lossSession log and gap-resolution record
Symbol mapping errorPre-trade validation prevents or contains the mismatchRejected test and mapping approval
Primary region unavailableFailover meets stated data-loss and service objectivesExercise result and reconciled recovery

Turn routing and risk language into versioned rules

Define inputs available to routing: legal entity, client group, account, instrument, side, size, exposure, counterparty status, price, depth, cost, capacity, session, and approved restrictions. Define the decision, priority, fallback, rejection, override, and audit fields. If rules change, store the version, approver, reason, effective time, tested cases, and rollback. Reconstruct which rule handled any historical order.

Separate pre-trade limits from dealing strategy. Credit, margin, order-size, price-band, frequency, and fat-finger controls may protect clients, the brokerage, or a counterparty. Exposure thresholds, auto-hedging, and internalization rules express risk appetite. Document ownership and independence so commercial operators cannot quietly bypass protective controls. Test boundaries, concurrent orders, currency conversion, and stale inputs.

Assess conflicts and client outcomes with compliance, not merely technical teams. A-book, B-book, and hybrid are industry descriptions, not complete policies. The brokerage should understand how price formation, markups, routing discretion, rejections, asymmetric treatment, slippage, hedging, and incentives interact with its contracts and obligations. Monitoring should compare disclosed behavior with actual outcomes across meaningful client and order groups.

Measure performance without accepting headline latency

Define timestamps and clocks before defining a threshold. Measure client receipt, platform receipt, bridge receipt, decision, counterparty send, acknowledgement, execution, return to the bridge, platform update, and client notification where available. Synchronize clocks, quantify error, and preserve raw events. An average measured inside one component cannot establish end-to-end execution speed or client experience.

Report distributions under representative load: median, high percentiles, timeout, rejection, partial fill, slippage, and recovery—not a single best result. Segment by instrument, session, counterparty, order type, size, region, and market condition. Separate network transit, queueing, application processing, and counterparty time where evidence permits. State the test topology and whether measurements come from demonstration, staging, or production.

Set capacity criteria for normal, planned peak, and stress conditions. Include price updates, order messages, session reconnects, reports, monitoring, and reconciliation, because non-trading workloads can compete for resources. Test backpressure and graceful degradation. A system that remains online while dropping data or building an unbounded queue has not passed resilience.

Review resilience, support, security, and change control

Map single points of failure across regions, networks, DNS, certificates, credentials, bridge instances, trading servers, databases, message stores, time sources, monitoring, and counterparties. Obtain recovery objectives and assumptions per service. Exercise process failure, network partition, data corruption, region loss, credential expiry, and restoration. Confirm who authorizes failover and how orders in uncertain state are reconciled.

Ask for the security responsibility matrix, administrative-access controls, encryption boundaries, key and certificate lifecycle, logging, vulnerability management, secure development, incident notification, backup, and supplier dependencies. Connectivity often requires sensitive credentials and allowlists; ownership of issuance, rotation, emergency revocation, and audit must be explicit. Review evidence with qualified security staff.

Define release notice, compatibility, test windows, rollback, emergency change, and counterparty certification. A bridge change can affect message semantics without a visible user-interface change. Maintain regression packs for mappings, order states, routing, prices, risk, reports, and reconciliation. Production changes should have approval, staged exposure, monitoring, and a reversible plan.

Decision checklist

  • Products, counterparties, sessions, expected flow, and legal entities are defined
  • Market-data rights, mappings, aggregation, markups, and stale-price rules are documented
  • Every order type has an end-to-end state model and bilateral certification cases
  • Routing, risk, overrides, and changes are versioned and reconstructable
  • Performance evidence uses distributions, synchronized timestamps, and realistic load
  • Counterparty, platform, bridge, position, and cash records are reconciled
  • Failover, message recovery, security, support, and change processes are exercised
  • Contracted scope covers adapters, environments, hosting, data, support, pricing, and exit

Normalize commercial scope and avoid bundle assumptions

Price the complete service: onboarding and certification, connectors, symbols, counterparties, environments, instances, regions, hosting, data, message or volume units, risk modules, reporting, monitoring, support, professional services, custom rules, upgrades, and termination. Model low, expected, peak, and migration scenarios. State third-party fees and minimum commitments separately. No generic monthly comparison is reliable without matched scope.

Contract for documentation, data ownership, audit cooperation, service levels, incident notification, maintenance, security, business continuity, change, subcontractors, portability, and termination assistance. Define acceptance tests and remedies for material failures. Service credits may be part of the agreement, but they do not replace architecture and controls that protect orders, balances, and clients.

RTX5 lists a bridge/gateway option on Entry and included bridge/gateway scope on Standard. Its roadmap lists the bridge as build not published (checked 9 November 2026), so confirm scope and accepted build in writing. Define adapters, routing, instruments, environments and failover in the quote, and validate counterparty sessions before launch. A bridge software licence is not a liquidity-provider contract, counterparty certification or a promise that an independent provider will onboard a brokerage.

Frequently asked questions

What is an MT5 liquidity bridge?

An MT5 liquidity bridge is connectivity software that links a MetaTrader 5 trading server to external liquidity providers. It usually passes prices into the server, forwards selected client orders out, and returns executions for booking. MetaQuotes announced a Gateway API in 2013 for building gateways of this kind, so confirm the current interface in its documentation. The bridge's scope, supported counterparties and failure handling are set by the vendor and the contract, so evaluate each one separately.

Is a liquidity bridge the same as a liquidity aggregator?

No. An aggregator combines quotes or depth from several sources into one consolidated price. A bridge carries prices and orders between the trading server and providers, and it may include aggregation, mapping and routing. Some products do both. Ask the vendor which functions it runs, where each routing decision is made, and which records prove the outcome.

Does a liquidity bridge guarantee fills or best execution?

No. A bridge transmits prices and orders, but fills depend on the liquidity provider, market conditions, order size and the broker's own execution rules. Best execution is an outcome the broker must monitor and evidence under its regulatory obligations. Responsibility does not transfer to a technology vendor, so review routing rules, rejections and slippage with compliance staff.

Is there an MT4 liquidity bridge too?

The same role exists in MT4 deployments, but the server interfaces, supported versions and vendor tooling differ from MT5. Confirm the exact MT4 server version and the bridge's supported interface in writing. Do not assume an MT5 test result carries over to MT4. Repeat order-state, price-feed and failover tests on the platform you will actually run.

What should a broker test before going live with a bridge?

Test the full order lifecycle, including partial fills, timeouts, rejections and disconnects. Check price staleness rules, symbol mapping, position and ledger updates, and reconciliation against the provider's records. Rehearse failover and recovery, and confirm who decides whether an order in an uncertain state is cancelled, confirmed or investigated. Keep the test evidence with the contract file.

Primary sources and evidence boundary

Sources are listed to support specific definitions, public vendor statements, and regulatory frameworks. They do not endorse Orrnn, prove that a product meets a requirement, or replace a current proposal, contract, legal opinion, technical test, or regulator decision.

The original source review was completed on 21 September 2026. RTX5 pricing and plan references were updated on 26 September 2026; the dated note below identifies that product source. Recheck time-sensitive requirements and commercial terms before relying on them.

  1. RTX5 broker pricing and plan inclusions

    RTX5 / Orrnn

    Product pricing reviewed 26 September 2026. Vendor-published commercial scope, not independent proof of performance, compatibility or regulatory approval. Inclusions vary by plan.

  2. MetaTrader 5 Gateways & Connectivity

    MetaQuotes

    MetaQuotes news item dated 21 August 2013 announcing the Gateway API for building gateways to other systems and exchanges. A dated vendor statement, not current documentation or a specification for any particular bridge.

  3. MetaTrader 5 for Brokers

    MetaQuotes

    MetaQuotes brokers page describing built-in liquidity aggregation, order matching and dedicated exchange gateways. Vendor-published and subject to change; check current documentation before relying on it.

  4. FIX Protocol

    FIX Trading Community

    Primary standards source; implementers still need counterparty-specific rules of engagement and certification.

  5. Supported Versions of the FIX Protocol

    FIX Trading Community

    Official explanation of supported legacy versions and FIX Latest as of 2026.

  6. MiFID II

    European Securities and Markets Authority

    Official entry point for EU MiFID II materials; applicability and execution obligations require qualified review.

  7. The NIST Cybersecurity Framework 2.0

    National Institute of Standards and Technology

    General risk-governance guidance relevant to the connectivity service and its supply chain.

Your next step

Explore an RTX5 configuration for your business.

Compare the published platform plans, then share the account capacity, client workflows and connectivity your business needs. A requirements discussion can establish the demonstration scope, quote and implementation dependencies. Module inclusions vary by plan.

Platform plans and inclusions