How to Run an EA on TradeLocker, DXtrade, Match Trader and cTrader
Key takeaways
- An MT4 expert advisor cannot run natively on TradeLocker, DXtrade, Match Trader or cTrader, because each of those platforms executes its own code and its own order routing rather than compiled MQL4.
- There are only three honest options: rewrite the strategy natively for each platform, run the EA on a MetaTrader terminal and mirror its fills with a trade copier, or wait for the firm to release its own automation support.
- A native rewrite is the cleanest result and the most expensive one, because the same logic has to be rebuilt in C# for cTrader cBots, in NinjaScript for NinjaTrader, and against an API for the web based platforms.
- Pine Script on TradingView describes a strategy and fires alerts, it does not place orders on a broker or prop account by itself, so it always needs a bridge that receives the alert and submits the order elsewhere.
- A trade copier copies fills after they happen, which means the destination account always enters a little later and at a slightly different price than the source.
- The source MetaTrader terminal has to stay online for a copier to work at all, which in practice means a VPS rather than a laptop that sleeps.
- Copying between your own accounts is not the same thing as following someone else's signal, and firms often treat those two cases under different rules, so read your rulebook before you connect anything.
Can you run an MT4 EA on TradeLocker, DXtrade or cTrader?
No, not directly. An expert advisor is compiled MQL4 code, and compiled MQL4 only runs inside the MetaTrader 4 terminal. TradeLocker, DXtrade, Match Trader and cTrader are separate products with their own languages, their own APIs and their own order routing. There is no import button, no compatibility mode, and no file conversion that turns an .ex4 into something they can run.
That matters because many prop firms have moved off MetaTrader onto web based platforms, and platform choice keeps changing. A firm can add one, drop one, or run several at once, so never take a blog post as proof of what your firm offers today. Open your dashboard and check what your account is actually issued on before you buy anything.
If your automation is an MT4 EA and your account is not MetaTrader, you have exactly three options. Rewrite the strategy natively for the platform you were given. Keep running the EA on a MetaTrader terminal and mirror its fills onto the prop account with a trade copier. Or wait for the firm to ship its own automation support. Everything else is a variation of those three.
Why did so many prop firms leave MetaTrader?
Mostly because a prop firm never controls MetaTrader access on its own. The firm does not own the platform, it reaches it through a broker or a white label arrangement, and that arrangement can be repriced, restricted or withdrawn by parties the firm has no say over. Building on a platform it can contract with directly removes that dependency. Treat that as the structural explanation rather than a documented one, since firms rarely publish why they switch.
The newer platforms also fit how a challenge is actually policed. A challenge is a set of limits, and a platform the firm operates lets it evaluate those limits on its own servers, in real time, across every account at once, instead of reconciling terminal side data after the fact. That priority shows up in what gets built first. Order routing and rule enforcement come before a retail facing automation API, which is why automation support on these platforms tends to arrive later than the platform itself.
Can you rebuild an EA natively for cTrader, NinjaTrader or TradingView?
Yes, but once per platform and in a different language each time. Native means the logic runs inside the platform, on the platform's own connection, with no second terminal in the chain and no copying delay. That is the cleanest outcome and the most expensive one, because none of your MQL4 code carries over.
Here is what native automation looks like on the platforms prop firms hand out today. Platform feature sets change, so check current documentation, and verify each one against your firm's terms as well, since permission to automate is a separate question from technical possibility.
- cTrader runs cBots, written in C# against the cTrader Automate API. It is a real automation environment and the closest thing to a like for like replacement for MQL4, but it is a rewrite, not a port.
- NinjaTrader runs NinjaScript, also C#, and shows up more often on the futures side than the FX side.
- TradingView runs Pine Script, which can describe a strategy and fire an alert but cannot place an order on a broker or prop account by itself. Pine always needs a bridge that receives the webhook and submits the order somewhere that can execute it.
- TradeLocker, DXtrade and Match Trader are web based platforms that do not expose a retail strategy language in the MQL4 sense. Automation there generally depends on API access, and whether that access reaches you is decided by the firm or broker running the account, not by you.
What does a trade copier actually do, and what does it not do?
A trade copier watches one account and reproduces its activity on another. Your EA keeps running on a MetaTrader terminal, where it was designed to run. When it opens, modifies or closes a position, the copier reads that event on the source account and sends a matching order to the destination account on the prop platform. The prop firm sees ordinary orders arriving on its own platform.
The important word is reproduces. A copier does not move your strategy anywhere. It moves the results of your strategy, after the fact, which creates a short list of consequences you should understand before relying on one.
- It copies fills, not intentions. The source has to fill first, then the destination is told. That is a delay, small in normal conditions and larger when the market is fast.
- The source terminal must stay online. If the MetaTrader machine sleeps, loses connection or reboots for updates, copying stops and the destination account is left holding whatever it already has. This is why a VPS is standard practice rather than a nice to have.
- Prices will differ. Two accounts on two liquidity providers do not fill at the same number, so entry, exit and therefore result will differ between source and destination.
- Symbols and contract specs will differ. Symbol names, digits, contract size and value per point are set by each broker, so lot conversion has to be configured deliberately, not assumed.
- Stops and targets need care. A stop level based on the source price may not be the same distance from price on the destination, so protective orders should be checked on the account that actually carries the risk.
How should risk be set when a copier sits between two accounts?
On the destination account, always. The prop firm evaluates the account it issued to you. It does not see your source terminal, it does not care what your source equity curve looks like, and it will not accept slippage as an explanation for a breached limit. So every risk parameter that matters should be sized against the balance, the daily loss limit and the drawdown of the funded or challenge account.
Then leave a buffer. A copier introduces a small difference in entry price on every trade, and that difference is a permanent cost sitting between your model and your real result. Settings calculated to stop exactly at the limit will not stop exactly at the limit once a copier is in the chain. Give the numbers room to come out worse than planned, and treat the daily limit as a line you never trade up against. If your firm uses a trailing drawdown the buffer matters more, because the line moves with your equity high, as [trailing drawdown explained](/blog/trailing-drawdown-explained) covers.
Test on demo before capital is involved. Run the copier from source to a demo destination for at least a few sessions and compare fills side by side. What you are looking for is not perfection, it is the size and consistency of the difference. A small and predictable gap is a cost you can size around. Random gaps that widen on the trades that matter most are a warning.
Is copying trades between your own accounts against prop firm rules?
It depends on what is being copied, and rules vary by firm, so the answer lives in your rulebook rather than in a general article. Copying your own signal from your own MetaTrader terminal onto your own prop account is self replication. Copying a signal produced by someone else, a vendor, a Telegram channel or a signal service, is copy trading. Firms tend to treat those separately, and the second attracts far more restrictions than the first.
The reason is risk correlation, not technology. A firm funding hundreds of traders who all mirror the same external signal is not running hundreds of independent accounts, it is running one large position split across many logins. That is why many rulebooks group copy trading, group trading and third party signals together. Your own automation on your own accounts is a different exposure profile, though it carries conditions of its own, covered in [same EA on multiple prop accounts](/blog/same-ea-multiple-prop-accounts).
Rules vary by firm, so always check yours. If the wording is ambiguous, ask support in writing and keep the reply. Confirm two things specifically: whether the firm permits automation at all on the platform you were issued, and whether it separates your own accounts from third party signals. Do not assume permission because the firm markets to automated traders. [Are trading bots allowed on prop firms](/blog/are-trading-bots-allowed-prop-firms) is the longer version.
How PraxAI handles platforms outside MetaTrader
PraxAI is an MT4 expert advisor, with the PraxAI HFT Engine running on MT4 and MT5. That is where the logic lives and where it was built to execute. For accounts issued on other platforms, there is an optional trade copier at $10 per month per account, reaching MT5, cTrader, Match Trader, TradeLocker and DXtrade. It is an add-on, not part of the licence you buy: the licence is a single payment, the copier is a separate monthly subscription billed per account, so five accounts on other platforms means five subscriptions.
The second honest note is that a copier is still a copier, so everything above applies here too. The MetaTrader source has to stay online on a VPS, fills reach the destination a moment later, and prices will not match to the pip. That includes the protective side. PraxAI GUARD flattens positions and locks the account before a loss limit is violated, and it does that on the account it runs on, which is the MetaTrader terminal. The firm still measures the destination account, so the buffer you leave has to absorb the gap between the two. Rules vary by firm, so always check yours, and note that no software promises guaranteed income: trading always carries risk.
Which option should you actually pick?
Pick by how long you expect to be on the platform. If it is one challenge on one platform, a copier is almost always the cheaper answer, because a native rewrite costs weeks of development and testing before it places its first order. If you expect to be on the same non MetaTrader platform for years, and the strategy is worth the investment, a native build removes an entire failure point permanently.
Waiting for the firm to release automation support is a legitimate third choice, but treat it as a choice and not a plan. Roadmaps slip, and support that does arrive can arrive restricted, for example limited to certain account types or placed behind an approval process. Waiting is reasonable if you are already trading manually and automation would be an upgrade. It is not reasonable if your entire method is the EA and your challenge clock is running.
The one thing that should not vary is the order of operations. Confirm what platform your account is on. Read the rulebook on automation and on copying. Then choose the technical route. Traders who do it in the opposite order tend to discover the rule after they have paid for the solution.
Frequently asked questions
Can I run an MT4 EA on TradeLocker?
Not natively. TradeLocker cannot execute compiled MQL4 code, so an EA has to either be rebuilt against whatever API access is available, or kept running on a MetaTrader terminal with a trade copier mirroring its fills onto the TradeLocker account. Whether either route is permitted is decided by your prop firm's rules, not by the platform alone, so check your terms first.
Does DXtrade support automated trading?
DXtrade is a web based platform without a retail strategy language comparable to MQL4, so automation generally depends on API access being made available by the broker or prop firm operating the account. Many traders reach it instead with a trade copier from a MetaTrader terminal. Availability varies by provider, so confirm with your firm before assuming either path is open to you.
Is a trade copier allowed by prop firms?
It depends on the firm and on what is being copied. Copying your own signal between your own accounts is usually treated differently from copying a third party signal service, which tends to be more restricted because it correlates many funded accounts into one position. Rules vary by firm, so always read yours, and ask support in writing if the wording is unclear.
How much delay does a trade copier add?
Enough to matter for scalping and usually not enough to matter for slower strategies. The copier can only act after the source account fills, then it has to send an order to a different platform on a different connection, so the destination entry is always later and at a slightly different price. Test the actual difference on a demo destination account before you size positions around it.
Do I need a VPS for a trade copier?
In practice, yes. The source MetaTrader terminal has to stay running and connected for anything to be copied at all, and a personal computer that sleeps, updates or drops its connection will stop copying without warning, potentially leaving open positions unmanaged on the destination account. A VPS keeps the source terminal online continuously.
Can I convert an MT4 EA into a cTrader cBot?
Not by conversion. cTrader cBots are written in C# against the cTrader Automate API, so moving a strategy across means reimplementing the logic and then retesting it, since indicator handling, order execution and symbol specifications do not behave identically to MQL4. Budget for the rewrite plus validation, not for a translation.
Which prop firms still use MetaTrader?
That changes too often to answer reliably in an article, because firms add and drop platforms based on their broker and technology arrangements. Some firms offer MetaTrader alongside newer platforms, some have moved away entirely, and some vary it by account type. Check the firm's current platform list on its own site or dashboard before you commit.
Want the bot that runs this discipline for you?