MT5 White Label Setup

MT5 Server Setup Guide for New Forex Brokers

Learn how to set up an MT5 server for your forex brokerage, covering hosting, configuration, security, CRM integration, and testing.

FX Launch Pad•October 28, 2026•4 min read

An MT5 server isn't an app you install. It's the operational core of your brokerage: it holds client accounts, runs order execution, applies margin and risk rules, and connects to your liquidity.

Many new brokers meet it only through a sales demo, then discover what it takes to run one. This guide explains how the server works, the choices you'll make, and a setup sequence that avoids common problems. It's written for founders and managers who need to ask the right questions, whether a provider runs the infrastructure or you do.

It's general information, not legal or technical advice. For pricing, see our MT5 white label cost breakdown, and for platform choice, see our MT4 vs MT5 guide.

First: Which Path Are You On?

There are two ways to get an MT5 server environment, and who does what is very different.

	White label	Your own server license
Who runs the servers	Your provider	You or a technology partner
Hosting, patching, backups	Provider	You
Security and DDoS protection	Provider	You
What you configure	Branding, groups, symbols, markups, risk rules	Everything, including infrastructure
Staff you need	Operations and risk	Operations, risk, and server administrators
Time to launch	Weeks	Months
Control	Limited to what the provider exposes	Full

MetaQuotes states that MT5 is deployed on the operator's own infrastructure, and that it doesn't provide the platform as a hosted service or have access to your servers, accounts, or client history. In other words, running an MT5 server means the operational responsibility is yours, or your provider's.

Most new brokers should start with a white label, as we explain in our platform comparison. Even then, understand what the provider is running, because their setup is your uptime and your risk.

How an MT5 Server Environment Is Put Together

An MT5 environment is several servers working together, not one machine.

Component	What it does
Trade server (main)	The core: holds accounts, processes orders, and applies rules
Backup trade server(s)	Takes over if the main server fails
History server(s)	Stores price and trade history
Access servers	Connect client terminals to the trade server and absorb connection load
Gateway	Connects the platform to your liquidity providers or bridge
Administrator and Manager terminals	Administrator is for technical configuration, and Manager is for account and client management
APIs	Manager, Server, Gateway, and Report interfaces for connecting your CRM, risk tools, and reporting
Protection layer	Many setups place an anti-DDoS proxy between the trade servers and client-facing access nodes

Two points are worth remembering.

Access servers protect the trade server: Clients connect to access nodes, not to the core, so a connection surge or an attack hits the access layer first.

The APIs are how your business connects: MetaQuotes licenses server-side interfaces, including the Manager API, that work on the trading server itself, with all accounts, deals, and real-time events. That's the right route for CRM, back-office, and risk integrations.

See our CRM feature checklist and bridge integration guide.

Hosting Decisions

1. Dedicated servers, not retail VPS plans

A production broker environment needs dedicated infrastructure in a professional data centre. Retail forex VPS plans are fine for testing, but not for holding client accounts.

2. Location

Choose data centres based on where your liquidity providers and clients are. Brokers serving European clients and connecting to ECN liquidity often use London-area financial data centres, while those serving North American venues use New York-area ones. Latency to your liquidity matters as much as latency to clients.

3. Redundancy

Run a backup trade server configured like the main one, ideally in a different data centre, with data replicated continuously. A backup in the same rack protects against hardware failure but not against a facility problem.

4. Indicative hardware

Published sizing varies widely by source and age, so treat the figures below as a starting point only.

Item	What providers report
CPU	Server-class Intel Xeon, quad-core or higher in older guides, and 8 or more cores in newer production guidance
RAM	16 GB in older guides, and 32 GB or more in recent hosting guidance, with some vendors suggesting 64 GB for small production environments
Storage	Mirrored (RAID) SSD or NVMe, with no spinning disks for trade and history servers
Network	100 Mbps minimum and 1 Gbps recommended, in both directions
Operating system	64-bit Windows Server. MetaQuotes ended 32-bit support on 1 January 2024.

Real sizing depends on your number of accounts, symbols, concurrent connections, and plugins. Ask MetaQuotes' current requirements and your provider for sizing at your expected volume, and at two to three times that volume. MetaQuotes' guidance also advises against third-party time-synchronization software on trading servers.

Setup Sequence

Choose your path (white label or own license) and the jurisdiction rules you must meet
Select the hosting provider or technology partner, with the data-centre locations decided
Provision the servers: main, backup, history, and access, plus an admin workstation
Install and license the components according to MetaQuotes' procedures
Connect the gateway to your liquidity provider or bridge, and test the price feed
Configure groups, symbols, margin, and execution rules (see below)
Set up administrator roles and permissions
Connect the CRM and payments through the APIs, so account creation, deposits, and withdrawals flow correctly
Harden security and set up monitoring and backups
Test thoroughly, then soft-launch with internal accounts
Go live gradually and monitor closely

Configuration Essentials

Area	What to decide
Groups	Account types, base currencies, and jurisdictions. Each group carries its own rules.
Symbols	Naming, contract size, digits, swap, trading sessions, and which instruments to offer
Margin and leverage	Leverage tiers and stop-out levels, within your regulator's limits.
Execution	Execution modes and fill policies that match your liquidity and book model
Pricing	Spreads, markups, and commissions by group
Risk controls	Position and exposure limits, rejection rules, and price checks
Time and sessions	Server time zone, daylight-saving changes, and rollover timing
Reports	Statements, confirmations, and regulatory reports

Decide your book model (A-book, B-book, or hybrid) before configuring execution and risk rules, because it drives most of these settings. See our business plan guide.

Security and Resilience

Your server holds client money records and personal data, so treat it as a regulated system.

Restrict administrative access to approved IP addresses or a VPN, with multi-factor authentication
Harden remote access, including remote desktop, and disable what you don't use
Separate administration from client access at the network level
Use role-based permissions, so staff see and change only what they need
Log administrative actions for audit
Test backups by restoring them, not only by taking them
Practise failover so a switch to the backup server isn't a first-time event
Monitor everything with alerts that reach a person who can act
Plan updates carefully, testing new builds on a staging environment before production
Vet plugins and connectors. Third-party tools that read or place trades can become a security risk, so never share administrator credentials, and review each integration

For EU-regulated firms, these disciplines also line up with operational resilience rules such as DORA.

Testing and Go-Live Checklist

[ ] Orders tested in every execution mode and for each account group
[ ] Price feed verified against your liquidity provider
[ ] Margin calls, stop-outs, and negative-balance handling tested
[ ] Deposits, withdrawals, and credits tested end-to-end with the CRM
[ ] Daylight-saving and rollover behaviour checked
[ ] Load tested with realistic concurrent connections
[ ] Failover to the backup server rehearsed
[ ] A full backup restored successfully
[ ] Administrator access and permissions reviewed
[ ] Reports and statements checked for accuracy
[ ] Soft launch with internal or test accounts before real clients

Common Mistakes

Treating the server as an installation, not an operation
Using a retail VPS for production
Putting main and backup servers in the same facility
Sizing for today's accounts, not for volatility peaks
Configuring execution before deciding the book model
Leaving administrator access open to the internet
Never testing a backup restore or a failover
Connecting the CRM and payments late, so balances drift
Ignoring daylight-saving and rollover settings
Assuming a white label provider handles everything, including your risk rules

For the wider pattern, see our platform setup mistakes guide.

What's New in 2026

64-bit only: MetaQuotes ended 32-bit support on 1 January 2024, so current builds need 64-bit Windows Server.
MT5 is the only realistic platform for new brokers: since new MT4 licences stopped in 2022.
Operational resilience is a regulatory topic: EU firms are subject to DORA, and partners increasingly ask for continuity and incident evidence.
API-first integration: is expected, with CRM, risk, and payments connected in real time.
Third-party connectors are multiplying: which makes vetting and access control more important.

About FX Launch Pad

When a founder asks about the server, our first question is who will operate it at 3 a.m. on a news day. The architecture is the easy part. The harder part is ownership of monitoring, failover, security, and changes. We plan the server environment together with the bridge, CRM, and payments, and we test the failure cases before real clients are on it.

If you're planning your MT5 setup and want to check the architecture and responsibilities before you commit, book a free consultation and we'll go through it with you.

Frequently Asked Questions

Q-1 What servers does an MT5 broker setup need?

Ans- At minimum, a main trade server, a backup trade server, a history server, and one or more access servers, plus a gateway to your liquidity and administrator and manager terminals. White label providers run these for you, while an own-license setup requires you or a partner to run them.

Q-2 Can I run an MT5 broker server on a VPS?

Ans- Retail VPS plans are fine for testing, but production environments holding client accounts generally need dedicated servers in a professional data centre, with redundancy across facilities.

Q-3 What are the hardware requirements for an MT5 server?

Ans- Published guidance varies, from 16 GB RAM in older guides to 32 GB or more in recent ones, with server-class CPUs, mirrored SSD or NVMe storage, and 100 Mbps to 1 Gbps networking on 64-bit Windows Server. Get current sizing from MetaQuotes and your provider for your expected volume.

Q-4 Does MetaQuotes manage my MT5 server?

Ans- No. MetaQuotes states that MT5 runs on the operator's own infrastructure and that it doesn't provide a hosted service or have access to your servers, accounts, or client history.

Q-5 How do I connect my CRM to the MT5 server?

Ans- Through MetaQuotes' server-side interfaces, such as the Manager API, which work on the trading server with real-time access to accounts and deals. That's the route for account creation, balances, and risk and reporting integrations.

Keep Reading