SchoolHeaderSchoolNavSchoolHeaderSchoolNavPlatform, liquidity, CRM, KYC, payments and risk arrive as one system rather than six contracts you have to make agree with each other.
Get Your DemoFrom nothing to first trade
The middle two are ours. The first and the last are yours, and they are the ones that actually set the date.
Where the company sits and what it is allowed to do. Everything after this depends on it, which is why it is worth starting first rather than in parallel.
The terminals you will offer, the bridge in front of your venues, your markup rules and how the book is to be run.
Portals branded, KYC provider connected, payment rails wired to your own accounts, and the partner plan configured before the first IB is signed.
Your desk trained on the console, the risk screen watched by someone who knows what it is telling them, and the portal live on your domain.
What you are actually buying
Assembled separately these are six vendors, six integrations and six people to call when something breaks between them.
MT5, cTrader, Match-Trader, Leverate, VertexFX and Piptrex, run side by side, with accounts and history syncing both ways.
Your own venues aggregated behind one bridge, with markup, routing and A-book, B-book or a split of the two decided by rule.
Admin console, trader’s room, IB portal and mobile apps, all reading one client record and one ledger.
Veriff or Sumsub inside signup, sanctions screening on a schedule, and an audit trail written as things happen rather than assembled later.
Cards, bank transfer, local rails, e-wallets and crypto on your own providers, settling into your accounts and reconciling on a shared key.
Net exposure by symbol, group and desk as positions move, with limits that raise alerts and hedge on their own if you would rather they did.
Why it matters that they fit
Six good systems that do not know about each other cost more to run than one adequate one that does.
The gateway confirms, the wallet is credited and the trading account is funded in one movement. Where those are three systems, somebody re-keys an amount between them — and eventually re-keys it wrong, on a Friday, for a client who is on the phone.
Accounts on every platform, documents, deposits, tickets and the partner who introduced them all hang off the same client. A support call answered with the whole relationship on screen is a different call from one answered with a name and a number.
Partner commission is calculated on the trade, in the same ledger the trade is recorded in. Bolted on afterwards it becomes a monthly export, a formula somebody inherited, and an argument with an IB about whose number is right.
Exposure lands on the desk’s screen from the same feed the fills came through. A risk report built from an overnight export tells you what your book was, which is a different and much less useful thing than what it is.
Approvals, rejections, adjustments and logins written in one place against the operator who made them. Spread across six systems, answering a regulator becomes a week of assembling evidence instead of an afternoon of exporting it.
When a deposit has not reached a platform, the interesting question is which of the six is at fault. With one supplier that question is ours to answer rather than yours to referee between vendors who each say it is the other one.
The whole desk
Everything a CFD brokerage runs on, delivered as one platform and branded as yours from the first screen a client sees.
Questions about the build
What people ask when they are setting up a CFD desk rather than replacing part of one.
No, but it is the thing to start first. The jurisdiction you choose shapes which markets you can serve, which payment providers will take you, what your KYC has to collect and how the platform is configured — so beginning it late is what usually pushes a launch. We can run the platform work alongside an application in progress, and we also handle company formation and licensing if you would rather one supplier carried both. What we will not do is tell you a licence is optional.
You should. The LP agreements, merchant accounts and the rates you negotiated stay yours; we connect to them rather than reselling them with a margin on top, and money settles into your accounts rather than through ours. Several venues can be aggregated behind one bridge and several PSPs can sit behind one payment method with routing and fallback. Adding another later is a configuration, so a new market does not have to wait for a release.
Yes, and plenty of desks do — usually CRM and payments first, with the platform bridge and partner programme following. The modules are parts of one system rather than products stitched together, so adding the next one is switching it on rather than integrating it. The one thing worth deciding early is the client record and the ledger, because everything else hangs off those and moving them later is the only genuinely disruptive change.
Run the brokerage. The platform removes the re-keying, the reconciliation and most of the reporting, but it does not decide your markup, approve a large withdrawal, judge a borderline KYC case or watch the book on a volatile morning. Desks that launch well come in with someone owning dealing, someone owning compliance and someone owning finance, even if all three are the same person at the start.
Most of the work we do is migrations. Client records, trading accounts, verified documents, the partner tree and balances come across together, and the platform connections are set up alongside so clients are not asked to change how they trade in the same week they are asked to learn a new portal. Existing referral links can usually keep working too, which matters more than it sounds to partners who have spent years putting them into their own material.