Plan a branded MT4 environment around the trading tools, account operations and integrations your brokerage already depends on. TGS scopes configuration, connectivity and technical support around an eligible platform arrangement.
Review the Expert Advisors, custom indicators and terminal workflows used by your clients. MT4 uses MQL4, so a move to another platform requires its own compatibility assessment. Test representative strategies in a non-production environment before changing account settings.
Document client groups, supported instruments, commissions, swaps and access responsibilities. Separate administrative changes from day-to-day account operations and define who approves a change to live trading conditions.
Match source symbols to broker-facing names, precision and contract specifications. Check quote timestamps, sessions and stale-price handling. A working price feed is a separate dependency from the path used to execute a trade.
Map the current account-opening, balance-operation and reporting workflows to the interfaces available under the platform arrangement. MT4 exposes several APIs; access to an individual interface must be confirmed before designing an integration.
Plan runtime capacity, restricted operational access, backups and a recovery procedure. Test terminal connections and quote delivery after a restore, rather than treating a successful file backup as proof of service recovery.
Agree which existing groups, users and integrations must be preserved. Use a documented validation checklist, a reversible change window and clear escalation ownership for issues found after handover.
An MT4 project is usually driven by an existing client base or a dependency on MT4-specific tools. Start by listing the workflows that must remain compatible: terminal access, MQL4 programs, reporting exports, account administration and upstream connectivity.
MetaQuotes states that new MT4 platform licenses are no longer available for purchase. An MT4 requirement therefore needs an assessment of the permitted existing arrangement and the rights available to the parties involved. TGS is an independent technology provider; platform rights and permitted use must be confirmed before implementation.
Capture the current symbol catalogue, account-group rules and operational permissions. Test a sample of account creation, quote delivery, trade and balance operations, reporting and recovery. Record expected results so the team can distinguish configuration differences from faults.
For a future MT5 transition, assess tools and data separately. Moving a brand or CRM connection does not automatically migrate an MQL4 strategy, an account history or a trading configuration. Use the MT4 versus MT5 guide to identify each dependency.
MetaQuotes says new MT4 platform licenses are no longer sold. Availability of an MT4 white label arrangement must be checked against existing rights, vendor terms and the proposed operating model.
A platform migration requires a separate compatibility review. Do not assume an MQL4 Expert Advisor or indicator will run unchanged in an MT5 environment.
Branding, market data, execution connectivity and CRM are separate project components. The proposal should state which components are included and which require third-party arrangements.
Send the current operating model, MT4 dependencies, required instruments, CRM and reporting workflows, expected hosting scope and the permitted platform arrangement. Avoid sending passwords in an initial enquiry.
MetaQuotes: MT4 APIs and licensing
Reviewed 30 September 2026. Deployment requirements depend on the agreed platform arrangement and supported interfaces.
Share your target platform, current systems and required workflows with the TGS technical team.
