summary: edgeful algos work with prop firm accounts and across multiple accounts and brokers. here's what you need to know about compatibility, automation rules, multi-account setup, copier vs direct signals, self-hedging risk, and the prop firm simulator.
single source of truth for compatibility: broker and prop firm support changes over time, so we maintain one dated compatibility matrix. see which broker accounts work with edgeful algo automation? for the current, verified list. check it before you connect; the guidance below explains how to run prop firm and multi-account setups.
supported brokers and account types
edgeful's automation works with Tradovate, NinjaTrader (brokerage), and ProjectX. many prop firms run their challenge and funded accounts on one of these platforms.
for the full list of supported and unsupported brokers, see which broker accounts work with edgeful algo automation?
don't see your broker? you can still use edgeful by manually executing trades. set up TradingView alerts for entry, stop-loss, and take-profit levels, then execute them manually on your broker's platform.
which prop firms are supported
if your prop firm clears through Tradovate or uses ProjectX as its infrastructure, you can connect it the same way as a standard account. to find out which infrastructure your prop firm uses, check their FAQ or contact their support team directly. look for the platform name they use for trade execution. that's the connection point.
prop firms using Rithmic
a Rithmic connection can't be automated. that's about the platform your account connects through, not the prop firm: Apex, for example, also offers Tradovate, and an Apex account connected via Tradovate automates normally. you can still use all of edgeful's algo tools for backtesting and analysis, but you'll place trades manually. for the full list of supported and unsupported brokers, see which broker accounts work with edgeful algo automation?
checking your firm's rules on automation
even if your prop firm uses a supported broker, you still need to confirm that automated trading is permitted under their challenge or funded account rules.
prop firm policies vary significantly. some permit fully automated trading with no restrictions. some allow automation but prohibit trading within the first few minutes of the session, which affects ORB setups specifically. some require manual execution only.
the right move is to read their terms of service and, if it's not clear, contact their support team directly before running automated strategies on a live challenge account. edgeful doesn't make specific recommendations on which prop firms to use or guarantee compatibility with any firm's current rules — policies change, and you're responsible for staying within your firm's guidelines.
multi-account setup
the rule in one line: 1 broker account = 1 strategy in edgeful = 1 webhook URL. every TradingView alert that trades that account (one per algo, per ticker) uses that same webhook URL.
the setup matrix
every multi-account and multi-algo question comes back to that one rule plus 2 conflict rules: one algo indicator per chart tab, and one algo per ticker per account at a time. find your setup below.
your setup | allowed? | strategies / webhook URLs | TradingView alerts |
the same algo on N accounts | yes | N strategies, N webhook URLs (one per account) | N alerts, one per account, each pasted with its own account's webhook. the alerts can all sit on the same chart |
N different algos on one account | yes, as long as they're on different tickers or their sessions never overlap | 1 strategy, 1 webhook URL | N alerts, one per algo, each algo on its own chart tab, all using the same webhook |
the same algo on several tickers, one account | yes (watch combined margin and exposure) | 1 strategy, 1 webhook URL | one alert per ticker, all using the same webhook |
the same ticker on different accounts | yes | one strategy per account | one alert per account, each with its own account's webhook |
two algos on the same ticker in the same account | no, unless their sessions never touch or overlap | — | send the second algo to a different account instead. the only exception is fully separate sessions, because each algo closes out at the end of its session |
two algos (or two variants) stacked on one chart tab | no | — | each algo indicator needs its own chart tab |
how many accounts per subscription | no cap | one all access subscription covers every account you connect | — |
trade copier | edgeful has no built-in trade copier | each account runs on its own direct signal | a third-party copier is optional and sits outside edgeful (see below) |
what's a "chart tab"? a separate TradingView chart with one edgeful algo indicator applied. you can open several charts side by side, even on the same ticker. the rule is one algo indicator per chart tab. the alerts you build on that chart can point at one account's webhook, or, when you run that same algo on several accounts, you can build one alert per account on the same chart.
for the conflict rules in full (sessions, manual trading, max loss, day-of-week), see running multiple algos — rules and conflicts.
prop sim-funded accounts show as "paper." a sim-funded prop account (a Tradeify sim funded account, for example) shows as paper in the algo dashboard. that's expected. when your firm moves the account (to live or funded, for example), refresh the broker connection so the change comes through: click + add broker and re-enter your details. don't delete the broker to do this — deleting a broker deletes every strategy attached to it.
how many accounts can one all access subscription run?
there's no cap. one all access subscription ($299/mo) lets you connect and automate as many broker accounts as you want — 1 prop firm PA, 5 of them, a personal account running alongside them, whatever your setup looks like. the subscription unlocks the automation feature; it doesn't meter how many accounts you run through it.
the only thing that scales with account count is setup: each account needs its own strategy in edgeful and its own webhook URL (see the table below). so 5 Tradovate PAs all running the same algo = 5 strategies and 5 webhook URLs, all under the one $299 subscription.
one caveat on Rithmic. a Rithmic connection can't be automated through edgeful at all, so if your Apex (or any other) accounts connect via Rithmic, you'll use the algos for backtesting and analysis and place the trades by hand. if your firm also offers Tradovate, connect through that and those accounts automate normally. Tradovate and ProjectX (Topstep / TopstepX) PAs automate normally, with no per-subscription limit on how many you connect. details in which broker accounts work with edgeful algo automation?
you can run algos across multiple accounts in 2 ways:
separate Tradovate logins: use unique credentials for each account. click Connect broker in edgeful and log in to each account sequentially.
Tradovate sub-accounts: create multiple sub-accounts (including demo) within a single login, and edgeful recognizes each as a separate entity.
either way, each account gets its own strategy in edgeful, and each strategy generates its own unique webhook URL.
common multi-account scenarios
find your setup in this table. it tells you exactly how many strategies, webhook URLs, and TradingView alerts you'll need.
your setup | strategies in edgeful | webhook URLs | TradingView alerts |
5 Tradovate accounts, all running the same algo | 5 | 5 unique URLs | 5 (each alert uses its account's webhook) |
1 account, running ORB + IB (on different tickers, or sessions that never overlap) | 1 | 1 URL | 2 (one alert per algo, each algo on its own chart tab, both pointing at the same webhook) |
1 personal Tradovate + 1 prop firm Tradovate | 2 | 2 unique URLs | 2 (each alert uses its account's webhook) |
SIM + live for the same algo | 2 | 2 unique URLs | 2 (don't mix them up — wrong webhook = wrong account) |
Same algo on NQ and ES on the same account | 1 | 1 URL | 2 (one chart per ticker, both pointing at the same webhook) |
3 prop firm accounts + 1 personal account | 4 | 4 unique URLs | 4 (each alert uses its account's webhook) |
2 algos on each of 3 accounts | 3 | 3 unique URLs | 6 (2 alerts × 3 accounts; each alert uses its account's webhook) |
name your strategies clearly when you have several ("Apex Live 01," "Tradovate SIM," "Topstep Funded NQ") so you don't paste the wrong webhook URL into the wrong TradingView alert. that mistake routes trades to the wrong account, which is the most expensive multi-account error to make.
trade copier vs direct signals — how edgeful runs multiple accounts
edgeful doesn't have a built-in trade copier. there's no master account that the others mirror. each account runs on direct signals: its own strategy, its own webhook URL, and its own TradingView alert that fires independently. when the alert fires, the order routes straight to that account.
that distinction matters when you're deciding how to run several accounts:
direct signals (the edgeful model): every account gets the same signal at the same time, straight from TradingView. there's no single master account whose fills everything else inherits, and each account's execution is independent. the tradeoff is setup: you build one strategy plus one alert per account (see the table above).
a third-party copier: one master account trades and a copier service mirrors those fills into the others. fewer alerts to manage, but you add a dependency, a copy delay, and a master account that everything else is tied to. if you go this route, edgeful drives the master via its webhook and the copier handles the rest, but the copier sits outside edgeful, so its behavior, and any prop-firm rules about copiers, are on you to confirm.
for most members, direct signals is the cleaner setup: the per-account alerts are a one-time build, and you avoid the copy-delay and shared-fate risk of a copier.
self-hedging and opposite positions across accounts
watch this one if you run the same algo across multiple prop accounts, or run both directions at once. when several accounts fire the same signal they all take the same side, and that's fine. the risk is when accounts end up holding opposite positions at the same time:
running a long-only version on one account and a short-only version on another, on the same instrument, at the same time
a copier or a misrouted webhook sending the wrong side to one account
trading correlated instruments (ES and NQ, or MES and ES) in opposite directions across accounts
two reasons this matters. first, opposite positions offset. you pay spread and commission on both sides for little net exposure, which rarely helps. second, and more important: many prop firms prohibit hedging (holding opposing positions across accounts, or self-hedging within one), and breaking that rule can fail a challenge or void a funded account. some firms (Lucid among them) treat cross-account hedging as a hard violation.
before you run multi-account or multi-direction setups, read your firm's rules on hedging and opposite positions, and double-check each strategy's direction filter and webhook so you're not accidentally short on one account and long on another. edgeful doesn't enforce a firm's hedging rules for you — staying inside them is on you.
Topstep and NinjaTrader
Topstep X: supported via ProjectX API. check your prop firm's rules on algo usage before you start. note that Topstep requires continuous contracts for both backtesting and live trading.
NinjaTrader: automation is supported. connect your NinjaTrader brokerage account directly in edgeful. both platforms let you automate across multiple brokers by creating separate strategies for each account, each linked to its own webhook.
drawdown limits and challenge rules
prop firm challenges typically have drawdown rules that your algo needs to stay within: either a fixed drawdown limit, a trailing drawdown, or both.
the ORB and engulfing algos have a max loss setting on the indicator in TradingView: a dollar cap on each trade (the IB algo doesn't have one, and there's no built-in daily limit). setting this to a level below your firm's daily drawdown limit is one way to add a safeguard, but understand that this is a soft limit based on your strategy parameters, not a guaranteed hard stop.
the most reliable way to evaluate your settings before going live is the prop firm simulator in the algo analyzer. upload your TradingView backtest data, set your firm's drawdown and profit target rules, and the simulator will show you how your algo would have performed against those constraints historically. the algo optimizer runs the same simulator on any result, with no export needed (see the next section). this is the right step before running any challenge, not after.
the fastest route: build it in the optimizer, then run the prop firm sim
you don't have to start from a TradingView backtest. the algo optimizer can build settings around your account's rules and test them against your firm's evaluation in one place.
open the optimizer. go to algos → algo optimizer, then pick your ticker and algo. if you'd rather start from settings that are already optimized, the algo templates page has them
set constraints from your account's rules. turn on max drawdown $ and set it just below your account's max loss, so every result already fits inside it. add min trades, and min win rate % if you prefer a strategy that wins more often than it loses
run it and read the ranking. results come back ranked by score, which weighs drawdown and consistency alongside P&L and win rate, so the top result isn't simply the biggest earner. tight constraints can return fewer than the full top 20
open a result and click prop firm sim. pick your firm and plan (or custom). the sim replays that result's trades through the evaluation rules and shows the pass rate for each account size, the average trades to pass, the fastest pass, and what caused the failures
read the warnings. the sim flags it when your largest single loss, or your average trade, is big relative to the account's drawdown limit. that usually means you need a smaller size or a bigger account
a pass rate is a simulation built from past trades, not a promise about the next challenge. treat it as a comparison tool: the higher it is, the less likely a bad run of trades stops you. and before you run anything live, confirm your firm allows automated trading on that account (the "checking your firm's rules on automation" section above covers how).
for the full optimizer walkthrough, see algo optimizer. to run the same simulator on a TradingView backtest, see algo analyzer.
the recommended workflow for prop firm traders
confirm your prop firm uses a supported broker
read your firm's terms of service on automated trading (including any rules on hedging or copiers)
find your settings in the algo optimizer with a max drawdown constraint set below your firm's limit, or backtest your chosen algo (ORB, IB, or engulfing) in TradingView's strategy report (formerly the strategy tester)
run the prop firm sim on the optimizer result, or put your TradingView backtest through the algo analyzer's prop firm simulator, using your firm's specific drawdown and profit target rules
optimize your settings until the simulated results stay within the firm's parameters
connect your account in edgeful, generate your webhook URL, and set up your TradingView alert
test on a demo account first before going live on the prop firm challenge or funded or a live cash account.
each of those steps matters. skipping the simulator before a live challenge is the most common thing members regret.