Liquidity product
Liquidity Bridge
Connect external liquidity providers to a venue. A managed bridge for wiring third-party liquidity into a ClonePips-enabled broker environment.
- Provider onboarding and credential isolation
- Session and heartbeat monitoring
- Automatic failover between liquidity sources
- Per-provider reconciliation reporting
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 1 platform modules, described on this page as design.
- Declared integrations: fix api — none is connected in this build.
Registry facts
- Category: liquidity
- Status: In development — described as design
- Intended for: brokers, institutions
- Delivers modules: 1
- Pricing basis: per broker
Why it exists
A dead connection should be visible, not silent
Wiring a third-party liquidity provider into a venue is routine until a session drops. The failure is rarely the connection itself; it is that the connection failed quietly, and no one could attribute the gap.
Liquidity Bridge describes provider onboarding with isolated credentials, session and heartbeat monitoring, explicit failover and per-provider reconciliation, so a broken source is a visible state rather than a silent one.
Each provider keeps its own credentials and its own reconciliation record, which means a discrepancy is attributable to a source instead of smeared across the venue.
- Provider onboarding with credential isolation.
- Session and heartbeat monitoring.
- Explicit failover with per-provider reconciliation.
Product view
A bridge monitor, illustrated
A connectivity view: connected sources, failover order and per-provider reconciliation, composed from demo data.
Liquidity bridge monitor
Demo dataConnected sources
- Primary source12 msConnected
- Secondary source18 msConnected
- Backup source31 msStandby
Illustrative sessions from demo data. No external provider is connected.
Failover order
- 01Primary source
- 02Secondary source
- 03Backup source
Reconciliation
- Tickets matched248 / 248
- Open breaks0
- Sessions healthy2 / 3
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 connected liquidity sources with heartbeat state and a failover order.
- Latency and session figures in the frame are fictional demo data.
- This product is in development; the frame illustrates the intended design, not a connected system.
- Illustrative product composition built from demo data. Not a live account or venue.
Design
How Liquidity Bridge is designed to work
Isolated credentials
Each provider connects through its own credential set, kept separate per source.
Explicit failover
Failover between liquidity sources is a configured behaviour with recorded outcomes.
Reconciliation per provider
Fill and session records are reconciled per source, so discrepancies are attributable.
Workflow
Liquidity Bridge end to end
How the pieces connect. The diagram names the stages; the labels live in configuration, like every other page.
A vertical slice through the stack: user experience surfaces, the core product engines, the execution layer and the trading platforms orders end up on.
1. User experience
4Surface each audience operates.
2. Core product
4Capabilities every surface shares.
Every surface talks to the same core
3. Execution
2Server-side routing and bridge.
Normalised orders and evaluations
4. Trading rails
3Where orders end up.
Routed to the venue's platforms
- A bridge connects at the execution layer, beneath the surfaces.
- Reconciliation reads the same ledger records the platform publishes.
- Venue-facing routing is a configured behaviour, not an implicit one.
Deployment
Deployment notes
- 01
Step 1
Onboards third-party liquidity providers with isolated credentials.
- 02
Step 2
Monitors sessions and heartbeats so a dead connection is visible, not silent.
- 03
Step 3
Fails over between sources on configured conditions and reports reconciliation per provider.
Questions
About Liquidity Bridge
Is this product available today?
No. The product registry lists Liquidity Bridge as in development; the availability section above is the source of truth for this build.
How does it connect?
Its declared integration is FIX. This build ships adapters and a declared interface — no external provider is connected here.
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.