14 venues, stated honestly

What you can trade, where

One dot per venue per asset class. The colour is the venue's tier, so a market you can trade today and a market behind an explicit build gate never look the same.

• live exec + recon
• feature-gated
• sidecar exec · recon not wired
• not offered by this venue

Asset classes are read from each bridge's own catalog in the shipped source. A venue's dot says the bridge covers that class — not that every instrument in it is listed on that venue today.

How far each bridge is wired

The same roster, one fact per column. EIP-712 means the venue signs orders with a key you hold; REST and WS are the wires it speaks. A venue with none of the three speaks something of its own, named in the notes directly under the table — which is also where a build gate goes. Every reconciled venue polls on an interval; Reconnect marks the four that also resync the moment a websocket comes back. Every venue mounts paper by default, so that is stated here once rather than repeated down a column.

• wired and live
• behind a build feature
• through a sidecar
• —not wired

• Binance — Market data is the live trade tape plus conflated L2 depth.
• Deribit — Orders ride a persistent authed JSON-RPC frame, not REST.
• cTrader — A dedicated authed protobuf socket — neither REST nor WS.
• Interactive Brokers — The Client Portal gateway plus its socket API, not a direct wire. Behind the ibkr feature.
• FXCM — The vendor ForexConnect SDK over an FFI shim, not a network protocol. Behind the fxcm feature + linked SDK.
• Dukascopy — A Java JForex sidecar process over JSON-lines stdio.
• Polymarket — Behind the polymarket feature · POLY_EXEC=1. Keyless CLOB feeds, with L2 recording. Its history is the archive’s, not the venue’s — this bridge serves no price history at all.

Generated from the same capability tables our CI gates — these tables cannot say more than the code does. A venue cannot appear here without passing the exec and market-data conformance harnesses, and a new venue reddens CI until every capability table classifies it. Hand-seeded 2026-09-02; regenerates from the Rust repo's release assets once the exporter ships.

What each row does not say

The caveats, the evidence and the deliberate gaps — one line per venue, at full width, where they are readable. This is also where the wire goes when it is not one of the three the matrix compares, and where a market-data feed that carries more than a live tape says so.

Where history comes from

The venues above are how you trade. These are how you fill the store the backtester reads — the same engine, replayed over data you already hold. Two are ours; the rest are adapters to somebody else's account, and we ship the adapter rather than the data.

• data.vike.io archive — Full L2 book, taker tape and derived top-of-book. Reads by ranged HTTP with row-group pruning, so a 7 GB day costs only the row groups your token actually touches — not a 7 GB download. Polymarket only — the archive collector pins that venue; Hyperliquid arrives through the metrics row above.
• data.vike.io metrics — Graded cohort positioning, and the hourly asset panel. Hourly, but not bars — a graded cohort ladder and a perp panel, landing as kind=cohort and kind=perp_metrics. Derived analytics on the same cadence as candles, answering a different question. The same cohort ladder and hourly panel vike.io renders, landing in your store as kind=cohort and kind=perp_metrics. The exchange is a parameter; Hyperliquid is what it defaults to.
• Databento — Intraday bars, trades, quotes and L2 book. A vendor account of your own; we ship the adapter, not the data.
• Tardis — Intraday trades, quotes and L2 book; bars by resample. A vendor account of your own; we ship the adapter, not the data.
• Yahoo — Daily OHLCV bars. No key. The provider seam is pluggable; Yahoo is the one shipped today.
• The venues themselves — Klines, tick history and funding, straight from the venue. L1 is Dukascopy alone (`.bi5` tick quotes); the rest are bars. No venue-direct source serves trades or full-depth book at all. No keys. Every one of these is a public endpoint. IBKR is the single exception and it is not a key either — it needs a running TWS or IB Gateway, whose login is the entitlement.

Every one of these lands in the same local store under a kind= the backtest harness already reads, so a source you add is a source every strategy can replay. The datasets behind vike.io →