Autonomous trading runtime. Controlled, state-first, observable.
Capital preservation first. Execution discipline. Read-model snapshots; no real-time signals or order feed.
Ingest connects to ticker, trade, L2 and L3 feeds and builds a run_symbol_state table per symbol. The route engine reads only from that state, then the execution engine places and tracks orders within safety guardrails. Observability snapshots read aggregated metrics from the same database and power Tier 1 and Tier 2 dashboards.
Deep dives: Kraken spot engine & observability
Articles for engineers and serious traders: L3 order book, WebSocket execution, regime detection, hybrid maker fees, safe API wiring, and low-latency infrastructure.
Kraken L3 · WebSocket · Hybrid maker · Regime
Metric cards
You see live market data (ticker/trade rows) but 0 execution orders/fills in 24h. That matches ingest-only or no live execution in this window — not a data error.
The 24h window is UTC in the database. Fills use exchange time (`ts_exchange`) when present, otherwise insert time. Orders count if created or last updated in that window (including fill updates). These are rows in your bot DB — not the same as every line in Kraken’s UI or “Trade rows” (L1 market feed).
Demo trades (Tier 1)
- SCOR/USD buy — filled(filled)
- BAL/USD buy — filled(filled)
- SCOR/USD buy — filled(filled)
Snapshot: 2026-04-03T13:36:19Z
What it is
- Capital preservation bias — risk guards, safety modes, exposure caps.
- Execution discipline — state-first, epochs, no loose state.
- Multi-asset microstructure awareness — filtering, suitability, L3-quality.
- Adaptive throttling — inactivity under uncertainty; strategy components disableable.
How it works (abstracted)
Market Data → Filtering layer → Opportunity scoring → Execution engine → Risk envelope → Feedback loop. Guardrails: exposure caps, kill conditions, monitoring, logging, failure isolation.
No parameters, thresholds or venue details published.
System philosophy
- The system prefers inactivity over uncertainty.
- Losses must remain explainable.
- Capital deployment requires measurable conditions.
- Strategy components can be disabled without total failure.
Production notes
No recent production notes. Strategy pauses, parameter reviews and monitoring events are maintained internally.
For a private inquiry or research dialogue: Access.