Futures Prop Firms That Allow Automated Trading
Most major futures prop firms allow automated trading — but the line between compliant algo trading and a rule-violating setup isn't always spelled out clearly, and it moves once an account goes from evaluation to funded.
The first question anyone building an automated strategy asks is whether the firm will actually allow it. The short version: yes, at every major futures prop firm, at least during the evaluation. The longer version depends on what a specific firm's compliance team considers "automated" — and on whether the account is still an evaluation or has already gone live and funded.
What "automated trading" means to a prop firm
Firms lump a range of approaches under this label, and treat them differently.
Semi-automated: TradingView alerts to a broker
A Pine Script strategy fires a signal on a confirmed bar close. TradingView sends a webhook to TradersPost or PickMyTrade, which places the order at the connected broker. A trader is watching, not clicking every fill. This is the most common setup among retail futures algo traders and is permitted, at minimum on the evaluation, at every firm covered below.
Fully automated: direct broker API, no human in the loop
A program connects straight to a broker's API, watches the market, and places orders without anyone reviewing each one. This is also broadly permitted — with one carve-out that matters everywhere: it can't cross into high-frequency territory.
What's banned everywhere
- High-frequency trading — orders placed in sub-second intervals to exploit microscopic price discrepancies
- Co-location / proximity hosting — running infrastructure physically near an exchange's matching engine for a speed edge
- Latency arbitrage — trading against the lag between a firm's own price feed and the real exchange
- Exploiting the firm's own systems — any strategy that profits from a firm's specific execution or simulated-fill quirks rather than real market behavior
Automation policy by firm
Always verify current terms directly before running a strategy live — policies shift, especially on funded accounts.
| Firm | Evaluation | Funded account | Key restriction |
|---|---|---|---|
| Apex Trader Funding | Yes | Manual-confirm execution only — no commercial/resold automation | No HFT, no co-location |
| Topstep | Yes, full automation | Policy has shifted repeatedly; semi-automated is the safer default | No HFT |
| TradeDay | Yes, via TradingView webhooks | Not specified in current terms — confirm directly | No HFT, no latency arbitrage |
| MyFundedFutures | Yes | Yes — explicitly permitted on both phases | No HFT, no co-location |
| FTMO (CFD accounts) | Yes, own-logic EAs | Yes, same own-logic condition | No shared public signal used by many accounts at once |
MyFundedFutures is the standout here — it's one of the only firms in this group that draws no line between evaluation and funded automation at all. Apex Trader Funding and Topstep have the deepest community tooling and documentation, but both carry a funded-account caveat worth reading closely rather than assuming a hands-off bot is automatically fine once the account converts.
The standard automation stack
The dominant setup for Pine Script traders at futures prop firms looks like this:
- Pine Script strategy in TradingView — runs on the chart, evaluates entry/exit logic on bar close, fires a webhook alert when conditions are met
- TradersPost or PickMyTrade — receives the webhook, translates it into a broker order, and manages the stop/target bracket
- Tradovate, Rithmic, or NinjaTrader — the brokerage account connected to the evaluation or funded account
The round trip from bar-close signal to order submission typically takes one to three seconds — orders of magnitude slower than anything resembling HFT. See our TradersPost setup walkthrough for the full connection steps.
What's actually not allowed
High-frequency trading
HFT means hundreds of orders per second exploiting sub-millisecond moves. Any strategy operating on 1-minute bars or higher, confirming entries at bar close, isn't within a mile of this category — even a strategy taking twenty trades a day.
Co-location and proximity hosting
Running a trading server in the same data center as an exchange's matching engine for a microsecond speed advantage. This requires contracting dedicated infrastructure from the exchange — nothing a retail TradingView + TradersPost setup can do by accident.
Latency arbitrage
Exploiting the gap between a firm's own price feed and the real exchange price. This targets the firm's infrastructure specifically, not real market behavior, and is banned everywhere.
Excessive order-to-fill ratios
Placing and immediately cancelling a very high volume of orders — a pattern associated with order-book manipulation. Standard strategies that enter once or twice a session never generate this pattern.
Cross-account copy trading at the same firm
Running identical trades simultaneously across multiple accounts at one firm is prohibited by most of them, especially during an evaluation. Running the same strategy across accounts at different firms is generally fine — check each firm's specific multi-account terms.
Keeping automation compliance risk near zero
- Bar-close entries only —
barstate.isconfirmedin Pine Script ensures a signal only fires after the candle closes, removing any appearance of intrabar scalping - Session filter — restrict trading to regular hours and pause around major scheduled news, which prevents the order-volume spikes that draw compliance attention
- Kill switch — a toggle input that disables new entries instantly without touching the underlying code
- Hard daily loss limit — a coded ceiling that halts trading for the session once hit, protecting the drawdown threshold and demonstrating systematic risk control
- Fixed contract sizing — no dynamic scaling based on account equity during the evaluation phase