Bots

Automated strategies with published mandates and hard limits.

You allocate capital to a strategy, not to a black box. Each bot states what it trades, how much it can hold, when it stops, and who can turn it off.

Strategy families

Representative sandbox mandates. Live strategies are onboarded through the operator console with full documentation.

Strategy	Engine	Horizon	Risk band	Mandate
Liquidity / market making	Hummingbot fleet	Intraday	Low–moderate	Quotes two-sided spreads on deep pairs with inventory skew and hard exposure caps.
Cross-venue basis	Python engine	Days	Low	Captures spot–perp funding spreads with delta-neutral construction.
Trend / momentum	Python engine	Weeks	Moderate–high	Systematic breakout sizing with volatility targeting and trailing stops.
Mean reversion	Hummingbot fleet	Hours	Moderate	Fades short-term dislocations within a bounded inventory band.

Every strategy publishes an AUM ceiling. Allocations stop when capacity is reached rather than degrading fills.

Operators can halt a single bot, a strategy family, or all execution instantly. Open orders are cancelled first.

Breaching a strategy's stated maximum drawdown de-risks it automatically and notifies allocated clients.

Bots report liveness. A missed heartbeat pauses new orders and raises an operator alert.

Hummingbot, an internal Python engine or an institutional exchange account all speak the same execution interface.

Mandate, instruments, sizing logic, expected turnover and stress behaviour are documented before a bot accepts capital.