Skip to Content

System & Hardware Requirements

OTX, a white-label App under your brand with seamless integration to your MT5 trading server. OTX contains frontend for both Android and iOS App and backend service to provide App functions needed by the App. OTX backend service will be deployed on your own hardware, thus we have no access to your servers, accounts, or your clients' trading history.

System OverviewOS & Hardware RequirementsNetwork ConfigurationPre-Installation RequirementsSystem CompatibilityStaged Deployment RecommendationConfiguration ManagementDomain ManagementTroubleshooting

System Overview

The OTX backend service is a set of server-based applications that connect to your MT5 servers to support all App functionalities. It requires:

  • Valid license
  • Valid domain name and SSL cert
  • MT5 server access through manager API
  • SMTP configuration for email functionality

Below are the detailed requirements for installation:

System Architecture


Option 1: Single-server setup (all-in-one)

Option 2: Distributed setup (separate web/database servers)

OS & Hardware Requirements

Supported OS:
  • Windows Server 2016/2019/2022 (64-bit) or above.​
Hardware Requirements:

Component

Minimum Spec

Recommended Spec

CPU

Quad-core, 2.5 GHz

Higher core count

RAM

8 GB

16 GB (large-scale)

Storage

200 GB SSD

+50 GB for logs/DB, and temporary files

Network

10 Mbps up/down

Low-latency connection

Network Configuration

The OTX backend service requires specific network access for communication with the MT5 server, email notifications, and the App:

Firewall Rules:

Service

Port/Direction

Notes  

MT5 API

Outbound: 443

Access to MT5 server URL (e.g., mt5.example.com) on the specified port
(default is often 443 for secure connections).

SMTP

Outbound: 587/465

TLS/SSL for email alerts

OTX API

Inbound: 2096

Mobile app communication

Critical:
  • Static IP Address or Fully Qualified Domain Name (FQDN) for consistent communication.
  • Domain name has a wildcard SSL certification
  • Verify that server allows outbound HTTPS traffic (port 443) for license validation and updates.
  • Verify that server allows inbound HTTPS traffic (port 2096) for app connect

Pre-Installation Requirements

Before running the installer, gather the following information and resources:

License File:
  • A valid license file is required for installation. This will be sent to you via email upon purchase.
  • Store the license file to an accessible location on your server.
MT5 Server Credentials:
  • Gather the following details before installation:
    • MT5 server URL (Manager Host)
    • Manager Login and Password
    • Note: Verify these credentials have sufficient permissions for account management.
  • Contact your MT5 server administrator or broker to obtain these credentials if you don’t already have them.
  • Verify that the credentials have the necessary permissions to manage accounts via the OTX Controller.
SMTP Configuration:
  • Prepare the following SMTP details:
    • SMTP Host/Port (e.g., smtp.yourdomain.com:587).
    • SMTP From email address (e.g., noreply@yourdomain.com).
    • SMTP Username and Password (e.g., the email account credentials or an app-specific password for services like Gmail).
  • Authorized to send emails and that the server allows outbound connections on the specified port.
Administrator Privileges:
  • You must have administrator/root access to the server to install the software and configure system settings.

Additional Notes

System Compatibility

The OTX installation process is designed to be non-disruptive and will not interfere with other applications running on the same system. However, when installing OTX on a server with existing production applications, we strongly recommend performing a full system backup of critical data prior to installation.

Staged Deployment Recommendation

1.    Test Environment
  • Use a non-production MT5 server
  • Simply input test MT5 server credentials during installation
  • Configure the DNS: ”otx.yourdomain.com” to point to the test server's public IP address
  • Validate:
    • Mobile app connection (port 2096).
    • Backend login
    • MT5 API/SMTP functionality
2.    Production Migration
  • After successful testing:
    • Uninstall OTX from the test server
    • Perform fresh installation on production server with live MT5 credentials
    • Reconfigure DNS: ”otx.yourdomain.com” to point to the production server's public IP address
  • Ensures clean deployment without test environment artifacts

Configuration Management

The installation wizard allows:

  • Step-back functionality to correct input errors
  • Configuration restart at any point
  • Real-time validation of critical parameters (MT5 connectivity, SMTP functionality)
  • Post-installation configuration updates through admin console

Domain Management

OTX requires dedicated subdomain configuration:

  • Single domain binding per installation
  • SSL must cover:
    • Primary domain (yourdomain.com)
    • OTX subdomain (otx.yourdomain.com)
  • DNS propagation should be verified before testing

Troubleshooting

Common resolution paths:

  • For installation errors: Restart setup process
  • For MT5 connection failures: Re-enter manager credentials
  • For domain issues: Verify DNS records and SSL binding
  • For mobile app connectivity: Check firewall rules for API ports

This staged approach minimizes risk to production systems while ensuring all components are properly validated before go-live. The installation process includes validation checks for each critical dependency (MT5 access, SMTP, license verification) to prevent configuration errors.