summary: edgeful isn't a build-any-strategy backtester where you write your own entries and exits and get an equity curve back. but a lot of what people mean by "backtest my strategy" you can do — every report is a historical backtest of a setup, you can customize and stack them to match how you trade, custom reports let you define and measure a setup of your own in plain English, and on all access the algos can be backtested in TradingView. here's the honest line between what's possible and what isn't.
first, what edgeful actually is
edgeful is a historical data platform, not a strategy IDE. it has already measured a large library of well-defined setups — gaps, initial balance, opening range, opening candle, sessions, ranges, and more — across years of history, and it shows you how often each one plays out.
you're not limited to that library either. with custom reports you can describe a measurement of your own in plain English and edgeful AI will write the analysis and run it against the data. what you still don't get is a place to code trade logic and have edgeful simulate fills and P&L. that framing is the key to understanding what you can and can't test.
what you can backtest
any report, over your lookback — that already is a backtest. when you run the gap report on NQ over the last year, you're backtesting "how often does the gap fill on NQ." same for IB breaks, ORB, opening candle continuation, and every other report. the percentages are the historical result of that setup. that covers a huge share of what traders are really asking when they say "can I backtest my strategy."
customize the setup to match how you trade. you're not stuck with defaults. change the session (NY, London, Asian), change the time window (for example a custom IB range like 10:20–10:30), and drill into the subreport breakdowns — by size, by rejection, by weekday, by close. that lets you test a much more specific version of a setup than the headline number.
build a report that measures your own setup. if the thing you want to test isn't one of edgeful's reports at all, build it. in the build tab inside edgeful AI you write the spec in plain English — what to measure, how to define each term, how to slice it — and edgeful AI writes and runs the analysis. it comes back with the method, the assumptions, and the code laid out over a 3-month sample so you can confirm it's measuring what you meant, then you save it and run it over any ticker, session, and date range. custom reports are included on every plan. full walkthrough: how to build custom reports with edgeful AI.
combine reports to test confluence. in edgeful AI's Analyze Reports flow you can stack up to 3 reports and ask the AI to find where they agree — and use the "find commonalities" prompt to surface the conditions that historically precede a given outcome. that's the closest thing to testing a multi-condition rule set without writing code. full walkthrough: how to analyze reports with edgeful AI.
backtest the algos in TradingView (all access). edgeful's algos run as strategies inside TradingView, so you can use TradingView's built-in strategy tester to backtest an algo's settings over history, then use the edgeful algo optimizer and algo analyzer to tune and review the results. this is the most "backtest my strategy" part of the platform — but it's testing edgeful's algo strategies with your settings, not arbitrary logic you've written. this is the one piece here that is tied to a plan.
what you can't do
get broker-style results for a rule set you write. a custom report measures how often something happens and what tends to follow it. it doesn't place trades, so it won't give you entries and exits, fills, slippage, a P&L curve, or a drawdown figure. if that's what you're after, that's TradingView's strategy tester on an edgeful algo, not a report.
upload your own indicator or strategy code for edgeful to run. you can't hand edgeful a Pine script and have it execute it against the data. describing what you want measured in plain English in a custom report is the supported path, and usually the faster one. (the other adjacent thing that exists: on all access, the algo analyzer lets you upload your own backtest results to review and analyze — but that's reviewing a backtest you already have, not edgeful generating one from your code.)
assume a custom report can measure anything you name. a custom report is built from the market data edgeful holds. if your setup depends on something outside that, the methodology check on the 3-month sample is where you'll see it — read the method and assumptions before you trust the numbers.
the practical path
if you've got a strategy in mind, the way to pressure-test it on edgeful is:
break it into the setups edgeful already measures. most strategies decompose into a few known pieces — a gap read, an IB or ORB break, an opening-candle bias, a session tendency.
run and customize those reports on your ticker, session, and time window to get each piece's historical odds.
build a custom report for the pieces that aren't covered. describe the measurement in the build tab and let edgeful AI write and run it.
stack them in edgeful AI to test whether the pieces line up the way your strategy assumes.
if you're on all access and want automation, build it as an edgeful algo and backtest that in TradingView.
for turning a report's numbers into an actual rule, start with from stats to trading rules.