Product roadmap

Original request from Juan Linares: "Great product but please add dark mode." There are two separate parts to this: Dark mode for the portal and main website (databento.com, databento.com/portal) Dark mode for the docs We can consider this only after Q1 2025 since we're doing a major rebranding of our website which is expected to finish by early April 2025. The new colors will make it easier for us to implement a dark mode.

We've received some requests recently for Binance data. Please upvote if this is of interest. We're still determining whether this is worth the risk.

Currently, indices are indirectly supported through tradable index instruments on CME futures, ETFs, etc. and we don't provide the index values (non-tradable) themselves. This may be sourced from a feed like the Cboe Global Indices Feed or NYSE Global Index Feed.

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

It would be helpful if OPRA trade conditions were included in the normalized schemas. This is useful information that's currently lost during normalization. Also include the "message type" of each last sale message. Similar to: https://roadmap.databento.com/roadmap/us-equity-trade-condition-codes

Could we add support to make the result of DBNStore.to_df a Polars dataframe as well? Perhaps the function signature could just be overloaded with a to_polars: bool argument. Something like: In Python @overload def to_df(self, to_polars: Literal[False]) -> pd.DataFrame: ... @overload def to_df(self, to_polars: Literal[True]) -> pl.DataFrame: ... Or, maybe to_df is split into two different functions to_pandas and to_polars. Either way, it would be helpful to avoid having to do pl.from_pandas(store.to_df().reset_index(drop=False)). Plus, Polars can convert to pyarrow-Pandas zero-copy, but not the other way around.

Databento's feed is based on CME's MBO feed and we do not overlay implied depth from the MBP feed. This creates the appearance of less liquidity and wider spreads compared to many vendors that are only using the MBP feed. Overlaying MBO and MBP creates several complications; we think using the direct book is better for signal generation and execution, and prefer not overlay implied MBP over MBO to form a composite book. At this time, users who are sensitive to implied orders can impute the implied book themselves. That said, we may expose the implied book for users who find this useful and prefer to compare our data to another reference.

A schema to encompass useful EOD information in various forms. Currently, users have to extract EOD prices from ohlcv-1d. However, this is aligned to UTC midnight. Users who want EOD data based on session end or other specific conventions, e.g. 3:45 PM ET (to avoid auction) have to extract this from ohlcv-1h or ohlcv-1m data. This could be provided either in the form of a new endpoint, new schema (e.g. 'ohlcv-eod' or 'eod'), or more session/market calendar functionality.

This request is to make the API documentation available for download so it can be referenced offline.

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)

Equity data from TSX with broker IDs (TSX is one of the few markets out there with post-trade transparency)

This ticket tracks the setup of Databento's layer 1 network architecture. We anticipate this in Aurora I initially, then several venues in NY4, followed by FR2. At the moment, our data takes at least one layer 3 hop before getting to our capture server. Hardware timestamps are taken on the host. This results in some additional latency (about 500-550 ns for the layer 3 hop) and timestamping jitter. This also results in more inconsistency (typically at the sub-microsecond level) across hosts. The new layer 1 architecture will replace the layer 3 hop, cutting down 500-550 ns to 5 ns, achieve better timestamping consistency between our hosts, and lower jitter from the exchange handoff.

This request is to capture all requests for AI skills and tools (i.e Claude skills) related to Databento's APIs.

This feature would allow the user to request trading calendar information (such as trading session start/end times) via our API. This is especially useful when considering trading sessions that can span multiple UTC dates (and hence the possibility of having multiple trading sessions within a single day). Keywords: Market calendar, trading holidays.