Terminal handbook
MM Flow Terminal
Live execution on Hyperliquid; additional venues available in staged mode, with full Lighter, Aster, and Derive support rolling out after testing. Built around signed orders, local credentials, and explicit user approval.
Self-custody
MM Flow servers never store exchange API secrets, private keys, seed phrases, or Lighter signer keys.
User-initiated
Alerts, copilot drafts, hotkeys, and analysis can prepare context, but live submits must be explicit user actions.
Signed forwarding
Where a venue needs a proxy, the route accepts only already-signed payloads on strict endpoint allowlists.
Venues
Four-venue execution architecture
| Venue | Execution | Credentials | Disclosure |
|---|---|---|---|
| Hyperliquid | live | wallet-signature | Orders are signed by the connected wallet and forwarded to Hyperliquid. MM Flow never receives a private key. |
| Lighter | beta | local-companion | Private Lighter signing is delegated to a loopback companion. The terminal stores only the companion URL/session token. |
| Aster | beta | encrypted-api-wallet | Aster API-wallet material is encrypted in the browser or kept session-only. Servers forward only signed allowlisted requests. |
| Derive | beta | session-key | Derive private orders use browser-side session-key signing. Referral code and extra fee fields stay off unless the user configures and approves them. |
Why free
MM Flow has no monthly terminal fee. Builder, integrator, or referral attribution can be used only where a venue supports it and only after the user approves it.
Not a venue
MM Flow is not a broker, dealer, exchange, custodian, advisor, prime broker, matching engine, or liquidity provider. It does not control user funds, orders, positions, or withdrawals.