A real-time, collateral-aware risk and margin engine for digital-asset trading infrastructure — built for exchanges, brokers, prime brokers and clearing venues.
Customer books now blend spot, perpetuals, futures, options and volatile collateral — while margin logic stays product-based, static, or too slow for live trading.
Spot, perps, futures and options no longer behave like isolated line items.
BTC, ETH and stablecoins carry their own risk — yet are often netted as static value.
Notional percentages and Greeks-only proxies miss offsets, concentration and stress.
Pre-trade checks and liquidation can't wait on a stale or partial recalculation cycle.
What is the customer's required margin right now?
How much available margin remains after positions, collateral and market risk?
How much more can they trade before breaching the portfolio constraint?
How does that change under current vs. stress views?
How are option exposures valued if the account becomes distressed?
CloudRisk Diversity evaluates the whole book as a single integrated risk object — returning margin, capacity and stress analytics within a defined low-latency budget.
Liquidation and margin-call levels from one model.
Upfront and ongoing trading buffer above the call level.
Resources net of applicable margin, at account level.
Tradeable long / short capacity by instrument & direction.
Portfolio diagnostics where enabled.
Blended, stress-aware margin measures.
Every instrument is revalued under shocked scenarios and represented as a PnL vector. Portfolio risk is the aggregation of those vectors — capturing offsets, concentration and nonlinearity that static percentages cannot.
Collateral balances are represented by their economic risk profile, so changes in collateral value flow through the same PnL-vector framework as trading positions.
In digital-asset markets, collateral can move as much as the positions it backs.
Engines that ignore collateral risk overstate resources exactly when stress hits.
Outputs reflect both the value of collateral and the risk of holding it.
For each enabled instrument, the engine solves how much additional long or short quantity the customer can add before reaching the portfolio constraint — portfolio-specific, not a static order-size cap.
Options follow the same principle — unit option PnL vectors scale linearly in contract quantity, so long / short option capacity is solved in the same framework.
The feeder connects to exchange websocket streams, normalizes venue-specific messages, enriches them with common metadata, and routes data into pricing, calibration, market-state construction and option-surface updates.
Direct connections across major crypto venues.
Venue messages mapped to one instrument vocabulary.
Feeds calibration, pricing and finalized market states.
Each option contributes a shocked revaluation vector reflecting spot, dividends, curves and Heston parameters, aggregated into the same portfolio outputs. No Greeks-only shortcut.
Backward-flat parameter selection for arbitrary maturities.
Values a set of positions from one consistent market state.
Aggregated by factor — no misleading scalars across currencies.
Risk and liquidation teams can compare immediate liquidation against hedged run-off or hold-to-maturity — instead of treating a forced sale as the only path.
Analytics support default-management decisions — they do not replace the customer's liquidation discretion.
Ingest · normalize · calibrate · build option surfaces · run historical simulation
Reads only finalized market states · portfolio aggregation · margin & single-order-limit solving
Target calibration cadence ~60s · the live path never consumes a failed or partial calibration — it holds the last finalized state.
Every live request is calculated against one defined risk state.
Heavy market preparation stays off the live request path.
Degraded-mode behaviour is easy to monitor, explain and govern.
Calibration and simulation are done upstream; each live request simply reads a finalized state and aggregates. Throughput grows by scaling out the live service — without changing methodology or relaxing the latency target. Feeders, calibration, market-state construction and risk calculation all scale independently.
External performance claims to be supported by benchmark methodology, concurrency levels, percentile latency and deployment topology.
Core data, messaging, orchestration and secrets-management run in clustered configurations across two regions with multiple data centres each — no critical work pinned to a single process or machine.
Two regions, multiple data centres — geographic and infrastructure redundancy.
Calibration and calculation are decoupled; worker-based processing where it fits.
Operational state held in clustered infrastructure; node failures absorbed.
If no new state is available, the service holds the last finalized one — never partial.
For institutional deployment, supported by failover behaviour, recovery objectives, monitoring model, alerting procedures and SLA assumptions.
CloudRisk Diversity provides quantitative outputs — margin, available margin, collateral-aware risk, stress analytics and single-order limits. Prudential, legal and default decisions remain with the customer.
The full institutional proposition is supported by an evidence pack — methodology transparency, performance evidence, operating resilience and a clear integration path.
Tell us about your venue and we'll arrange a technical walkthrough.