English 
Türkçe 
Español 
Français 
Deutsch 
Português 
中文 
العربية 
Русский 
日本語 MT5 Support for Brokers: MetaTrader 5 Server and Platform Operations
MetaQuotes licenses MetaTrader 5, but your brokerage runs, configures and supports it. FXSUPPORT handles the day-to-day MT5 server work so your dealing and IT teams can focus on clients.
MT5 support for brokers: trade, history, access and backup servers, daily MT5 server tasks, netting vs hedging, Ultency and bridges, APIs and MT4 migration.
What MT5 support for brokers covers, and why MetaQuotes leaves it to you
MT5 support covers everything needed to keep a licensed MetaTrader 5 platform trading correctly every day: server health, configuration, connectivity, data, plugins and incident response. It is a broker-side job because MetaQuotes sells the platform but does not operate it for you.
MetaQuotes states this directly on its broker page:
“You independently deploy our software on your own hardware, as well as maintain your server infrastructure and fully control support and administration. We do not offer SaaS or other similar solutions which would permit even partial external management or third-party control over your company's operations, and thus we have no access to your servers, accounts, or your clients' trading history.”— MetaTrader 5 for Brokers, MetaQuotes (accessed October 2026)
Running MT5 therefore takes four kinds of work:
- Infrastructure: servers, networks, access points, backups, monitoring and security hardening.
- Platform administration: symbols, groups, trading sessions, swaps, margin settings, manager permissions and reports.
- Connectivity: data feeds, gateways, Ultency or third-party bridges such as PrimeXM XCore, oneZero Hub or Match-Trade, and FIX API links.
- Development and integration: server and manager plugins, Manager API and Web API integrations with your CRM, client portal and back office.
FXSUPPORT provides outsourced MT5 technical support and managed operations for brokers and prop firms: setup, updates, backups, configuration, log monitoring and bridge configuration, plus plugin development, risk operations and MT4 to MT5 migration. If you run both platforms, our MetaTrader support overview and MT4 support page cover the shared ground.
MT5 platform components: what each server does and what support involves
A MetaTrader 5 platform is a set of separate server roles, not one machine. MetaQuotes describes MT5 as “based on a distributed architecture, where different functions are performed on different servers,” which lets brokers add servers to increase performance or reduce load on individual components.
The table below maps the main components named in MetaQuotes' public materials to the support work each one creates. The exact set you have depends on your licence: MetaQuotes lists Entry (1,000 real accounts, with a main trade server serving real and demo accounts), Standard (25,000 real accounts, with distributed trade processing) and Enterprise (200,000 real accounts, with “a complete set of all available system components”).
| Component | Role (per MetaQuotes public materials) | What MT5 support involves |
|---|---|---|
| Main trade server | Core trade processing; on the Entry licence it services both real and demo accounts. | Configuration of symbols, groups, sessions and margin; restarts and updates in maintenance windows; database and log checks; plugin loading. |
| Additional trade servers | Distributed trade processing within one system (Standard and Enterprise licences). | Splitting load across servers, keeping configuration consistent, monitoring each node. |
| History server | Stores and serves price history; the Server API can extend both the trade server and the history server. | Checking quote and bar history, fixing gaps or spikes, handling splits and reverse splits of tick and bar history. |
| Access servers | Entry points that client terminals connect to; trade servers “can be hidden behind multiple access points.” The MT5 web terminal runs on the broker's access server. | Placing access points near clients, load distribution, DDoS exposure, certificate and connectivity checks, web terminal availability. |
| Backup server | Continuously synchronises with the primary trade server and can take over if the main site fails (Finance Magnates, June 2026). | Verifying sync, documenting and testing the failover procedure, choosing a separate site or country. |
| Gateways and Ultency | Connect MT5 to liquidity providers and exchanges; Ultency is MetaQuotes' built-in aggregation and matching engine. | Gateway setup and updates, routing rules, quote quality checks, rejected-order investigation. |
| Administrator and Manager terminals | Desktop tools for configuring the platform and for role-based staff such as administrators, dealers, accountants and risk managers. | Permission design, manager accounts, audit of who can change what. |
| APIs (Server, Manager, Gateway, Report, Web) | Extend the platform and integrate it with websites, CRM, trading and post-trading systems. | Building and maintaining plugins and integrations, testing them after every platform update. |
Client terminals (desktop / mobile / web)
|
+-----------+-----------+
| | |
Access srv Access srv Access srv (near clients, absorb traffic)
| | |
+-----------+-----------+
|
Main trade server <--- sync ---> Backup server (other site)
| |
History server Gateways / Ultency / bridge
|
Liquidity providers, exchanges, data feeds
MetaQuotes also sells hosted access servers (Equinix LD4, NY4 and HK1 among other locations, per its May 2022 announcement) and, according to Finance Magnates in June 2026, an Amsterdam location for MT5 backup servers, so a broker with a main server in London can keep its backup in another country.
Common MT5 server tasks: daily, weekly and event-driven
Most MT5 support work is routine; the expensive problems come from routine work that was skipped. A good plan names who does each task and when.
| Frequency | Task | Why it matters |
|---|---|---|
| Continuous | Server, access point and gateway monitoring; log monitoring for errors and disconnections | Catches feed stalls, gateway drops and resource problems before clients notice. |
| Daily | Backup verification; check of quote flow and history; review of rejected or requoted orders | Backups that are never tested are not backups; bad ticks become client disputes. |
| Daily (end of day) | End-of-day and evening risk reports; swap and rollover checks; toxic-flow lists | Dealing and risk teams start the next day with clean numbers. |
| Weekly | Review of manager permissions, new groups and symbol changes; disk and database growth | Stops configuration drift and unexpected storage problems. |
| Event-driven | Daylight saving time changes and bank holidays: session and schedule updates | Wrong sessions cause trading outside market hours or blocked trading. |
| Event-driven | New symbols, contract changes, stock splits and corporate actions | MT5 supports corporate actions and history splits, but someone has to run them correctly. |
| Event-driven | MetaQuotes platform builds, plugin and gateway updates | Updates should be staged, tested against your plugins and rolled back if needed. |
| Event-driven | Incidents: outages, DDoS, feed or bridge failure, mass margin calls | A written runbook shortens recovery time. |
Example: a daylight saving time change done properly.
- List every symbol and group whose sessions depend on a market that changes its clocks (US, UK, EU, Australia) and the dates of each change.
- Confirm with your liquidity providers and data feed how their trading and quote sessions will move.
- Prepare the new quote and trade session times, plus any holiday schedules for the same weeks.
- Apply the changes in a planned window and check that swaps and rollover times still match your policy.
- Watch the first session open for missing quotes and rejected orders, then notify dealing and client support.
For server-level failures, see our forex server troubleshooting guide and the list of common MetaTrader errors.
Netting vs hedging on MT5: a configuration decision with support consequences
MT5 supports two position accounting systems, netting and hedging, and the broker sets which one each account uses. That choice changes how positions close, how margin is calculated and how your plugins, reports and bridges must behave.
“Two position accounting systems are supported in the trading platform: Netting and Hedging. The system used depends on the account and is set by the broker.”— MetaTrader 5 Help, MetaQuotes (accessed October 2026)
Hedging was added to MT5 in April 2016 as a second system similar to the MT4 model, which is why older articles still call MT5 “netting-only”.
| Aspect | Netting | Hedging |
|---|---|---|
| Positions per symbol | One common position per symbol | Multiple positions per symbol, including opposite directions |
| Opposite deal | Reduces, closes or reverses the existing position | Opens a separate position; a position cannot be reversed |
| Closing | Opposite deal of the same symbol and volume | Explicit close of the specific position |
| Margin | Calculated on the net position | “Hedged margin” calculation is available |
| Typical use | Exchange-traded instruments such as futures and stocks | Retail forex and CFD accounts used to the MT4 model |
| Support impact | Simpler exposure; reporting by symbol | Position-level reporting; MT4-style plugins and EAs migrate more easily |
Practical support points we check on every MT5 platform:
- Groups are set to the accounting system the business model expects, and migrated MT4 clients land on hedging groups unless decided otherwise.
- Server plugins, the bridge and risk reports handle positions the right way for each mode; a plugin written for netting can miscount exposure on hedging accounts.
Not sure your MT5 groups, gateways and backups are set up right?
Send us a short description of your MT5 platform. We will review it and reply with the issues we would fix first, free of charge.
Request a free technical review WhatsApp TelegramUltency, gateways and third-party bridges: how MT5 reaches liquidity
MT5 reaches liquidity providers and exchanges through gateways: MetaQuotes' own Ultency matching engine, MetaQuotes gateways, or a third-party bridge running alongside the platform. Each option shifts which configuration lives inside MT5 and which lives in an external system.
MetaQuotes describes Ultency as a built-in solution for liquidity aggregation and order matching, with access to “more than 30 liquidity providers”. According to MetaQuotes' Ultency page, brokers can assign liquidity providers per instrument, set providers and markups per client or group, route between A-Book, B-Book and C-Book execution (partial hedge, overhedge, reverse hedge), filter incoming prices against other providers and define automatic coverage rules. Instrument and session parameters are configured once in MT5.
Third-party bridges remain common. PrimeXM describes its “MT4 Bridge and MT5 Gateway” as “a powerful yet light-weight server side plugin which connects MT4 and MT5 platforms to the client's XCore order management and reporting engine.” oneZero says its Hub connects to customers through front-end platforms “including MetaTrader 4/5”, and Match-Trade offers an MT4/MT5 bridge with its own risk management system.
| Option | Where routing and aggregation live | Support focus |
|---|---|---|
| Ultency (MetaQuotes) | Inside the MT5 ecosystem, configured from the platform | Provider selection per symbol and group, A/B/C-Book rules, price filters, coverage accounts |
| PrimeXM XCore | External XCore engine, connected through the MT5 Gateway plugin | Gateway plugin versions, symbol mapping, XCore routing and reports |
| oneZero Hub | External oneZero Hub, connected to MT5 | Symbol mapping, pricing and risk rules in the Hub, MT5 side connection health |
| Match-Trade bridge | External bridge with Match-Trade risk management | Bridge configuration, group routing, liquidity accounts |
| Direct FIX API to an LP | A gateway or bridge speaking FIX to the provider | Session settings, symbol mapping, reconnection and message logs |
These are technologies we work with. Which one fits depends on your liquidity relationships, how much routing logic you want outside MT5, and whether you also run MT4. For setup details, see PrimeXM XCore integration, oneZero Hub integration, Match-Trade integration, FIX API integration and our overview of forex bridge solutions.
MT5 APIs and plugins: where custom work happens
MetaTrader 5 exposes five public API families, and most broker-specific behaviour (CRM sync, custom reports, risk rules, bonus logic) is built on them. Supporting MT5 therefore includes supporting the code your brokerage has added to it.
- Server API: “can help you add more functions to MetaTrader 5 Trade Server and MetaTrader 5 History Server” (MetaQuotes). This is where server plugins live.
- Manager API: for custom administration and management utilities, “or even your own manager terminal.” MetaQuotes lists C++, ASP.Net and PHP for MT5, against C++ only for MT4.
- Gateway API: integration with other trading systems and creation of custom data feeds.
- Report API: expands the reports produced by MT5 trade servers.
- Web API: integration with websites and other company services, such as a client portal or CRM.
The usual failure is ownership, not the API: an old plugin, no source code in the company's hands, and no test after a platform update. When we take over an MT5 platform, we list every plugin and integration, confirm who holds the source code, and add them to the update test plan. FXSUPPORT develops server and manager plugins, Expert Advisors and Manager/Web API integrations; see MetaTrader plugin development, MetaTrader API integration and forex CRM solutions.
MT5 vs MT4: what changes for your support team
MT5 removes several MT4 limits and adds server-side features, so MT5 support covers more configuration surface than MT4 support. The differences that matter most to administrators come from MetaQuotes' own comparison page.
| Feature | MetaTrader 5 | MetaTrader 4 |
|---|---|---|
| Server architecture | Distributed | Single |
| Account groups | Unlimited | 512 |
| Security groups | Unlimited | 32 |
| Symbols | Unlimited | 1,024 |
| Orders database size | Unlimited | Up to 10M orders |
| Position accounting | Netting and hedging | Hedging only |
| Execution modes | 4 | 3 |
| Order fill policies | Fill or Kill, Immediate or Cancel, Return | Fill or Kill |
| Balance transaction types | Balance, Credit, Correction, Charge, Bonus, Commission, Agent, Interest | Balance, Credit |
| SQL export | Native (MySQL, MSSQL, Oracle) | Limited (MySQL) |
| Pending order types | 6 | 4 |
There is also a commercial reason brokers move: MetaQuotes states on its MT4 broker page that “The MetaTrader 4 trading platform licenses are no longer available for purchase.” New brokerages therefore start on MT5, and existing MT4 brokers plan a move. Migration is its own project (plugin rewrites, group and symbol mapping, data migration, parallel running). Read our MT4 to MT5 migration guide for the full plan, or the MT4 support page if you will keep MT4 running for a while.
How FXSUPPORT MT5 support works
FXSUPPORT takes over the technical operation of your MT5 platform, or the parts of it you choose, under a written scope. Engagements start with a free technical review so both sides know the current state before anything changes.
- Free technical review. You describe your MT5 setup (licence type, server locations, gateways or bridge, plugins, CRM). We reply with the risks and gaps we see.
- Scope and quote. We agree what we own (for example monitoring, configuration changes, DST/holiday updates, backups, bridge support, plugin maintenance) and what stays with your team.
- Access and documentation. Manager and administrator accounts with the right permissions, server access, and a documented inventory of components, plugins and integrations.
- Stabilise. Fix the urgent items from the review first: backups, failover, monitoring gaps, exposed access points, outdated gateways.
- Run. Ongoing monitoring and the daily, weekly and event-driven tasks above, with a 99.9% uptime target for the infrastructure we manage.
- Improve. Plugins, API integrations, reports, prop-trading or MAM/PAMM setups and migrations as separate, scoped projects.
Platform support
Setup, updates, backups, configuration, log monitoring and MetaTrader administration.
Infrastructure
Server and VPS hosting with servers in the UK and the Netherlands, monitoring and DDoS/security hardening. See MetaTrader server hosting.
Risk operations
End-of-day and evening reports, toxic-flow lists, session and DST/holiday schedule checks.
Connectivity
Data feed setup and liquidity integrations with PrimeXM XCore, oneZero Hub, Match-Trade and FIX API. See liquidity provider integration.
Outsourcing fits brokers that are launching, rely on one MT5 administrator who cannot cover nights and holidays, or inherited an undocumented platform. Many keep a platform owner in-house and outsource monitoring, out-of-hours cover and development.
Cost depends on scope rather than a fixed price list. The main factors are the number of servers and regions, gateway or bridge count, plugin and integration volume, coverage hours, and whether hosting is included. We quote after the review. Brokers still choosing a setup can start with forex broker solutions or MetaTrader white label.
Frequently asked questions
What is MT5 support for brokers?
Does MetaQuotes support or manage my MT5 server?
What are the main MT5 server components?
What is the difference between netting and hedging in MT5?
Is Ultency a replacement for a third-party bridge?
Who handles daylight saving time and holiday sessions on MT5?
How do MT5 backups and failover work?
What uptime do you work to on MT5?
Can you work with the MT5 Manager API, Web API and server plugins?
Can you move our brokerage from MT4 to MT5?
What is an MT5 grey label, and does it need MT5 support?
How much does MT5 support cost?
Sources
- MetaTrader 5 for Brokers — MetaQuotes (accessed 8 October 2026)
- MetaTrader 5 for Brokers (Ultency, payments, automations) — MetaQuotes (accessed 8 October 2026)
- Order the MetaTrader 5 Trading Platform (Entry, Standard, Enterprise) — MetaQuotes (accessed 8 October 2026)
- Ultency Matching Engine — MetaQuotes (accessed 8 October 2026)
- Comparison of MetaTrader 5 and MetaTrader 4 — MetaQuotes (accessed 8 October 2026)
- MetaTrader 5 Help: General Concepts (position accounting) — MetaQuotes (accessed 8 October 2026)
- MetaTrader 5 release notes, 22 April 2016 (hedging added) — MetaQuotes (accessed 8 October 2026)
- MetaTrader 5 Access Server Hosting, 5 May 2022 — MetaQuotes (accessed 8 October 2026)
- New Web Terminal, 12 October 2022 — MetaQuotes (accessed 8 October 2026)
- Retail Brokers Gain Amsterdam Hosting Location for MT5 Backup Servers, 25 June 2026 — Finance Magnates (accessed 8 October 2026)
- MetaTrader 4 for Brokers — MetaQuotes (accessed 8 October 2026)
- XCore — PrimeXM (accessed 8 October 2026)
- Retail Brokers — oneZero (accessed 8 October 2026)
- MT4 / MT5 Server Hosting and Support — Match-Trade Technologies (accessed 8 October 2026)
FXSUPPORT is not affiliated with MetaQuotes Ltd. or the vendors named on this page. General information, not legal or investment advice.
Get a second pair of eyes on your MT5 server
Send us a short description of your MetaTrader 5 setup. We review components, groups, gateways and backups and tell you what we would fix first.