Why Fintechee Doesn’t Run a Traditional Risk Engine
Continuously analyzing large volumes of accounts in real time is CPU-expensive. Fintechee’s Trading Core stays lightweight by design; risk analysis happens at the Dashboard + JavaScript layer instead, on demand.
Example Workflow
- An A Book account shows a large, unexpected loss
- An admin investigates through Dashboard analytics
- The admin opens a hedge account to offset exposure
- No change is made to the original account’s A/B classification
Trading Core → Dashboard API → JS analysis logic → manual or automated action
FAQ
Why doesn’t Fintechee have a traditional backend risk engine?
Continuously analyzing large numbers of accounts in real time is computationally expensive. Fintechee keeps the Trading Core lightweight and moves risk analysis to the Dashboard and JavaScript layer, where it runs on demand.
If a risky account is found, does the admin change its A/B Book status?
Not necessarily. A common response is opening a separate hedge account to offset exposure, without altering the original account’s book classification.