Risk controls before, during and after execution.
DAROS RMS puts hard limits around automated and manual trading — pre-trade checks, live exposure control, a central kill switch and alerting — so systems trade only inside boundaries you define.
Most stacks discover risk after the order has already hit the broker’s margin ledger. DAROS RMS validates pre-trade, inside the order path — quantity, price bands, margin and remaining loss headroom — so a fat-finger or a runaway loop is stopped before it ever leaves your infrastructure.
What breaks without it
These are the failure patterns DAROS RMS is built to remove:
- Algorithms trading beyond safe limits
- Copy systems amplifying risk across accounts
- No central kill switch when something misbehaves
- No real-time view of exposure across strategies
- Weak live-trading discipline once capital is at stake
Built for
- Anyone deploying automation with real capital
- Prop desks managing traders and allocations
- Copy-trading operators protecting child accounts
- Fintechs adding a risk layer to client tools
Spec sheet & configuration
Where this module sits in the pipeline, what it handles, and what its configuration looks like. Figures marked as design targets are benchmarked per deployment.
| PRE-TRADE OVERHEAD | Single-digit-millisecond design target in-path — benchmarked per deployment, never bypassed |
| LIMIT SCOPES | Order · strategy · account · portfolio · desk |
| HARD CONTROLS | Kill switch · auto-pause on breach · manual override |
| CHECK TYPES | Qty / price band · margin · symbol permissions · loss headroom · order rate |
| AUDIT | Every check, breach, halt and override logged with timestamps |
Values are design targets and depend on deployment environment, broker APIs and data sources. Nothing here is a performance or return claim.
{
"scope": "strategy:daily-opt-01",
"daily_loss_limit": 25000,
"max_exposure": 400000,
"order_rate": { "max_per_min": 12 },
"symbols": { "allow": ["NIFTY*", "BANKNIFTY*"] },
"on_breach": ["pause_strategy",
"cancel_working", "alert:ops"],
"kill_switch": "armed"
}What DAROS RMS does
Daily loss limits
Hard stops at the day level, per account and per desk.
Strategy-level limits
Cap loss, order count and exposure for each strategy independently.
Account-level limits
Protect each account — including copy children — with its own boundaries.
Portfolio exposure control
Aggregate exposure views and caps across instruments and strategies.
Symbol / instrument restrictions
Whitelist or block instruments, expiries and segments.
Kill switch
One control to halt routing, cancel working orders and freeze strategies.
Manual override
Human-in-the-loop controls for pausing, resuming and intervening.
Pre-trade checks
Quantity, price band, margin and limit checks before any order routes.
Post-trade monitoring
Fills feed live exposure and loss tracking after execution.
Alerts & escalation rules
Threshold breaches notify the right people, in order.
How it runs in practice
Pre-trade gate
Strategy emits an order → RMS validates quantity, symbol permissions, margin and remaining daily-loss headroom → the order routes only if every check passes.
Live-day discipline
A strategy hits 80% of its daily loss limit → RMS raises an alert → at 100% it pauses the strategy, cancels working orders and notifies the operator.
Desk-wide halt
An operator triggers the kill switch → routing stops across all strategies and accounts → working orders are cancelled → the halt event is fully logged.
How it connects with other DAROS modules
No module runs alone. DAROS RMS plugs into the rest of the platform:
All modules:
Review your risk infrastructure with a system architect.
Walk us through your current limits — where they live, who can bypass them, and what happens on breach. We will show you where RMS hardens the path.