Skip to main content

Technical Requirements

Below you will find the necessary permissions that should be granted in the MT Manager API console to establish a connection between our system and your trading platform.

This document also outlines the technical requirements for the hardware and software necessary to install our frontend and backend components.

Whitelist of IPs​

When we receive the credentials for the connection, we will provide the list of our IPs that we will use to connect to your MT4/MT5 servers.

⚠️ If frontend/backend is installed in Brokerpilot's cloud, please add IPs provided to your whitelist.

MT5 Connection and Permission Requirements​

To integrate with MT5, the following are the minimum requirements for our system to go live:

  • Export your server settings to a .json file (see Picture No. 3).
  • The export must include:
    • CommonConfig
    • TradeServer
    • OrdersRange
    • DealsRange

⚠️ Please ensure you remove any sensitive network configurations or IP addresses from the .json file before sending it to us.

Example .json file settings​

server-mode

  • Picture No.2 – Export Settings

  • Picture No.3 – Context Menu for Export

Picture References​

  • Picture No.4 – MT5 Permissions
    Required checkboxes are highlighted in red frames.

MT4 Connection Requirements​

For MT4:

  • Checking "Connections" is optional.

  • You will have access to groups of accounts that you specify in the Manager interface.

  • Picture No.5 – MT4 Permissions

Additional Permissions​

If you would like to utilize triggers that allow direct control of leverage and spreads inside the MT platforms, Admin permissions are required along with a few additional checkboxes.

  • Picture No.5 – Additional Permissions
    Required checkboxes are highlighted in red frames.

Installation Information​

Your installation option is self-hosting. You are required to provide us with hardware and software specified below.

Server Configuration Requirements

🖥️ Backend: Windows Server​

1 Server​

RequirementMinimumRecommended
CPU1 Core, 2 Threads2 Cores, 4 Threads
RAM24 GB33 GB
Storage100 GB100 GB

2 Servers​

RequirementMinimumRecommended
CPU2 Cores, 4 Threads4 Cores, 8 Threads
RAM34 GB48–64 GB
Storage100 GB150 GB

5+ Servers​

RequirementMinimumRecommended
CPU5 Cores, 10 Threads6 Cores, 12 Threads
RAM64 GB80–128 GB
Storage140 GB150 GB

🌐 Frontend: Linux Server (LTS)​

1 / 2 / 5+ Servers​

RequirementMinimumRecommended
CPU1 Core, 2 Threads2 Cores, 4 Threads
RAM4 GB4 GB
Storage20 GB40 GB

Hotplug Capable: Support for adding 4 CPU cores and 8–16 GB RAM and Storage.

🗃️ Database: RDS or Linux Ubuntu LTS + PostgreSQL​

1 Server​

RequirementMinimumRecommended
CPU2 Cores, 4 Threads3 Cores, 6 Threads
RAM4 GB8 GB
Storage200 GB200 GB

2 Servers​

RequirementMinimumRecommended
CPU2 Cores, 4 Threads3 Cores, 6 Threads
RAM4 GB8 GB
Storage400 GB600 GB

5+ Servers​

RequirementMinimumRecommended
CPU2 Cores, 4 Threads3 Cores, 6 Threads
RAM4 GB8 GB
Storage1 TB1 TB

⚠️ We expect the following rights for PostgreSQL: read, write, delete, create tables, modify tables, drop tables, create databases, drop databases, create drop schemas.

Server Connection Diagram

🔌 Brokerpilot Port & Connection Requirements

🚪 Required Open Ports​

Backend Server​

  • Ports to open:
    14500, 3389, 5986, 10050, 10051

Frontend Server​

  • Ports to open:
    22, 80, 443, 7701, 10050, 10051

Database Server​

  • Ports to open:
    5432, 10050, 10051

🌐 Connection Options​

Option 1: Brokerpilot Hosts DNS​

  • A DNS record in the format of brokername.brokerpilot.net is created by the Brokerpilot team.
  • This DNS points to the Brokerpilot server.
  • Brokerpilot sets up and configures Nginx for the frontend server.
  • ⚠️ If ports 80 and 443 are closed to the internet, obtaining an SSL certificate for brokername.brokerpilot.net may not be possible.

Option 2: Client Hosts DNS​

  • The client creates the DNS record on their own DNS server.
  • The client sets up the SSL connection on their own web server.
  • The Brokerpilot team provides the location path and proxy_pass configuration.

Option 3: SSH Tunnel (SSL-Friendly)​

  • A DNS record in the format brokername.brokerpilot.net is created by the Brokerpilot team.
  • The DNS points to the Brokerpilot server.
  • All frontend traffic is tunneled through SSH to the frontend server.
  • ✅ No issues with SSL certificate issuance in this configuration.