PLATFORM · RISK MANAGEMENT
Real-time exposure. Automated response.
Live exposure by symbol, client, desk, and broker. Hierarchical limit cascade. Automated risk rules. Stopout with session-level audit. Negative balance protection enforced at the engine.
Risk management in brokerage software is usually a monitor bolted onto a trading engine that doesn't know the monitor exists. When the market moves, the risk team reads a stale dashboard and calls someone. Slate's risk layer is not bolted on — it's inside the trading engine, inside the ledger, inside the workflow engine. It sees every trade as the trade happens, enforces limits before fills, and acts on exposure without waiting for a human to notice.
Live exposure
A dashboard that shows the state of your book right now, not thirty seconds ago.
Slate's exposure dashboard is driven by the same event stream the trading engine writes to when it posts a trade. A new position shows up on the dashboard within a second of the fill. Exposure is pivotable by symbol, by client, by client group, by sales desk, by broker entity, and back up to a holding level. Aggregations update live; there is no refresh button because there's no stale cache to refresh.
Hierarchical limits
Per-trader, per-group, per-desk, per-broker — all enforced at the engine.
Risk limits in Slate are a cascade. A trader has an individual limit. The trader's group has a group limit. The group's desk has a desk limit. The desk's broker has a broker-level limit. A new order must pass every limit it's subject to before the trading engine will accept it. When a trader approaches their individual cap, the engine throttles new order flow and alerts the agent. When a group limit is breached, the system enforces immediately and the risk desk sees the breach before the client does.
Automated risk rules
Condition, threshold, action, audit — and no phone call required.
The risk engine fires on conditions the risk team sets: net exposure on a symbol crosses a threshold, notional on a desk exceeds a limit, a high-value client takes a directional position above a cap. The action can be a margin reduction for the client cohort, a trading restriction, a trigger to the compliance desk, or an alert to the sales floor. Every action is atomic, audited, and reversible. The risk team supervises; the system acts.
Stopout and negative balance protection
Session-level audit on every liquidation. NBP enforced at the engine, not the CRM.
When a client's margin falls below the stopout threshold, the trading engine fires the stopout through the session layer — every liquidation, margin call, and NBP event is recorded in the TimescaleDB financial ledger with the exposure state at the moment of the fire. NBP is a hard rule at the engine: a client can never end a session owing money they don't have, because the engine never lets the session get there.
Real-time exposure dashboard · Hierarchical limit cascade · Auto-hedge rules · 5 asset classes · Session-level stopout audit · NBP at engine · TimescaleDB financial ledger
Use this to solve
See the exposure the way your risk desk wishes they could.
Book a demo and we'll show you an automated risk rule firing against a live trader's book.