Databento

Name: Databento
Brand: Databento

A simpler, faster way to get market data.

Est 2019|Valuation $110M|Raised $37.5M|39 Ref Customers

LinkedIn 22K|Web traffic 165K|FTEs 43|HQ Salt Lake City, UT

MarketsMarket Data & Reference Data

Published Oct 15, 2026

01Common complaints

- Budget-constrained users who only need OHLCV bars or delayed/aggregated data; lower-cost retail APIs may be more appropriate. - Organizations unable to manage usage-based experimentation and caching; exploratory workflows that re-query large volumes repeatedly can increase costs. - Organizations that require public SOC 2 or ISO 27001 attestations as a strict prerequisite and rely only on publicly posted compliance claims; the vendor does not clearly publish those certifications in the public materials reviewed. - Teams seeking turnkey datasets delivered into a managed warehouse marketplace (for example, Snowflake marketplace) with minimal engineering; the vendor is API-centric and may require integration work.

Deal disqualifiers (poor fit)

Need only for daily or minute aggregates and no microstructure.
Requirement for an extensive set of third-party reviews or standardized public enterprise compliance disclosures prior to procurement.

Vendor-acknowledged or observable limitations

Live pricing model transition: the vendor announced changes to live data pricing for certain datasets, transitioning away from usage-based live pricing in some cases; this can affect customers that preferred purely usage-based live spend.
Asset-class coverage: Spot FX is referenced as forthcoming, indicating incomplete coverage for some asset classes at the time of review.

Technical and operational limitations inferred from user discussions

Cost control requires disciplined usage and caching to avoid unexpected billing for exploratory queries.
Data interpretation complexity: tasks such as futures roll selection and exchange-specific message semantics require expertise and can cause user confusion if not handled correctly.

02Why they buy

Observed characteristics and commonly cited strengths: - Developer-oriented tooling and documentation are frequently mentioned in community discussions. - Access to order book depth (L2/L3) and fine-grained timestamps is a primary capability cited by users who need microstructure. - DBN format and open-source tooling (dbn repository) offer an approach for efficient storage and parsing that some users find useful. Balanced caveat: - These capabilities are most valuable when microstructure fidelity is required. For many analytics workloads that rely on higher-level aggregates, the added complexity and cost may not provide incremental decision value.

03Field reports

Review platform coverage reality check

G2: the vendor has a public profile but limited substantive reviews were visible in the listing reviewed.
Capterra / TrustRadius: no significant review footprint identified in the sources reviewed.

Publicly available user feedback is primarily from community forums and vendor-supplied case studies.

Community feedback summary (public forums)

Reported positive themes from community posts include: - Favorable impressions of the API and documentation. - Positive remarks about support responsiveness from some users. - Users reporting useful historical L2/L3 data and timestamping precision. Reported negative or mixed themes include: - Cost surprises during exploratory usage when caching or download controls were not applied. - Onboarding friction where identity, employer, or address information was requested for licensing compliance. - Questions about exchange licensing and occasional confusion over inactive contracts that can appear as data gaps to end users. These comments are anecdotal and should be corroborated for procurement decisions.

Vendor / partner case study characterization

Vendor-supplied case studies and partner blog posts present selective success narratives where the vendor is integrated into customer products or workflows. These materials typically emphasize integration scenarios and qualitative benefits rather than quantified business impact; buyers should request measurable metrics where relevant.

Why customers cited the vendor (common reasons from materials and community discussion)

Developer-oriented tooling (SDKs and documentation).
Access to order book depth and precise timestamps.
Ability to download large historical slices.
Perception of favorable pricing relative to legacy vendors for equivalent microstructure data.

Why some customers might leave or avoid the vendor

Potential for rapid cost growth during exploratory usage without appropriate caching and controls.
Licensing complexity for certain feeds and related paperwork.
Organizations that only require higher-level aggregates (minute/daily bars) may find lower-cost alternatives more appropriate.

Desktop trading platform partner story

What is described: - A desktop trading platform integrated the vendor to provide access to normalized order book data and sub-second timestamps for strategy design, backtesting, and live workflows. Critical evaluation: - The case study is narrative and product-focused and contains limited quantified business impact (no hard ROI figures, detailed latency benchmarks, or rigorous cost comparisons). It illustrates a plausible integration use case (data inside a trading platform) but should be validated with direct metrics for procurement purposes.

Corporate actions / reference data release (press release)

What is described:

A vendor press release announces corporate actions and reference data APIs with claims about coverage.

Critical evaluation:

These claims originate from vendor press releases; buyers should validate coverage with sample queries and confirm alignment with internal identifiers and point-in-time requirements.

04Best fit

Company sizes

Most suitable customers appear to be organizations ranging from small quant teams to institutional trading groups that require detailed market microstructure data and are prepared to manage licensing and storage costs.

Industries / verticals

Hedge funds and proprietary trading firms
Broker-dealers and market making teams
Fintech companies and trading platform developers
Academic and quant research programs requiring microstructure data

Roles and personas

Quantitative researchers and data scientists
Market data engineers and platform engineers
Execution and trading system developers
Procurement and compliance teams for licensing and redistribution agreements

Qualification criteria (good fit)

Requirement for order book depth (L2/L3), precise timestamps, or venue-like replay.
Need for self-serve licensing and API-based access to high-throughput historical downloads.
Ability to implement caching and data-lake practices to control usage-based costs.

05The pitch

What the product does (core value proposition)

Databento is a licensed market data provider that delivers real-time and historical financial market data via HTTP and a binary Raw TCP protocol, plus a self-serve web portal. The product emphasizes high-resolution L1/L2/L3 order book data, schema normalization, and developer tooling (official Python/C++/Rust clients, comprehensive documentation, low-latency delivery, and usage-based options for historical data). Key product pillars, based on Databento’s own positioning: - Unified access across asset classes (equities, futures, options; Spot FX listed as forthcoming). - Normalization and multiple schemas (e.g., trades, TBBO, MBP-1, MBP-10, MBO) and multiple output encodings (DBN binary, CSV, JSON; Parquet referenced on some pages). - Sourcing and timestamping: captured from colocation facilities and presented with low-latency delivery metrics and uptime targets.

Target market and market positioning

Databento is positioned as a developer-oriented, self-service alternative to traditional enterprise market data vendors and to retail-focused API providers. Target audiences referenced in vendor materials and community discussion include quant researchers, trading teams, fintech developers, and organizations ranging from early-stage startups to investment firms. Feature emphasis observed in materials and discussions includes full order book (L3) delivery, normalized formats, and venue-level sourcing.

Get a comprehensive analysis of Databento including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →

Published Oct 15, 2026

01Common complaints

Budget-constrained users who only need OHLCV bars or delayed/aggregated data; lower-cost retail APIs may be more appropriate.
Organizations unable to manage usage-based experimentation and caching; exploratory workflows that re-query large volumes repeatedly can increase costs.
Organizations that require public SOC 2 or ISO 27001 attestations as a strict prerequisite and rely only on publicly posted compliance claims; the vendor does not clearly publish those certifications in the public materials reviewed.
Teams seeking turnkey datasets delivered into a managed warehouse marketplace (for example, Snowflake marketplace) with minimal engineering; the vendor is API-centric and may require integration work.

Deal disqualifiers (poor fit)

Need only for daily or minute aggregates and no microstructure.
Requirement for an extensive set of third-party reviews or standardized public enterprise compliance disclosures prior to procurement.

Vendor-acknowledged or observable limitations

Live pricing model transition: the vendor announced changes to live data pricing for certain datasets, transitioning away from usage-based live pricing in some cases; this can affect customers that preferred purely usage-based live spend.
Asset-class coverage: Spot FX is referenced as forthcoming, indicating incomplete coverage for some asset classes at the time of review.

Technical and operational limitations inferred from user discussions

Cost control requires disciplined usage and caching to avoid unexpected billing for exploratory queries.
Data interpretation complexity: tasks such as futures roll selection and exchange-specific message semantics require expertise and can cause user confusion if not handled correctly.

02Why they buy

Observed characteristics and commonly cited strengths:

Developer-oriented tooling and documentation are frequently mentioned in community discussions.
Access to order book depth (L2/L3) and fine-grained timestamps is a primary capability cited by users who need microstructure.
DBN format and open-source tooling (dbn repository) offer an approach for efficient storage and parsing that some users find useful.

Balanced caveat:

These capabilities are most valuable when microstructure fidelity is required. For many analytics workloads that rely on higher-level aggregates, the added complexity and cost may not provide incremental decision value.

03Field reports

Review platform coverage reality check

G2: the vendor has a public profile but limited substantive reviews were visible in the listing reviewed.
Capterra / TrustRadius: no significant review footprint identified in the sources reviewed.

Publicly available user feedback is primarily from community forums and vendor-supplied case studies.

Community feedback summary (public forums)

Reported positive themes from community posts include:

Favorable impressions of the API and documentation.
Positive remarks about support responsiveness from some users.
Users reporting useful historical L2/L3 data and timestamping precision.

Reported negative or mixed themes include:

Cost surprises during exploratory usage when caching or download controls were not applied.
Onboarding friction where identity, employer, or address information was requested for licensing compliance.
Questions about exchange licensing and occasional confusion over inactive contracts that can appear as data gaps to end users.

These comments are anecdotal and should be corroborated for procurement decisions.

Vendor / partner case study characterization

Why customers cited the vendor (common reasons from materials and community discussion)

Developer-oriented tooling (SDKs and documentation).
Access to order book depth and precise timestamps.
Ability to download large historical slices.
Perception of favorable pricing relative to legacy vendors for equivalent microstructure data.

Why some customers might leave or avoid the vendor

Potential for rapid cost growth during exploratory usage without appropriate caching and controls.
Licensing complexity for certain feeds and related paperwork.
Organizations that only require higher-level aggregates (minute/daily bars) may find lower-cost alternatives more appropriate.

Desktop trading platform partner story

What is described:

A desktop trading platform integrated the vendor to provide access to normalized order book data and sub-second timestamps for strategy design, backtesting, and live workflows.

Critical evaluation:

The case study is narrative and product-focused and contains limited quantified business impact (no hard ROI figures, detailed latency benchmarks, or rigorous cost comparisons). It illustrates a plausible integration use case (data inside a trading platform) but should be validated with direct metrics for procurement purposes.

Corporate actions / reference data release (press release)

What is described:

A vendor press release announces corporate actions and reference data APIs with claims about coverage.

Critical evaluation:

These claims originate from vendor press releases; buyers should validate coverage with sample queries and confirm alignment with internal identifiers and point-in-time requirements.

04Best fit

Company sizes

Industries / verticals

Hedge funds and proprietary trading firms
Broker-dealers and market making teams
Fintech companies and trading platform developers
Academic and quant research programs requiring microstructure data

Roles and personas

Quantitative researchers and data scientists
Market data engineers and platform engineers
Execution and trading system developers
Procurement and compliance teams for licensing and redistribution agreements

Qualification criteria (good fit)

Requirement for order book depth (L2/L3), precise timestamps, or venue-like replay.
Need for self-serve licensing and API-based access to high-throughput historical downloads.
Ability to implement caching and data-lake practices to control usage-based costs.

05The pitch

What the product does (core value proposition)

Key product pillars, based on Databento’s own positioning:

Unified access across asset classes (equities, futures, options; Spot FX listed as forthcoming).
Normalization and multiple schemas (e.g., trades, TBBO, MBP-1, MBP-10, MBO) and multiple output encodings (DBN binary, CSV, JSON; Parquet referenced on some pages).
Sourcing and timestamping: captured from colocation facilities and presented with low-latency delivery metrics and uptime targets.

Target market and market positioning

Feature emphasis observed in materials and discussions includes full order book (L3) delivery, normalized formats, and venue-level sourcing.

Get a comprehensive analysis of Databento including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →