Platforms
MetaTrader 5, built properly and then kept that way
The install is the easy part. What decides whether the environment is still correct in two years is the symbol tree, the group policy and whether anybody is maintaining the calendar. We take all three.
See it live
One terminal, built on a symbol tree that makes sense
Instrument groups, watchlists and order entry all trace back to the structure configured underneath — get that right and the terminal takes care of itself.
What gets configured
Six decisions that shape everything downstream
The symbol tree
Instruments are grouped into a structure that reflects how you actually price, not a copy of a demo server. Contract size, tick value, precision and quote sources are set per symbol and reviewed when anything upstream changes.
Client groups
Leverage bands, commission, spread markup, permitted instruments and margin behaviour are defined per group. New groups are cloned from a reviewed baseline so nobody hand-builds one at 6pm on a Friday.
Gateways and providers
Price and execution links to each provider, with symbol mapping in between. Where a provider names an instrument differently, the mapping absorbs it rather than the platform inheriting the difference.
Sessions and holidays
Trading sessions follow a maintained calendar. Holiday schedules, early closes and rollover boundaries are applied ahead of the date rather than after a client trades into a closed market.
Swaps and financing
Swap rates are reviewed on a schedule against what your providers actually charge, with triple-swap days configured per instrument group rather than assumed to be Wednesday everywhere.
Access and permissions
Administrative access is restricted by address and role, with each change traceable to a person. Shared administrator credentials are removed as part of onboarding.
The standing list
What actually happens every week
None of this is dramatic. It is the accumulation of it being nobody’s job that causes the incidents.
Corporate actions applied to equity instruments before the open
Swap rate review against provider statements
Session and holiday calendar maintenance
Gateway health and reconnection handling
Quote gap and stale price investigation
Backup verification by restore, not by log
Patch and update windows scheduled outside market hours
Failover rehearsal on a fixed cadence
When something goes wrong
Contain first, diagnose second
- 01
Detect
Monitoring watches feed staleness, gateway state, rejection rates and resource pressure. Most incidents are visible in one of those before a client notices anything.
- 02
Contain
The first action is to stop the damage — disable a bad gateway, fall back to a secondary feed, or suspend a symbol — rather than to diagnose while clients keep trading.
- 03
Explain
You get a written account of what happened, what was changed, and what will stop it recurring. It is not a status page update.
FAQ
MetaTrader 5 administration: common questions
6 short answers to what teams ask before a demo.
Both. Taking over an existing environment starts with a review rather than a change: we document the current configuration, flag what we consider risky, and agree an order of work before touching anything.
You do, always. We work under named accounts with the permissions the work requires, and every administrative change is attributable to a person. If the engagement ends, our access is removed and yours is unaffected.
Through a request that records what is changing, why, who approved it and how to reverse it. Routine changes have standing approval; anything touching leverage, margin or symbol economics is confirmed with you first.
Coverage does not depend on one person's calendar. Session and holiday changes are applied in advance from a maintained schedule, and there is a rota behind the named engineer on your account.
Yes. Managed hosting is a separate part of the engagement. If your infrastructure already sits where it needs to be, we administer the platform on it and leave the hosting arrangement alone.
A straightforward build is usually a matter of days once provider credentials and instrument requirements are confirmed. What extends it is almost never the install — it is waiting on third-party approvals and deciding how the book should be structured.
Still have a question?
A specialist will answer it directly, with your set-up in mind.
Ask a specialistLet us look at the server you already have
We will go through the symbol tree, the group policy, the gateways and the backup arrangement, and write down what we would change.