Quant Trading Fleet
Built a live-server paper-trading system connecting strategy bots, broker abstractions, persistent execution data, controls, logging, and a monitoring dashboard.
Period · 2025-Present
Role · Individual project
01 · Business / research question
The question
What operating infrastructure is required to move trading rules from standalone scripts into a controllable and observable service?
02 · Evidence
What the analysis used
03 · Analysis
How the work progressed
- 01
Separate strategy and broker logic
Created broker abstractions for exchange-specific data and order behavior.
- 02
Make state observable
Modeled bot states, settings, execution history, and operational logs in SQLite.
- 03
Add operator control
Implemented FastAPI services, asynchronous bot controls, and a React/TypeScript dashboard.
- 04
Validate operations
Containerized the service and began live-server paper-trading validation.
04 · Interpretation
Main insight
Automated trading is also an operations-design problem.
A usable service needs state visibility, logging, parameter governance, test modes, recovery behavior, and human supervision.
The project demonstrates how financial-service data is generated, stored, monitored, and governed.
05 · Practical decision
Decision value
The system makes strategy operations inspectable and supports structured validation before any consideration of real-money use.
06 · Validation
Limitations and next checks
- •A formal paper-trading validation report is still needed.
- •Uptime, failed-order, reconciliation, duplicate-order, restart, and logging criteria should be defined.
- •Every strategy and broker mode requires end-to-end validation before the system is described as stable.
07 · Visual evidence
Evidence, with boundaries
Operating-system architecture
Verified sourceThe diagram shows the connection among strategies, broker abstraction, execution data, controls, and monitoring. It supports the implemented architecture; it does not evidence real-money operation, returns, win rate, or profitability.
Source · Current FastAPI/React architecture and portfolio codebase
Paper-trading operational checklist
Verified source- Live-server paper tradingIn validation
- Bot state and setting controlsImplemented
- Execution history and logsImplemented
- Failed-order and reconciliation criteriaPending
- Duplicate-order and restart criteriaPending
- Formal validation reportPending
- Paper-trading validation only · no real-money operation or return claim.
The checklist separates implemented operating controls from validation criteria still to be defined. It does not report or imply any real-money performance.
Source · Implemented controls plus documented validation gaps
Dashboard and execution-history screenshots
Pending verificationPublic-safe redacted screenshots pending
Anonymize bot and account fields, redact performance values, and keep the paper-trading disclaimer inside the image.
The current interface includes paper-equity and paper-PnL fields that could be misread without context. Screenshots remain pending until a redacted, explicitly paper-trading-only export is prepared.