Your brand, connected to the full broker stack
An MT5 White Label project needs more than a terminal carrying your name. Account structure, instrument specifications, market-data sources, execution connections and back-office workflows must fit the way your brokerage will operate.
TSG Server brings the platform and infrastructure work into one delivery brief. Whether you are launching a new environment or extending an existing one, the proposed configuration starts with your markets, access needs, regions and connected systems. White label MT5 scope is agreed against those requirements.
What your MT5 project can include
| Layer | Project deliverable | How to review it |
|---|---|---|
| Platform and branding | Agreed brand presentation, terminal options and environment configuration | Walk through the approved client access paths |
| Accounts and instruments | Group model, permissions and instrument specifications | Validate representative accounts, margin rules and instrument cases |
| Hosting topology | Production roles, access paths and capacity assumptions | Review the deployment map and a measured workload profile |
| Market data and connectivity | Symbol mapping, connection boundaries and feed/bridge dependencies | Check timestamps, market sessions and failure behaviour |
| CRM / API workflows | Agreed account and back-office integration scenarios | Trace a successful request, a rejection and a retry |
| Operations | Monitoring ownership, backup plan and handover record | Check escalation, restore evidence and change approval |
Optional components and third-party services are listed separately. Platform licensing and branding rights must match the actual delivery arrangement; the proposal records who provides and controls them.
Design around your markets and account model
MT5 supports a multi-asset platform model, but the instruments a brokerage can offer depend on its configuration, access, data, execution connectivity and commercial arrangements. Start with a defined instrument universe and sample contract specifications.
Record the required account behaviour and verify it in the proposed environment. A platform feature appearing in a catalogue does not mean it is enabled for every account or included in every implementation. The MT5 symbol guide shows the configuration evidence to gather.
A delivery sequence with visible acceptance points
- Discovery: record markets, account structure, client access, regions and existing dependencies.
- Architecture: agree component ownership, external connections, resource assumptions and recovery objectives.
- Configuration and integration: prepare the agreed environment and connected workflows.
- Validation: run account, instrument, connectivity, reporting and recovery checks with designated owners.
- Handover: review the configuration record, escalation route and outstanding actions before acceptance.
Use the MT5 deployment checklist to compare the promised scope with the evidence delivered.
Illustrative blueprint: add MT5 beside an existing brokerage
Illustrative project. This is a proposed architecture scenario, not a claimed customer deployment.
An existing brokerage introduces MT5 for an agreed set of instruments while retaining its current operating systems. Discovery identifies which CRM workflows are shared, how account identity is represented and where reporting remains platform-specific.
A staged trial validates an instrument sample, account permissions, account creation, reporting reconciliation and the escalation route for unavailable dependencies. The launch decision uses a written acceptance record. The topology can then be reviewed against measured activity rather than an assumed account-count-to-hardware formula.
MT5 White Label questions
What is included in an MT5 White Label?
The agreed environment can include branding, platform configuration, hosting and connected data, execution and CRM workstreams. TSG records the exact inclusions, external dependencies and operating responsibilities in the project scope.
Can I connect the platform to my existing CRM?
Share the CRM, available interfaces, rights and required account workflows. The integration plan should document authentication, supported actions, failure handling and how the result is reconciled.
How do I request an MT5 White Label quote?
Prepare the platform, hosting, connectivity, CRM and recovery requirements in the MT5 cost and project scope tool. Pricing follows a review of that scope.