Skip to content
Genesis Ark

02 / Execution management

Available

Reach every venue through one gateway, and route each order on what you will actually pay

Qubit's execution layer gives your desk normalized access to every connected exchange and OTC venue. Its smart order router reads the consolidated book and places child orders where the all-in price is best after fees, at the size you need, with the balance you actually have on each venue.

Layer
Core · Standalone · Add-on
Works on its own
Yes
Interfaces
FIX, REST, WebSocket in; venue adapters out
Fig. 1. A parent order split across venues by all-in price after fees. Illustrative composition with sample data.

01 / The problem

The best displayed price is often not the best price you can get

The top of the book on one exchange can hide thin depth behind it, a high taker fee, or a balance you do not have on that venue. Splitting an order across venues by hand is slow, and every venue has its own symbols, precision rules, rate limits and error codes. Desks end up either overpaying on one venue or paying engineers to maintain a pile of exchange integrations.

02 / What it does

What the execution layer handles

  1. 01

    Normalized venue access

    One order model across every connected venue. Qubit translates symbols, precision, lot sizes and venue-specific order flags in both directions.

  2. 02

    Fee-aware routing

    The router compares venues on the all-in price: book price plus your maker or taker fee on each venue, by fee tier where configured.

  3. 03

    Depth-aware routing

    It walks the consolidated book to the size of the order, rather than routing to a top-of-book quote that cannot fill it.

  4. 04

    Balance-aware routing

    Only venues where the account holds enough quote or base currency are eligible, so child orders are not rejected for insufficient funds.

  5. 05

    Venue controls

    Include or exclude venues per account, order or instrument, set a per-venue maximum child size and keep a venue in a reduced-use state after errors.

  6. 06

    Rate limit management

    Qubit tracks each venue's request budget per key and paces orders and cancels to stay inside it.

  7. 07

    Direct market access

    Traders can still send an order to a named venue, with the same risk checks and audit trail as routed orders.

Fig. 2. Each stage writes to the audit trail.

03 / How it works

How a routed order is placed

  1. 01

    Snapshot

    When a routed order arrives, the router reads the consolidated book for the instrument, the account's balances on each venue and the configured fees.

  2. 02

    Rank

    It ranks price levels across venues on all-in price, skipping venues that are excluded, disconnected, short of balance or near their rate limit.

  3. 03

    Slice

    It sizes child orders against available depth and per-venue limits, and chooses to take liquidity, post it or do both, according to the routing instruction.

  4. 04

    Send and watch

    Child orders go out in parallel. As fills, rejects and book changes arrive, the router reprices or reroutes the remainder.

  5. 05

    Complete

    The parent completes when filled, canceled or when its limit price can no longer be met, and every routing decision is kept for TCA.

04 / Specifics

Technical specifics

Routing instructions

Take (sweep displayed liquidity up to a limit price), post (rest passively on the best eligible venue), and take then post (sweep what is available inside the limit, rest the remainder).

Routing inputs

Consolidated L2 book, configured maker and taker fees per venue and account, available balance per venue, per-venue minimum and maximum order size, venue health and rate limit headroom.

Venue adapter responsibilities

Order entry, amend and cancel; execution and fill events; balance and position queries; open-order and fill recovery after reconnect; mapping of venue error codes to a common set of reject reasons.

Interfaces in

Qubit OMS, REST and WebSocket APIs, FIX order entry (see Connectivity).

Interfaces out

Venue REST, WebSocket and FIX APIs, through one adapter per venue. The current list of connected venues and the status of each is on the Integrations page.

05 / Controls and audit

What you configure, and what gets written down

Configurable

  • Venues included or excluded per account, order or instrument
  • Maker and taker fees per venue and account, by fee tier
  • Per-venue minimum and maximum child order size
  • Reduced-use state for a venue after errors
  • Routing instruction per order: take, post, or take then post
  • Manual venue exclusion by a trader at any time

Logged to the audit trail

  • routed order received · book, balance and fee snapshot
  • venue ranking · eligible and skipped venues, with reason
  • child order sent · venue, size, price, take or post
  • reprice and reroute of the remainder
  • venue health change · eligible, reduced use, excluded
  • parent complete · filled, canceled or limit unreachable

06 / Where it fits

Works on its own
Yes, as the unified exchange API: one API and FIX gateway to many venues, for firms that keep their own OMS.
Needs the core
Smart order routing needs the core platform and the market data module, because it routes against live positions, balances and the consolidated book.
Who uses it
Funds and asset managers executing size, prop trading firms, brokers routing client flow, exchanges sourcing external liquidity, fintechs that need one connection instead of many.

FAQ

Questions we get asked

  • Can we use the execution layer without the rest of Qubit?

    Yes. The unified exchange API is sold on its own. Your OMS or front end sends orders over FIX or REST, and Qubit handles each venue's connection, symbols and rules. Smart order routing needs the core.

  • Whose exchange accounts are used?

    Yours. Qubit connects with your API keys to your accounts, under your liquidity agreements and fee tiers. Qubit is not a broker and does not trade on its own account.

  • How does the router handle a venue that is degrading?

    Venues with repeated errors, rising reject rates or a lost market data feed drop out of the eligible set until their health recovers. Traders see the venue state on screen and can exclude a venue manually at any time.

  • Does routing take withdrawal or transfer costs into account?

    The router prices the trade itself: book price and trading fees, against balances already on each venue. Moving balances between venues is handled by treasury, which proposes rebalancing transfers based on where you trade.

  • Can we add a venue that is not connected yet?

    Yes. New adapters are built against a common interface. We add venues as part of our release cycle, and clients with source access can build their own.

See how your orders would route

Bring a recent order and its fills. We will walk through how Qubit would have split it across your venues.