Best DOM Trading Software: How to Choose a Ladder (2026)
Choosing the best DOM trading software is not a feature comparison — it is a data and permissions question. Before any ladder looks good, check what depth the platform can actually receive, how the ladder behaves under speed, and whether your account allows order entry at all. Here is an evaluation method you can run in one session.
Senzoukria · Learn · Updated 17 September 2026
About this guide: Senzoukria publishes it and sells one of the products mentioned. It is an evaluation method, not an independent latency benchmark or a ranking of every ladder on the market. If you want the reading skill rather than the buying decision, start with how to read the DOM and the depth of market mechanics guide.
What “best DOM trading software” actually means
A ladder is a rendering of a data feed. Two platforms showing the same instrument can display different depth, different aggregation and different update behaviour, because they are receiving different data under different entitlements. So the phrase best DOM trading software has no universal answer: the honest version of the question is which ladder, on my feed, for my instrument, with my account permissions.
This page is scoped to the ladder. For platform-level comparison on footprint and heatmap capability, see the order flow software comparison.
Before any feature: can it receive depth, and how much?
Depth reception is the number of price levels a platform receives from its feed on each side of the book, and it is set by the data source, not by the ladder. A platform can draw a long ladder and still be fed only the best bid and offer; the rows below stay empty or stale.
Three things to establish before anything else:
- Which connection carries depth. A broker connection, a data vendor and a local bridge are three different sources, and a platform may support depth on one and not on another.
- How many levels that connection delivers. Depth data for futures is usually sold in tiers, and the tier — not the depth of market software — decides how far down the ladder you can see.
- Whether depth history is available at all. Live depth and recorded depth are separate products. A platform that streams a book perfectly may have no way to replay yesterday’s.
Record the answers before you look at a screenshot. An empty ladder during a quiet pre-open tells you nothing about coverage; a ladder that never fills below the top level during regular hours tells you a great deal.
Aggregated depth against order-by-order
Aggregated depth reports one total size per price level; order-by-order depth reports each individual resting order, in queue sequence. They support different readings, and no ladder can recover the second from the first.
| Question | Aggregated depth | Order-by-order depth |
|---|---|---|
| How much size rests at this price? | Yes — one total per level | Yes — as a sum of individual orders |
| How many separate orders make up that size? | No | Yes |
| Where would my order sit in the queue? | No — estimated at best | Yes, within the feed’s documented fields |
| Did a level shrink from a trade or a cancellation? | Only by matching trades to book changes | More directly, order by order |
| Who placed the order? | No | No — participant identity is not published |
CME documents both families of feed and the fields each one exposes: Market by Order and Market by Price. The practical consequence is that a claim built on queue position or on single-order behaviour requires an order-by-order feed and the licence that goes with it. On aggregated data, that claim is an inference, not a measurement.
The ladder itself: aggregation, recentring, clicks, keyboard
Once the data is settled, DOM ladder software is judged on behaviour under speed. The details that matter are rarely in the feature list:
- Price aggregation. Grouping several ticks per row makes a thin book readable and hides fine structure. Check that the grouping step is explicit and that totals per row are consistent with the ungrouped ladder.
- Recentring. When price runs, does the ladder scroll, jump, or stay anchored until you ask? A ladder that recentres unexpectedly moves the row under your cursor.
- Click behaviour. Which mouse button does what, whether a click is confirmed, and whether there is an unambiguous flatten control.
- Keyboard. Check that the shortcuts exist, are remappable and keep working when the ladder is a detached window.
- Update rate. A ladder redrawing on every message can cost more than it shows. Watch it on a fast session, not on a quiet one.
None of this shows on a marketing page; it shows on a live session — hence the checklist below.
Order entry from the ladder is an account permission
Clicking a ladder to place an order requires a routing permission on the account behind the connection; the software only presents the control. It is an easy step to skip, because a demonstration video cannot show your entitlements.
Separate these four things explicitly, because vendors often bundle them in one sentence:
- Market data access — receiving depth for the instrument.
- Depth history access — replaying or recording the book.
- Manual order routing — sending orders from the ladder, by hand.
- Automated routing — any rule that sends an order without a human click.
On a funded or evaluation account, points 3 and 4 are frequently governed by rules that have nothing to do with your software choice. Check them against the account agreement before buying a licence for the ladder: order flow software and prop firm rules sets out how to verify data access, manual routing and automation separately.
DOM, heatmap and footprint: one screen or three tools
The three views are not substitutes. The DOM shows displayed resting size at this instant; a liquidity heatmap shows how that resting size has persisted, grown or drained over time; a footprint chart shows what actually executed at each price.
| View | Answers | Cannot answer |
|---|---|---|
| DOM ladder | What size is displayed at each price right now | Whether it will still be there when price arrives |
| Liquidity heatmap | How long that size has been sitting, and where it drained | Who executed against it, and with what aggression |
| Footprint | What traded at each price, by side, per bar | What is still waiting above and below |
DOM and heatmap software in a single application can remove the synchronisation problem — one clock, one feed — provided the views share an instrument and a session definition. Three separate tools can work, but you then own the alignment: identical contract, identical session boundaries, identical price grouping, or it is not a comparison.
Operating system and machine
A native DOM trading platform on Windows usually assumes a local connector distributed as a Windows binary, a GPU able to redraw the ladder without tearing, and a display arrangement where the ladder keeps a stable position. Check those assumptions before the licence: they decide whether the ladder is usable on the machine you own.
Outside Windows, the questions are which edition is native, which connections it supports, and whether it is labelled beta. A virtual machine is a legitimate answer, but it adds a layer between the feed and the ladder, and that layer belongs in your evaluation. The comparison hub covers per-platform cases, including Mac.
Total cost: four separate lines
The software licence, the market-data subscription, the exchange entitlement and the account fees are independent charges, and a platform price rarely includes them all. Compare candidates on the sum, over the same period, in the same currency.
| Line | Paid to | What to verify |
|---|---|---|
| Software licence | The platform vendor | Edition, renewal rate, whether the ladder is in the base tier |
| Depth market data | Broker or data vendor | Levels delivered, aggregated or order-by-order, history included or not |
| Exchange entitlement | The exchange | Professional or non-professional status, per-exchange fees, taxes |
| Account fees | Broker or prop firm | Platform fees, routing permissions, evaluation or reset costs |
How Senzoukria shows it
Senzoukria is a native Windows desktop application; macOS and Linux builds exist in beta. It renders a DOM panel next to a bid × ask footprint and a liquidity heatmap in the same application, on the same connection.
- Futures. Depth and trades come from a Rithmic connection or from Databento CME data. Rithmic credentials are issued by your broker or prop firm, and the depth levels and history you receive depend on that account and its entitlements, not on Senzoukria.
- Crypto. Binance Spot and Perp and Bybit are supported for analysis: book, trades and charts. Senzoukria does not route crypto orders.
- Order entry. The DOM panel itself is read-only: there is no click-to-trade on the ladder. Manual routing on a Rithmic connection happens from the order ticket, the chart-pinned quick-trade bar and the chart context menu, and only where the account permits it. The strategy autopilot must be armed explicitly by a human, is never persisted across restarts and does not resume by itself.
- Options context. GEX and options flow views are conditional: they require an options data source, and without one they are not available.
- Cost. Eligible subscriptions start at $9 for the first month, then $29 a month; the annual option is $240 paid once a year. See current terms. Market data and exchange fees are billed separately by your broker, vendor or exchange. The download page lists the current builds per operating system.
Charts on this website are demonstrations. They do not establish the depth, history or routing permissions your own account will have.
Common mistakes
- Judging the ladder on a quiet market. Aggregation, recentring and update cost only become visible on a fast session.
- Assuming the licence includes the data. Depth is billed separately by the broker, vendor or exchange.
- Confusing rendered rows with received levels. An empty row below the top of the book is a coverage fact, not a design choice.
- Reading queue position off aggregated depth. Without an order-by-order feed, that number is an estimate, and the ladder should say so.
- Buying the ladder before checking routing permissions. On evaluation and funded accounts, the account agreement decides what your clicks may do.
- Calling every pulled level a spoof. Cancellation is observable; intent is not established by a ladder snapshot.
A one-session checklist, with the evidence to record
- Note the connection, instrument, contract month and session, then screenshot the ladder during regular hours. Record how many levels actually carry size.
- Change the price grouping one step and confirm the row totals stay consistent with the ungrouped ladder.
- Let price run without touching the mouse, and note whether rows move under the cursor.
- Test the keyboard controls on a detached ladder window, and confirm there is a flatten control you can hit without reading the screen.
- Attempt a working order only if your account permits it, on a simulated or demo account first, and record which permission allowed or refused it.
- Open the heatmap and footprint on the same instrument and check that a level seen on the ladder appears at the same price and time in both.
- Write down the four cost lines with their amounts and renewal dates, and compare the totals rather than the licence prices.
Key takeaway: a ladder can only display what its feed delivers and can only send what your account permits. Verify depth reception, depth format, ladder behaviour under speed and routing permission first — the interface comparison is the last step, not the first.
Frequently asked questions
- What is DOM trading software?
- DOM trading software is an application that receives depth-of-market data from an exchange or broker and displays it as a price ladder: resting bid size below the market, resting ask size above it, updating in real time. Some ladders are display-only; others also send orders, which is a separate account permission rather than a property of the software.
- How do I choose the best DOM trading software?
- Start with the data, not the interface. Confirm which feed the platform connects to, how many depth levels that feed delivers for your instrument, and whether the depth is aggregated per price or order-by-order. Then test the ladder on a fast session and check price aggregation, recentring and keyboard behaviour before comparing licence prices.
- What is the difference between aggregated depth and order-by-order depth?
- Aggregated depth gives one total size per price level. Order-by-order depth lists the individual resting orders at each level, including their queue order. Aggregated data tells you how much is waiting; order-by-order data lets you follow individual orders and estimate queue position. CME documents both families of feed, and which one reaches your ladder depends on the entitlement attached to your data subscription.
- Does DOM software let me place orders from the ladder?
- Only if your account permits it. Order entry depends on the broker or prop firm connection, the account state and the routing permission attached to it, not on the software alone. A read-only data connection will display a full ladder and refuse every click, which is the expected behaviour and not a defect.
- Do I need a DOM if I already use a footprint chart and a heatmap?
- They answer different questions. The DOM shows displayed resting liquidity right now at the best prices; the heatmap shows how that resting liquidity has evolved over time; the footprint shows what actually executed. No single view separates resting size from executions, so the three are complementary rather than interchangeable.
- Does DOM trading software need Windows?
- Not necessarily, but Windows is where most connectors are first supported: several broker and prop-firm components are distributed as Windows binaries. Native builds for macOS and Linux exist and are sometimes labelled beta, so check the specific edition and the connections it actually supports rather than the product name.