ATAS, Sierra Chart and Bookmap all display order-flow information, but they put their generality in different places. This page compares the architectural axes that decide how each platform is configured, and where each one forces a compromise. It is a structural comparison; nothing here is a recommendation to acquire anything.
01 Chart engine
ATAS treats the footprint bar as a first-class bar type: aggregation, cluster mode and profile construction are engine-level concepts, so a panel is defined once and every view inherits the definition. Sierra Chart assembles chart bars and studies as separate layers, which allows arbitrary composition of bar types and studies at the cost of more configuration surface. Bookmap begins from the order book: its primary surface is a liquidity heat map, and price-and-time charts are derived views over the reconstructed book.
The consequence for configuration is direct. In ATAS the work is in choosing the right bar rule and cluster mode; in Sierra Chart it is in assembling the study stack; in Bookmap it is in deciding how much book history to reconstruct and display.
02 Order-flow depth
Depth handling differs in what is retained. A ladder that shows resting size at a moment is not the same as a heat map that retains the history of resting size. The first supports decisions about the current queue; the second supports pattern recognition over time. ATAS provides the first through its depth ladder configuration, with aggregation steps and pull-and-stack annotations described on the Smart DOM depth settings page.
| Axis | ATAS | Sierra Chart | Bookmap |
|---|---|---|---|
| Chart engine | Integrated engine; footprint and profile are bar-type level concepts | Modular engine; chart bars and studies composed as separate layers | Book-first renderer; heat map primary, price charts derived |
| Order-flow depth | Configurable depth ladder with aggregation steps and event annotations | Depth-of-market study with per-chart configuration | Reconstructed book history with liquidity heat maps |
| Replay model | Recorded tick playback inside the same chart objects | Historical series replay across bars and ticks | Recorded book replay with heat-map animation retained |
| Footprint support | Native cluster modes: bid x ask, volume, delta, diagonal imbalance | Numbers bars with extensive per-cell configuration | Footprint overlay with volume-dot modes inside the heat map |
| Extensibility | Per-panel indicator instances and reusable input templates | Large study library plus user study sources | Add-on layer focused on book-derived indicators |
03 Replay model
Replay is where configurations are validated, so the model matters as much as the display. A tick replay inside the same chart objects — the ATAS approach — reproduces the live panels exactly, which makes a session reviewable with the same instance inputs. A bar-series replay is cheaper in storage but cannot show intra-bar sequence. Book replay is the most faithful to the original environment and the heaviest in storage.
- Same-object replay — best for configuration verification.
- Series replay — best for reviewing higher-time-frame structure.
- Book replay — required whenever the ladder itself is the object of study.
04 Extensibility and configuration depth
Extensibility describes how much of the platform can be redefined without leaving it. A platform with per-instance inputs and templates allows a desk to standardise its panels without writing anything new. A platform with user-authored studies allows behaviour that the vendor never anticipated, at the cost of maintaining that code. Neither approach is superior; the choice depends on whether the desk's value is in standardisation or in bespoke measurement.
Every platform above forces one compromise. Configuring footprint and profile as engine concepts means accepting the vendor's set of cluster modes. Assembling studies means accepting more surface to keep consistent. Starting from the book means accepting larger storage and a different visual idiom.
05 Choosing by task, not by reputation
Pick the platform whose primary surface matches the recurring task. If the recurring task is reading cluster structure at a fixed aggregation, engine-level footprint configuration is the shortest path. If it is comparing many study variants, a modular study stack is the shortest path. If it is studying how liquidity evolved through a session, a reconstructed-book surface is the shortest path.
Common configuration questions about all three are answered on the FAQ page, and the vocabulary used throughout this comparison is defined in the glossary.