Trading software product

MetaTrader MT4/MT5 Trading Bot Engine

A MetaTrader Trading Bot Engine for demo and client-controlled live workflows, with multiple strategy credentials, environment-aware order records, and MT5 or bridge-based connectivity paths.

MetaTrader Trading Bot Engine dashboard showing strategy controls and demo-mode status; live mode is separately configured.

Implementation scope

What this product implements

The hub models one MetaTrader account with multiple strategies. Each strategy receives an API key, while authenticated operators manage settings and review recorded orders.

The default path records a demo order without requiring a local terminal. When configured, the product offers separate paths for direct MT5 integration or a REST bridge that can submit a market-order request.

The dashboard includes configuration, strategy management, environment-aware order history, a test form, and a defined live gate.

Engineering choices

Clear boundaries in the application design

Demo mode is the default

The configuration defaults to paper or demo operation, with a separate live setting and credential requirements for client-controlled live use.

Connection methods are explicit

The implementation distinguishes direct MT5 terminal access from a bridge-based approach instead of assuming MT4 and MT5 have identical integration options.

Signals are attributable

Strategy API keys and stored order fields provide an application-level record of the platform environment and order identifier when one is available.

Validation approach

How the product can be reviewed

  • A dashboard test-signal workflow and environment-aware order history support review of defined application states.
  • Demo records can be used to review configuration and handoff expectations without making a financial-performance claim.

Current boundaries

Important limitations

  • The product supports demo and client-controlled live workflows where the required connection path, credentials, and live gate are configured. Demo mode is the default.
  • Direct MT5 use requires a local terminal. MT4 requires a bridge or Expert Advisor because it does not provide the same official Python path; live MT4 bridge validation remains a separate implementation step.
  • Demo verification checks defined application behaviour only. It does not validate a strategy's profitability, establish live execution results, or imply broker approval.
  • Sun Cluster provides software engineering, not investment advice, brokerage, custody, or discretionary trading services.
Open WhatsApp chat with Sun Cluster