Compare the complete service, not the trading screen
Both approaches need a working account journey: registration, verification, funding, spot trading, records and withdrawals. Ask which parts are supplied, which require configuration and which need separate development. A familiar trading interface says little about the work needed behind it. Use the same requirements list for each proposal so a lower headline price does not simply reflect a smaller scope.
Separate branding control from product control
Changing a logo, colour and domain is different from changing an order workflow or adding a new account type. Identify the decisions your business must control at launch and the changes it may need later. Ask who can make those changes, how they are tested and how they are priced. For a custom build, also agree code ownership, documentation and maintenance responsibilities. For a white label, establish the configuration boundary and how requests outside it are handled.
Evaluate the liquidity agreement alongside the technology
An exchange needs an agreed source of execution and a clear way to fund and settle it. Under Lumora’s qualifying white-label model, there is no platform licence fee in exchange for exclusive use of Lumora liquidity for client spot execution. That relationship belongs in the comparison from the start. Review execution pricing, supported markets, settlement, minimum commitments if any, and what happens during an interruption. A software decision and a liquidity decision can be commercially linked.
Build a total-cost view
A platform licence fee is one cost line. Compare implementation, bespoke work, hosting and support, vendor accounts, verification, custody, banking, liquidity and staffing where relevant. Establish which costs are fixed, which vary with activity and which are paid to third parties. Client markups create gross revenue before those costs; they are not the same as profit. Use realistic scenarios for your own client activity rather than treating a provider’s revenue illustration as a forecast.
Decide who operates the service
A white label does not remove the need for an operating team. Name the functions responsible for client review, funding exceptions, trading investigations, reconciliation and support. These can sit with your team, a scoped managed service or a shared arrangement. Any proposed use of a Lumora entity or regulatory arrangement needs its own assessment of products, clients, countries and responsibilities. Platform access alone does not authorise your business to provide a regulated service.
Choose against evidence and a realistic change plan
Before committing, request a demonstration using your most important client journeys and agree an acceptance plan for the actual deployment. Include stale prices, rejected payments, permission boundaries and provider interruptions alongside successful trades. Document the support boundary, release process, data access and exit arrangements. A white label may fit a business that can work within a defined platform and liquidity model. A custom build may fit requirements that justify owning more of the software and its ongoing operation. The best choice is the one whose responsibilities and costs your team can explain.