Case studies - Real-time decision support for quant trading
A custom platform that pipes broker-API tick data into real-time monitoring of 80 instruments — ORB, VWAP, order-flow imbalance and institutional flow, distilled by a scoring engine into clear visual cues for disciplined intraday trading.
- Client
- Financial trading clientActive
- Year
- Services
- Custom development · Low-latency frontend + Python
Seeing certainty in a flood of data
In modern trading the constraint is rarely too little information — it's fragmentation. When an opportunity appears, what actually decides the outcome usually hides in the intersection of several conditions at once: a clean break above the opening range (ORB), order-flow imbalance tipping the same way, and large institutional orders stepping in to confirm.
This client wanted a system that broke past the single-instrument view — one that could scan their 80 self-selected instruments and surface where those conditions converge. The goal was to make decisions data-supported rather than intuition-driven.
Dashboard Wireframe
trader.copilot · Whole-market visibility at a glance
Main view · Tab switches change the view in real time
Expand Panel
Price chart (price + VWAP + signal markers) · Full Signal Matrix conditions · Smart-money / retail flow
⋮ 50 pre-market static + 30 intraday dynamic backfill
List Pane
Detail Pane
Institutional flow
Volume
Technical indicators
List Pane
Detail Pane
Institutional flow
Volume
Technical indicators
Three tab views
Watchlist
MONITOR
Live Card List · 4-stage Pipeline progress · Signal tags · Heat-sorted
Ranking
RANKING
Pre-market / intraday rankings · List ↔ detail · Dual-pane
Explorer
EXPLORER
Daily candles · Institutional net flow · PostgreSQL historical source
Alert Overlay
Encoding the trader's logic, lowering cognitive load
We built a decision hub that processes high-volume tick data and runs multi-dimensional logic in real time. It has to react within milliseconds — computing each indicator, weighting them into a Heat Score, then translating the result into a clear visual cue. The point isn't speed for its own sake; it's freeing the trader from low-level data wrangling so their attention goes to strategy.
Engineering for consistency and reliability
To make this the trader's reliable backbone, we made several core architectural choices.
1. Deep market context integrated in real time
The system doesn't just display indicators — it structures the underlying logic. We implemented a full matrix from Opening Range Breakout (ORB) trend detection to VWAP confirmation to RSI strength filtering. A custom scoring engine weights each indicator's strength so that every signal on screen represents a convergence of multiple favorable conditions.
2. Clean signal filtering
To help the trader hold rhythm intraday, we built cooldown mechanisms and signal TTLs into the system. These automatically filter out noise during consolidation, ensuring alerts fire only at genuine turning points — protecting the trader's psychological consistency from market chop.
3. Millisecond alerts and discipline automation
Stop-loss execution is where psychology breaks down most easily. We moved this burden to the backend: when ticks hit preset conditions, the system completes the calculation and pushes a high-priority alert within milliseconds. For extreme market conditions like flash crashes, the system also tightens thresholds dynamically — defending the trader's risk floor precisely when it matters most.
4. Industrial-grade state recovery and continuity
Trading systems live or die on stability. We designed 30-second state snapshots (State Persistence) with automatic Gap Fill on reconnect. Even during mid-session network disruptions or restarts, the system replays missing ticks and restores all historical state and scoring — keeping decision context continuous across the full 4.5-hour trading session.
Architecture
From exchange to user screen · five-layer separation
Layered Architecture
Top to bottom: what the user sees → how the system processes it → where the data originates
FRONTEND
/ What the user seesLive-updating board, signal tags, charts, stop-loss overlays — everything the user directly interacts with
Vanilla JS ES Module · Tailwind · Lightweight Charts · Lucide Icons · WebSocket Client
WEB SERVER
/ Real-time pushPushes computed signals, quotes, and stop-loss state to the frontend at millisecond latency; also serves query APIs
Python · FastAPI · WebSocket · Uvicorn · asyncio
BUSINESS LOGIC
/ The system's brainPre-market screening, intraday monitoring, signal evaluation, stop-loss calculation, end-of-day scoring — all autonomous decision logic
intraday_monitor · data_manager · dynamic_scanner · position_manager · eod_scorer · premarket_scanner
DATA STORAGE
/ Persistent memoryStores every trade, signal, position, and historical bar — system can resume mid-session after restart
PostgreSQL × 2 · asyncpg connection pool · trading_system DB (intraday state) · trade-ops DB (historical bars + institutional data)
DATA SOURCES
/ Source of quotes and historyLive quotes via broker API for first-hand exchange fills; historical data from an independent data pipeline
SinoPac Shioaji API · TWSE · TAIFEX · Institutional flow historical pipeline
Built with an AI-native workflow
A system at this scope — real-time tick processing, an 80-instrument scoring matrix, millisecond risk control, snapshot-based state recovery — conventionally runs six months to a year from design to launch, often longer. We delivered it in under three months, with a small team. The engineering itself was AI-native: we worked with Claude across architecture, implementation, and the refactors that kept the codebase clean as the signal logic grew.
One distinction we hold carefully. AI accelerated how the system was built — not what it decides. The trading signals run on deterministic, auditable rules; no language model sits in the decision path making market calls. In a financial tool that boundary is deliberate, and keeping it explicit is part of the engineering discipline.
That working method isn't unique to this project. Using AI to move faster on the engineering, while judgment and architecture stay firmly human, is what lets us take on data-intensive systems of this complexity and deliver them on timelines that weren't realistic a few years ago.
A broader, calmer field of view
After delivery, the client turned fragmented intraday monitoring into a steady, disciplined rhythm. With the system handling tick processing and signal filtering across all 80 instruments, they can reserve their most valuable mental capacity for what actually matters: timing an entry and managing overall risk.
Before / After
Intraday rhythm · From window-switching to map-reading
Before
Open broker app
Only one instrument at a time — the rest of the market is invisible
Only percent change visible
Switching windows, checking indicators, watching the clock — all manual
Half a morning consumed by these repeated motions
After
Open trader.copilot
Whole screen shows live state across all 80 instruments
Signals, volume, institutional flow, stop-loss distance — all visible
System handles switching, calculation, timing
Time freed for judgment: entry · scaling in · holding overnight
For helloio, this project left us with more than the code. It sharpened how we think about using tools to filter out market noise and return trading to clear decisions — and the experience of handling dense real-time data streams and shaping them into a calm interface now sits behind how we help clients in any field solve data-intensive problems.
Engagement scope
- Real-time data pipeline and API integration
- 80-instrument parallel monitoring architecture
- Quantitative indicator matrix and scoring engine
- Millisecond risk control and defensive mechanisms
- Smart-money flow and OBI tracking
- End-of-day position scoring system
- State snapshots and automatic recovery
- Cross-environment state sync and fault tolerance
- Parallel monitoring
- 80 instruments
- State snapshot interval
- 30 seconds
- Decision and risk response
- Millisecond
- Intraday high availability
- Zero interruption