Skip to content
Genesis Ark

Qubit platform

A modular OEMS: start with one module, grow into the full platform

Qubit is built in layers. Read-only modules and trading tools work on their own. The core order management platform ships as one product, and add-ons run on top of it. Every layer shares the same connectors, data model and permissions.

01 / Why modular

Buy what you need, not a platform migration

Replacing a desk's trading stack in one move is slow and risky. Most firms want to fix one problem first: a reconciliation that takes half a day, TCA nobody trusts, or exposure that lives in five exchange consoles. Qubit lets you start there.

A read-only module installs against the venue accounts you already have, with read-only API keys. It cannot place an order. When it has earned its place, the trading modules and the core platform reuse the same connectors, instrument model and accounts, so the next step is a configuration change, not a new integration.

02 / Module map

How the platform is built

Layer 4
Add-ons

needs Core

Layer 3
Core OEMS

ships as one product

Layer 1
Shared foundation
  • Venue adapters
  • Common data model
  • Authentication

under every module

Fig. 1. Each layer reuses the one below it. A module bought on its own today is the same code the full platform runs. Illustrative composition with sample data.
  1. Add-ons

    Need the core

    Smart order routing, RFQ and OTC hub, auto-hedging, treasury and settlement, custody connectors, white-label brokerage.

    On the roadmap: margin and derivatives, market surveillance.

  2. Core platform

    Ships as one product

    Order management, execution gateway, accounts and permissions, position and balance ledger, pre-trade risk, audit trail.

  3. Standalone modules

    Work on their own

    Read-only: portfolio risk, reconciliation and trade capture, TCA, market data, reporting.

    Trading tools: unified exchange API, execution algorithms, pre-trade risk gateway, client pricing engine.

  4. Shared foundation

    In every install

    Venue connectors, common data model, authentication and permissions.

03 / Core OEMS

The core: one product, because it has to be

Six parts of an OEMS cannot be sold separately, because each depends on the others in real time. A fill has to update the order, the position and the risk limits in the same step. A risk check needs the live position. An auditor needs every one of those events in one log.

  1. 01

    Order management

    The lifecycle and state machine for every order, parent and child.

    Ships with the core · Details

  2. 02

    Execution gateway

    Venue adapters that turn orders into venue calls and venue events back into order state.

    Ships with the core · Details

  3. 03

    Accounts and permissions

    Who may trade what, on which account, up to which limit.

    Ships with the core · Details

  4. 04

    Position and balance ledger

    Positions and balances updated on every fill, per account and per venue.

    Ships with the core · Details

  5. 05

    Pre-trade risk

    Checks every order against limits and live positions before it is routed.

    Ships with the core · Details

  6. 06

    Audit trail

    An append-only, timestamped record of every event.

    Ships with the core · Details

The core is judged on one thing: after a disconnect, a restart or a venue outage, every order and every position is still correct.

04 / Ways to start

Three common starting points

  1. 01

    Start with visibility

    Portfolio risk, reconciliation, TCA and reporting.

    Read-only keys, no live-order risk, quick to install. Right for a desk that wants one view of exposure and a clean daily reconciliation before changing how it trades.

  2. 02

    Start with execution

    The unified exchange API, algorithms and pre-trade risk gateway.

    Right for a fund, prop firm or fintech that already has an OMS or a front end and needs normalized venue access, slicing and controls.

  3. 03

    Start with the platform

    The core plus the add-ons you need: smart order routing, RFQ, client pricing and auto-hedging, settlement.

    Right for a broker, bank or OTC desk that wants Qubit to be its order book of record.

05 / Deployment and integration

Installs where your other systems already are

Qubit ships as containers for your own cloud account or data center, or runs as a dedicated managed instance. It connects to venues through its adapters, to your clients through FIX, REST and WebSocket, and to your custodian, core banking and compliance tools through documented interfaces. KYC, screening, custody and banking stay with the providers you already use.

Fig. 2. Where the platform runs, what it connects to, and where the flow of funds stays. Illustrative composition with sample data.

What every module shares

One instrument model
Each venue's symbols, tick sizes, lot sizes, minimum notional and price precision are mapped to one internal instrument, so BTC-USDT means the same thing in routing, risk, TCA and reporting.
One account model
Firm, desk, trader, account and venue sub-account, with the same permissions everywhere.
One set of order states
The same states and transitions in the blotter, the API, the FIX gateway and the reports.
One authentication layer
Single sign-on through your identity provider, role-based access and API credentials scoped per application.
One event log
Every module writes to the same audit trail, so a question that crosses modules has one answer.

06 / How modules are sold

License the modules you use

Qubit is licensed module by module, not as a single platform subscription.

Start with a read-only module such as portfolio risk, reconciliation or TCA. Add trading modules when you are ready, and add the core platform when you want Qubit to be your order book of record. Each license comes with annual maintenance and support, which covers releases, security fixes and a support tier agreed in your contract.

07 / All modules

Every module and its status

Grouped by layer. Roadmap modules are planned and not available, and we do not publish dates for them.

Standalone modules

Work on their own · 08

Add-ons

Need the core · 09

FAQ

Questions we get asked

  • Can we start with one module and add the core later without migrating data?

    Yes. Standalone modules use the same data model and connectors as the core. When you add the core, existing accounts, instruments and history carry over.

  • Do the standalone trading modules need the Qubit front end?

    No. The unified exchange API, algorithms and pre-trade risk gateway can sit behind your own front end or OMS, connected over FIX or the APIs.

  • What does "runs on the core" mean in practice?

    Those modules need live order state, positions and limits from the core to work. Smart order routing, RFQ, auto-hedging and settlement all fall in this group.

  • Is the white-label brokerage a separate product?

    It is a configuration of the core with client pricing, auto-hedging, the ledger and custody connectors, delivered first as a headless API. See the white-label solution page for scope.

  • Which modules are on the roadmap?

    Margin and derivatives, market surveillance and DeFi venues. They are planned and not available, and we do not publish dates for them.

Find your starting module

A short scoping call is usually enough to map your current stack to Qubit's modules and pick a sensible first step.