Execution and risk systems that behave the same in production as in backtest.

Most trading infrastructure fails in the gap between the backtest and the venue: fills that were assumed, state that was stale, a reconnection path nobody tested, a risk limit enforced in a spreadsheet. The strategy is the client's edge. The infrastructure is where the edge quietly leaks.

We build the infrastructure. Execution paths, backtesting that is actually reproducible, simulation against forked state, and risk engines that enforce limits in the system rather than in a policy document. Rust where correctness and latency justify it.

We do not design strategies, take discretion, or publish performance figures. You own the edge and the outcome. We make sure the machinery underneath does what you think it does.

Talk to Anupam →Fixed fee, scoped in writing before anything starts. No hourly billing, no verbal scope.

Scope

What an infrastructure engagement covers.

INVENTORY

Every path that can lose money

Where the current system lies to you: assumed fills, stale state, unhandled reconnects, limits enforced outside the code path. The list is the scope.

BOUNDED BUILD

Execution & simulation

Execution paths built against real venue and protocol behaviour, with simulation against forked state so a change can be evaluated before it touches capital.

ALWAYS

Risk enforced in code

Position, exposure and drawdown limits enforced by the system, not by discipline. Breaches halt rather than warn.

HANDOFF

Reproducibility

Deterministic backtests, pinned data, and a test suite your team can run. A result you cannot reproduce is not a result.

Scope your infrastructure on a qualifying call.

Anupam Shah

Founder · replies same business day

Book a qualifying call →

Fixed fee, scoped in writing before anything starts. No hourly billing, no verbal scope.

Related: DeFi protocol engineering · AI agents for on-chain systems · How we work & pricing