The white-label pitch always sounds the same: launch in weeks, full feature set, your brand on top. And it is mostly true — getting a branded platform live has never been easier. The hard part is what happens in month six, when your platform stops being a checklist and starts being your business.
We run our own brokerage on the same stack we license, so we have lived both sides of this decision. Here are the questions we would ask any vendor — including us.
1. Was this stack ever run in production by its vendor?
Most platform vendors have never operated a brokerage. Their software is shaped by feature requests, not by margin calls at 3 a.m. Ask the vendor: do you run this yourself, with real users and real money? The difference shows up in the boring places — reconciliation, liquidation edge cases, what happens to an order when the price feed hiccups.
2. Can you take one module, or is it all-or-nothing?
Turnkey suites are efficient until you outgrow one part of them. Then you discover the CRM, the platform, the liquidity and the risk engine are welded together, and replacing one means replacing everything. Modularity is not a buzzword — it is the difference between an upgrade and a migration. You should be able to embed a terminal over your existing backend, or take a risk engine without the front-end, and keep your users and data with you.
3. Where does the margin math live?
If margin, PnL and liquidation are computed in the client, every desktop, mobile and API user can see a different number — and one of them will screenshot it. Server-side risk with a single source of truth is table stakes for anything beyond a demo. Bonus points: a liquidation preview computed before the order leaves the client.
4. What happens on mobile?
Retail flow is mobile-first everywhere that matters — LATAM, Southeast Asia, MENA. A desktop platform with a squeezed-down responsive mode is not a mobile strategy. Ask to see the actual mobile experience for the workflows that earn you money: deposit, first trade, position management.
5. How do deposits actually arrive?
Global card rails ignore or overcharge exactly the geographies where retail brokers grow. If your users pay with PIX, QRIS or local bank transfers, the payments layer is not an integration detail — it is the top of your funnel. One status contract across fiat, crypto and local methods saves months of reconciliation pain.
6. What is the AI story — beyond a chatbot?
Every platform added a support chatbot in 2024. The interesting question in 2026 is whether AI can touch the trading loop safely: read the chart, explain the news, prepare an order — and still leave the final confirm to the human, with risk limits enforced server-side where no prompt can override them. If the vendor's AI story has no guardrails story, it is a demo, not a product.
7. What do you actually get to see before you sign?
Slides are free. Working software is evidence. If a vendor cannot show you the platform live — dense with data, under real load, on a stand you can click through — assume the gap between the deck and the build is wide.
The short version
| Question | Weak answer | Strong answer |
|---|---|---|
| Run in production? | "Our clients run it" | Vendor operates it daily |
| Modular? | Full suite only | Any module, your data stays yours |
| Risk engine | Client-side math | Server-authoritative, previewed pre-trade |
| Mobile | Responsive desktop | Purpose-built mobile UX |
| Payments | Card gateway list | Local methods + crypto, one status contract |
| AI | Support chatbot | Agent with server-side guardrails |
| Proof | Slide deck | Live stand, real interfaces |
That last row is the one we would push hardest on. It is also why every product page on this site opens with a working interface instead of an illustration — and why our demos are thirty minutes with an engineer, not a sales deck.