FTMO HFT: Read the Conduct Rule, Not Just the Strategy Label
The phrase FTMO HFT does not by itself establish whether a particular implementation is permitted. FTMO's selected CFD forbidden-practices page, checked 24 October 2026, addresses conduct and platform activity. This guide records that scope without substituting a strategy label for the applicable agreement.
Explore the separate research worksheet on this site
The selected policy concerns what an implementation does
The reviewed CFD policy prohibits exploiting price errors or delayed feeds and using ultra-high-speed or other tools to manipulate, abuse or gain an unfair advantage. It also addresses hyperactive automated trading producing more than 2,000 server requests per day through relevant opening, modification or closing activity.
The request provision is not a blanket approval for anything below a numerical count. Other conduct, risk and account rules can apply independently. This guide does not declare all HFT permitted or prohibited across every FTMO product, including its separately presented Futures programmes.
A completed-trade count is not a request log
For an invented journal, one field records 40 closed trades and another contains an incomplete order-event log. Forty closed trades cannot establish that only 40 server requests occurred. Openings, pending orders, modifications and closings can be different observations.
Keep identifiers, event type, timestamp and the source of the count. Where the platform's actual counting method or complete log has not been verified, leave the request total unresolved. This is an audit distinction, not an implementation recipe or a way to evade a restriction.
| Record | Example | Do not infer |
|---|---|---|
| Closed trades | 40 invented completed trades | 40 total server requests |
| Order-event log | Incomplete | A complete count or zero activity |
| Selected policy provision | Read with all other conditions | A safe operating allowance |
| Another programme | Its own applicable rules | Permission transferred from FTMO |
Approval needs the selected product and actual behaviour
A software vendor's label, a backtest or an advertised trading speed cannot establish permission under a provider's current terms. The relevant review needs the exact programme, account stage, platform and behaviour, together with all applicable conditions.
This page does not run an EA, send orders, benchmark a platform, test a limit or determine a Canadian reader's eligibility. It does not provide a personal legal or compliance conclusion. No market or provider system was used for the illustrative record.
Carry the distinction into a different programme
A useful comparison keeps strategy description, conduct rules and actual system observations separately attributable. It does not copy one provider's numerical provision into another programme or treat a missing log as a zero count.
The optional HashHedge link concerns another programme. FTMO wording, a software label or the example trade count does not authorise an implementation there. Review the destination's own current conditions before registering.
Sources and rule dates
- FTMO: selected CFD forbidden trading practices
Checked 2026-10-24. Conduct and excessive-request wording only; not every product, a personal approval or a tested enforcement threshold.