which markets edgeful supports
edgeful reports and algos work with:
US futures — ES, NQ, YM, RTY, CL, GC, MES, MNQ, MBT, and more
stocks and ETFs — SPY, QQQ, AAPL, and any ticker on major US exchanges
forex — EUR/USD, GBP/USD, and other major pairs (broker dependent)
crypto — BTC, ETH, and other pairs (broker dependent)
international futures — DAX and other non-US contracts (with some caveats)
the reports on edgeful.com cover 150+ instruments. the algo automation is available for any ticker your broker supports — but there are important setup differences depending on what you're trading.
the timezone factor
edgeful reports and algos use the NY session as the default reference point. that means:
the "session open" is 9:30 AM ET
the "previous session close" is based on the NY close
gap calculations, IB ranges, and ORB timing all anchor to Eastern Time
if you're trading from a different timezone, this doesn't change anything about how the data works — but it changes when things happen for you.
example: if you're in Europe and trading DAX with edgeful's ORB algo, the ORB window starts at 9:30 AM ET (3:30 PM CET). that's the NY session ORB — not the Frankfurt open. make sure this aligns with how you actually want to trade.
you can customize session times in the algo indicator settings on TradingView. if you want the ORB to reference a different opening window (say, the Frankfurt open at 9:00 AM CET), adjust the time inputs on the indicator accordingly.
algo-specific considerations
ORB (opening range breakout)
works on any ticker. the opening range window is customizable — 5-minute, 15-minute, or 30-minute. default is based on the NY session (9:30 AM ET), but you can change the start time in the indicator settings.
for non-US markets: adjust the ORB start time to match the session open you're targeting. if you're trading DAX and want to capture the European session open, set it to your preferred local open time.
IB (initial balance)
the IB is specifically defined as the first hour of the NY session — 9:30 to 10:30 AM ET. this is a fixed concept in market structure.
for non-US markets: the IB concept still applies if your market has a defined session open. but the edgeful IB report data on the website is calculated from the NY session. if you're applying IB logic to DAX or forex, you're using the indicator on your chart (which you can customize) — not the pre-calculated report data.
gap fill
works on any ticker. the "gap" is measured from the previous session close to the current session open. which session counts as "previous" depends on the indicator settings.
for futures and forex: use the "gap fill by session" variant, which references the NY session close instead of a calendar-day close. for non-US instruments, make sure the session settings in the indicator match the session you're actually trading.
engulfing
pattern-based — works on any ticker, any timeframe. no session dependency. this is the most straightforward algo to use on non-US markets.
TradingView setup for non-US tickers
contract symbols
TradingView uses exchange-specific symbols. a few things to watch:
DAX futures — use the correct exchange prefix. the symbol format varies depending on your data provider (e.g., FDAX1! for continuous on EUREX)
forex — use standard pairs (EURUSD, GBPUSD). make sure your TradingView data subscription covers forex if it's not included in your plan
crypto — use exchange-specific symbols (BINANCE:BTCUSDT, COINBASE:BTCUSD, etc.)
for backtesting, use continuous contracts (the "1!" suffix) to get uninterrupted historical data. for live alerts, you may need the specific front-month contract — check your broker's requirements.
data subscriptions
TradingView charges separately for real-time data on different exchanges. if you're trading DAX, you'll need EUREX data. if you're trading forex, check whether your TradingView plan includes it or requires an add-on.
this is separate from edgeful — it's a TradingView billing item. if you already have real-time data through your broker (NinjaTrader, Tradovate), you still need TradingView data separately for the alerts to work correctly.
chart timezone
set your TradingView chart timezone to match the session you're trading. this doesn't change the data — but it makes the chart easier to read and ensures your indicator time settings make sense visually.
go to TradingView chart settings → timezone → select your preferred timezone (or use "exchange" to match the instrument's native timezone).
broker compatibility for non-US markets
the supported brokers for edgeful automation are:
Tradovate — primarily US futures. some international products available depending on your account type
NinjaTrader (brokerage) — US futures and some international contracts
ProjectX (Topstep) — US futures only
if your broker doesn't support edgeful automation for the specific non-US instrument you want to trade, you can still use the algo indicators on TradingView manually. set up alerts for entries, TP, and SL — then execute the trades yourself at your broker. you won't get automated execution, but you'll get the algo signals.
Rithmic-based prop firms (Apex Trader Funding, etc.) do not support TradingView webhook automation. this applies to both US and non-US instruments.
what's not supported (yet)
pre-calculated report data for non-US instruments — edgeful's report library on the website is focused on US futures, stocks, and ETFs. you won't find a DAX gap fill report page with historical stats. the algos and indicators work on any TradingView chart, but the website report data doesn't cover every international instrument.
session-specific reports for non-NY sessions — the "by session" report variants (London, Asian) exist for US instruments. applying them to European or Asian-native instruments requires manual interpretation of the data.
these are product-level limitations, not bugs. as edgeful expands coverage, more international data will be added to the report library.