EventWe're exhibiting at Forex Expo Dubai πŸ‡¦πŸ‡ͺMeet us at Forex Expo Dubai πŸ‡¦πŸ‡ͺAt Forex Expo Dubai πŸ‡¦πŸ‡ͺ22–23 Sep 202622–23 SepSee the schedule
By role

Stop firefighting. Start forecasting.

Configure the rules once and the engine enforces them on every tick, across every account. Your team spends the day on genuine edge cases and organised abuse instead of chasing alerts through a spreadsheet.

Risk queueLive
AutoNews-window tradeacct 71220 Β· frozen by rule
QueueDD proximity 92%acct 88015 Β· watching
QueueCopy-trade cluster6 accounts Β· investigating
Mean time to action38s
The risk lead's problem

Manual oversight doesn't scale past a few thousand accounts.

Alerts arrive too late

By the time a polled system notices a drawdown breach, the account has already moved well past the limit.

Coordinated abuse hides

Ten accounts individually within the rules can be one hedged strategy harvesting your payout policy.

No decision record

An override happens, nobody records why, and six months later there's no way to defend or learn from it.

What changes

The desk you'd design if you had the time.

Capability06 included

Tick-level enforcement

Drawdown, exposure and conduct rules evaluated per tick with server-side action in under 80ms.

Pattern detection

Copy clusters, latency abuse and cross-account hedging surfaced with evidence attached.

Rules without engineers

Eight rule categories configured in a builder, versioned, with in-flight accounts unaffected.

Queue and SLA management

Shift-based routing, reassignment and SLA tracking so nothing sits unowned.

Full decision trail

Every override, freeze and clearance recorded with actor, evidence and justification.

Risk posture reporting

Breach rates, override frequency and exposure trends, per program and per analyst.

Server-side enforcement41 ms median latencyEvery change audit-loggedIncluded on every plan
Risk desk

What's included

Standard on every firm running on the platform. No add-on tier, no per-seat unlock.

06capabilities
included by default
  • 01Real-time enforcement across 8+ rule categories
  • 02AI layer for patterns rules don't describe
  • 03Shift-based queue routing and SLAs
  • 04Every override logged with justification
  • 05Evidence attached to every flag
  • 06Shift handover notes carried in the queue
Questions

Questions operators ask

Yes. The engine is a configuration surface, not an opinion β€” the eight rule categories cover what prop firms actually enforce, and anything unusual can be expressed through custom rules or the API.
It runs beside them. Rules are deterministic and enforce what you already know; the model layer is probabilistic and surfaces coordinated or novel behaviour. It recommends and evidences β€” your team still decides.
Enforcement state is held server-side on the trading platform, so an account frozen stays frozen. Feed interruptions backfill on reconnect, and sustained loss raises an operational alert rather than failing quietly.
Let's talk

Bring us a scenario that broke you.

Describe a case your current setup missed and we'll show the engine catching it.