Δt 14.20ms
derivance→∂/∂t→∫ dt→chronix
c
erivance
hronix

derivance · data intelligence

Trading infrastructure for crypto desks

Market data, backtesting, execution and risk controls in one low‑latency engine.

chronix
DocsRequest access
// who it's for

Built for your desk.

Pick your desk. Each path shows how Chronix is deployed, what changed, and the numbers behind it.

Share infrastructure. Separate client controls.

Manage multiple clients, accounts and venues through one operational system, with risk, limits and account state kept separate for each client.

Client problem
Smaller clients couldn't individually generate enough volume to keep favorable exchange conditions — lower rate limits, higher trading fees.
What Chronix did
Aggregate 100+ client trading flows through shared infrastructure while each client's risk, positions and attribution stay separate.
// Prime brokers — full page
Every client’s account under control.
what it solves · features · 3 cases · setup · FAQ
Open the prime brokers page →
Example deployment
CLIENTSACCOUNT · RISK LIMITSVENUESCLIENT AAccount Arisk limits ACLIENT BAccount Brisk limits BCLIENT CAccount Crisk limits CCLIENT DAccount Drisk limits DCHRONIXOMS · risk per clientBINANCEBYBITOKXaggregate risk · monitoring
$300K+

saved in trading fees per month

4.2×

higher order rate limit

100+

clients on best market conditions

Everything above, in full: the prime brokers page →

// under the hood

Every use case above runs on the same Chronix engine. Here's how it's built, module by module.

// the system

Five roles. One engine.

Every desk role plugs into the same core through its own surface. Pick one and follow its path from people to venues.

SURFACES
CORE
CONNECTIVITY
VENUES
// risk

Risk on the same path. Before the exchange.

Every order clears your limits before it leaves for the venue. Breach one and it never arrives. An alert fires before you even reach a soft limit.

RISKEXCH⚠ soft limit✓✕

Pre-trade gate

Every order clears your limits before it leaves for the venue. Breach one and it never arrives, and an alert fires before you even reach a soft limit.

// backtest

Backtest is live. The same code.

One code path in research and in production. Historical market data, real fills, your live engine. What you test is what you trade.

// latency

Double-digit µs in the engine.

We won't pretend a round trip to the exchange is microseconds; that leg is physics. The part we own, we make fast: strategy to the wire in 15–20 µs, and we colocate so the hop to the venue stays sub-millisecond. A generic stack loses an order of magnitude at both.

chronix~15–20 µs~300–500 µsENGINELow-LatencyConnectivityEXCHANGEgeneric stack~300–500 µs~2–3 msSTACKStandardConnectivityEXCHANGE
Engine

Your strategy to low-latency connectivity in ~15–20 µs.

Connectivity

Colocated link to the venue: sub-millisecond, not milliseconds.

Honest

The exchange round trip is physics. We don't call it microseconds.

// the surfaces

One engine. Three ways in.

The same low-latency core runs behind a strategy SDK, your own stack, or the terminal. The terminal is one surface on the engine, not the engine itself.

01

Strategy SDK

your algos

Code against the engine

Write your strategy in Rust, C/C++ or Python. The same compiled binary runs in backtest and live, so research never drifts from production.

chronix · strategy sdk
use chronix::prelude::*;
#[strategy] // your alpha, one struct
impl Momentum {
fn on_tick(&mut self, book: &Book) {
let edge = self.signal(book);
if edge > self.threshold {
self.buy(book.best_ask, self.size) // routed through risk
.post_only()
.submit();
}
}
}
let engine = Chronix::connect(); // Rust · C/C++ · Python
engine.strategy(Momentum::default())
.backtest(jan..jun) // same compiled binary
.go_live(); // unchanged, in prod
▋
02

Headless

your stack

The engine, no UI

Run the core behind your own front end and infrastructure. Market data, orders and risk are all driven over a typed API. Everything the terminal does, headless.

chronix · headless api
POST /sessions // auth, a typed client
GET /md/stream?symbols=BTC,ETH // normalized book, 12 venues
← bbo · depth · trades, one schema
POST /orders // execution + risk, one path
{ side, qty, type: "post_only" }
← 202 staged, risk ok, live
GET /positions // cross-venue state, real-time
WS /fills // streaming fills + acks
▋
03

Terminal & UI

desk · agent · admin

The full trading desk

Dual-venue DOM ladders, multi-symbol charts, blotter, positions and balances on one screen. The terminal is the engine with a face, not a separate app talking to it.

chronix · terminal · live
Chronix trading terminal: dual DOM ladders, multi-symbol chart, orders blotter, positions and balances.

Or just tell the agent

Ask in plain language and the agent reads the live terminal state through typed tools, then builds widgets, formulas or layouts against it. Staged, approved, audited. AI that never trades unwatched.

chronix · terminal · agent
Chronix agent: reads orders, positions and balances through tools, answers and builds in the terminal.

And the admin panel

Start, stop or archive a strategy; pause, resume, hedge or unwind from one bar. Limits, spreads, formulas: every parameter is live-editable and submitted under audit.

chronix · admin · control live · audited
parameters
Strategy params: max loss, offset, spread formula, vol half-lives, post-only, all live editable.
controls
Strategy controls: start, stop, archive, pause, resume, hedge and closing actions.

Send this request to let Derivance L.L.C-FZ use your email and message to respond and discuss access to Chronix. This does not subscribe you to marketing. Please don't include passwords, API keys or trading account details. Read our Privacy Policy.

A quick security check appears when you start filling out the form.

or just message us

Prefer email? [email protected]Protected by hCaptcha when you use this form: Privacy and Terms.