MetaTrader Support for Brokers: MT4 & MT5 | FXSUPPORT

FXSUPPORT

MT4 & MT5 support for brokers

MetaTrader Support for Brokers: Outsourced MT4 & MT5 Technical Support

MetaQuotes licenses the platform; your brokerage runs it. FXSUPPORT monitors, maintains and fixes your MT4 and MT5 servers, gateways and bridges, while you keep ownership, access and control.

Outsourced MetaTrader support for brokers: MT4 and MT5 server monitoring, incident response, updates and backups. Compare on-call, managed and hybrid models.

By the FXSUPPORT Editorial Team · Updated 8 October 2026

Short answer: MetaTrader support for brokers is outsourced technical operation of your MT4 or MT5 back end: monitoring trade, history and access servers, gateways and bridges; applying builds; checking backups; and responding to incidents. MetaQuotes does not run your servers, so the broker or a provider such as FXSUPPORT does.

What MetaTrader support for brokers actually is

MetaTrader support for brokers is the day-to-day engineering work that keeps a brokerage's own MT4 or MT5 servers running, correctly configured and recoverable. It is different from retail "MetaTrader help", which answers traders' questions about the terminal.

The reason brokers need it is structural. MetaQuotes sells the platform but leaves operation to the licensee. On its broker page, MetaQuotes says so directly:

"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."— MetaQuotes, MetaTrader 5 for Brokers (accessed October 2026)

In practice, that means the broker carries every operational task: patching the servers, applying MetaTrader builds, watching the data feed, keeping the liquidity bridge connected, rotating logs, testing backups and getting the platform back after a failure. Some brokers build an in-house team for this. Many outsource part or all of it.

A MetaTrader back end has more moving parts than most owners expect. MetaQuotes describes MT5 as "based on a distributed architecture, where different functions are performed on different servers", and lists the MT4 back office as "trade servers, access points, manager terminals, various gateways and data feeds". Add a bridge such as PrimeXM XCore or oneZero Hub, a CRM, server plugins and a Manager or Web API integration, and a typical brokerage has a dozen components that can each fail on their own.

FXSUPPORT provides outsourced MT4/MT5 platform support and managed operations for forex brokers and prop firms. We are an independent provider: FXSUPPORT is not affiliated with MetaQuotes Ltd. or with any vendor named on this page.

What FXSUPPORT's MetaTrader support covers

Our MetaTrader support covers the servers, the platform configuration and the integrations around them, for MT4, MT5 or both running side by side. The table shows the scope by area.

Scope of FXSUPPORT MetaTrader support by area
Area	What we do	MT4	MT5
Servers and monitoring	Monitor trade, history and access servers, OS health, disk, network and services; alerting and on-call response	Yes	Yes
Platform updates	Plan, test and apply MetaTrader builds and OS patches in low-volume windows, with rollback steps	Yes	Yes
Backups and recovery	Backup schedules, restore checks, documented recovery runbooks	Yes	Yes
Configuration	Groups, symbols, sessions, swaps, margin settings, permissions, DST and holiday schedule checks	Yes	Yes
Gateways and bridges	Gateway and bridge configuration and monitoring (PrimeXM XCore, oneZero Hub, Match-Trade, FIX API)	Yes	Yes
Data feeds	Feed setup, quote checks, stale-price and spread alerts	Yes	Yes
Plugins and APIs	Plugin installation and compatibility checks after builds; Manager and Web API integrations; custom plugin development	Yes	Yes
Log monitoring	Journal and log review for errors, rejected requests and connection problems	Yes	Yes
Security	Access review, firewall rules, DDoS and security hardening	Yes	Yes
Risk operations	End-of-day and evening reports, toxic-flow lists, session checks	Yes	Yes

Related work that often starts as a support ticket has its own page: MT4 to MT5 migration, plugin development, bridge solutions and MetaTrader server hosting on our servers in the UK and the Netherlands. Platform-specific detail is on MT4 support and MT5 support.

Support models: on-call, managed or hybrid

There are three common ways to buy MetaTrader support: on-call (you call us when something breaks), managed (we run operations), or hybrid (your team runs daily admin and we cover monitoring, escalations and out-of-hours). The right model depends on whether you already have a MetaTrader administrator.

MetaTrader support models compared
	On-call	Managed	Hybrid
Best for	Brokers with a capable in-house admin who need expert backup	New or small brokers without platform staff	Brokers with an admin in one time zone who need 24/7 cover
Who watches alerts	Your team	FXSUPPORT, 24/7	FXSUPPORT, with escalation to your team
Builds and patches	Your team, we advise	FXSUPPORT, after your approval	Agreed split, written down
Daily config changes	Your team	FXSUPPORT, on your written request	Usually your team
Incident response	On request	FXSUPPORT leads	FXSUPPORT leads out of hours
Reporting	Per incident	Regular operations report	Regular operations report
Main risk	Slow start: we learn the setup during the incident	Less in-house knowledge	Unclear ownership if the split is not documented

Our advice: even with on-call support, let the provider document your environment first. An engineer who has never seen your bridge configuration loses the first part of an outage just reading it.

How we handle a MetaTrader incident

Every incident follows the same path: detect, classify severity, stabilise trading, fix the cause, then write it up. A fixed process matters because a trading outage is a bad moment to decide who calls the liquidity provider.

The structure follows established practice from site reliability engineering. Google's SRE book describes an incident system "based on the Incident Command System", with one person in charge and a written record:

"The incident commander's most important responsibility is to keep a living incident document."— Google, Site Reliability Engineering, "Managing Incidents" (accessed October 2026)

Example severity levels for MetaTrader incidents
Level	Meaning	MetaTrader examples
P1 – critical	Trading stopped or prices wrong for many clients	Trade server down; all access points unreachable; bridge disconnected from all liquidity providers; frozen quotes on major symbols
P2 – major	Trading works but is degraded	One access point down; one LP disconnected; slow execution; history server not syncing
P3 – minor	Limited impact, workaround exists	Single group misconfigured; report plugin failing; one symbol session wrong
P4 – request	Planned change or question	New symbol, new group, build update request, API access

Target response times for each level are agreed in your contract, not set by a template. The steps for a P1 or P2:

Detect. An alert fires or your dealing desk reports a problem through the agreed channel.
Classify and assign. The on-call engineer sets the severity and becomes incident lead.
Notify. Your named contacts are informed, with what is known and what is not.
Stabilise. Restore trading first: fail over to a backup server or route, restart a failed service, or disable a faulty plugin with your approval.
Diagnose. Check the server journals, bridge logs and monitoring history around the start time.
Fix and verify. Apply the fix and confirm prices, executions and logins on live and demo accounts.
Report. A written incident report: timeline, impact, cause, actions and follow-ups.

The incident report gives your dealing and compliance teams what they need for client complaints, and for regulatory reporting if your jurisdiction requires it. For common error patterns, see MetaTrader common errors and forex server troubleshooting.

Not sure your setup would survive a P1?

We review your MT4/MT5 servers, monitoring, backups and bridge configuration and tell you where the single points of failure are.

Request a free technical review WhatsApp Telegram

MetaTrader monitoring checklist

Good MetaTrader monitoring watches both the servers and what traders experience: prices, executions and logins. Server CPU alone will not tell you that quotes stopped updating.

A practical starting point is the "four golden signals" from Google's SRE book, which says the signals "are latency, traffic, errors, and saturation". Mapped to MetaTrader:

Four golden signals applied to an MT4/MT5 platform
Signal	What to watch on MetaTrader
Latency	Execution time from request to fill; bridge round-trip to LPs; ping from access points to the trade server
Traffic	Connected clients, requests per minute, API sessions, quote ticks per symbol
Errors	Rejected or requoted requests, gateway disconnects, journal errors, failed logins, plugin exceptions
Saturation	CPU, RAM, disk space and disk I/O on trade and history servers; network bandwidth; database growth

On top of the four signals, our checklist covers platform-specific items:

Quote freshness: alert when a symbol's last tick is older than its expected interval during the session.
Spread checks: alert on abnormal spreads against the configured markup.
Feed and bridge status: every LP and data feed connection, with failover state.
Service health: trade, history and access server processes, and backup or failover servers.
Backups: each backup job completed, and periodic restore tests.
Certificates and licences: expiry dates tracked well in advance.
Sessions and calendars: trading sessions, DST changes and holiday schedules checked before they happen.
Security: unusual manager logins, admin access from new IP addresses, traffic spikes that look like DDoS.
End-of-day: swaps applied, daily reports generated, rollover completed.

More detail is on forex risk management and MetaTrader administration.

What a 99.9% uptime target means in minutes

A 99.9% uptime target allows about 43 minutes of unavailability per month, or 8.76 hours per year. FXSUPPORT works to a 99.9% uptime target. It is a target because many outage causes, such as LP or data-centre failures, sit outside any single provider's control.

Allowed unavailability by availability level (Google SRE availability table)
Availability	Per year	Per month	Per week
99%	3.65 days	7.2 hours	1.68 hours
99.5%	1.83 days	3.6 hours	50.4 minutes
99.9%	8.76 hours	43.2 minutes	10.1 minutes
99.95%	4.38 hours	21.6 minutes	5.04 minutes

Two practical points. First, agree whether planned maintenance counts. Forex trades around the clock on weekdays, so build updates are usually scheduled for the weekend. Second, high availability is designed in: MetaQuotes notes that MT5 trade servers "can be hidden behind multiple access points", and backup servers and redundant bridge routes cut the length of an outage. Monitoring only shortens the time to detect one. See server troubleshooting for redundancy patterns.

Onboarding: how support starts

Onboarding turns an unknown environment into a documented, monitored one before we take on-call responsibility. The steps are the same for MT4 and MT5.

Free technical review. A call and a questionnaire about your servers, licence, bridge, LPs, plugins and current pain points.
Scope and model. We propose on-call, managed or hybrid support and write down who does what.
Access. You create named accounts for our engineers with the minimum rights needed. No shared passwords.
Assessment. We audit server architecture, configuration, security, backups and monitoring coverage, and list the risks we find.
Documentation. An environment map: servers, IP addresses, gateways, LP sessions, plugins, schedules and contacts.
Monitoring and alerting. We deploy checks from the list above and agree on alert channels and escalation contacts.
Runbooks. We write recovery steps for the likely failures: trade server restart, failover, bridge reconnect, feed switch, restore.
Go-live. On-call cover starts on an agreed date, with a review after the first weeks.
Ongoing improvement. Regular reviews of incidents, capacity and planned builds.

How long onboarding takes depends on how much of the environment is already documented and how quickly access is granted.

What the broker keeps control of

With outsourced MetaTrader support, the broker keeps ownership of the licence, the servers' admin credentials, the client data and all commercial and risk decisions. The provider operates the platform on the broker's instructions. Regulators expect exactly this split.

In the UK, the FCA Handbook says a firm that outsources critical or important operational functions "remains fully responsible for discharging all of its obligations under the regulatory system", and that the outsourcing "must not result in the delegation by senior personnel of their responsibility" (SYSC 8.1.6R). In the EU, the Digital Operational Resilience Act (DORA), which applies from 17 January 2025, says financial entities using ICT service providers "shall, at all times, remain fully responsible for compliance with, and the discharge of, all obligations under this Regulation and applicable financial services law" (Article 28(1)(a)).

Typical responsibility split in managed MetaTrader support
Item	Broker	FXSUPPORT
MetaQuotes licence and contract	Owns	Technical input only
Master admin credentials	Owns, can revoke our access at any time	Named accounts with agreed rights
Spreads, markups, leverage, swaps, A/B-book routing	Decides	Configures on written request
Client data and trading history	Owns	Accesses only as needed for support
Build updates	Approves timing	Tests, schedules, applies, rolls back
Monitoring and incident response	Informed, approves trading-impacting actions	Runs
LP and bridge vendor contracts	Owns	Technical contact for configuration
Regulatory reporting	Responsible	Provides incident reports and logs

This is general information, not legal advice. Check your own regulator's outsourcing rules and put the split in your service agreement.

MT4 and MT5: what changes for support

Both platforms need the same core support, but MT4 support is now about keeping an installed base stable, while MT5 support also means keeping up with frequent builds.

"The MetaTrader 4 trading platform licenses are no longer available for purchase. We focus our efforts on the development of MetaTrader 5, and further conceptual updates will only be released for this multi-asset platform."— MetaQuotes, MetaTrader 4 for Brokers (accessed October 2026)

For brokers still on MT4, that means more work on stability, compatibility of older plugins and migration planning. MT4 also has fixed limits that MT5 removed: MetaQuotes' comparison lists 1,024 symbols on MT4 against unlimited on MT5, and hedging only on MT4 against netting plus hedging on MT5.

On MT5, change management is the main task. MetaQuotes' release notes show Build 6060 on 23 July 2026, Build 6180 on 3 September 2026 and Build 6230 on 24 September 2026: three platform builds in about nine weeks. Each one needs a decision, a test of your plugins and bridge, and a planned window. MT5 also has more integration points. MetaQuotes lists the Report, Server, Gateway, Manager and Web APIs, and each custom integration needs to be retested after a build.

MT5 licences come in three tiers by real-account capacity, according to MetaQuotes: Entry (1,000), Standard (25,000) and Enterprise (200,000). The tier also affects which server components you run, and so what has to be monitored.

How to choose a MetaTrader support provider

Choose a provider on scope, process and transparency, not on headline numbers. Ask these questions before signing:

Is support tied to other products?

Some providers include support only with their own bridge, liquidity or hosting. Check whether you can change one without losing the other.

Is the process written down?

Ask for an example incident report, a severity table and a sample runbook.

How is access controlled?

Named accounts, minimum rights, and access you can revoke. Avoid any setup where the provider holds your only admin password.

What is promised, exactly?

Check whether an uptime figure is a target or a contractual commitment, how downtime is measured and what is excluded.

Who covers your night?

Check who answers a P1 at 03:00 on a Monday in your trading time zone.

Can they go beyond break-fix?

Plugins, API integration, migration and risk reports often follow. One team that knows your setup reduces handovers.

On cost: FXSUPPORT does not publish prices because the work varies by setup. The main cost factors are the support model, MT4, MT5 or both, the number of servers and access points, the number of bridges, LPs and plugins, the coverage hours, and whether hosting is included. We quote after the free technical review.

Frequently asked questions

What is MetaTrader support for brokers?

It is technical operation of a brokerage's MT4 or MT5 back end: monitoring servers, gateways and bridges, applying builds and patches, managing configuration and backups, and responding to incidents. It is different from helping retail traders use the terminal.

Does MetaQuotes provide server support to brokers?

MetaQuotes develops and licenses the platform. It says brokers "maintain your server infrastructure and fully control support and administration", and that it has no access to brokers' servers. Day-to-day operation therefore sits with the broker or a provider the broker chooses.

Do you support both MT4 and MT5?

Yes. We support MT4, MT5 and brokers running both side by side, including the bridges, plugins and integrations around them. For a planned move, see MT4 to MT5 migration.

Can I still get support for MT4 if new licences cannot be bought?

Yes. MetaQuotes stopped selling MT4 licences, but brokers with existing MT4 installations still need monitoring, maintenance and incident response. We support existing MT4 servers and can help plan a migration when you are ready.

What is the difference between on-call and managed support?

With on-call support, your team runs the platform and calls us when needed. With managed support, we monitor 24/7, apply updates after your approval and lead incident response. Hybrid support splits the work, usually with us covering monitoring and out-of-hours.

What uptime do you work to?

We work to a 99.9% uptime target, which equals about 43 minutes of unavailability per month. Many outage causes, such as LP or data-centre failures, are outside any one provider's control. Response times per severity level are agreed in your contract.

Who keeps the admin passwords?

You do. We work through named accounts with the rights the scope needs, and you can revoke them at any time. The licence, client data and commercial settings stay under your control.

Am I still responsible to my regulator if I outsource?

Yes. The FCA says a firm that outsources critical functions "remains fully responsible", and DORA says EU financial entities remain fully responsible when using ICT providers. This is general information, not legal advice.

What do you monitor on a MetaTrader server?

Latency, traffic, errors and saturation on trade, history and access servers, plus quote freshness, spreads, bridge and LP connections, backups, certificate and licence expiry, session and DST schedules, and suspicious admin logins.

How do you handle MetaTrader build updates?

We review each release, test it against your plugins and bridge where possible, and apply it in a window you approve, usually at the weekend, with rollback steps ready.

How do I set up trade server redundancy for a brokerage?

Run several access points in front of the trade server, keep a backup server synchronised, use redundant bridge routes to your LPs, and test failover on a schedule. We design and test this as part of our support.

Can you support a grey label or white label setup?

Yes, within what the setup allows. An MT5 grey label is a brokerage set up inside another company's licensed MetaTrader 5 server: you get your own client groups and your brand on the WebTrader, mobile apps, CRM and client portal, while the MT5 server licence stays with the provider. Server-level work then needs the provider's cooperation. A white label gives more control. See MetaTrader white label.

How much does MetaTrader support cost?

It depends on the support model, platforms, number of servers, bridges, LPs and plugins, coverage hours and whether hosting is included. We give a quote after a free technical review.

How do we start?

Use the contact form, email [email protected], or message us on WhatsApp or Telegram with a short description of your setup. We start with a free technical review.

Sources

MetaTrader 5 for Brokers — MetaQuotes (accessed 8 October 2026)
MetaTrader 4 for Brokers — MetaQuotes (accessed 8 October 2026)
Buy the MetaTrader 5 Platform (licence types) — MetaQuotes (accessed 8 October 2026)
MetaTrader 5 vs MetaTrader 4 comparison — MetaQuotes (accessed 8 October 2026)
What's new in MetaTrader 5 (release notes) — MetaQuotes (accessed 8 October 2026)
SYSC 8.1 General outsourcing requirements — FCA Handbook (accessed 8 October 2026)
Regulation (EU) 2022/2554 (DORA), Article 28 — EUR-Lex (accessed 8 October 2026)
Digital Operational Resilience Act (DORA) — ESMA (accessed 8 October 2026)
Monitoring Distributed Systems — Google, Site Reliability Engineering (accessed 8 October 2026)
Managing Incidents — Google, Site Reliability Engineering (accessed 8 October 2026)
Availability Table — Google, Site Reliability Engineering (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 MetaTrader setup

Send us a short description of your MT4 or MT5 environment. We review servers, monitoring, backups and bridge setup, then propose the support model that fits.

Request a free technical review View All Services

Explore More