MT5 White Label Setup and Broker Infrastructure

This page covers the broker’s direct MetaQuotes licensing relationship and deployment of its own MT5 environment. MetaQuotes uses the wording “White Label licensing” on its broker page. Main Label, Full Licence and Full Server are market terms often used for this direct arrangement. The actual rights and limits come from the licence agreement, not the label used in a sales proposal.

A secondary White Label uses another licence holder’s infrastructure. Its permissions, branding, integrations and data access depend on the upstream arrangement. A direct licence establishes the broker’s own licensing relationship with MetaQuotes. These arrangements should not be treated as interchangeable.

Grey Label is an informal supplier term, generally used for a more limited branded or introducing arrangement under another operator. It is not a reliable description of a standard MetaQuotes licence. Verify the licence holder, contracting entity, server ownership, permissions and data access before assessing such an offer.

No. A supplier’s marketing page does not establish permission to create a new arrangement. Any offer requires current written confirmation of the relevant licence holder’s rights and the applicable approvals. EBS FinTech’s new MT5 setup service on this page is built around a direct licensing application.

Do not infer unlimited accounts, every module, a perpetual right to use the software or source code access from the words Full Licence or Full Server. Confirm licence capacity, included functions, recurring fees, restrictions and termination terms in the actual MetaQuotes agreement. Main Label is also an industry description rather than a promise of unrestricted use.

No. A MetaTrader licence grants software usage rights under its terms. It does not authorise regulated brokerage activity in a jurisdiction or replace the broker’s legal obligations. Company registration, financial authorisation and software approval are separate matters.

No. MetaQuotes decides approval and its licensing terms. EBS FinTech coordinates application preparation, technical deployment, integrations and ongoing support. The broker remains responsible for the accuracy of its application and its own business obligations.

Prepare company and ownership records, director and shareholder information, the relevant regulatory authorisations, business model, target markets, product scope, business website and a technical plan. MetaQuotes may request further evidence. The current applicant specific requirements must be confirmed during review; incorporation alone does not establish eligibility.

No. Company formation, a legal opinion, an existing banking relationship or a previous vendor introduction cannot guarantee MetaQuotes acceptance. Any regulatory authorisation must cover the intended activity. A legal opinion should not be assumed to substitute for a licence required by law or by MetaQuotes.

For the direct deployment described here, the licensed broker controls the server environment. EBS FinTech can deploy and manage it under an agreed technical service scope. Administrator and Manager accounts, permitted actions, security controls and handover responsibilities should be documented. Outsourcing maintenance does not by itself transfer the software licence.

Brand identity and server naming are part of project planning, subject to MetaQuotes approval and the available platform functions. Terminal branding, mobile distribution, domains and additional brands should be checked individually. A direct licence does not automatically permit every brand or distribution arrangement.

The proposal should identify platform licensing, initial technical setup, hosting, recurring maintenance, bridge or gateway services, CRM and other vendor charges. Liquidity deposits, trading costs and other provider requirements are separate unless expressly included. The quote should state who invoices each item, when billing starts and any minimum term.

Timelines depend on application and licence approval, data centre selection, server readiness and third party integrations. Once contracts and access are in place, we prepare a schedule for the LP, bridge, CRM and testing scope. A technical deployment estimate should not be presented as a guaranteed MetaQuotes approval timeline.

No. MetaQuotes no longer issues new MT4 broker server licences. We support existing MT4 environments with hosting, maintenance, troubleshooting and migration planning, subject to the client’s existing rights and authorised access.

Yes. We first review the topology, licence status, access, versions, connected systems, backups and known incidents. A handover plan defines the maintenance window, rollback steps, technical responsibilities and vendor contacts before any live changes.

No. The platforms have different data structures and trading behaviour. Accounts, balances, open positions, historical records, symbols, groups and CRM references need an agreed migration method and reconciliation. MT4 Expert Advisors and other custom programs also need a separate MT5 compatibility review.

Yes, where the existing MT4 licence and the approved MT5 setup permit it. We can plan coexistence architecture, shared operating procedures and a controlled transition. The process should specify how client accounts, reporting, support and each platform’s trading conditions are handled.

Yes. We design routing around the broker’s selected LP and bridge model, subject to technical compatibility and the relevant commercial agreements. Work can include symbol mapping, groups, markups, execution rules, reporting and recovery procedures. EBS FinTech provides the technical integration and does not act as the liquidity counterparty.

No. The appropriate connection may be an available native connection, gateway or a third party bridge, depending on the execution model, selected providers and required features. We confirm the route and compatible components before proposing additional software.

Yes. The technical scope can cover account creation, KYC status, deposits and withdrawals, reporting, rebates and IB workflows through the permitted APIs and vendor interfaces. Approval of client transactions and handling of client money remain with the broker and its approved payment providers.

The agreed acceptance plan covers account creation, permissions, symbol specifications, sessions, margin, quote flow, order routing, reports and connected CRM functions. Monitoring, backup restoration and failover behaviour are tested where supported. Any unresolved dependency should be recorded before acceptance.

Yes. Monitoring, alerting, planned updates, backups and incident procedures can form part of the maintenance package. Support hours, response targets, access requirements and escalation routes are defined in the service agreement. Resolution may depend on MetaQuotes, the LP, bridge or another vendor.

Send target regions, expected client activity, instruments, execution model, current application or licence status, preferred LP and bridge, CRM choice and desired launch date. For an existing environment, include the hosting location, integration list and known issues. Please do not send passwords or identity documents through the initial enquiry form.