Semi-Automated vs. Fully Automated Trading: What Prop Firms Actually Allow
Both count as 'automated trading' in a prop firm's terms of service, but they're not interchangeable — and on at least one major firm, which one an account uses on a funded account isn't optional.
Reading "automated trading" in a prop firm's terms of service doesn't settle much on its own — a TradingView strategy firing a webhook and a fully hands-off broker-API bot are both technically automated, but they aren't treated the same way by every firm. Knowing which category a setup falls into, and what a specific firm expects for each, matters before running either one on a live evaluation.
Semi-automated trading: Pine Script plus alerts
Semi-automated trading means a strategy generates signals on its own, but order execution runs through a human-monitored alert layer rather than a direct API connection.
The typical flow: a Pine Script strategy runs in TradingView with alerts attached to its entry and exit conditions. When a signal fires on a confirmed bar close, TradingView sends a webhook to TradersPost or PickMyTrade, which places the corresponding order at the broker. A trader is watching the chart — not clicking the order, but present and able to intervene.
On Apex Trader Funding's live Performance Account specifically, this is the required style for a commercial or resold strategy — allowed during the evaluation. not allowed for commercial/resold automation on live performance accounts — a script may still drive manual-confirm execution.
Fully automated trading: direct broker API
Fully automated trading connects a program directly to a broker's API — Tradovate's REST API, NinjaTrader's C# framework, a Rithmic data connection — and places orders with no human reviewing each one. The program watches market data, runs its own logic, and can trade on a schedule with nobody at the screen.
This is more flexible than the webhook approach: custom order types, dynamic sizing, and multi-leg logic that Pine Script can't express are all possible. It's also more infrastructure — a running server, API credentials to manage, and ongoing maintenance.
MyFundedFutures is notably permissive here: explicitly permitted on both the evaluation and the live funded account — one of the few firms allowing this on both phases. That's a real point of difference from firms that only bless full automation on the evaluation and pull it back once an account is funded.
What actually gets an account flagged
Neither style is inherently risky under normal operation. What draws a compliance review is a specific pattern, not the automation style itself.
Volume anomalies
An unusually high number of orders per session, especially with rapid cancellations, reads as HFT-adjacent regardless of intent. A strategy entering once or a handful of times a session never approaches this.
Co-location signatures
Orders arriving faster than any human-monitored connection could realistically achieve suggest co-located infrastructure — a hardware and networking concern, not something a standard cloud VPS or home connection can produce by accident.
Latency arbitrage patterns
Trades that consistently land during the brief window a firm's price feed lags the real exchange, and that are consistently profitable in that exact window, suggest a strategy built specifically around that lag — not something an indicator-based system does by chance.
Cross-account copy trading at the same firm
Running identical trades across multiple accounts at one firm simultaneously is a risk-concentration issue the firm cares about regardless of whether the trades were placed by a human or a bot.
Choosing between the two
| Semi-automated (TradingView + webhook) | Fully automated (API bot) | |
|---|---|---|
| Setup complexity | Low — Pine Script plus a TradersPost account | High — broker API, a hosted server, ongoing code maintenance |
| Ongoing cost | TradingView plan plus TradersPost, roughly $30–60/mo combined | Server costs, plus developer time if something breaks |
| Backtesting | Built into TradingView's Strategy Tester | Custom or third-party tooling required |
| Flexibility | Limited to what Pine Script can express | Full programming language, effectively unlimited logic |
| Firm-specific limits | Required style on Apex's live funded account | Explicitly allowed on both phases at MyFundedFutures |
| Best for | Most futures prop firm traders running one or two strategies | Developers with logic Pine Script genuinely can't express |
For most futures prop firm traders — running a strategy or two on MES, MNQ, ES, or NQ during US market hours — semi-automated via TradingView is the practical default. Setup is fast, backtesting is built in, and it already satisfies the stricter of the two standards used by any major firm.
The practical workflow
- Write or buy a Pine Script strategy and backtest it in TradingView's Strategy Tester against several years of data
- Connect TradingView alerts to TradersPost or PickMyTrade with the strategy's JSON webhook payload
- Link that service to the Tradovate or Rithmic account tied to the evaluation
- Set the strategy live — orders fire automatically at bar close, monitored rather than clicked
See our TradersPost setup walkthrough for the exact connection steps, and which firms allow what for a full firm-by-firm breakdown.