deploy · the operator owns the host
three deploy targets · railway · docker · local
the engine is open-source and self-hosted. you pick the host. railway is the easiest path · docker runs anywhere · local is the dev mode. all three auto-pair with the cockpit via the same signed-heartbeat handshake. zero never custodies your engine, your wallet, or your trades.
three first-class targets
| target | time | state | what it gives you |
|---|---|---|---|
railway · one-click | ~90s | primary | one-click template launches the engine on railway · privy-managed wallet auto-provisioned · cockpit auto-pairs via signed heartbeat · operator owns the project. |
docker · anywhere | ~3m | first-class | pull the image · `docker run` on any vps · cockpit auto-pairs the moment the heartbeat reaches the receiver · same signed handshake as railway. |
local · laptop | ~5m | dev mode | clone the engine repo · `pnpm dev` against a local engine · the cockpit speaks to localhost over the same signed protocol · ideal for strategy work and replay. |
what holds across all three
| property | what it means |
|---|---|
custody | operator-self-hosted hyperliquid via privy-managed api wallet · zero-universe never holds keys. |
pairing | engine emits a signed heartbeat to /app/api/deployments/claim · cockpit binds the engine to the operator account on first valid signature. |
lease | live trading requires the operator to grant a small, time-boxed lease · revocable from the cockpit at any time. |
mode | auto / semi / manual · controlled from the chrome · maps to engine modes.{comfort,sport,track} + paused-with-manual. |
self-custodial · always
the dual-track license (engine apache-2.0 public · cockpit proprietary) lets you fork the engine, audit every line, and run the host you own. zero ships the cockpit. you ship the engine. the wallet is yours. the trades are yours. the lease is revocable. article i.1.