Skip to main content

Vote for ideas and share your own — that's how you shape the development of ATAS

We read every idea, and you can see what's already in progress on the roadmap.

Perhaps your idea has already been posted — find it and support it with your vote. One request with 50 votes moves faster than five identical ones with 10 each.

Didn't find it? Create a post. One post = one idea.

Doesn't belong here:

  1. Questions and issues with the platform — contact support@atas.net

  2. Several ideas in one post — such posts are rejected

Option Board: add SPX/SPXW and NDX/NDXP index options (incl. 0DTE) with real-time OPRA data

Note: this is not a request for more X-Ray indicators. It is a request for the raw index options chain data (SPX/SPXW and NDX/NDXP, including 0DTE) in the Option Board and the API, so traders can do their own analysis. Summary: The Option Board currently supports CME futures options (ES, NQ, etc.). This request is to add US cash-settled index options on the S&P 500 and Nasdaq-100: SPX / SPXW and NDX / NDXP, including the same-day (0DTE) expirations. Motivation SPX and NDX options carry most of the US index options volume; 0DTE SPXW alone is a large share of daily volume. Dealer hedging of these options is done largely in ES and NQ futures, so their positioning has a direct impact on the instruments ATAS users trade. ES/NQ futures options are a much thinner market (especially NQ), so they cannot replace SPX/NDX data for strike-level analysis (volume and open interest concentration, call/put walls, gamma levels). Today traders need a second platform for this data while executing in ATAS. Instruments and scope Roots: SPX (AM-settled monthly), SPXW (PM-settled weeklies and dailies), NDX, NDXP (PM-settled weeklies and dailies). All listed expirations, with at least the nearest 5 expirations and the 0DTE expiration selectable by default. Strike chain around the money (configurable range), not only a fixed number of strikes. Underlying: real-time SPX and NDX cash index values. Data required per contract (real time) Best bid / best ask (with sizes) Last trade price and size Cumulative daily volume Open interest (daily value from OCC) Time and sales (trade-by-trade prints with price, size and time), if possible Optional: implied volatility and Greeks (delta, gamma) as already shown for futures options Option Board features Same layout and features as for futures options (chain by expiration, calls/puts, volume and OI columns). Optional display of strikes converted to the related future (ES for SPX, NQ for NDX) using the live basis (future price - index price), so levels can be read directly on ES/NQ charts. Programmatic access: Expose these contracts through the same options data interface already used by the Option Board for futures options (expirations, chain, per-contract market data subscription), so they can also be used in charts, custom studies and strategies. Data sources (for reference): This requires US options data from OPRA plus the Cboe (SPX) and Nasdaq (NDX) index feeds. Rithmic does not carry this data, so it would need a connection/data provider that includes OPRA and index data, available as an add-on subscription for users who want it. Example use case: An NQ trader opens the Option Board, selects NDXP with today's expiration and sees in real time which strikes concentrate volume and open interest. Those strikes are then marked on the NQ chart (converted with the live basis) as potential support, resistance or magnet levels for the session. If you trade ES or NQ and want SPX/NDX options inside ATAS, please vote for this idea. Thank you.

NICOLAE1 month ago

Add online verification to prevent pirated ATAS and attacks from disrupting server stability

Introduce an online license verification system to prevent pirated versions of ATAS and unauthorized attacks from compromising server stability. I've noticed widespread use of pirated ATAS software, along with mass registrations using temporary email addresses to access the 14-day free Rithmic data trial. I suspect this may be contributing to ATAS server instability. Rithmic connectivity also seems significantly less stable on ATAS than on other platforms like Bookmap. I believe this could be due to software piracy and abuse of the free 14-day Rithmic trial. Users have also cracked ATAS to bypass the restriction of allowing only one free Rithmic account. ATAS also needs to optimize its Rithmic connectivity

Aurora5 days ago

Подключение брокера TradeZero

Добрый день! Прошу рассмотреть возможность интеграции брокера TradeZero в торговую платформу ATAS для активной внутридневной торговли американскими акциями. TradeZero представляет интерес для активных трейдеров благодаря относительно низким требованиям к открытию маржинального счёта, возможности поиска и аренды акций для коротких продаж (short locates), конкурентоспособным торговым комиссиям и наличию API для интеграции со сторонними торговыми платформами. На данный момент существующие брокерские подключения ATAS имеют ряд ограничений для активной торговли американскими акциями, особенно в сегменте low-float и penny stocks: Interactive Brokers — относительно высокие требования к маржинальному счёту, ограничения на торговлю отдельными низколиквидными акциями, а также ограниченная доступность инструментов для коротких продаж. EXANTE — сравнительно высокие комиссии, которые могут существенно влиять на рентабельность стратегий с большим количеством внутридневных сделок. При этом в ATAS уже реализовано подключение качественных американских биржевых данных к примеру через DxFeed. Таким образом, интеграция TradeZero позволила бы объединить профессиональные инструменты анализа рыночной ликвидности ATAS с брокерской инфраструктурой, ориентированной на активную торговлю американскими акциями. Считаю, что такое подключение могло бы существенно повысить привлекательность ATAS для трейдеров американского фондового рынка и привлечь новую аудиторию, специализирующуюся на внутридневной торговле. Также предлагаю рассмотреть возможность интеграции других брокеров с аналогичными торговыми условиями, поддержкой short locates и доступным API. Спасибо за рассмотрение предложения!

Yevhen1 month ago

Request for QUIK connector refinement - transfer of the "Execution condition: Passive only" (Post-Only) parameter

Hello! I'm writing regarding a question I've already raised with your support team. It concerns connecting ATAS to QUIK (broker KIT Finance). QUIK allows you to place orders with the "Post-Only" execution condition. This allows traders to act as makers and avoid paying the 0.03% exchange commission on each trade. For active traders, this represents a significant savings: with a monthly turnover of 10 million rubles, losses amount to 3,000 rubles, or 36,000 rubles per year. However, as your employee Alexander Khayosh confirmed, when orders are sent from ATAS, the Post-Only flag is not transmitted to QUIK—all orders are processed as regular limit or market orders. As a result, when a limit order is executed immediately, I become a taker and pay a higher commission, even if Post-Only mode is enabled in ATAS. The ATAS documentation specifies the IOrderOptionPostOnly interface with the PostOnly flag. This means that the platform architecturally supports this. The problem lies specifically with the QUIK connector, which does not transmit this parameter to the transaction. I request that you consider improving the QUIK connector so that the Post-Only flag is correctly transmitted to QUIK in the "Execution Condition" parameter = "Passive Only" (or BOOK_OR_CANCEL in the universal transaction format). This is critical for traders who use ATAS for analysis but are forced to submit orders manually in QUIK simply to save on exchange fees. Without this improvement, ATAS is less cost-effective than submitting orders manually in QUIK. Please advise: 1. Is it possible to implement this feature in the QUIK connector? 2. If so, when can it be included in the update? 3. If implementation is not planned, what are the alternative ways to convey the Post-Only feature in QUIK? I am happy to pro

Musa1 month ago

ПРОКСИРОВАНИЕ ТРАФФИКА

странно что до сих пор нет функиции проксировать траффик. даже в более простых ПО типа приводы CS, TT етс. есть возможность подключить прокси и сократить пинг до торговых площадок (BINANCE? BByte) критично для скальпинга и не только

yogun26 days ago

Built-in Integration with SpotGamma (HIRO Engine & Dealer Levels) for ATAS X Ultra

Hi ATAS Team, First of all, I want to highly praise the incredible performance of ATAS X on macOS. Running the native build on an Apple Silicon Mac is flawless, and the rendering speed of the DOM Heatmap alongside volume data is truly industry-leading. I also want to commend your recent focus on the options ecosystem, specifically the introduction of the Options GEX Profile, Expected Move, and the Options Board for Ultra users. Providing localized Gamma Exposure calculations is a massive step in the right direction for futures day traders who rely on institutional structural levels (like Put/Call Walls and 0DTE dynamic flows). To take ATAS X Ultra to the absolute absolute next level, I would love to propose an official integration/API plugin with SpotGamma. While computing GEX locally is a great feature, many professional day traders already utilize SpotGamma’s Advanced/Alpha tiers for their proprietary behavioral dealer models, advanced Vanna/Charm projections, and most importantly, the HIRO (Hedging Impact Real-Time Options) Engine. Currently, SpotGamma lacks a direct plugin for ATAS on macOS, forcing traders to manually copy-paste levels or look at a separate browser window. Having a dedicated connection module inside ATAS where we could input our SpotGamma API Key to seamlessly plot the HIRO hedging pressure and institutional levels directly onto our dxFeed/Rithmic futures charts would be a complete game-changer. Given your excellent track record with third-party integrations, bridging the gap between ATAS’s world-class Order Flow execution and SpotGamma's institutional options data would create the ultimate trading workspace. Thank you for continuously improving this amazing platform!

Tomer2 months ago

Precise exchange timestamps and data-gap alerts for order flow and MBO traders

Know exactly when every order and trade happened, and know when your data has a hole in it. If you trade order flow, DOM or MBO, timing is everything. Was that iceberg refilled before or after the sweep? Did your limit order get filled because of a real aggressor, or because the book was rebuilt? How much latency is there between the exchange and your screen? Today ATAS already receives this information from providers like Rithmic, but most of it never reaches our indicators and strategies. This idea asks ATAS to pass it through. You would get: More accurate order flow analysis. Correct ordering of trades and book events, down to the nanosecond. Sweeps, icebergs, absorption and queue position become measurable instead of estimated. Real latency visibility. See how old the data is when it reaches you, and spot when your connection or the provider is lagging. Trustworthy history and replay. Know when the book was reset or data was missed, so a gap doesn’t silently distort your indicators, backtests or statistics. Better execution review. Compare your own fills against the exact market events around them. ATAS has already started: SourceTimeNs exists for MarketByOrder and Trade from Alpha 8.0.16.107. This idea is about finishing the job so every data path gets the same precision. What exactly is requested: Nanosecond exchange time on MarketDataArg. Add the same SourceTimeNs (exchange time, nanoseconds, from the provider) to MarketDataArg, which is used by OnNewTrade, MarketDepthChanged and cumulative trades. Provider receive time. Add an optional ProviderReceiveTimeNs on MarketByOrder, Trade and MarketDataArg: the time the provider’s server received the event. For Rithmic, JopSsboe/JopNsecs. This allows measuring exchange → provider → platform latency. Clock-source flag. Time is currently exchange time, falls back to provider send time, and uses local time for book snapshots. Please add a small enum (for example TimeSource = Exchange | ProviderSend | Local) so indicators know which clock a value comes from and can handle the fallback correctly. Book rebuild / gap notification. Raise an event to indicators and strategies when the provider signals a book rebuild or reset (Rithmic DboBookRebuild), including the instrument and the time. This way, code can mark data as incomplete instead of treating a reset as real market activity. Expose PreviousPrice on MarketByOrder. Rithmic already sends the previous price on order modifications. Exposing it lets indicators tell a price-modify from a new order. Per-event platform sequence number. A monotonic counter per instrument, assigned by ATAS as events arrive from the connector, so indicators can prove no event was dropped between the provider and the indicator. Batch / end-of-update marker. When the provider delivers several book changes together (for example, one aggressive order sweeping several levels), mark the last event of the batch so the book can be evaluated in consistent states. Compatibility: all changes are additive and optional (nullable properties, one new event). Existing indicators and strategies keep working unchanged. Providers that don’t supply a field simply leave it empty. If you care about precise order flow, MBO or execution quality, please vote.

Ruben2 months ago
1

Failsafe Dual Data Feeds

Hi ATAS Team, First off, I want to say how impressed I am with the platform. The order flow visualization and clarity are incredible, and the cross-platform optimization across both Windows and Mac is seamless. ATASX completely replaced Deepcharts for me. I have a feature suggestion that would solve a major pain point for active traders who want high reliability without managing a complex VPS setup: A Smart Quote System (Multi-Feed Failover). The Problem Data feed performance and latency fluctuate unpredictably throughout the trading day. While one provider (e.g., Rithmic) might lag during high-volatility opens while another (e.g., dxFeed) stays steady, the situation can easily reverse later in the session without warning. Because these latency spikes and delays are impossible to predict or time, manually monitoring feed health and switching providers during active market conditions costs critical time, focus, and trade execution precision. The Feature Proposal Allow ATAS to connect and maintain two active quote providers simultaneously, governed by an automated backend failover mechanism: Real-Time Health & Latency Monitoring: ATAS continuously tracks incoming data health, packet flow, and latency for both connected feeds in the background. Seamless Automatic Failover: If the primary feed experiences delays or breaches a latency threshold, ATAS automatically routes chart data to the healthier secondary feed—without freezing charts, losing historical tick data, or interrupting the user workflow. Running concurrently removes the need to predict provider stability, drastically minimizes latency issues, and provides institutional-grade redundancy right out of the box. Thanks for building such an outstanding platform, and I look forward to seeing how ATAS continues to evolve!

KEVIN2 months ago

Add More US Stock Symbols to ATAS Local Charts (DX Feed Data Quality is Inconsistent)

Feature Request: I'd like to request that ATAS expand the list of US stock symbols available on local charts, rather than routing them through DX Feed. Why this matters: ATAS's local charts are noticeably smoother and cleaner than DX Feed charts for US stocks currently supported. Indicators especially Volume Profile with Delta levels and Big Trades map much more accurately on local charts. DX Feed charts for US stocks show visible noise, which throws off delta and volume profile accuracy, making it harder to trust the data for real trading decisions. Right now, only a limited number of US stock symbols are available on local charts, forcing traders to fall back on DX Feed for everything else, even though the local chart quality is clearly superior. Request: Please add more popular/high-volume US stock tickers (e.g., large-cap and frequently traded names) to the local chart symbol list. This would let traders use ATAS's more reliable local data and indicators across a wider range of stocks instead of being limited to a small set. Impact: This would directly improve: Volume Profile & Delta accuracy Big Trade/order flow reliability Overall charting experience for US equity traders on ATAS

Chaitanya2 months ago
In Progress

Full MBO support for stocks (dxFeed) + Heatmap compatibility with any GPU

Hello ATAS team and community, I am a stock trader currently evaluating a full migration from Bookmap to ATAS. I would like ATAS to become my only platform, but two limitations are currently blocking that move. 1. Full Market-By-Order (MBO) support for stocks via dxFeed dxFeed already includes MBO data in their Market Depth subscriptions. However, ATAS does not yet support receiving or visualizing this MBO data. This prevents proper iceberg detection, advanced order-flow tools, and a truly complete heatmap experience for stocks. Futures and options traders already enjoy a high level of functionality in ATAS. Stock traders need the same level of support. Request: Please prioritize and complete MBO integration with dxFeed (and any other relevant stock data feeds) so that stock heatmaps, iceberg detection, and market-depth tools reach parity with the futures/options side. 2. Heatmap GPU compatibility – Vulkan restriction The heatmap currently only works properly on GPUs with Vulkan support. Many traders (including myself) use other graphics cards (older NVIDIA, AMD, Intel, etc.). Request: Please fix/optimize the heatmap so it works reliably on any modern graphics card, without being limited to Vulkan. These two improvements would allow many stock traders to fully abandon Bookmap and use ATAS as their primary platform. The heatmap is already working for stocks in basic form — adding proper MBO support and broader GPU compatibility would make it complete. Best regards, Sami

SAMI3 months ago

Add Support for Kraken Derivatives US / Bitnomial Perpetual Futures (PBTCUC)

I would like to request support in ATAS for Kraken Derivatives US, particularly its Bitcoin perpetual futures contract PBTCUC, which is listed on Bitnomial Exchange. ATAS already supports Kraken Spot and Kraken's international derivatives API, including flexible and inverse futures/perpetual instruments. However, ATAS Support has confirmed that Kraken Derivatives US is a separate service and its Bitnomial-listed contracts are not currently available through the existing Kraken connector. This creates an important gap for U.S.-based ATAS crypto traders. Kraken Derivatives US provides U.S. customers access to regulated perpetual-style cryptocurrency futures, but we currently cannot analyze the actual order book for these contracts or execute them through ATAS. Adding support would allow U.S. traders to: Analyze the actual PBTCUC Bitcoin perpetual futures order book within ATAS. Use ATAS order-flow tools such as footprint charts, DOM, Smart Tape, delta, volume profiles, heatmaps, and liquidity analysis on the market we are actually trading. Execute Kraken Derivatives US/Bitnomial contracts directly through ATAS if trading integration is possible. Avoid analyzing BTC perpetual order flow from an international exchange such as Binance or Kraken International while executing on a completely different U.S. market. For order-flow trading, having the same market for analysis and execution is extremely important. Although Bitcoin prices across exchanges generally track each other, resting liquidity, executed volume, delta, absorption, and other order-flow information are specific to each exchange's order book. Even if direct trading integration cannot be added initially, Bitnomial/Kraken Derivatives US market-data support would be extremely useful as a first step. Ideally, support would eventually provide: Bitnomial/Kraken Derivatives US market data → full ATAS order-flow analysis → account connection → direct execution of PBTCUC and other supported U.S. crypto derivatives within ATAS. With regulated crypto perpetual futures becoming available to U.S. traders, I believe this would be a valuable addition for ATAS's U.S. customer base. Thank you for considering it.

Kelley2 months ago

Feature Request: cTrader & CFD Broker Integration with Cross-Trading and Micro-Lot Sizing

Overview Requesting a native connection to cTrader (and general CFD broker endpoints) that enables cross-asset execution. This would allow traders to perform order flow analysis on centralized futures feeds (e.g., Rithmic, DxFeed, CQG) while executing corresponding trades on CFD platforms like cTrader (e.g., NAS100, US500, GER40). Key Components 1. Native cTrader / CFD Connector Integrate cTrader Open API (or cTID integration) directly into ATAS's connection list alongside existing futures and crypto feeds. Allow ATAS to act as the primary execution frontend while routing orders to cTrader / CFD accounts. 2. Symbol Mapping / Cross-Trading Engine Data Feed: CME Futures via Rithmic, DxFeed, or CQG (e.g., NQ, ES). Execution Endpoint: cTrader CFD symbols (e.g., NAS100, US500, USTEC). Enable one-click execution from ATAS charts/DOM (analyzing CME order flow/footprint) that immediately places the equivalent order on the connected CFD instrument. 3. Fractional & Micro-Lot Sizing Support (Down to 0.01 Lots) CFD brokers allow precise risk management with flexible contract sizes starting from 0.01 lots. ATAS UI Requirement: Ensure order entry modules, DOM, chart trading panels, and risk parameters allow entering fractional trade sizes (e.g., 0.01, 0.05, 0.10) rather than restricting inputs to integer contract amounts. Why This Adds Value to ATAS Expanded User Base: Many retail traders and prop firm account holders use cTrader due to lower leverage restrictions and competitive fees, but lack high-grade order flow and volume profile tools on cTrader's native charts.

Wesley3 months ago

Добавить биржу Lighter DEX во вкладку "Подключения"

Это децентрализированная криптобиржа, особенность которой отсутствие торговых комиссий для тейкеров и мейкеров. Было бы очень круто торговать через нее. Спасибо!

Artyom3 months ago

Auto-hide/disable burnt accounts (Balance = 0) from ADataFeeder/NT8 connection

When connecting to NinjaTrader 8 via ADataFeeder, ATAS shows all linked accounts as "connected" (green dot) with no distinction between active and burnt/violated prop-firm accounts. Users with many prop-firm accounts (25+) have to manually check each one to find out which are still tradable. The NinjaConnector debug log already contains everything needed to detect this: every "Portfolio changed" event reports Bal/Avl. Burnt accounts consistently show: Bal: 0/0/0, Avl: 0 while active accounts show a positive balance (e.g. 49545.38, 51786.46, 50016.39...). NinjaTrader 8 already handles this correctly: accounts with Balance = 0 are automatically removed/disabled from the quick account-selection list. ATAS should replicate this behavior, since the data is already available through the same ADataFeeder connection. Requested improvement: Automatically detect accounts with Balance = 0 (and Available = 0) coming from the ADataFeeder/NT8 feed. Hide/disable these accounts from the quick account picker, or visually flag them as "not operative / burnt". Make this configurable (on/off) in the connection settings, for users who still want to see all accounts. Minimum alternative: add a "Balance = 0" filter/column in the Accounts/Positions tables so these accounts can be quickly hidden. Attached: a log excerpt and an account-panel mockup from NT8 showing the pattern (account numbers masked).

Umberto4 months ago

Atas X Mac Transaction Connector

Hello. When will the Atas X version for Mac be available? Finam in Russia only works with it. Connection. Can you set it up? Please???

Angel3 months ago

Include Databento as a data feed

Databento would be a great addition as a data feed. Their data is more detailed than Rithmic (down to nanoseconds). I work wit it to create strategies and backtest. It would be a dream if they’re live feed hooked right into ATAS!

Dennis4 months ago
2

API s settings do not allow EU citizens to connect their crypto api

Hi as a EU citizen I am guessing I am not the only one having this problem. Atas currently supports API implementation from some certain crypto exchanges, however ATAS accepts the API from the .com domains. As eu citizens and under the obligation to open an account under the eu domains, obviously this is a problem, as the API that we create are not supported by ATAS. As it is almost impossible for the EU citiznes to open an account with the .com domains, it would make sense if the ATAS devs would find a solution to this problem by creating a fix that allows any eu account to connectt the API’s to the ATAS platform. thanks

Matthaios5 months ago
1

Hyperliquid

Hyperliquid perpetual futures market-data integration Required data: - Trades and Bid/Ask classification - Footprint and clusters - DOM/order-book liquidity - Open Interest - Liquidations - Historical tick data and Market Replay Phase 1: Read-only market-data connection Phase 2: Wallet and order-execution connection

YESONG5 months ago

ATAS X missing Connections

There are a couple missing connections that are missing on ATAS X but are available on ATAS. For example Kraken.

Ricardo5 months ago