Skip to content
Genesis Ark

Solutions

One trading core, configured for the way your firm trades

Every institution that trades crypto needs the same foundation: orders that are never lost, positions that are correct after a venue disconnects, risk checks that run before an order leaves the building, and an audit trail a regulator can read. What changes from firm to firm is the workflow on top. Qubit is licensed module by module, so you buy the parts your workflow needs and run them on infrastructure you control.

01 / Segments

Who Qubit is built for

  1. 01

    Brokers

    Agency and principal crypto brokerage

    Route client orders across venues, apply per-client pricing and limits, and prove best execution with your own records.

    Read: Qubit for brokers

  2. 02

    Banks and neobanks

    Crypto trading inside a regulated bank

    Add crypto trading inside your own data center or cloud account, with the controls, approvals and vendor documentation your risk committee expects.

    Read: Qubit for banks

  3. 03

    Exchanges

    Liquidity, hedging and institutional access

    Source external liquidity, hedge inventory and reconcile your ledger with the venues you trade on. Qubit sits next to your matching engine, not in place of it.

    Read: Qubit for exchanges

  4. 04

    OTC desks

    Quote, fill, hedge and settle

    Request quotes from several dealers at once, stream marked-up prices to clients and hedge the moment a client fills.

    Read: Qubit for OTC desks

  5. 05

    Asset managers and hedge funds

    Best execution across venues

    Give portfolio managers one view of exposure across exchanges and custodians, and give traders the algorithms and evidence they need for best execution.

    Read: Qubit for asset managers

  6. 06

    Proprietary trading firms

    Low-overhead access and risk

    One API to every venue, firm-wide risk limits and a kill switch that works across all of them at once.

    Read: Qubit for prop trading

  7. 07

    Fintechs launching crypto

    Brokerage-in-a-box for fintechs

    A brokerage-in-a-box: ledger, pricing, hedging and an admin console behind your brand, while you keep the license and the customers.

    Read: White-label brokerage

02 / Module fit

Which modules each segment usually licenses

Read down a column to see a segment's typical license set, as described on its page. Every license is per module, so any of these can change for your firm.

Module fit by segment
ModuleBrokersBanks and neobanksExchangesOTC desksAsset managers and fundsProprietary tradingWhite-label brokerage
Core
Core OEMS bundleTypicalTypicalRequiredTypicalTypicalOptionalTypical
Standalone
Pre-trade riskStart hereIn core bundleIn core bundleIn core bundleIn core bundleTypicalIn core bundle
Portfolio and risk monitorNot typicalNot typicalTypicalTypicalStart hereTypicalNot typical
Reconciliation and trade captureTypicalTypicalTypicalNot typicalTypicalNot typicalNot typical
Transaction cost analysisStart hereNot typicalNot typicalTypicalTypicalTypicalNot typical
Market data and consolidated bookNot typicalNot typicalTypicalNot typicalNot typicalTypicalNot typical
Reporting and statementsTypicalTypicalTypicalTypicalTypicalNot typicalTypical
Unified exchange APINot typicalNot typicalNot typicalNot typicalNot typicalTypicalNot typical
Execution algorithmsTypicalNot typicalTypicalTypicalTypicalTypicalNot typical
Client pricing engineOptionalTypicalNot typicalTypicalNot typicalNot typicalTypical
Add-ons
Smart order routingTypicalTypicalTypicalNot typicalTypicalOptionalNot typical
RFQ and OTC hubNot typicalTypicalTypicalTypicalTypicalNot typicalNot typical
Auto-hedgingOptionalTypicalTypicalTypicalNot typicalNot typicalTypical
White-label brokerageEarly accessNot typicalOptionalNot typicalNot typicalNot typicalNot typicalTypical
Treasury and settlementNot typicalTypicalTypicalTypicalNot typicalNot typicalTypical
Custody connectorsNot typicalTypicalTypicalTypicalTypicalNot typicalTypical
Margin and derivativesRoadmapNot typicalNot typicalNot typicalNot typicalRoadmapRoadmapNot typical
Market surveillanceRoadmapNot typicalRoadmapRoadmapNot typicalNot typicalNot typicalNot typical

Note. “In core bundle” means the module ships inside the Core OEMS bundle that segment licenses. Roadmap modules are listed where a segment page names them; they are not available today.

03 / Adoption

Start where the risk is lowest

Most firms do not replace their trading stack in one step, and they should not have to. Qubit modules are designed to be adopted in waves.

  1. 01

    Visibility first.

    Portfolio and risk monitor, Reconciliation and trade capture, TCA and Reporting and statements read data through read-only API keys and fill records. They place no orders, install quickly and give your team a clear picture of where you stand.

  2. 02

    Trading tools next.

    The Unified exchange trading API, Execution algorithms, Pre-trade risk gateway, Market data and Client pricing engine reuse the same venue connectors and work alongside the systems you already run.

  3. 03

    The full platform when you are ready.

    The Core OEMS bundle and its add-ons (Smart order routing, RFQ and OTC hub, Auto-hedging, Treasury and settlement, Custody connectors, White-label brokerage) take over order and position management end to end.

Each wave reuses the connectors and data model of the one before, so nothing you license early is thrown away later.

04 / Every client

What stays the same for every client

Infrastructure only.

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 infrastructure or a dedicated instance.

Run Qubit in your own environment, or have us operate a dedicated single-tenant instance for you. See Deployment.

Your data.

Orders, fills, positions and client records stay in databases you own.

Licensed by module.

Perpetual or term licenses per module, with annual maintenance and support. See Licensing.

Tell us how your desk trades today

A 45-minute call with an engineer, not a sales script. Bring your workflow and your constraints; we will tell you which modules fit and which do not.