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
- Smart order routingAvailable
- RFQ and OTC hubAvailable
- Auto-hedgingAvailable
- White-label brokerageEarly access
- Treasury and settlementAvailable
- Custody connectorsAvailable
- Margin and derivativesRoadmap
- Market surveillanceRoadmap
- DeFi connectivityRoadmap
needs Core
- Order managementAvailable
- Execution gatewayAvailable
- Accounts and permissionsAvailable
- Position and balance ledgerAvailable
- Pre-trade riskAvailable
- Audit trailAvailable
ships as one product
- Portfolio and risk monitorAvailable
- Reconciliation and trade captureAvailable
- Transaction cost analysisAvailable
- Market data and consolidated bookAvailable
- Reporting and statementsAvailable
- Unified exchange APIAvailable
- Execution algorithmsAvailable
- Client pricing engineAvailable
works on its own
- Venue adapters
- Common data model
- Authentication
under every module
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.
Core platform
Ships as one product
Order management, execution gateway, accounts and permissions, position and balance ledger, pre-trade risk, audit trail.
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.
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.
- 01
Order management
The lifecycle and state machine for every order, parent and child.
Ships with the core · Details
- 02
Execution gateway
Venue adapters that turn orders into venue calls and venue events back into order state.
Ships with the core · Details
- 03
Accounts and permissions
Who may trade what, on which account, up to which limit.
Ships with the core · Details
- 04
Position and balance ledger
Positions and balances updated on every fill, per account and per venue.
Ships with the core · Details
- 05
Pre-trade risk
Checks every order against limits and live positions before it is routed.
Ships with the core · Details
- 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
- 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.
- 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.
- 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.
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-USDTmeans 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.
Core OEMS
Ships as one product · 06
- Order management
Order lifecycle and state machine for parent and child orders, amendments, cancels and fills.
Available - Execution gateway
Venue adapters that turn orders into exchange calls and turn fills back into order state.
Available - Accounts and permissions
Desks, traders, accounts and entitlements that decide who may trade what, where.
Available - Position and balance ledger
Every fill updates positions and balances at once, so risk and P&L read the same numbers.
Available - Pre-trade risk
Limit, price band and restricted-list checks that run before an order leaves the building.
Available - Audit trail
An append-only, timestamped event log of every order, change, check and fill.
Available
Standalone modules
Work on their own · 08
- Portfolio and risk monitor
Balances, positions, P&L and exposure across venues through read-only API keys.
Available - Reconciliation and trade capture
Matches internal records against venue fills, balances and custody statements.
Available - Transaction cost analysis
Scores fills against arrival, VWAP and other benchmarks, with fees and slippage in basis points.
Available - Market data and consolidated book
Normalized feeds and a consolidated order book across connected venues.
Available - Reporting and statements
Client statements, trade confirmations, tax lines and regulatory exports.
Available - Unified exchange API
One FIX, REST and WebSocket interface to many venues.
Available - Execution algorithms
TWAP, VWAP, POV, iceberg and pegged strategies with parameter controls.
Available - Client pricing engine
Streams prices to clients with spreads and markups per tier, pair and size.
Available
Add-ons
Need the core · 09
- Smart order routing
Splits orders across venues by price after fees, depth and venue constraints.
Available - RFQ and OTC hub
Requests quotes from several dealers at once and executes against the best response.
Available - Auto-hedging
Offsets client trades on venues automatically, with netting and hedge thresholds.
Available - White-label brokerage
Branded or headless brokerage for your own customers, built on the core.
Early access - Treasury and settlement
Balances, transfers between venues and custodians, and netted settlement.
Available - Custody connectors
Connections to institutional custodians and wallet infrastructure.
Available - Margin and derivatives
Collateral, funding rates and perpetual positions in the ledger and risk engine.
Roadmap - Market surveillance
Detection of wash trading, spoofing and layering from order and trade data.
Roadmap - DeFi connectivity
Routing to on-chain liquidity alongside centralized venues.
Roadmap
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.