Skip to content
ClonePips

Liquidity product

Liquidity Hub

Aggregate and route liquidity across venues. A routing layer that aggregates broker and external liquidity and exposes it to connected execution venues.

  • Venue aggregation and normalised pricing
  • Routing rules by symbol, size and latency
  • Depth and fill monitoring
  • Venue-level exposure limits
Request a demoWhat is available today

Demo data — fictional sample content for interface development. Not real ClonePips customer data.

Availability

In development in this build

This product is designed but not released. Everything below describes the intended design and is marked accordingly.

  • Listed in development in the product registry — not available today.
  • Slated to deliver 2 platform modules, described on this page as design.
  • Declared integrations: fix api, mt4, mt5 — none is connected in this build.

Registry facts

  • Category: liquidity
  • Status: In development — described as design
  • Intended for: brokers, institutions
  • Delivers modules: 2
  • Pricing basis: usage based

Why it exists

Pricing fragments across venues

Once a broker quotes more than one liquidity source, price is no longer one number. Each venue has its own format, depth and latency, and the routing decision between them becomes a configuration problem rather than a plumbing one.

Liquidity Hub describes a normalised pricing layer: venue formats translated once, routing rules evaluated per order, and depth and fill behaviour exposed so an operator can see where fills come from.

Because normalization happens once, everything downstream — execution, risk and analytics — reads a single price shape instead of learning each venue's dialect.

  • Venue aggregation with normalised pricing.
  • Routing rules by symbol, size and latency.
  • Depth and fill monitoring per venue.

Product view

Aggregated depth, illustrated

A routing view of aggregated liquidity: depth by symbol, routing rules and recent fills, composed from demo data.

Illustrative product composition for Liquidity Hub. The frame shows a price depth panel with routing rules and per-venue fills. Depth and fill figures in the frame are fictional demo data. This product is in development; the frame illustrates the intended design.

Liquidity hub console

Demo data

Aggregated depth by symbol

  • EUR/USD

    4 venues quoting

    Spread 0.2Quoting

  • GBP/USD

    3 venues quoting

    Spread 0.4Quoting

  • XAU/USD

    3 venues quoting

    Spread 1.1Quoting

  • USD/JPY

    2 venues quoting

    Spread 0.3Thin

Illustrative depth from demo data. No venue is connected.

Routing rules

  • Best price by symbol

    Route to the tightest quoting venue.

  • Cap by size

    Split orders above the venue depth cap.

  • Latency guard

    Skip venues above the latency ceiling.

Recent fills

  • EURUSDbuy

    1.5 lots

  • GBPUSDsell

    1 lots

  • EURUSDsell

    0.8 lots

  • EURGBPbuy

    2 lots

Performance figures shown on this site are illustrative demo data. Past performance is not indicative of future results.

Demo data — fictional sample content for interface development. Not real ClonePips customer data.

  • The frame shows a price depth panel with routing rules and per-venue fills.
  • Depth and fill figures in the frame are fictional demo data.
  • This product is in development; the frame illustrates the intended design.
  • Illustrative product composition built from demo data. Not a live account or venue.

Design

How Liquidity Hub is designed to work

Normalised pricing

Venue-specific quoting formats are translated once, so everything downstream reads a single price shape.

Rule-driven routing

Routing decisions are configuration evaluated per order, recorded with the outcome.

Depth and fill visibility

The hub exposes depth and fill behaviour per venue so a broker can see where fills come from.

Workflow

Liquidity Hub end to end

How the pieces connect. The diagram names the stages; the labels live in configuration, like every other page.

A diagram of how a venue runs on the platform: brokers, the shared platform model, capability engines, the execution layer and the trading platforms orders reach.

1. Brokers

The venue a platform sits behind.

2. Platform

The shared domain model.

Servers, liquidity and client accounts

3. Engines

7

Capability modules that act on the model.

Signals, allocations and rules act on venues

4. Execution

Where replicated orders reach a venue.

Replicated orders pass risk checks

5. Trading platforms

3

Deployment targets for copying.

Orders reach follower accounts

  • Aggregated pricing feeds the execution layer rather than bypassing it.
  • Routing decisions are recorded beside the venues they chose.
  • Depth and exposure monitoring sit alongside the routing rules.

Audience

Who operates it

The hub is a broker and institutional surface: it exists to make multi-venue pricing legible to the people running execution.

  • Brokers aggregate their own and external liquidity under one policy.
  • Institutions state routing and depth requirements as configuration.
  • Exposure limits are evaluated at the venue level, not per order alone.

Declared integration surfaces

  • FIX API for venue connectivity.
  • MT4 and MT5 deployment targets.
  • Routing and depth as configuration, not code changes.

Deployment

Deployment notes

  1. 01

    Step 1

    Aggregates broker and external liquidity into a normalised pricing layer.

  2. 02

    Step 2

    Routing rules decide by symbol, size and latency before an order leaves the venue.

  3. 03

    Step 3

    Depth, fill and exposure monitoring sit beside the routing rules, not behind them.

Questions

About Liquidity Hub

Is this product available today?

No. The product registry lists Liquidity Hub as in development, and this page describes the intended design only.

Which execution venues does it connect?

Its declared integrations are FIX, MT4 and MT5. No venue is connected in this build, and the page states no live connection.

Notices

Risk warning

Trading foreign exchange, CFDs and leveraged instruments on margin carries a high level of risk and may not be suitable for all investors.

No advice

Information on this site is provided for general information only and does not constitute investment advice or a recommendation.

Demo data

Demo data — fictional sample content for interface development. Not real ClonePips customer data.

Next

Discuss this product's place in your stack

Bring the venue, the execution setup and the fee model you run; the demo covers the platform and the commercial basis.

Request a demoCompare the suite