The MetaTrader 5 CRM.
Beyond the trading screen.

The operational layer around MT5

A trading platform records accounts and trades. A broker CRM connects those records to client relationships, staff responsibility, verification, support and financial workflows. TGS CRM gives operators a shared environment with role-based permissions and separate broker connections.

The current production package includes client records, tasks and contact history, trader and partner portals, KYC document review, 2FA, account operations and analytics. These are workflow tools; enabling a feature does not automatically configure an external provider or approve a client.

A connected set of broker modules

Multi-account oversight, approved trading batches and copy trading sit alongside client operations. Payment adapters require provider credentials and configuration. MT5 balance operations are tracked separately from the receipt of external payments and from bank payouts.

• Client and account records, documents, tasks and support
• Trader portal, partner portal and IB workflows
• MAM allocation and copy-trading strategies
• Payment intake, balance operations and financial reconciliation
• Staff roles, 2FA and audit records

Integration and deployment

The CRM connects through authorized MT5 Web API access. Each connection has its own endpoint, exact group and manager credentials. Hosting requires PHP 8.3 or later, supported extensions, HTTPS and private storage outside the public directory. Background processing needs a configured CLI worker or scheduler.

Before production, verify API permissions, client access, payment callbacks, reconciliation and backup recovery. Administrative commands and financial changes use preparation and confirmation workflows; uncertain results require investigation. Scope the CRM and server deployment together so responsibility for every integration is clear.