Order Flow Platform Comparison

ATAS vs Bookmap: Footprint Cluster Analytics vs Market-by-Order Liquidity Heatmap

In an atas vs bookmap comparison, both platforms target microstructure order-flow traders on CME and Eurex futures, yet they visualize opposite sides of the auction: ATAS specializes in executed-volume cluster/footprint charts (`Bid x Ask`, Delta, Imbalance, Market Profile/TPO, and Smart Tape), whereas Bookmap renders a sub-millisecond GPU heatmap of resting limit orders across full Market-by-Order (`MBO`) depth alongside Volume Dots and Iceberg/Stop-Run trackers.

AI Quant Team, AI SIGNALS COMPANYUpdated: 4 min read

Key facts

Core analytical lens
ATAS: executed footprint clusters & TPO · Bookmap: resting MBO limit-order heatmap
Signature tools
ATAS: Bid×Ask Imbalance, Smart Tape, Big Trades · Bookmap: Heatmap, Iceberg & Stops
Futures data feeds
Rithmic, CQG, dxFeed (CME MBO Level 3 depth recommended on Bookmap)
Operating systems
ATAS: Windows .NET workstation · Bookmap: native Windows, macOS & web client
Where AISAS fits
Closed B2B AI macro/index regime research; zero order-book execution

Executed footprint clusters (ATAS) vs resting MBO liquidity (Bookmap)

Every futures trade occurs when an aggressive market order consumes a passive resting limit order. ATAS (Advanced Time And Sales) organizes that executed flow into customizable bar structures — time, range, tick, volume, or reversal footprints — displaying exact `Bid x Ask` contracts traded at every price step, diagonal bid/ask imbalances, per-bar Delta, Cumulative Volume Delta (CVD), and composite TPO / Volume Profiles.

Bookmap approaches microstructure chronologically along a continuous time axis without compressing ticks into discrete candlesticks first. Its GPU-rendered color gradient plots historical changes in every resting Level 2 / Level 3 limit price level, letting scalpers visually spot large liquidity walls sitting above `ES` or `NQ`, spoofing/pulling behavior ahead of price contact, absorption via proportional Volume Dots, and hidden Iceberg orders via CME Market-by-Order (`MBO`) order-ID tracking.

Side-by-side specification table: ATAS vs Bookmap

Comparison of ATAS and Bookmap based on official vendor documentation. Add-on modules, MBO data surcharges, and supported brokers evolve — verify current compatibility on atas.net and bookmap.com.
DimensionATAS (Advanced Time And Sales)Bookmap
Primary visualizationFootprint / Cluster bars, Volume Profile, TPO & Smart TapeContinuous 2D/3D historical order-book heatmap + Volume Dots
Passive depth analysisDOM Levels indicator & Smart DOM ladderFull MBO queue-level liquidity heatmap, Liquidity Tracker & Icebergs
Aggressive tape toolsSmart Tape (filtered aggregated prints), Big Trades, Stacked ImbalancesVolume Dots, CVD sub-chart & Stop-Run burst detection
CME MBO (Level 3) useSupported on compatible feeds for depth/DOM toolsCore strength: individual order-ID queue priority, Stops & Iceberg add-ons
Multi-timeframe contextStrong: daily/weekly TPO, VWAP bands & classical technical chartsFocused on ultra-short-term tick/second microstructure horizons
Extensibility / APIC# (.NET) custom indicators and automated strategiesJava / Python L1/MBO API for custom order-book add-ons
OS supportNative Windows (.NET) desktop applicationNative Windows & macOS desktop clients plus browser edition

Rithmic, CQG and dxFeed: why data feed selection matters

Neither ATAS nor Bookmap is a brokerage firm; both rely on external real-time market-data feeds to populate their charts. On CME Group futures (`ES`, `NQ`, `MNQ`, `6E`, `CL`, `GC`), feed capability directly determines which analytical features work:

  • Full CME Market-by-Order (MBO) via dxFeed or Rithmic: Transmits individual resting limit order IDs and sizes rather than just aggregated price-level totals. Bookmap's native Stops & Icebergs Tracker relies on MBO packets to distinguish genuine hidden liquidity refills from new orders.
  • Historical tick backfill for footprints: ATAS downloads historical tick-by-tick Bid/Ask history so that opening a 30-minute or 5-day Footprint and TPO workspace renders past clusters immediately without having to keep your PC running all week.
  • GPU and RAM considerations: Rendering sub-millisecond MBO depth across multiple instruments (`ES` + `NQ`) in Bookmap benefits from a dedicated GPU and ample RAM, whereas ATAS emphasizes multi-core CPU performance when calculating dozens of cluster indicators.

When to choose ATAS, Bookmap, or run both side by side

Traders who frame setups around Value Area High/Low, composite TPO profiles, anchored VWAPs, and bar-close footprint absorption typically prefer ATAS as their primary workstation. Ultra-short-term DOM/tape scalpers watching resting liquidity pulls and iceberg absorption on `ES` and `NQ` lean toward Bookmap — and many institutional futures desks run Bookmap on one monitor for resting-limit context while executing from footprint/DOM software on another. Compare more options in our top futures trading platforms guide and ATAS vs Sierra Chart comparison.

Where AISAS fits above micro-second order flow

Frequently asked questions

Does ATAS have a heatmap like Bookmap?

ATAS includes a DOM Levels indicator that plots historical resting depth on cluster charts, while Bookmap is purpose-built from the ground up around a high-frame-rate GPU Market-by-Order heatmap and order-ID Iceberg/Stop trackers.

Does Bookmap have Footprint and TPO charts like ATAS?

Bookmap offers footprint add-ons and volume profiles, yet ATAS provides a much broader native library of multi-timeframe Footprint modes, diagonal imbalance filters, Market Profile (TPO), and Smart Tape analytics.

Which data feed do I need for CME futures on ATAS or Bookmap?

Both connect to professional futures feeds such as Rithmic, dxFeed, and CQG (plus selected crypto exchanges). For full MBO Iceberg and queue-position tracking on CME contracts, verify that your feed subscription includes Market-by-Order depth.

Can macOS users run ATAS vs Bookmap natively?

Bookmap provides a native macOS desktop application alongside Windows and web versions, whereas ATAS is architected primarily as a Windows .NET desktop terminal (commonly run via virtualization on Apple Silicon Macs).

Does AISAS integrate into ATAS or Bookmap as an execution plugin?

No. AISAS is a standalone, closed proprietary AI research system by AI SIGNALS COMPANY P.S.A. with zero platform plugins, zero brokerage connections, and zero automated trading.

Sources

  1. ATAS — Official Order Flow, Footprint & Smart Tape Documentation
  2. Bookmap — Market-by-Order (MBO) Heatmap & Liquidity Add-ons
  3. CME Group — Market-by-Order (MBO) Globex Data Specification

Comparisons

Ready to see the analysis?

By submitting this form, you agree to our privacy policy and terms of service.