Actual, target, and outstanding work.
See marked positions beside aggregate intent. In-flight and uncertain rows rise to the top, with order state and live fills reflected as jinghong publishes them.
C++23 / Wt / Internal operations
Every book.
One place to act.
Hyperion is the multi-account command surface for seeing the live book, supervising trading robots, and controlling risk. Track positions, targets, orders, marks, and request rate—then freeze or flatten without changing tools.
The command surface
Risk is useful when it is visible—and controllable.
HTTP seeds the account. Pub/sub keeps it live. Hyperion joins holdings, intents, in-flight orders, quotes, fills, cash, robot heartbeats, and liquidator locks into one operational view.
Trade from the same view that confirms the fill.
Set a signed share target for the Hyperion source, watch bid, ask, last, and estimated cash impact, then follow the STATUS stream from accepted intent through fill.
Know who is alive and what each bot wants.
Heartbeats and intents reveal source age, liveness, mute state, and per-symbol demand. Mute a source to zero its demand; unmute it when the strategy is ready to participate again.
Freeze trading. Flatten exposure. Preserve the distinction.
Block globally or by symbol without closing a position. Liquidate through Alpaca and apply a block in the same action. Clear blocks and robot mutes deliberately, not ambiguously.
The signal path
Subscribe. Reconcile. Act.
Hyperion does not pretend to be the broker or the market-data feed. It composes the sources already responsible for those truths and gives the operator a focused control plane.
goblin-slurp
Trades and quotes publish as T:SYM and Q:SYM.
goblin-core
Redis-compatible Pub/Sub over a Unix-domain socket.
Hyperion
Wt/C++ sessions join marks, book state, robots, locks, and controls.
jinghong × N
One process, ORDER/STATUS pair, HTTP base, and tab per account.
HTTP boots the view. STATUS keeps it live.
Hyperion seeds each book from jinghong, polls account cash and equity lightly, and relies on live STATUS events for the execution path.
Account routes stay explicit.
Each account env defines its label, ORDER and STATUS channels, and HTTP base, keeping every operator tab aligned with one order book.
Documentation
From source tree to a live desk.
Start with the product overview, understand the bus and order-server contracts, then install against the topology of the target host.
01
Start with Hyperion
What the terminal shows, how accounts are configured, and the quickest path to a local build.
Product overview
02
Wire the trading stack
goblin-core, goblin-slurp, order-server channel contracts, startup order, security, and failure modes.
System setup
03
Build and operate it
Dependencies, CMake, master config, account envs, Wt resources, systemd, verification, and troubleshooting.
Installation guide
~/hyperion · quick build
# C++23 · Wt 4 · curl · hiredis · json
$ cmake -S . -B build \
-DCMAKE_BUILD_TYPE=Release \
-DCMAKE_PREFIX_PATH=/opt/wt
$ cmake --build build -j
$ ./build/hyperion \
--config /etc/hyperion/hyperion.json \
--docroot ./static \
--resources-dir /opt/wt/share/Wt/resources \
--http-listen 127.0.0.1:8110Need the complete dependency and service setup? Read the installation guide →