Press releases hit the wire, then the tape. The raw feed is published ~3 ms after
dispatch and is never delayed by anything below. Every product feature is a separate
channel that references the release by release_id, so you pay only for
what you subscribe to.
The built-in v5 ModernBERT checkpoint scores each release on a separate scores channel with p_win, a direction (up / flat) and a magnitude bucket, running in parallel with the raw feed rather than in front of it.
Per-user API keys mint a Centrifugo connection JWT for alerts, releases, releases:<TICKER> and the derived channels, and the same key reads the release archive over /v1 (10 req/s, burst 30).
Upload an ONNX graph plus a JSON manifest (ONNX is data, not code, which is the whole reason for the restriction) and receive its outputs on your private user:scores#<id> channel; models whose p95 latency exceeds their budget_ms are disabled and told why.
Schwab executes server-side via OAuth (refresh tokens last 7 days, so you re-link weekly); IBKR is honest about needing a local connector that you run next to your own TWS/IB Gateway, receiving signals on user:signals#<id>.
A nightly fundamentals snapshot (market cap, float, short interest) is joined to each release by an O(1) in-memory lookup and rebroadcast on screen:<preset> about 1 ms after releases; no live API call is ever made per release.
The dashboard form for the rule brokersvc enforces (max_position_usd, max_daily_trades, manual_confirm, kill switch) exists, but end-to-end automated execution is not shipped and should be treated as paper-only.