01
Risk before execution
Every order is evaluated by a server-side risk engine. Daily loss, drawdown, exposure, correlation, and lot limits can reject a trade before MT5 ever sees it.
Institutional trading infrastructure
Trade only what the risk engine allows.
QuantVeo is a risk-first algorithmic and copy-trading platform. Strategies propose. Python decides. MT5 executes. Frontends, EAs, and followers cannot bypass control.
- 0
- client-side risk decisions
- 1
- central approval path
- 3
- kill-switch layers
- ∞
- audit trail on every order
QuantVeo Prime · live
WebSocket · 38ms
Equity
$251,108.19
Daily P/L
$1,840.22
Drawdown
-3.40%
| Symbol | Side | P/L |
|---|---|---|
| EURUSD | BUY | $417.60 |
| XAUUSD | BUY | $264.00 |
| GBPUSD | SELL | $232.00 |
TRADE_REJECTED
NAS100 SELL 0.30 rejected — correlated US30 exposure would exceed limit.
Control plane
FastAPI
Strategy, risk, copy, API
PostgreSQL
Books and audit of record
Redis
Live state and queues
MT5 / MQL5
Execution bridge only
The principle
Built as infrastructure, not a chart with buttons.
02
Python is the authority
Strategies generate signals. The trading engine sizes, prices, and approves. The MQL5 EA only executes instructions it did not invent.
03
Copy without blindness
Followers inherit master fills, then pass their own risk engine. A trade that is safe for the master can still be rejected for a follower.
Hard limits
If a rule is violated, the trade is rejected. There is no override in the client.
Per-trade risk
Configurable % of equity. Position size is calculated after the signal, never before the check.
Daily loss & drawdown
Account-level and strategy-level ceilings. Breach stops new approvals, not history.
Exposure & correlation
Lot, leverage, open position, and correlated-book limits evaluated together.
Kill switches
Global, account, and strategy. Authorized resume only. Event is written to the audit log.
Idempotent execution
The same instruction cannot fill twice across EA restart, timeout, or retry.
Follower isolation
Each copy order is a new risk decision. Master approval is never inherited.
Architecture
One decision path.
01
Signal
02
Size / SL / TP
03
Risk engine
04
Approve
05
MT5 EA
06
Fill
- Strategy brain
- Python / FastAPI
- Risk engine
- Server-side, non-bypassable
- Execution
- MQL5 EA → MT5
- State
- PostgreSQL + Redis
- Console
- Next.js
- Mobile
- React Native
Copy trading
Master fills are proposals. Follower risk is independent.
Fixed lot, equity-percent, or risk-multiplier allocation. Symbol maps, SL/TP sync, partial closes, and emergency stop. A paused follower keeps existing risk management on open positions.
How copy trading worksSample reject
TRADE_REQUESTED
RISK_CHECK_STARTED
RISK_CHECK_FAILED · correlated exposure
TRADE_REJECTED
NAS100 not sent to MT5
Coming soon
Marketplace first. Then mobile, docs, and the journal.
Soon
Strategy marketplace
Subscribe to versioned strategies. Follower risk still applies.
Soon
Mobile monitor
Balances, positions, and risk alerts on iOS and Android.
Soon
Public API & docs
REST and WebSocket for operators who integrate the control plane.
Soon
Journal
Architecture notes. No signals. No trade calls.
See the operator console.
Inspect equity, rejected orders, strategy versions, copy relationships, and the risk audit stream.