Skip to content

Venue capability matrix

VerifiedOwner Documentation integratorLast verified backend@efa38e04e2db37a444e9f17100323c2ad4b83647 nautilus-trader@648970ce64a304d93da0a29320cb6e19b905fa39 (v2.0.0rc3)

This page is generated

Rendered from manifest/venue-surface.json, extracted from the venue profile package and the upstream adapters package at the two pinned commits. There is no hand-maintained venue list anywhere in this repository, and the build fails if the committed page stops matching its input.

What the columns mean

Four different things get called "supported". They are kept apart.

Column What it asserts How it was established
Upstream adapter The pinned NautilusTrader release ships an adapter subpackage for this venue. Directory listing of the upstream adapters package at the pinned commit.
ONIX profile ONIX has a venue integration profile module for it. Directory listing of the venue profile package at the backend pin.
Focused tests ONIX has tests naming this venue specifically. Filename match across the backend test tree at the pin. Test presence, not test outcome — nothing was executed.
Configured deployment Some ONIX deployment is configured to run it. Not established. This pass read Git objects only.
Observed production It was seen carrying live data in production. Not established. This pass started no process and observed no feed.

A profile plus a passing-by-name test file is evidence that the integration was built and exercised. It is not evidence that anyone is running it.

Venues

Venue Upstream adapter ONIX profile Focused tests Configured deployment Observed production
Architect AX yes yes 1 not established not established
Betfair yes yes 1 not established not established
Binance yes yes 9 not established not established
BitMEX yes yes 1 not established not established
Blockchain.com yes yes 1 not established not established
Bybit yes yes 3 not established not established
Coinbase yes yes 1 not established not established
Databento yes yes 1 not established not established
Deribit yes yes 1 not established not established
Derive yes yes 1 not established not established
dYdX yes yes 1 not established not established
Hyperliquid yes yes 5 not established not established
Interactive Brokers yes yes 12 not established not established
Kraken yes yes 1 not established not established
Lighter yes yes 1 not established not established
OKX yes yes 1 not established not established
Polymarket yes yes 1 not established not established
Tardis yes yes 1 not established not established

18 venue integrations. Every one has both an upstream adapter at the pinned release and an ONIX profile module, and every one has at least one focused test naming it.

Counting, and one thing that is not a venue

The upstream adapters package contains 19 subpackages at the pinned release. ONIX has 18 venue profiles. The difference is not a gap:

Upstream subpackage Why there is no ONIX venue profile
sandbox A simulated execution client, not an exchange integration. It is counted here so the difference between 19 upstream subpackages and 18 venues is visible rather than silently absorbed.

Documentation that reports 19 venue integrations has counted a simulated execution client as an exchange.

One naming difference is worth stating plainly: ONIX names its Interactive Brokers profile module ibkr, while the upstream package is interactive_brokers. That single alias is declared in the extractor, never inferred from a prefix.

Focused tests per venue

Test files are listed so a reviewer can go and read them rather than take a count on trust. Presence is what is claimed; no test was executed by this documentation pass.

Architect AXtest_venues_profile_architect_ax.py

Betfairtest_venues_profile_betfair.py

Binancetest_binance_discovery_preflight.py, test_binance_history_deep.py, test_binance_history_floor.py, test_binance_profiles_wire.py, test_binance_stream_capacity.py, test_internal_1m_binance_routing.py, test_spine_binance_deep_continuation.py, test_spine_binance_paged_floor.py, test_venues_profile_binance.py

BitMEXtest_venues_profile_bitmex.py

Blockchain.comtest_venues_profile_blockchain.py

Bybittest_bybit_adapter_authority.py, test_bybit_authority_repair_gateway.py, test_stage1_bybit_channel_suppression.py

Coinbasetest_venues_profile_coinbase.py

Databentotest_venues_profile_databento.py

Deribittest_venues_profile_deribit.py

Derivetest_venues_profile_derive.py

dYdXtest_venues_profile_dydx.py

Hyperliquidtest_hyperliquid_backtest_boundary.py, test_hyperliquid_confirmation.py, test_hyperliquid_one_ip_live_gate.py, test_hyperliquid_patched_runtime.py, test_internal_1m_hyperliquid_ack.py

Interactive Brokerstest_gateway_v2_ibkr.py, test_ibkr_config.py, test_ibkr_contract.py, test_ibkr_execution.py, test_ibkr_execution_admission.py, test_ibkr_execution_gate.py, test_ibkr_execution_readiness.py, test_ibkr_operator_strategy.py, test_ibkr_preview.py, test_ibkr_roster.py, test_ibkr_search.py, test_ibkr_session.py

Krakentest_venues_profile_kraken.py

Lightertest_venues_profile_lighter.py

OKXtest_venues_profile_okx.py

Polymarkettest_venues_profile_polymarket.py

Tardistest_venues_profile_tardis.py

Evidence and source pins for this page

Verified. Current behaviour, confirmed in source at the pinned commit.

Verified on against the following immutable sources:

  • onix-docs:manifest/venue-surface.json
  • backend:python/src/onix_engine/venues/profiles/

Status tokens are defined on the documentation and status model page. Every pin on this site is listed under versions and source pins.