Skip to content

Platform

Coherent planes for ingest, modeling, simulation, risk, and execution.

Chronix is engineered as a spine, not an integration science fair. Rust-native components share contracts, logs, and deployment rituals so your team spends time on alpha — not plumbing.

End-to-end flow

A single narrative from capture to fills.

Every stage emits structured telemetry so humans and agents reason about the same ground truth. The diagram is native Mermaid — expand it when you’re projecting in a war room.

Pipeline — capture to fills

Scroll to pan · Close or ESC to exit

Metal & VMs

Performance profiles for colo reality — and cloud pragmatism.

The same codebase bends toward pinned cores on heavy iron or compact footprints on lean VMs without rewriting your strategies.

  • Determinism: tuning recipes isolate jitter sources before you chase phantom slippage.
  • Throughput: capture pipelines prioritize freshness and honest sequencing over vanity dashboards.
  • Portability: when workloads move, Chronix contracts travel with them — no bespoke rewiring.
FIG — Host readiness — profiling and guardrails for production hosts

Adapters

Market data and trading connectivity without duplicate dialects.

Byte-native parsers and execution adapters share semantics so research, risk, and desk tooling disagree less often — and recover faster when venues misbehave.

Coverage focuses on venues institutional desks already trade: centralized liquidity and their wire realities — expressed through Chronix’s unified contracts instead of a zoo of vendor SDKs.

Adding a venue inherits observability, replay hooks, and risk checkpoints — not another siloed science project.

FIG — Adapter plane — multiplexed venues, single internal language

StraDeK

Strategy code that stays honest beside production.

StraDeK modules declare feeds, risk hooks, and deployment class in one place so promotion from sim to prod is a contract diff — not a tribal memory exercise.

StraDeK module sketch
StraDeK.module("basis_arb_core", {
  feeds: ["binance:futures", "bybit:spot"],
  risk: ["global.delta", "venue.latency_watch"],
  deploy: { class: "low_latency", regions: ["tyo", "ldn"] },
  hooks: {
    on_breach: "chronix.alert.page_ops",
  },
});

Engagement

Want the architecture review pack?

We’ll walk your team through data planes, failover modes, and how MCP tooling slots into your existing SDLC.