How it works
One fixed bill.
One operated bridge.
What you're actually buying: a managed FIX bridge with a fixed monthly fee, an onboarding sequence with no skipped steps, and a migration path that never bets your book on a cutover date.
The deployment model
ModernMarkets runs as a managed bridge. We operate the infrastructure — connectivity, monitoring, upgrades, incident response — and your desk keeps full authority over pricing, routing, risk and client policy. Your platform (MetaTrader or cTrader) connects to the bridge; the bridge holds one dedicated FIX session per liquidity provider on the other side.
You do not install and babysit software. You get an operated system with a desk on the other end of it, 24/5.
Pricing
One fixed monthly fee, set by the shape of your deployment: how many platforms, how many LP sessions, and how much hands-on operation you want. It does not change with your volume.
We price this way on purpose. The costs of running a bridge scale with the number of connections and the people serving you — not with the flow through it. A bill that scales with your volume is a tax on your growth, collected by your infrastructure vendor. Your best month should cost you the same as your worst.
The full argument is in the journal: Why your bridge bill should not scale with your best months.
Onboarding
Onboarding runs in a fixed sequence. No step is skipped, including for early-access clients:
- Application — the request-access form, followed by a call with the desk.
- KYB review — we onboard eligible institutional counterparties only.
- Sandbox — your platform connected to the bridge in a non-production environment; symbols mapped, routing policy configured.
- Parallel run — the bridge runs alongside your existing setup on live market data, without touching production flow, until the numbers agree.
- FIX certification — each LP session goes through the counterparty's conformance process before it carries an order.
- Go-live — staged cutover, with the desk watching.
Migrating from an incumbent bridge
You do not have to jump. The parallel-run stage exists precisely so that a working desk never bets its book on a cutover date. Your current bridge keeps running; ours runs beside it; you compare journals. Cutover happens per platform — and can happen per client group — only when your desk says the numbers agree.
Your LP relationships are yours. We certify sessions with your existing counterparties; nothing about the migration forces a change of liquidity.
Current status
We publish where we actually are, in sequence:
- Bridge core — in build, order lifecycle and journal architecture in place.
- First LP certification — in progress.
- Production go-live — on our own brokerage first. We run our own flow through the bridge before any client does.
- Early-access clients — onboarded after the soak period, in order of application.
Roadmap
The lifecycle beyond the bridge — Issue (tokenized real-world instruments) and Settle (one settlement layer across banking and tokenized rails) — is design-stage work, marked ROADMAP wherever it appears on this site. We describe the architecture because it drives decisions we make in the core system today; we will not describe it as live before it is.