MT5 White Label Cost Breakdown: A Component-by-Component Model
Costs attach to components, and components attach to owners. A component-based model shows who bills what, on what basis and how it scales, which is what you need to compare two white label quotes.
Define the component list
Platform and setup, hosting, support, CRM, payment integration, liquidity bridge, branding and website, compliance tooling, staffing. Add rows for anything your architecture needs. See the turnkey component guide.
Record owner and billing basis
For each component record who invoices it (provider, third party or you), whether it is one-off or recurring, and what it scales with: fixed, per user, per volume or per feature.
Platform component
The listed white label setups run from $2,200 to $2,500 per month, subject to confirmation, for the platform setup.
Infrastructure and operations
Include hosting, backups, monitoring and incident response with the response times in the SLA. See our MT5 hosting guide.
Integrations
Include set-up and recurring costs for CRM, payments and the bridge, plus testing effort. Each has third-party dependencies; see our liquidity guide and PSP guide.
Compare two quotes
Normalise both quotes into the same component table and mark gaps. Ask for pricing on every gap. For the grey label view, see the grey label cost model.
Cost drivers worth tracking
- Number of active clients and accounts.
- Number of integrations and their volumes.
- Support tickets per client.
- Hosting load by plugin.
Track the drivers monthly so you can explain changes in the bill and forecast the next period.
Component model and billing basis
List each component with its owner, billing basis (monthly, per unit, per transaction, one-off), unit price, minimum and escalator. Components typically include platform and licence, infrastructure and hosting, bridge and liquidity connection, CRM and Manager API, payment integrations, monitoring and backups, support and training.
A component model lets you compare vendors on the same structure and see where a quote is silent. Silent components are either included, excluded or forgotten, and each must be resolved in writing.
Total cost comparison template
| Component | Vendor A year 1 | Vendor A year 3 | Vendor B year 1 | Vendor B year 3 |
|---|---|---|---|---|
| Platform | ||||
| Infrastructure | ||||
| Bridge | ||||
| CRM and API | ||||
| Payments | ||||
| Monitoring | ||||
| Support | ||||
| One-off items | ||||
| Total |
Compute the totals for each growth scenario and look at where each vendor’s cost steps.
Infrastructure and operations
Infrastructure costs depend on load, redundancy and monitoring. Request the sizing assumptions: expected accounts, concurrent sessions, orders per second, history retention. Ask how capacity scales and what the price steps are.
Ask for service levels: availability target, recovery time and recovery point objectives, maintenance windows and credits for breach. Costs that look low often reflect weaker service levels.
Integration cost drivers
Integration cost scales with number of systems, number of workflows, test depth and ownership of maintenance. Request a work breakdown with effort estimates and assumptions. Compare effort per workflow across vendors.
Track drivers monthly after launch (accounts, integrations, tickets, hosting load) so that changes in the bill can be explained and forecast.
Contract mechanics
Review price escalators, minimum terms, termination fees, change request rates and the definition of included support. Agree a change rate card in advance. See our white label cost guide for scenario modelling.
Worked example: normalising two vendor quotes
Vendor X lists a platform fee, infrastructure and bridge as separate monthly items and charges integration hourly. Vendor Y lists a bundled monthly fee and fixed-price integration. Normalised into the component model, Y’s bundle is split by the vendor’s own breakdown and X’s hourly rates are converted using the workflow effort estimates.
The normalised totals at twelve and thirty-six months, under the expected and high growth scenarios, show X cheaper at low volume and Y cheaper beyond a crossover point. The crossover client count becomes a decision input.
Service levels and credits
Compare service levels alongside price. A lower price with weaker availability targets and no credits can cost more after incidents. Translate downtime into cost using your own revenue per hour and incident handling cost.
Write remedies into the contract and track actual performance monthly.
Negotiation using the component model
The component model supports negotiation. Identify components where vendors differ widely and ask the higher-priced vendor to explain the difference. Ask for bundled discounts, price protection on stepped components and caps on escalators. Trade term length against unit price only after calculating the effect on exit cost.
Keep the model with notes on each concession, so that the final contract reflects what was agreed and later reviews can check compliance.
Frequently asked questions
Why use a component model?
To compare quotes on identical structure and expose silent components.
What service levels should I ask for?
Availability, recovery time and point objectives, maintenance windows and remedies.
How do I track costs after launch?
Monitor cost drivers monthly and compare actuals with the model.
What contract terms affect cost?
Escalators, minimum terms, termination fees and change rates.