Qubit by Genesis Ark · Institutional crypto OEMS
Every crypto order, from ticket to reconciled position, on infrastructure you control.
Qubit is an order and execution management system for brokers, banks, exchanges, OTC desks and funds. It runs on your own servers or as a dedicated managed instance, it is licensed module by module, and your orders, positions and client data stay with you.
Sample order events: a 12.5 BTC buy order is accepted, passes pre-trade checks, is routed to four venues and fills in full.
The problem
Crypto liquidity is fragmented. Your desk should not be.
A single client order in crypto can touch several exchanges, an OTC dealer and a custodian, each with its own API, symbology, fee schedule and rate limits. Most desks hold this together with a router from one vendor, a risk spreadsheet, exchange web consoles and an end-of-day reconciliation that someone runs by hand.
That works until it does not: a venue drops its WebSocket mid-fill, a fat-fingered order reaches the book, a balance on one exchange no longer matches the ledger, or a regulator asks for the full history of an order and its children. Qubit puts order state, risk, execution and post-trade in one system with one data model, so the answer to "what happened to this order" is a query, not an investigation.
- Client funds or assets held by us. Infrastructure only, never in the flow of funds.
- 0Client funds or assets held by us. Infrastructure only, never in the flow of funds.
- Deployment models: self-hosted, or a dedicated managed instance.
- 2Deployment models: self-hosted, or a dedicated managed instance.
- Licensing, with annual maintenance and support.
- Per moduleLicensing, with annual maintenance and support.
- Interfaces, with one order model across all three.
- FIX · REST · WSInterfaces, with one order model across all three.
Order lifecycle
What happens between “send” and “settled”
01
Captured
The order arrives from the Qubit blotter, your own front end over REST or WebSocket, or a client over FIX. It gets an internal ID, keeps your client order ID, and its first state is written to the audit log before anything else happens.
02
Checked
Pre-trade risk runs every applicable check: account permissions, restricted instruments, order size, price collar against the reference price, credit and position limits, open-order and message-rate limits. A failure rejects the order with a specific reason.
Pre-trade risk · DESK-01ILLUSTRATIVEFig. 1. Pre-trade checks on a sample order, one blocked by the price collar. Illustrative composition with sample data. 03
Worked
A direct order goes to its venue. A parent order goes to an algorithm or to the smart order router, which slices it into child orders and places them across venues based on the consolidated book, fees and available balance.
04
Filled
Fills come back from each venue, are normalized and are applied to the order and to the position ledger in one step, so risk and P&L always see the same numbers as the blotter.
Smart order routing · ORD-8812ILLUSTRATIVEFig. 2. A parent order split across four venues by price after fees. Illustrative composition with sample data. 05
Reconciled
Post-trade matches every fill against venue reports and custody balances, books it in the double-entry ledger and flags any break for a person to resolve.
06
Reported
TCA scores the execution, and reporting turns the same records into client confirmations, statements and regulatory exports.
Reconciliation · VENUE AILLUSTRATIVEFig. 3. Internal ledger matched against a venue statement, with one break flagged. Illustrative composition with sample data.
One order ID follows the trade from step 1 to step 6. Nothing is rekeyed.
The platform
One platform, twelve modules, one data model
Buy the whole platform or start with one module. Every module shares the same instruments, accounts, orders and fills, so adding the next one does not mean another integration project.
- 01Order managementThe order book of record: lifecycle, parent and child orders, allocations and a full audit trail.
- 02Execution and smart order routingNormalized access to every connected venue, with routing that weighs price, depth, fees and available balance.
- 03AlgorithmsTWAP, VWAP, POV, iceberg and pegged strategies with parameters you can change in flight.
- 04RFQ and OTCRequest quotes from several dealers at once, compare them against the lit market and keep every quote for best execution.
- 05Pre-trade riskLimits, price collars, credit and restricted lists checked on every order before it leaves the building.
- 06Portfolio riskBalances, positions, P&L and exposure across venues and custodians, through read-only keys.
- 07Post-tradeTrade capture, three-way reconciliation, a double-entry ledger, settlement and treasury.
- 08TCAFills scored against arrival, VWAP, TWAP and markouts, with fees included.
- 09Market dataNormalized order books, trades and reference data, and a consolidated book across venues.
- 10Client pricing and auto-hedgingStreaming prices per client tier with spreads and skew, and hedging that offsets client flow automatically.
- 11ConnectivityFIX, REST and WebSocket APIs in, venue adapters out.
- 12ReportingStatements, confirmations, best execution, regulatory exports and India TDS reports.
RoadmapOn the roadmap: margin and derivatives, market surveillance and DeFi venues. Planned, not available, no release date published.
System of record
The parts that matter at 3 a.m. on a Sunday
Crypto trades around the clock and venues fail without notice. The core of Qubit is designed around the failures a desk actually sees.
- No lost orders
- Every order and every state change is written to a persistent event log before it is acknowledged. A restart replays the log and resumes from the last known state.
- No duplicate orders
- Client order IDs are idempotent: a retried request after a timeout returns the original order instead of creating a second one.
- Correct positions after a disconnect
- When a venue session drops, Qubit marks its open orders as unknown, reconnects, pulls open orders and recent fills from the venue and reconciles them before trading resumes on that venue.
- Cancel on disconnect
- If a client session or a trader's connection drops, you choose per session whether its working orders stay working or are canceled.
- Kill switch
- Halt all trading, or trading for one account, trader, instrument or venue, from one control. Halting cancels working orders and blocks new ones until a permitted user lifts it.
- Full audit trail
- Every order, amendment, cancel, fill, quote, risk decision, limit change and login is timestamped and attributed. The log is append-only and exportable.
Deployment
Your infrastructure, or a dedicated instance run for you
Most institutional crypto platforms are hosted, multi-tenant services. That is a reasonable choice for many firms. It is a hard one for a bank whose data must stay in-country, a broker whose regulator wants the trading system inside its own perimeter, or a desk that does not want its order flow sitting on a vendor's servers.
Qubit is built to be installed. You can run it yourself or have us run a dedicated instance for you.
| Attribute | Self-hosted | Dedicated managed instance |
|---|---|---|
| Where it runs | Your data center or your cloud account | A single-tenant install for your firm, in our cloud account or yours |
| Who operates it | Your team; we ship releases and support | Us, under an agreed support agreement |
| Your data | Never leaves your environment | Isolated to your instance; never shared with other clients |
| Upgrades | You schedule them | Scheduled with you |
| Best for | Banks, regulated brokers, firms with in-house platform teams | Fintechs and smaller desks without a trading infrastructure team |
Licensing
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 it 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. Source access is available for firms that want their own developers to customize the platform. We do not publish a price list; pricing depends on modules, deployment model and support tier.
Trust and control
Infrastructure only. Your funds, keys and clients stay yours.
- Never in the flow of funds
- Qubit does not hold client money or crypto, is not a counterparty to any trade and does not settle on anyone's behalf. Transfers are instructions that your custodian or bank executes and signs.
- Your exchange keys stay in your environment
- In a self-hosted install, venue API keys are stored encrypted in your infrastructure and are never sent to us.
- Permissions that match your org chart
- Firm, desk, trader and account hierarchy, with role-based permissions on who may trade, approve, change limits or view data.
- Four-eyes on sensitive changes
- Limit increases, new accounts and manual ledger adjustments can require a second approver.
- Evidence for auditors
- The audit trail, risk decisions and reconciliation history are exportable for internal audit, external audit and regulators.
- Security controls, described plainly
- The Security page lists the controls we build and operate. We do not claim certifications we do not hold; certification is on our roadmap.
Who it is for
Built for the firms that run crypto desks
- BrokersOffer crypto to your clients with your own pricing, limits and hedging, and keep the client relationship.
- BanksAdd crypto trading inside your own perimeter, with the controls, audit trail and data residency your risk team expects.
- ExchangesRoute client orders to external liquidity, run an OTC desk beside your order book and reconcile both.
- OTC desksQuote clients from a consolidated price, hedge automatically and settle with counterparties on a net basis.
- Asset managers and hedge fundsExecute size across venues with algorithms, see exposure in one place and prove best execution.
- Proprietary trading firmsDirect, normalized access to many venues, with pre-trade risk that does not get in the way.
- FintechsLaunch a branded crypto brokerage on a headless API without building the trading core yourself.
Regional fit
Global by design, built with India, the Middle East and Southeast Asia in mind
The large hosted platforms were built around US and European venues and reporting. Qubit was built with the markets they serve less well in mind. That means adapters for regional venues alongside global ones, pricing in local currencies such as INR built from USDT pairs and FX, and reporting that includes India's TDS on virtual digital asset transfers. It also means a deployment model that works where data has to stay in the country.
None of this makes Qubit a regional product. The same platform serves a desk in Singapore, Dubai, Mumbai or London.
For developers
APIs your engineers will recognize
Order entry, drop copy and market data over FIX. Reference data, configuration and reporting over REST. Streaming orders, positions and prices over WebSocket. One instrument model and one set of order states across all three, documented with examples.
// Request (illustrative){ "clientOrderId": "desk01-20261031-0042", "account": "DESK-01", "instrument": "BTC-USDT", "side": "BUY", "type": "LIMIT", "quantity": "2.50000000", "limitPrice": "64210.00", "timeInForce": "GTC"}// Response{ "orderId": "ORD-8812", "clientOrderId": "desk01-20261031-0042", "status": "NEW"}Illustrative request. See the API overview for the reference.
Working with us
What to expect from us
01
We tell you what is live
Every module on this site carries its status. Roadmap items are labeled and carry no date until we can commit to one.
02
We scope in writing
Modules, venues, deployment and acceptance criteria are written into the agreement before work starts.
03
We stay an infrastructure provider
KYC, trading licenses, custody and banking stay with you and your chosen providers. We integrate with them; we do not replace them.
04
Your developers can build on it
Source access and documented APIs mean you are not waiting on our roadmap for every change.
From insights
All insights- Buyer's guideOMS vs EMS vs OEMS in crypto: what each one does and which one you needWhat an OMS, an EMS and an OEMS each do in institutional crypto trading, how they differ from traditional markets, and how to decide which one your firm needs.
- ExecutionSmart order routing after fees: what "best price" really meansWhy the best quoted price is rarely the best executed price in crypto, and what a smart order router must weigh: fees, depth, fee tiers, balances and latency.
- DeploymentSelf-hosted vs SaaS trading infrastructure: how to chooseComparing SaaS, dedicated managed and self-hosted deployment for institutional crypto trading systems: data residency, operations, security, cost and exit.
FAQ
Questions we get asked
Is Qubit a broker, exchange or custodian?
No. Qubit is software. It does not hold client funds or assets, it is not a counterparty, and it never sits in the flow of funds. Your firm keeps its own licenses, liquidity agreements, custodians and banks.
Can we run Qubit on our own infrastructure?
Yes. Self-hosting is the default model. Qubit installs in your data center or cloud account, and your data and venue keys stay there. If you would rather not operate it, we can run a dedicated single-tenant instance for you.
Do we have to buy the whole platform?
No. Read-only modules (portfolio risk, reconciliation, TCA, market data, reporting) and several trading modules work on their own. The core order management platform ships as one product, and add-ons such as smart order routing and RFQ run on top of it. Each module page says which is which.
Which venues do you connect to?
The Integrations page lists venue, custody and data connections with the status of each. If a venue you need is missing, tell us; adding adapters is standard work, and your own developers can build one against the adapter interface.
How is Qubit priced?
As a license per module, with annual maintenance and support. Pricing depends on the modules, the deployment model and the support tier, so we quote it after a scoping call. The Licensing page explains the model.
Do you hold SOC 2 or ISO 27001?
Not today, and we do not claim to. The Security page describes the controls we build and operate. Certification is on our roadmap, and we are glad to walk your security team through the controls in detail.
See Qubit on your own workflow
Tell us how your desk trades today: venues, order flow, risk process and where post-trade breaks. We will show you the modules that fit and how they would deploy in your environment.