Blog
Background, process, and examples covering custom indicators and automated trading strategies on ATAS.
For a manual trader, rollover is a date in the calendar. For a bot, it hits the test data, the live orders and every level calculated across the switch - all at once.
Renko and range bars filter out noise because bars form on price movement rather than time. That same property makes backtests on these charts deceptively smooth.
A forward test is the first check without hindsight. Its value lies less in the result than in how it deviates from the backtest - provided you compare the two the right way.
A strategy you've traded yourself for months feels unambiguous. Only when it gets programmed does it show how many decisions were quietly being made in your head.
MetaTrader 5 and ATAS often get compared as if they sat on the same shelf. What really separates them is less the feature list than the question of which data exists at all.
A signal sitting perfectly at the low on your chart often didn't exist yet when the low formed. That gap between hindsight and real time is called repainting.
A time window written into the code as a constant is wrong several times a year - no error message, no crash, just different trades.
A large order resting in the book is not a commitment. It can disappear in the same second it was read - and that is where most automated order book rules fall apart.
A footprint always shows the same raw data - but a different question depending on the mode. Choosing the view decides what can become visible at all.
Between the signal and the fill sits a price difference no backtest accounts for on its own. With small targets, that difference decides the entire expectancy.
High-impact releases are the one source of danger known days in advance. That's exactly why they belong in the bot's logic - but not the way most people build it first.
CVD sums aggressive buying against aggressive selling. But the real decision when building one is a different question entirely: when the sum starts over at zero.
The prettier the backtest curve, the more skeptical you should be. Here's how overfitting arises, how to spot it, and how to avoid it when building a strategy.
A single imbalance is a footprint. Three on top of each other are a zone. Here's how stacked imbalances form and what actually matters when detecting them automatically.
The higher timeframe says what to trade, the lower one says when. Here's how to build that principle cleanly into an automated strategy.
Both explain why a move stalls - but for completely different reasons. Here's the difference, and what it means for detecting them automatically.
Breaking out of the trading range from the first minutes after the open - one of the best-known strategies for US futures. Here's how that becomes an automated ATAS bot.
Price makes a new high, delta doesn't confirm it - a classic early warning sign in order flow. Here's how delta divergence gets built reliably as a custom ATAS indicator.
Every ATAS indicator used to fire its own, independent alert. Webhooks now let multiple conditions combine into a single, reliable signal.
ATAS already ships with several volume profile tools. A custom variant is still often worth it - here's when and why.
A bot that only knows entries and exits but never calculates position size is incomplete. Here's how risk management gets built cleanly into an automated ATAS strategy.
Both platforms are built around order flow, but they emphasize very different things. Here's how ATAS and Bookmap actually differ - and where custom development makes sense for each.
A bot is only as reliable as the machine running it. Here's what actually matters for running an ATAS bot continuously - and when a VPS becomes necessary.
Spotting ICT concepts like Fair Value Gaps and Order Blocks by hand takes time and is error-prone. Here's how to turn them into a custom ATAS indicator that detects them automatically.
Pine Script and C# solve the same problem in fundamentally different ways. Here's what actually matters when porting a TradingView indicator to ATAS.
A trading bot alone doesn't make your trading commercial - but past a certain point, it can. Here are the criteria German tax authorities actually look at.
Both platforms let you build custom tools in C#, but they're built for different jobs. Here's how ATAS and NinjaTrader actually compare once a ready-made indicator isn't enough anymore.
A lot of failed challenge attempts come down to execution, not strategy. Here's what to check before automating one on ATAS - and what no bot can fix for you.
Many traders have a very precise idea of their ideal indicator - they just haven't found one in the store that matches it exactly. Here's how custom development works.
Executing a signal manually under time pressure is error-prone. An automated strategy follows a fixed rule set instead - here's how a bot like that comes together.
ATAS already ships with an extensive order flow toolkit. Most experienced traders still hit a wall eventually - that's exactly where the ATAS API comes in.
