A fight
MyForexFunds for Algo developers
MT4/MT5 EA policy is decent; the relaunch context means proof-of-payout precedes scaled deployment.
Persona: Fully systematic, EA / cBot deployed, latency-sensitive, backtest-driven.
Rules at a glance
MyForexFunds, the six numbers.
- Profit target
- 8.0%
- Daily loss cap
- 5.0%
- Max drawdown
- 8.0%(static)
- Payout cadence
- 14 days
- Recommended risk/trade
- 0.4%
- Status
- pending-relaunch
Persona context
How Algo developers think about prop firms.
Algorithmic operators care about a different rulebook entirely. The single most important rule is the firm's EA / "expert advisor" policy: some firms allow any EA, some ban scalping-class EAs, some require manual review of the code, and some explicitly disallow latency-arbitrage or copy-trade EAs. Second is API access — without an order-routing API, the algo has to drive a desktop MT4/MT5 instance via heuristics, which loses 50–200ms of latency. Third is the backtest-correctness story: most firms publish rules but not a deterministic simulator, so the algo trader has to build one themselves to pre-flight strategies. Slippage and spread modelling matter more here than for discretionary operators because edge is so much thinner.
- EA / bot policy
- API access vs platform-only
- Latency to firm bridge
- Backtest determinism (firm-rule simulator)
- Copy-trade / multi-account rules
The specific analysis
MyForexFunds × Algo developers.
Algo developers can run on MyForexFunds with the standard MT4/MT5 EA policy: expert advisors are permitted, with the usual exclusions on latency-arbitrage and copy-trade-internal. No native API, so the algo drives the desktop platform. The 8% static drawdown is friendly to backtest determinism, the floor doesn't move. The 5% daily cap is generous. The 8% target reaches in 4–6 weeks at a reasonable algorithmic pace. The genuine concern for algo developers is operational risk on the firm side: an algo running 24/7 generates more idle profit between payout cycles than a discretionary persona does, which is exactly the kind of idle capital that gets stuck if the firm has a payout-pipeline issue. The remediation is the same: take the smallest challenge first, verify two consecutive payouts, then scale.
Workarounds
- Run the algo at $25k or $50k first; scale only after two clean payout cycles
- Mirror the strategy on FTMO for redundancy
- Pre-flight against MFF's actual rules in the Glitch Executor backtester
Account killers
- A grid / martingale EA recovering on a deep adverse move breaches the static 8% DD
- Compounding profit at MFF for months without payout verification
Run the math
Three calculators pre-flight your strategy.
- Firm-rule drawdown calculator , project equity floor and breach distance under MyForexFunds.
- Firm-mode position sizing , recommended 0.4% risk-per-trade for a algo developer.
- Prop firm vs self-funded cost , total cost to pass MyForexFunds given your realistic pass-rate.
FAQ
Questions about MyForexFunds for algo developers.
Is MyForexFunds a good fit for algo developers?
MT4/MT5 EA policy is decent; the relaunch context means proof-of-payout precedes scaled deployment. Algo developers can run on MyForexFunds with the standard MT4/MT5 EA policy: expert advisors are permitted, with the usual exclusions on latency-arbitrage and copy-trade-internal. No native API, so the algo drives the desktop platform. The 8% static drawdown is friendly to backtest determinism, the floor doesn't move. The 5% daily cap is generous. The 8% target reaches in 4–6 weeks at a reasonable algorithmic pace. The genuine concern for algo developers is operational risk on the firm side: an algo running 24/7 generates more idle profit between payout cycles than a discretionary persona does, which is exactly the kind of idle capital that gets stuck if the firm has a payout-pipeline issue. The remediation is the same: take the smallest challenge first, verify two consecutive payouts, then scale.
What's the biggest rule risk for a algo developer at MyForexFunds?
A grid / martingale EA recovering on a deep adverse move breaches the static 8% DD
What risk-per-trade percentage do you recommend?
0.4% of equity per trade is the conservative starting point for a algo developer at MyForexFunds. Use Glitch Executor's position-sizing calculator to confirm the lot size respects both your risk budget and the firm's drawdown cushion.
Does the firm permit trading through high-impact news?
MyForexFunds enforces a news blackout around high-impact releases. Plan entries either fully before or fully after the release.
How does the drawdown rule work specifically?
MyForexFunds uses a static 8.0% drawdown anchored to the starting balance, it doesn't follow your highs.
Compare and shortlist
Where this fits in the wider research.
- Best prop-firm challenges shortlist
- MyForexFunds, full rule + payout brief
- Current prop-firm partner offers
- MyForexFunds drawdown calculator
Authored and reviewed by Ryan Tran (Strategy Lead, Glitch Executor). Last reviewed . Rule values pulled from the firm-rule registry in this repo; verify with MyForexFunds directly before funding.
Same firm, different personas