Workable
FTMO Phase 1 for Algo developers
MT4/MT5-friendly with permissive EA policy; broker spreads are the variable to model.
Persona: Fully systematic, EA / cBot deployed, latency-sensitive, backtest-driven.
Rules at a glance
FTMO Phase 1, the six numbers.
- Profit target
- 10.0%
- Daily loss cap
- 5.0%
- Max drawdown
- 10.0%(static)
- Payout cadence
- 14 days
- Recommended risk/trade
- 0.5%
- Status
- live
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
FTMO Phase 1 × Algo developers.
FTMO Phase 1 is workable for algo developers with one significant caveat: the platform is MT4 / MT5 only, with no native API access. Algos run as MQL4/MQL5 EAs against the firm's broker stable, and the broker mix means spread + slippage profiles vary significantly between accounts. The firm permits EAs without prior approval but disallows latency-arbitrage and tick-scalping classes (sub-1-second hold times trigger review). Copy-trade EAs are not permitted within FTMO accounts (no internal copying), but external copy from a master signal account is allowed. The 10% static DD makes backtest determinism much easier than trailing-DD firms, the floor never moves so historical replay is exact. Algo developers should reproduce the firm's spread profile in their backtest using FTMO's published broker spreads, not the broker's headline numbers.
Workarounds
- Backtest against 1.5× the broker's typical spread to model release-time widening
- Avoid sub-second hold-time EAs to stay clear of the tick-scalping rule
- Use Glitch Executor's firm-rule-aware backtester for deterministic pass/fail simulation
Account killers
- A grid EA that recovers via martingale will breach DD on a deep adverse move
- Latency-arb EAs are explicitly excluded, running one risks account termination
Run the math
Three calculators pre-flight your strategy.
- Firm-rule drawdown calculator , project equity floor and breach distance under FTMO Phase 1.
- Firm-mode position sizing , recommended 0.5% risk-per-trade for a algo developer.
- Prop firm vs self-funded cost , total cost to pass FTMO Phase 1 given your realistic pass-rate.
FAQ
Questions about FTMO Phase 1 for algo developers.
Is FTMO Phase 1 a good fit for algo developers?
MT4/MT5-friendly with permissive EA policy; broker spreads are the variable to model. FTMO Phase 1 is workable for algo developers with one significant caveat: the platform is MT4 / MT5 only, with no native API access. Algos run as MQL4/MQL5 EAs against the firm's broker stable, and the broker mix means spread + slippage profiles vary significantly between accounts. The firm permits EAs without prior approval but disallows latency-arbitrage and tick-scalping classes (sub-1-second hold times trigger review). Copy-trade EAs are not permitted within FTMO accounts (no internal copying), but external copy from a master signal account is allowed. The 10% static DD makes backtest determinism much easier than trailing-DD firms, the floor never moves so historical replay is exact. Algo developers should reproduce the firm's spread profile in their backtest using FTMO's published broker spreads, not the broker's headline numbers.
What's the biggest rule risk for a algo developer at FTMO Phase 1?
A grid EA that recovers via martingale will breach DD on a deep adverse move
What risk-per-trade percentage do you recommend?
0.5% of equity per trade is the conservative starting point for a algo developer at FTMO Phase 1. 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?
Yes, FTMO is the only firm in the supported set that explicitly permits holding through news, subject to a "dominant source" review at payout.
How does the drawdown rule work specifically?
FTMO Phase 1 uses a static 10.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
- FTMO Phase 1, full rule + payout brief
- Current prop-firm partner offers
- FTMO Phase 1 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 FTMO Phase 1 directly before funding.
Same firm, different personas