Skip to content
Genesis Ark

09 / Portfolio risk

Available

See every balance, position and exposure across venues in one view

Qubit's portfolio risk module pulls balances, positions and trades from each exchange and custodian with read-only keys and shows them in one place: P&L, and exposure by asset, venue and counterparty, with alerts when a number crosses a line you set.

Layer
Standalone, read-only
Works on its own
Yes
Interfaces
Read-only venue APIs, custody connectors
Fig. 1. Exposure by venue and asset, with utilization against concentration limits. Illustrative composition with sample data.

01 / The problem

Your exposure lives in ten browser tabs

A desk with accounts on several exchanges, a custodian and two OTC counterparties has no single place where its position is true. Someone exports balances, pastes them into a spreadsheet, prices them at whatever mark was handy and sends it around. By the time the risk report arrives, it describes the morning. And the question that matters most in crypto, how much do we have on each venue if it stops processing withdrawals, is the hardest one to answer.

02 / What it does

What the module shows

  1. 01

    Consolidated balances

    Every asset on every connected exchange account, sub-account and custody wallet, in native units and in your reporting currency.

  2. 02

    Positions and P&L

    Positions per instrument and account with realized and unrealized P&L, using the cost basis method you choose.

  3. 03

    Exposure by asset

    Net and gross exposure per asset, including stablecoins treated as their own risk, not as cash.

  4. 04

    Exposure by venue and counterparty

    How much of your capital sits on each exchange, custodian and OTC counterparty, as an amount and as a share of the total.

  5. 05

    Concentration limits

    Set a maximum exposure per venue, counterparty or asset and see utilization against each.

  6. 06

    Alerts

    Notify risk users when a limit is approached or breached, a venue stops responding or a balance changes beyond a threshold.

  7. 07

    History

    Snapshots at fixed intervals, so you can compare exposure today with any earlier point.

03 / How it works

From read-only keys to a live risk view

Fig. 2. The stages below, in order. Each one writes to the audit trail.
  1. 01

    Connect

    Add read-only API keys for each exchange account and connect custody accounts. In a self-hosted install the keys stay in your environment.

  2. 02

    Collect

    Qubit polls and streams balances, positions and fills from each source and normalizes assets and instruments to one model.

  3. 03

    Price

    Positions are marked to a reference price from the market data module or a pricing source you choose.

  4. 04

    Aggregate

    Balances roll up by account, desk, entity, asset, venue and counterparty.

  5. 05

    Alert

    Limits and thresholds are checked on every update, and breaches go to the users and channels you configure.

04 / Specifics

Technical specifics

Sources

Exchange accounts and sub-accounts through read-only API keys, custody accounts through custody connectors, OTC counterparty balances from settlement records, and positions from the Qubit ledger when the core is installed.

Marks

Last trade, mid or a composite reference price from the market data module, configurable per asset, with stale-price flags.

P&L methods

FIFO, LIFO or weighted average cost, per entity. Realized, unrealized and fee-inclusive P&L.

Grouping dimensions

Legal entity, desk, strategy, account, asset, venue, counterparty.

Alert channels

In-app, email and webhook.

05 / Controls and audit

What you configure, and what gets written down

Configurable

  • Read-only keys per exchange account and sub-account
  • Mark source per asset
  • Cost basis method per entity
  • Concentration limits per venue, counterparty or asset
  • Alert thresholds, recipients and channels
  • Account to legal entity mapping

Logged to the audit trail

  • source connected or disconnected · last update time
  • balance change beyond threshold
  • limit approached or breached · utilization
  • venue stopped responding
  • stale price flagged
  • snapshot taken

06 / Where it fits

Works on its own
Yes. It is read-only and needs only API access to your exchange and custody accounts. It cannot place orders.
Needs the core
No. With the core platform installed, it reads positions directly from the Qubit ledger as well as from venues.
Who uses it
Hedge funds and asset managers, prop trading firms, brokers and OTC desks holding inventory, treasury teams at exchanges and fintechs.

FAQ

Questions we get asked

  • Can this module trade or move funds?

    No. It uses read-only keys and has no order or withdrawal path. That is why it can be installed quickly and with little operational risk.

  • How current is the data?

    It depends on what each venue provides. Where a venue streams account updates, balances update as they change. Where it only offers polling, Qubit polls within the venue's rate limits. Each source shows the time of its last update.

  • How do you treat stablecoins?

    As assets with their own exposure, not as cash. You can see how much of your position depends on each stablecoin issuer and set limits on it.

  • Can we see exposure per legal entity?

    Yes. Accounts map to legal entities, and every view can be grouped and filtered by entity.

Know where your capital is, on every venue, right now

A scoping call with an engineer, then a demo on sample data that mirrors your venues, desks and limits.