Architecture
Fourteen services. Zero servers.
The platform's fourteen microservices run as independent Cloudflare Workers communicating via internal service bindings — no exposed inter-service HTTP, no network round trips, no service discovery overhead. Each automated trading unit is a Durable Object: a single-tenant compute instance with its own embedded SQLite database, isolated state, and deterministic resumption after any interruption. As a result, hundreds of concurrent strategy instances can run in parallel at negligible marginal cost.
Minute-resolution price and volume data for several tracked crypto assets spans multiple years in Cloudflare R2, enabling backtesting at the granularity that matters for short-to-medium timeframe strategies. The twelve signal sources are cached in KV with a 10-minute TTL, keeping inference costs predictable while maintaining meaningful freshness. Signal sources include price feeds, on-chain activity metrics, derivatives market data (funding rates, open interest), macro indicators, and aggregated newsstand and social sentiment across the assets under research.
Strategy parameter optimization uses a two-phase approach. Latin Hypercube Sampling covers the first 20% of iterations, spreading initial experiments evenly across the search space rather than clustering near defaults. The remaining 80% are guided by a language model that reads the full backtest history and proposes the next configuration, weighted against Sharpe ratio, Sortino ratio, maximum drawdown, and win rate. AI-guided search consistently outperforms both grid and random baselines, particularly in higher-dimensional parameter spaces.