Product roadmap

Submit dataset requests and feature ideas here. For bug reports, use our chat support or issues tracker instead.

Trending
  1. JPX Futures

    It would be great if Japan Exchange Group (Nikkei 225, etc) could be supported. CME Nikkei 225 volume is too low.

    Michael Aaron B

    8

  2. Backfill US equities history before 2018

    The earliest that our tick history (L1 and better) goes back to is 2018, which is the start of our Nasdaq TotalView-ITCH coverage. While backfill of daily/OHLCV/L0 data is in progress, which will bring daily history back to at least 2010, we have no immediate plans to backfill our tick history yet. The root issue is that we cannot find a quality source that we trust for this granularity of data prior to 2018. While several sources exist, most of them do not meet our accuracy/quality control standards. This ticket tracks backfill of US equities - especially tick history for those venues - back to before 2018.

    Tessa Hollinger

    1

  3. Parquet encoding

    Support Parquet as a form of encoding, aside from dbn, CSV and JSON.

    Tessa Hollinger

    12

  4. Calculated options greeks schema

    Add a schema for calculated metrics like options greeks, e.g. implied volatility, delta, etc.

    Carter Green

    13

  5. Equities reference, fundamental and static data

    e.g. Shares outstanding, short interest, market capitalization, P/E ratio etc.

    Tessa Hollinger

    3

  6. Indian stock and derivatives data

    National Stock Exchange (NSE) and Bombay Stock Exchange (BSE) data.

    Amit S

    8

  7. Limited support for L2/L3/MBP-10/MBO on Standard plans

    The legacy live usage-based plans allowed users to access L2/L3 data. However L2/L3 were pulled from the Standard plan. One possibility to increase the value of the Standard plan is to offer limited access to L2/L3, perhaps gated by a quota on symbol subscriptions per account, etc.

    Tessa Hollinger

    4

  8. HKEX

    Securities and futures data.

    Tessa Hollinger

    2

  9. Singapore Exchange (SGX) data

    Stocks and derivatives data from the Singapore Exchange (SGX)

    Carter Green

    1

  10. Euronext equities and futures (Milan, Paris, Amsterdam, Oslo, Brussels, Lisbon, Dublin) and LuxSE

    This ticket tracks all Euronext cash and derivatives markets. This includes, for example: Euronext Milan (formerly Borsa Italiana)Euronext Paris futures (CAC40, Milling Wheat, Corn, Rapeseed, etc.)Euronext Paris equitiesEuronext AmsterdamEuronext OsloEuronext BrusselsEuronext LisbonEuronext DublinLuxembourg Stock Exchange (LuxSE)

    Josip V

    5

  11. Official R client library

    This client library makes all our historical and live features easier to integrate in R on Windows, Linux, and Mac OS. R is currently already supported through our HTTP API and Raw TCP protocol, which are both language-agnostic.

    Tessa Hollinger

    0

  12. Cboe Europe (BXE, CXE, DXE)

    All Cboe Europe on-book equities markets - BXE, CXE, DXE. Captured at Equinix LD4.

    Tessa Hollinger

    0

  13. Tag Options Contracts as Weekly (Monday, Tuesday, etc), Monthly, EOM, Quarterly in Instrument Defs

    right now after i download the Instrument Defs data i have to manually derive the contract cycle and then tag it myself, would be amazing if i didn't have to do that... since for Opra options it also requires me to maintain a market holidays calendar and then check for expiration rollbacks etc. for CMEs it just requires storing and matching the root symbology, so it's less error prone, but still a very manual process. and obviously knowing the cycle is extremely vital when you're doing things like choosing contracts to interpolate over to calculate variance strips, or things like for CME options calculating tick rules which for some (like SR3) depend on the cycle... etc

    Victor S

    1

  14. OPRA data compression and conflation

    Currently, it is not possible to subscribe to CMBP-1 of all OPRA symbols at once with the ALL_SYMBOLS parameter. OPRA is the lone exception where we restrict users from subscribing to CMBP-1 for all symbols at this time, because the feed is too large (1~ Gbps average, 1.4+ million contracts) to be consumed over public internet for practically all users. Even if you have enough bandwidth, your client will need to be very fast to avoid TCP backpressure. To get access to all OPRA symbols real-time, you'll need to shard symbols across multiple connections. This roadmap ticket tracks the introduction of compression and conflation to subscribe to all symbols over internet.

    Tessa Hollinger

    0

  15. Performance improvements for OPRA

    Currently, batch download for OPRA as the full dataset is large. Some of our filtering algorithms scan through the full dataset sequentially, so the batch download jobs could spend hours in I/O. For example, when fetching QQQ.OPT from a day of 11.2 TB uncompressed data, it spends 1+ hour in I/O alone just going through the ~11.2 TB of unrelated data.

    Tessa Hollinger

    1