Services
Engineering for teams that trade
Fixed-scope work around the same stack we sell and run: connectors, measurement, and the systems between a strategy and the exchange.
Exchange connectors
A venue adapter to the Connect contract or to your own interface: order entry, private streams, market data, rate budgets, reconnect logic, tests against the venue's testnet and against recorded traffic. Spot, perpetuals, and the odd venue with a FIX gateway.
Latency and placement audits
Where your time goes, measured from your servers: DNS, TCP and TLS, first request, warm requests, order acknowledgement, market-data arrival. Then the question that matters: which region, which provider, and whether co-location is worth it for your order rate.
Trading-system development
Execution and hedging components in Rust: quoting engines with maker-only semantics, multi-venue hedgers, position and risk ledgers, replay from recorded data. We build the parts that must be fast and boring, you keep the alpha.
How an engagement runs
- 1A call, forty minutes.What you trade, where, at what rate, what breaks today.
- 2A written scope with a fixed price.Deliverables, acceptance tests, dates. No hourly billing on open-ended work.
- 3Delivery in your repository.Code, tests and a short operating note. You own all of it.
- 4Handover and a warranty window.Thirty days of fixes for anything that fails its acceptance test.