Inside Bookmap’s MBO Stops & Icebergs Add-On: Who Built It and Why It’s Not Built-In

he MBO Iceberg (Stops & Icebergs) add-on in Bookmap wasn’t built by an independent third-party developer or an external team—it is a flagship native add-on developed in-house by Bookmap’s core R&D team (under its parent company, VeloxPro).

The reason this add-on is widely considered the industry gold standard—and why developers from other professional platforms like Investor/RT or the Sierra Chart community struggle to replicate it—comes down to the team’s pedigree and its underlying algorithmic logic:

  • A Hardcore HFT and Quant Founding Team: Bookmap was founded in Israel by former high-frequency trading (HFT) system architects and quantitative traders, including Tsachi Zach (founder and former CEO) and Sergeyotes. Coming from a background in low-level matching engines and market microstructure, the team knows the CME’s underlying MDP 3.0 (Market Data Platform) packet architecture inside and out.
  • Proprietary Order ID Tracking Algorithm (Zero Guesswork): Most “iceberg detectors” on standard retail platforms rely on Level 2 (MBP) data, making probabilistic guesses when a price level shows small displayed liquidity but high traded volume—a method that frequently mistakes institutional millisecond-level order reloading for iceberg orders. In contrast, when the CME rolled out MBO (Market-By-Order) data in 2017, the Bookmap team leveraged the unique Order ID attached to every single order and the exact matching engine message sequence to build a 100% deterministic native iceberg detection algorithm. When the visible portion of a specific Order ID is exhausted and instantly refreshes at the same queue position, the add-on pinpoints the Native Iceberg right on the chart—tracking its Detection (D), Transactions (T), and full Execution (E).
  • Refined with Elite Floor and Screen Traders: While developing and iterating the MBO Bundle (which includes Stops & Icebergs On-Chart / Sub-Chart, Liquidity Tracker Pro, and more), the Bookmap team worked closely with elite practitioners like legendary Chicago S&P 500 futures ($ES) trader Scott Pulcini (featured in Enhancing Trader Performance, who once accounted for several percent of total daily $ES volume). This real-world feedback allowed them to turn the interplay between Stop Runs and Iceberg Absorption directly into actionable visual signals.

Simply put, this add-on is the crown jewel of the Bookmap team (VeloxPro), serving as the core technological moat behind their Global+ subscription and MBO Bundle.

There are four primary reasons why Bookmap packages its proprietary Stops & Icebergs (MBO) tool as a separate downloadable .jar add-on rather than hardcoding it into the main platform like CVD, VWAP, or standard Absorption and Sweeps:

1. Data Feed Specificity (MBO Is Exclusive to CME, Not Universal)

  • Built-In Indicators (e.g., CVD, VWAP, Absorption, Sweeps): These rely on standard Level 2 (MBP – Market By Price) depth-of-book data and Time & Sales tape data. Whether you are trading US equities (Nasdaq/NYSE), crypto (Binance/Bybit), or other futures markets, these metrics can be calculated the moment any standard feed connects. Because they work universally across all asset classes, they belong directly in the software core.
  • Stops & Icebergs (MBO): This module strictly requires the Chicago Mercantile Exchange’s (CME) proprietary MDP 3.0 MBO (Market By Order) data feed, transmitted via a provider that supports the full MBO protocol—specifically Rithmic or Bookmap Data. For traders who only watch crypto or US stocks, or who connect via feeds that don’t pass full MBO data (like CQG or Tradovate), this module cannot function at all. Decoupling it allows traders to load it strictly on demand.

2. Hardware Performance and Memory Footprint (Heavy Compute Load)

  • Standard Level 2 data only requires tracking the aggregate volume at each price tier. MBO data, on the other hand, requires real-time tracking of tens of thousands of individual Order IDs—monitoring their exact queue position, modifications, cancellations, and millisecond-level matching sequences (especially during high-velocity events like Non-Farm Payrolls, CPI releases, or the US cash open on $ES and NQ, where message traffic spikes massively).
  • Leaving the MBO parsing engine built-in and running by default would consume significant CPU and RAM resources, causing lag or chart rendering delays on lower-spec machines. Keeping it as a separate add-on ensures that only CME futures traders who actively need native iceberg tracking take on that processing load.

3. Monetization and Tiered Pricing Strategy

  • This is a classic software monetization model. Bookmap historically structured its core platform into tiers—Digital, Global, and Global Plus—while packaging institutional-grade tools into the MBO Bundle (comprising Stops & Icebergs Sub-Chart, On-Chart, Liquidity Tracker Pro, etc.).
  • Distributing it as a standalone add-on allows Bookmap to manage access permissions seamlessly via its backend licensing system. Whether sold separately in the early days or bundled into the Global Plus tier and advanced add-on packages today, it acts as a primary value driver for users upgrading to premium plans.

4. Decoupled Update Cycles (Seamless Hotfixes)

  • The core Bookmap client (e.g., versions 7.5 or 7.6) is a massive software architecture where every major release requires extensive QA testing. Meanwhile, the CME occasionally tweaks its underlying data protocol, or Bookmap’s quant team needs to fine-tune the iceberg filtering logic (such as refining how synthetic icebergs or stop clusters are parsed).
  • Hosting it as a modular package inside the Add-ons Manager / Marketplace lets the team push incremental updates to Stops & Icebergs independently. Traders can simply click “Update” to upgrade the add-on in seconds without having to redownload and reinstall the entire Bookmap desktop client.
0 Comments
Scroll to Top