Roadmap.
Hyperliquid in 2027, then further exchanges in phases through 2029. Every venue after Hyperliquid is planned, subject to a data agreement with the exchange. Below is what each phase covers, the target years, and how pre-registered partners change the order.
Phase by phase.
Once a data agreement is in place, each venue is captured from two regions for at least 90 days before early access, so it ships with history.
We are building the capture and normalization pipeline and taking pre-registrations. Hyperliquid has been recorded internally from Tokyo and Ireland since November 2025; that archive powers our research and becomes the first product.
The first release. Trades, full depth, funding and L4 order flow with the on-chain address on every order, plus the first eight extended fields and chain intelligence. History starts in November 2025. The v1 REST API, WebSocket stream, bulk S3 delivery and Python SDK all go live with early access.
Datasets: trades quotes candles book_l2 book_l3 book_l4 funding open_interest liquidations mark_index instruments extended gaps
Planned: spot, perpetuals, dated futures, options chains, funding, L2 and L3, each subject to a data agreement with the exchange. The history available for each venue depends on the agreement with that venue. N. Virginia joins Tokyo and Ireland as a capture region during this phase, and chain intelligence adds Tron to its five Phase 1 chains.
Planned: US spot, options, fiat pairs and further perpetuals, each subject to a data agreement with the exchange. Options venues add to options_chain, with implied volatility and greeks where the agreement includes them. L4 is offered if a venue's data agreement includes participant-level data.
KuCoin, Bitfinex, Bitstamp and dYdX are planned, each subject to a data agreement with the exchange. Up to eight more slots go to further spot and derivatives venues, chosen by partner votes.
What ships alongside the venues.
Datasets and delivery work run on their own track. Venue-dependent items follow the data agreements behind them.
| Item | What it adds | Plans | Target |
|---|---|---|---|
| API v1 | REST, WebSocket, bulk S3 and the Python SDK (pip install fdc). The spec is a draft today. | All | Q1 2027 |
| Extended fields, first set | OFI-ML, VPIN, QUEUE, CXL/FILL, RESIL, LAMBDA, MARKOUT and PART, on a 100 ms grid, starting on Hyperliquid. | All | Q1 2027 |
| Raw tier | Untouched venue messages as captured, delivered next to the normalized tables on request. | Desk, Enterprise | Q2 2027 |
| Tokyo cross-connect | Live stream delivery over a private cross-connect in Tokyo. | Enterprise | Q2 2027 |
| Chain intelligence | Wallet clustering and on-chain flow attribution (L4+) in chain_entities and chain_flows, with a confidence score on every match. | Enterprise, Desk add-on | Q1 2027 |
| Cross-venue extended fields | Fields that need more than one venue: perp-spot basis across venues, cross-venue lead-lag and funding dispersion. | All | 2028 |
| Options chains | options_chain with IV and greeks, for venues whose data agreements include options data. | Desk, Enterprise | 2027 |
| SOC 2 Type I | Independent audit of our security controls. Type II follows. | All | 2027 |
Changes to targets are announced in the changelog and on the blog. See security for the SOC 2 plan.
What decides the order.
The phase list above sets the broad sequence. Inside each phase, and for the open Phase 4 slots, the order comes from the people who will use the data.
Pre-register and cast your votesMove your venue up the list.
Pre-registered partners vote on venues and datasets, get early access to each phase and lock in pre-sale pricing for 12 months.
EARLY ACCESS · PRE-SALE PRICINGPre-register for early access → DANIEL GARCIA · CEO & FOUNDERdaniel@financedatacloud.com →