Offering two trading platforms as a broker sounds like double the infrastructure. In practice the harder problem is not the second platform. It is keeping one CRM, one liquidity setup and one view of risk while clients trade across both. A broker that bolts a second platform onto a separate back office ends up managing two businesses under one licence, with a dealing desk that can only see half its own book at a time.
This is a broker-side guide to doing it properly: routing liquidity per platform, letting clients choose without splitting the client database, and keeping dealing-desk visibility across whatever platform a trade happens to be on.
Why brokers add a second platform
Clients ask for it more often than brokers expect. A trader who has run MetaTrader 5 for years does not want to relearn a terminal, and a trader who wants depth of market and C# automation will look for cTrader specifically. Some brokers add a second platform after the 2022 Apple App Store removal of MetaTrader made single-platform dependency visible in a way it had not been before; others add one after watching how quickly a handful of prop firms had to adapt in 2024 when MetaQuotes tightened its licensing terms. Either way, the decision is rarely about the platform itself. It is about not asking every client to fit one terminal.
Liquidity routing per platform
The first real design decision is where prices and execution come from on each platform. A broker can point both platforms at the same liquidity provider over FIX, which keeps pricing consistent for the same instrument regardless of which terminal a client opens it in, or run separate liquidity relationships per platform if volumes or asset mixes differ enough to justify it. What should not happen is routing decided ad hoc per platform with no shared view of aggregate exposure. If platform A is quietly building a large net position in an instrument while platform B is doing the same in the opposite direction, a broker with two disconnected dealing setups will not see it until it shows up in the P&L.
One CRM, not one CRM per platform
Clients should pick a platform without the broker splitting its client database in two. A trader who opens an account on platform A should be the same client record if they later ask for an account on platform B, with one KYC file, one deposit and withdrawal history, and one support ticket queue. SGHK's Broker CRM connects in one click to MetaTrader 4, MetaTrader 5, cTrader, DXtrade, NinjaTrader, Match-Trader and TradeLocker as well as eTrader, so accounts opened on any of them sit in the same back office. That single view is also what makes IB and affiliate tracking work correctly. A client introduced by a partner should stay attributed to that partner no matter which platform they end up trading on.
Dealing-desk visibility across platforms
This is where most multi-platform brokers still have a gap. MetaTrader, cTrader and DXtrade each ship a dealing interface, but combining exposure, toxic-flow scoring and routing rules across two of them usually means a bridge or a plugin from a third vendor, configured separately for each platform and reconciled by hand. eTrader takes a different approach: the built-in eTrader Dealing Desk covers live order flow, net exposure, top-risk accounts and toxic-flow scoring for the eTrader book directly, with A-book, B-book and hybrid routing, including split routing that sends a set percentage of an order to the liquidity provider and fills the rest in house. A broker running eTrader alongside MetaTrader or cTrader still needs bridge tooling to get the same exposure view on the other platform. That is a genuine cost of running MetaTrader or cTrader, not a flaw unique to either; the fair comparison is that eTrader's desk comes with the platform, while the others' equivalents are assembled.
The point is not that any one platform is wrong to run. It is that a broker offering two platforms should decide, before launch, whether it wants one combined risk view or two separate ones it reconciles manually. Reconciling manually works until the day a large position slips through the gap between them.
What clients actually notice
Clients rarely comment on the back-office architecture. What they notice is whether their deposit shows up on both platforms' balances at the same speed, whether support already knows their account history when they switch platforms, and whether the spread and execution they get on one platform is explainable next to the other. All three come from the same root: one CRM and one liquidity and risk view feeding both platforms, rather than two parallel operations sharing a logo.
Getting started without a rebuild
A broker already running one platform does not need to migrate anything to add a second. Confirm the CRM you use, or plan to use, has a working bridge to both platforms before signing the second integration. Decide liquidity routing and exposure limits per platform up front rather than after volume arrives. Keep KYC, deposits and IB attribution unified from day one so a client who trades on both platforms is one client, not two. A firm considering eTrader as its second platform gets the price feed, native apps and dealing desk bundled in, which is one less integration to manage compared with a platform that needs its own bridge, feed and risk plugins assembled separately.
"Clients should be able to pick a platform without the broker splitting its own business in two. That only works if one CRM and one dealing desk view sit behind both."
— The SGHK Team
Key Takeaways
- Brokers add a second platform for client preference and vendor-risk reasons, not to run two separate businesses under one licence.
- Liquidity routing and exposure limits should be decided per platform up front, with a combined view of net exposure across both.
- One CRM bridging both platforms keeps KYC, deposits and IB attribution unified instead of split into two client databases.
- eTrader's dealing desk with A-book, B-book and hybrid routing is built into the platform; MetaTrader and cTrader need bridge or plugin tooling for the same exposure visibility.
Frequently Asked Questions
Should a broker use the same liquidity provider for both platforms?
It depends on volume and asset mix, but the more important requirement is a combined view of net exposure across both platforms, whether the liquidity relationship is shared or separate. Without it, a position building on one platform can offset or compound a position on the other with nobody watching the total.
Can one CRM really open accounts on two different trading platforms?
Yes. SGHK's Broker CRM connects in one click to MetaTrader 4, MetaTrader 5, cTrader, DXtrade, NinjaTrader, Match-Trader and TradeLocker as well as eTrader, so a client's KYC, deposits and account history stay in one place regardless of which platform they trade on.
Does eTrader's dealing desk cover a second platform running alongside it?
No, it covers the eTrader book directly. A broker running eTrader next to MetaTrader or cTrader still needs a bridge or plugin to get the same exposure and routing view on the other platform, the same as combining any two platforms would require.
What is the biggest mistake brokers make when adding a second platform?
Treating it as a second business with its own CRM, its own KYC and its own risk view. That doubles operational work and creates blind spots in exposure. The fix is one CRM and one combined risk view feeding both platforms from the start.
About SGHK
SGHK is a FinTech company that designs and builds its own software for the trading industry: the eTrader trading platform, Launch your Broker and Launch your Prop Firm. Every product is written, hosted and supported in-house and licensed to trading firms, with the CRMs branded to them, all hosted by us in the cloud, managed by each firm and built to scale across clustered servers as our clients grow. Everything is encrypted, and each firm is the only one with access to its data and its clients' data.