MT5 Manager API developer for brokers and prop firms.
For brokers, prop firms and platform teams whose product depends on MetaTrader 5 data.
I built the MetaTrader 5 integration for a live prop-trading platform: a C#/.NET service on MetaQuotes' native Manager API, and a monitor that checks every account's loss rules every few seconds. If your product depends on MT5 data being fast and correct, this is work I have already done in production.
Delivered in production
Manager API services
A standalone C#/.NET service: accounts, positions, deals, orders, daily history, batch reads and trading-rights control, secured with API keys and an IP allow-list.
Real-time risk monitoring
Daily-loss, max-loss and equity rules checked every few seconds from the locally pumped cache, with idempotent fail flows.
Backend integration
A typed client in your backend, rule snapshots published through Redis, and callbacks that are safe to retry.
Admin tooling on MT5 data
Account statistics and guarded admin actions: manual pass or fail, freeze, close all positions.
Health and operations
Connection health checks, alert emails, auto-reconnect, separate demo and live services, and a deployment runbook.
Performance and correctness fixes
Finding out why reads are slow or numbers disagree: pumped cache versus network requests, SDK thread safety, deal classification and day boundaries.
What I can build next
Investor portals, wallets and IB commissions
Not yet delivered as a finished product
Products I can design and build on top of an MT5 integration. I have not delivered this exact combination as a finished product. The MT5, payment and dashboard parts each come from production work.
Investor dashboards
Trading history, P&L, balance, equity, margin and performance reports per account, with balance-threshold alerts.
Wallets on a ledger
Separate investor and IB wallets on a double-entry ledger: deposits, withdrawals, internal transfers and commission deductions, each posted exactly once.
IB and sub-IB commissions
Multi-level referral trees, commission formulas agreed in writing with worked examples, and month-end runs that can be resumed and audited.
CRM and back-office sync
MT5 accounts, groups and balance operations kept in step with your CRM or client area through an adapter, not scattered API calls.
Before it goes liveTwo things decide feasibility before any code: what MT5 access you really have (a Manager login belongs to one broker's server) and whether the wallet you describe is regulated in your market. A discovery sprint answers both.
How we can work together
Start small. Commit when it works.
Every engagement starts with a written scope. You know what you are getting, what it costs and what is left out before any work begins.
- 01Fixed fee · 1 to 3 weeks
Technical discovery sprint
I review your requirements, existing code and third-party access, then deliver a written architecture, a feasibility and risk report and a milestone plan. Yours to keep, whoever builds it.
- 02Paid by milestone
Fixed-scope MVP build
A defined first release, built in milestones on a staging environment you can use throughout. You pay for delivered milestones, not for hours.
- 03Monthly
Founding engineer contract
I join as your hands-on technical owner: architecture, backend, front end, infrastructure and releases, working directly with you.
- 04Part-time · monthly
Fractional technical lead
You already have a developer or a small team. I own the architecture and the risky parts, review the work and keep delivery honest.
I quote each engagement in USD after a first call. I work from Malaysia with no agency layer, so the budget goes into engineering, not account management. I price on scope and responsibility, and I am not the cheapest option.
- You work with the person doing the work
- Written scope and milestones
- Source code, access and documentation handed over
- NDA on request
How we would work
- 01
A short call
A no-obligation conversation about what you are building, what exists already and what success looks like.
- 02
A written scope
What I will build, what I will not, the risks and the price. Larger or unclear projects start with a short, paid discovery sprint.
- 03
Small, visible releases
You see working software early and often, on a staging environment you can click through.
- 04
Handover and support
Source code, access, documentation and runbooks, with ongoing support if you want it.
Related notes
- 11 Nov 2026MT5 Manager API vs Web API: which one should your back office use?From production work
- 11 Nov 2026Designing an MT5 investor portal with wallets and IB commissions: the five questions that decide the buildDesign proposal
- 4 Oct 2026Building on the MetaTrader 5 Manager API: five lessons from a real-time risk monitorFrom production work
Questions
- Do you have your own MT5 server or Manager API licence?
- No. Manager API access belongs to the broker or the firm that licenses the MT5 server. I build with the access you have, and the first step is confirming exactly what that access allows.
- Manager API or Web API?
- Often both. The Manager API keeps a live local copy of users and positions, so reads take milliseconds, which is what monitoring needs. The Web API is plain HTTPS and easy to call from any backend, and is fine for low-volume reads and for writes. I have used both on the same platform.
- Can one integration read accounts at several brokers?
- Not with one login. A Manager or Web API login is tied to a single broker's server. Several brokers means one access route per broker behind a common adapter, and accounts identified by server and login together.
- Which languages do you use for MT5 work?
- C#/.NET on the native Manager API in production. I have also worked with MetaQuotes' Python manager package in my own prototype, tested against a simulator. The rest of your backend can be in any language: it talks to the MT5 service over HTTP.
- Can you fix an existing MT5 integration?
- Yes. Slow reads, accounts showing the wrong figures and rule calculations that disagree with the terminal are problems I have traced and fixed. I reproduce the problem and prove the cause before changing code.
- Do you build Expert Advisors, indicators or trading bots?
- No. I build server-side systems for firms: integrations, monitoring, back offices and portals. Not strategies or signals.
Tell me what you are building.
A few lines are enough: what it is, where it stands today, and what you need from an engineer. The form is just below, or email me if you prefer. I reply within two working days.