Managed infrastructure. A separate line of business from our platform, and it does not require you to adopt it.
MT4 server hosting
We host and operate your MetaTrader 4 server: the infrastructure it runs on, the upkeep, the monitoring and the people who answer at three in the morning.
Who this is for
Brokers who already hold an MT4 server licence, or who are acquiring one, and who do not want to employ the systems team that running it properly requires. Not for brokers looking to obtain a licence — that is MetaQuotes’ decision, not ours.
Licence position
The MT4 server licence is issued by MetaQuotes directly to you and remains in your name. We operate the software under your licence; we do not sublicense it, and if you leave, the licence goes with you because it was never ours.
What is included.
- 01
Provisioning and configuration of the main server, trade servers, history and data feed components.
- 02
Colocated hosting with redundant power and network, and DDoS filtering in front of it.
- 03
Monitoring of the server processes, feed continuity, disk, memory and connection counts, with alerting to us rather than to you.
- 04
Backups on a fixed schedule, with restores tested rather than assumed.
- 05
Plugin hosting and deployment, including gateway and reporting plugins you already run.
- 06
Manager and Administrator access for your own staff, with the accounts and permissions you specify.
- 07
Version upgrades planned with you, applied in a window you choose.
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 MT4 server licence itself. It is issued by MetaQuotes, held by you, and stays yours.
- Third-party plugin licences — we deploy and host them; you own the commercial relationship.
- Liquidity. A bridge to your provider is in scope; the provider relationship is yours.
- Regulatory reporting content. We keep the systems running and the data available; what gets filed is yours.
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
What you run today: server build, plugin list, gateway configuration, current host and current pain.
- 02
Target build
The configuration we will run, written down and agreed before anything is provisioned.
- 03
Parallel build
The new environment is stood up and exercised while the existing one keeps serving clients.
- 04
Rehearsed cutover
The move is practised end to end, including the rollback, before it is done for real.
- 05
Cutover in a window you pick
Usually a weekend. Rollback stays available until you sign off.
- 06
Handover
Access, monitoring visibility, escalation contacts and the runbook, in writing.
Technical detail.
| Components | Main server, trade servers, history server, data feed, gateways. |
|---|---|
| Access | Manager and Administrator terminals for your staff. |
| Plugins | Hosted and deployed; you hold the licences. |
| 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.
- Do you take over our existing licence, or do we need a new one?
- Neither. Your existing licence stays exactly as it is, in your name. We operate under it. Nothing about the licence changes because the hosting changed.
- Can our own systems people keep their access?
- Yes. Manager and Administrator access is configured for whoever you name, with the permissions you set. We are not a gatekeeper between you and your own server.
- What happens if we want to leave?
- You take the licence, the data and the configuration. We document the migration out as carefully as the migration in, and there is no period where you are locked in while we are slow about it.
- Who is on the other end of a ticket at 3am?
- An engineer who can change the thing that is broken. Not a first line whose only escalation is to wake someone else up.
6open items on this page
- Confirmation of MetaQuotes’ current position on issuing new MT4 server licences, so the audience note above is precise rather than cautious.
- 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.