Book a scoping call
Home / Work / Multi-Venue Execution & Routing Layer
Quantitative finance Colabs venturePaper-locked, live path gated

Multi-Venue Execution & Routing Layer

One broker over 105 exchanges, with the live switch deliberately hard to flip.

What we set out to build

Independence from any single execution vendor, and the ability to route the same strategy across venues without rewriting it. The founder wanted to own the execution layer rather than rent it.

What was built

  • A unified order interface across 105 exchanges through one adapter surface
  • Deterministic client order IDs, so a retry can never become a duplicate fill
  • Fail-closed risk gates: if a check cannot run, the order does not go
  • A triple-switch live gate — three independent conditions must be true before real money moves
  • Full paper mode as the default state, not an afterthought

What it achieves

  • 775 tests, with the risk gates and idempotency tested as first-class behaviour
  • The system has never placed an unintended live order, because the default is paper and the gate requires deliberate action in three separate places
  • On-chain execution was deliberately NOT built: the custody blockers were documented instead of engineered around
The hard part: Deciding what not to build. On-chain routing was technically achievable and commercially attractive, and it was left out because the custody model could not be made safe. That decision is written down in the repository rather than forgotten.

The stack

Python, ccxt, asyncio.

Common questions

How was this built?

This was built through Colabs, our sister company. A founder brought the idea and the domain knowledge, Colabs brought the team, the founder funded the build with a monthly subscription, and they hold equity in the company that resulted. We label every case study, because a studio that publishes its prices and argues the other side of its own comparisons has to be equally precise about its own portfolio.

What state is it in?

Paper-locked, live path gated. We state that plainly rather than describing everything as production: several things here are deliberately gated, and the reason is usually evidence rather than a missing feature.

Can you build something like this for us?

That is the point of publishing it. The same patterns are in the catalogue at published prices, and you can scope your own version on the plain-English page without contacting us first.

Where to next

If something here is close to what you need, the same patterns are in the catalogue at published prices, or you can describe your version in plain English and get it scoped and priced without talking to anyone.

[ // / QUANTITATIVE FINANCE ]

Other quantitative finance work

Built with the same discipline, in the same domain.

Want something like this built?

The catalogue prices the patterns behind this work. Describe your version and the engine will scope it, including an allowance for anything nobody has costed.