A valid signal can still become an unsafe order when liquidity thins, exposure changes or a venue starts behaving abnormally.
Risk & Execution
OKAI Solutions
Aegis AI
byOKAI SolutionsA defensive layer between signal and action.
Checks proposed orders against exposure, liquidity, venue health and hard limits. If a feed is stale or a rule breaks, execution stops and the reason is logged.
Policy enforcement · blocks on stale stateRequest a technical walkthrough →Proposed orderBTC–PERP / BUY£240,000 notional · venue 02
- ✓Position limitwithin policy
- ✓Venue healthnormal
- !Order-book depthresize required
Gate decisionHOLD · REVIEW SIZE
- Used by
- Algorithmic trading teams, crypto funds, market makers and risk operators
- Inputs
- Orders, positions, limits, order-book liquidity, volatility, venue health and live portfolio exposure
- Produces
- Pre-trade checks, position sizing constraints, circuit-breaker decisions, escalation events and an immutable audit trail
What happens when Aegis AI is in the loop.
Aegis checks the proposed order against live positions, liquidity, venue health and hard policy before it leaves the system.
The order is approved, resized or stopped. Every check, override and operator decision remains in the execution record.
Inside Aegis AI
Six visible stages connect the source to the operator. Nothing important disappears inside a single model call.
- 01Portfolio and venue state
- 02Risk-factor calculation
- 03Liquidity and slippage model
- 04Policy engine
- 05Circuit breaker and approval
- 06Execution gateway and audit
Acceptance targets
These are validation criteria for a scoped pilot. They are not presented as observed customer results.
- 01
Every order is checked against current exposure and configured limits
- 02
A stale market or portfolio feed blocks automated execution
- 03
Circuit-breaker events record the trigger, decision and responsible operator
- 04
Retry and failover tests produce no duplicate orders
Start with the workflow
Contact OKAI →