Skip to content
Genesis Ark

Solutions / Proprietary trading

One API, one risk layer, every venue

Every trading team in a prop firm eventually writes its own exchange connectors, its own risk checks and its own position tracking. Qubit gives your firm one of each. Strategies talk to a single API, firm-wide limits are enforced before any order reaches a venue, and a kill switch can stop trading for a strategy, a trader or the whole firm across every venue at once. It runs on your servers, close to the venues you trade.

01 / The workflow

A day on a prop desk, step by step

Each step is labeled with the part of the platform that handles it.

  1. 01

    Connect once

    InConnectivity
  2. 02

    One data format

    InMarket data
  3. 03

    Firm-wide limits

    InPre-trade risk
  4. 04

    Enter and exit size

    InAlgorithms
  5. 05

    Firm exposure

    InPortfolio risk
  6. 06

    Cost per strategy

    InTransaction cost analysis

02 / What we hear

What we hear from prop firms

  • 01 Duplicate connectors

    “Each desk built its own connectors. When an exchange changes its API, three teams fix the same bug.”

  • 02 Firm exposure

    “Risk limits live inside each strategy, so nobody sees the firm's total exposure until the end of the day.”

  • 03 Kill switch

    “We need a kill switch that works everywhere at once, not one per bot.”

  • 04 Market data

    “Market data from each venue arrives in a different format, and normalizing it is a full-time job.”

  • 05 Order flow

    “Our edge is in the strategies. We are not sending order flow through anyone else's cloud.”

03 / How it fits

How Qubit fits your workflow

  1. 01

    Connect once

    Strategies connect once. The Unified exchange trading API gives every strategy one REST, WebSocket or FIX interface to every venue you trade, with normalized symbols, order types and error codes.

    Connectivity
  2. 02

    One data format

    Market data and consolidated order book delivers normalized prices, trades and depth from every venue, so strategies consume one format.

    Market data
  3. 03

    Firm-wide limits

    The Pre-trade risk gateway checks every order against per-strategy, per-trader and firm-wide limits: notional, position, order rate, price collars and restricted instruments. The kill switch sits here.

    Pre-trade risk
  4. 04

    Enter and exit size

    Execution algorithms handle the routine work of entering and exiting size, so strategy code can focus on signals.

    Algorithms
  5. 05

    Firm exposure

    The Portfolio and risk monitor shows positions, exposure and P&L for every strategy and for the firm in one place, in real time.

    Portfolio risk
  6. 06

    Cost per strategy

    TCA shows what each strategy pays in slippage and fees, by venue and by time of day.

    Transaction cost analysis

Fig. 1 / Proprietary trading

Fig. 1. Per-strategy and firm-wide limits checked before an order reaches a venue, with the kill switch scope shown. Illustrative composition with sample data.

04 / Deployment

On your servers, close to the venues

Prop firms self-host Qubit on their own servers or cloud instances, usually in the regions closest to the venues they trade. Because Qubit runs in your environment, you can measure latency in your own setup, with your own venues, before you commit. See Deployment.

05 / Regulation

Infrastructure only. Never in the flow of funds.

Qubit never holds client money or crypto and is never in the flow of funds. Your banks and custodians hold assets. Your venue and liquidity agreements stay in your name.

Your strategies stay yours. They call Qubit's API for venue access, market data and risk checks, and Qubit never sees the logic behind an order.

FAQ

Questions we get asked

  • What latency should we expect?

    We do not publish latency figures, because they depend on where Qubit runs, which venues you trade and how your network is built. During evaluation we help you measure order-to-venue and market-data latency in your own environment.

  • Can our strategies keep their own code and logic?

    Yes. Your strategies stay yours. They call Qubit's API for venue access, market data and risk checks, and Qubit never sees the logic behind an order.

  • How does the kill switch work?

    An authorized user or an automated rule can halt new orders and cancel open orders for a strategy, a trader, an account or the whole firm. The action applies across every connected venue and is written to the audit trail.

  • Do you support perpetuals and futures?

    Order routing for derivatives depends on each venue adapter and is confirmed per venue during onboarding. The Margin and derivatives module, which adds collateral and funding-rate management, is on the roadmap.

Test it where your strategies run

We will set up an evaluation in your environment so you can measure it against your current connectors with your own venues.