Engineering· 8 min read
Why Cascade never holds customer money
- Written by
- The Cascade team
- Published
- Draft · 2026

Anyone can ask a question about the future. Answering it with a portfolio is the hard part. Before we built that engine, we wrote one rule it can never break.
Cascade never holds customer money. It is a platform invariant in every jurisdiction. Compute is ours; the system of record is a flag. The broker keeps the money, the licence and the customer.Cascade never holds customer money. It is a platform invariant in every jurisdiction. Compute is ours; the system of record is a flag. Order routing is a flag that defaults to the tenant’s own routes. The broker keeps the money, the licence and the customer.
Regulated parameters fail closed. No policy pack, no trading.
A jurisdiction policy pack sits outside tenant configuration and overrides it. Tenants differ by configuration, never by fork, and everything is auditable per tenant.A jurisdiction policy pack sits outside tenant configuration and overrides it. Law is the outer clamp. Tenants differ by configuration, never by fork, and everything is auditable per tenant.
Basket { constituents[...] }Basket { constituents[symbol, direction, weight] }Mark { basket_id, index_value }Mark { basket_id, index_value, ts }→ NetExposure, HedgeDelta→ NetExposure, HedgeDelta→ RiskSignal (advisory)→ Valuation, RiskSignal (advisory only)
Read next
- Tenants differ by configuration, never by fork
- Working toward ISO 27001, said plainly