Managed infrastructure. A separate line of business from our platform, and it does not require you to adopt it.
MT5 server hosting
We host and operate your MetaTrader 5 server, including the multi-asset and hedging configurations MT5 supports and MT4 does not.
Who this is for
Brokers running MT5, or moving from MT4 to MT5, who want the platform operated properly without hiring for it. Also brokers whose current host is technically fine but unreachable when it matters.
Licence position
The MT5 server licence is issued by MetaQuotes directly to you and remains in your name. We operate the software under your licence, never a sublicence, so leaving is a migration rather than a renegotiation.
What is included.
- 01
Provisioning and configuration of the full MT5 topology: main, trade, history, backup and access servers.
- 02
Colocated hosting with redundant power and network, and DDoS filtering in front of it.
- 03
Monitoring across processes, feed continuity, database health and connection counts, alerting to us first.
- 04
Backups on a fixed schedule with tested restores.
- 05
Gateway and plugin hosting, including your existing gateways to liquidity and payments.
- 06
Manager, Administrator and Web API access for your staff and your own tooling.
- 07
Multi-asset and hedging configuration where your licence covers it.
- 08
Version upgrades planned with you and applied in your window.
The useful half. Anyone can list what is included.
What is not included.
Stated up front so you are not finding it out during an incident. If something you need is on this list, say so before you sign rather than after.
- The MT5 server licence. Issued by MetaQuotes, held by you, and it stays yours.
- Third-party plugin and gateway licences.
- Liquidity provider relationships.
- MT4-to-MT5 data conversion decisions — we run the migration, but which history and which fields carry over is a commercial call only you can make.
Structure, not numbers. The targets are figures and none is verified yet.
How support is structured.
Response targets are numbers, and no number appears on this site until it carries its definition and its measurement. What can be stated now is the shape: what starts the clock, how severity is decided, and what counts as finished.
- What starts the clock
- A ticket raised through the support channel, or an alert from our own monitoring — whichever comes first. If we detect it before you report it, the clock started when the monitor fired, not when you noticed.
- Severity, set by impact not by opinion
- Severity is defined by what a client cannot do: trade, deposit, withdraw, or log in. It is not negotiated per ticket, and it is not lowered because a workaround exists.
- Escalation path
- One queue, and it is engineers rather than a first line reading a script. Escalation is by elapsed time against severity, automatic, and does not require you to ask.
- What counts as resolved
- Service restored and cause identified are two separate states, and the ticket does not close on the first one. You get the cause in writing.
How a migration runs.
- 01
Inventory
Current topology, gateway list, plugin list, database size and growth rate.
- 02
Target build
The configuration we will run — including whether you are consolidating servers — agreed in writing first.
- 03
Parallel build
Stood up alongside what you have, exercised with real load patterns.
- 04
Rehearsed cutover
Practised end to end, rollback included, before the real one.
- 05
Cutover in a window you pick
Rollback stays available until you sign off.
- 06
Handover
Access, monitoring, escalation contacts and runbook, documented.
Technical detail.
| Components | Main, trade, history, backup and access servers. |
|---|---|
| APIs | Manager API, Web API, Gateway API available to your tooling. |
| Asset classes | Multi-asset and hedging where your licence allows. |
| Backups | Scheduled, with restore testing. |
| Network | Colocated, redundant, DDoS filtered. |
Pricing.
Figures not published yet. Setup and monthly pricing for this service is a commercial decision that has not been made, and inventing a “from” number would be the first thing on this page that was not true. What is settled is what you get for it — the scope above is the complete list, and the boundary section is the complete exclusion list. When figures exist they go through the same gate as every other number on this site.
Questions that come up.
- We are on MT4 and want MT5. Can you run both during the move?
- Yes, and that is usually how it goes. The MT5 environment runs in parallel while MT4 keeps serving clients, and accounts move in groups rather than all at once.
- Does our closed trade history come across from MT4?
- Technically yes. Which history and which fields you carry over is a decision with reporting and regulatory consequences, so it is yours to make and we implement it — we will tell you what each option costs in effort.
- Can we keep our own gateways?
- Yes. Existing gateways are hosted and deployed as they are. We do not require you to change provider as a condition of hosting.
- Who holds the database?
- You do. It is your data on infrastructure we operate, and an export is a request rather than a project.
5open items on this page
- Response and resolution targets per severity — these are figures and none is verified yet, so no number appears on the page (see /trust/execution for the rule).
- Uptime commitment, and the measurement window it is calculated over.
- Pricing: setup and monthly figures per configuration.
- A dedicated infrastructure enquiry route. The demo form is for the platform and would be the wrong intent here, so the CTA currently points at the support plans page.
- Confirmation of our current data-centre footprint, so the colocation options can be listed by name rather than described.
Next step.
The support arrangement behind this service is the thing worth reading before you talk to anyone, including us.
A dedicated enquiry form for infrastructure work is outstanding — it is on the list above. The demo form is for the platform and would be the wrong thing to send you to.