MT plugin development
Make MetaTrader do what your desk actually needs.
The platform is fixed; your business is not. Server-side plugins close the gap between what MetaTrader ships and how you actually operate.
Where you are now
The gap between the platform and the desk
Every brokerage ends up with rules the platform does not express — a margin policy with an exception, a routing decision that depends on the client tier, a report somebody rebuilds in a spreadsheet every Monday. The usual answer is a manual process that works until the person doing it is on holiday.
What the work covers
Risk and margin rules
Exposure limits, stop-out behaviour and margin policy enforced in the server rather than watched by a person.
Order routing
Route by instrument, client group or liquidity conditions, with the decision recorded rather than inferred afterwards.
Data out, in real time
Push trades, balances and events to your CRM, warehouse or BI as they happen — not as a nightly export that is already stale.
Integrations the platform lacks
Payment providers, KYC, notification channels — wired at the server so the behaviour is the same however the client connects.
Reporting that matches your books
Statements and regulatory extracts generated from the platform's own data, in the shape your auditor asks for.
Built to be handed over
Source, build instructions and a runbook. A plugin only we can rebuild is a dependency, and we are not selling one.
The technical answer
How it works in practice
| Platforms | MetaTrader 4 and MetaTrader 5, server-side |
|---|---|
| Delivery | Source and binaries, with build instructions |
| Environments | Developed against your demo server first |
| Support | Maintenance through platform updates |
| Ownership | The code is yours |
Describe the rule you cannot express
Tell us the behaviour your desk needs and we will tell you whether a plugin is the right answer — sometimes it is not.