Work

Exchange systems, matching to reporting

Matching engine, order management, clearing, reconciliation and regulatory reporting.

Result

99.9%uptime on integrations

99.9% uptime on integrations.

Exchanges and execution venues

Matching, clearing and reporting must never disagree, and every outside link has to stay up.

In production

recon · end of daybusiness date 2026-09-22

matching1,284,902trades

→

clearing1,284,902novated

→

positions18,441accounts

→

reporting1,284,902acked

check	left	right	finished (UTC)
matching ↔ clearing	1,284,902	1,284,902	22:04:11
clearing ↔ positions	18,441	18,441	22:06:37
fees ↔ ledger	1,284,902	1,284,902	22:07:02
trade reports ↔ regulator acks	1,284,902	1,284,902	23:41:55

integration uptime, last 30 days: 99.9% · next run 2026-09-23 22:00 UTC

End-of-day reconciliation from matching to regulatory reports.

order-audit · ORD-22-0918442107business date 2026-09-22

time (UTC)	event	detail	system
14:26:03.118204	received	buy 1.000 BTC-USD limit 64,190.0	gateway
14:26:03.118231	validated	member limits, price band ±5%	risk
14:26:03.118239	sequenced	seq 918,442,107	sequencer
14:26:03.118252	partial fill	0.400 @ 64,189.5 · T-5520117	matching
14:26:07.902113	filled	0.600 @ 64,190.0 · T-5520391	matching
14:26:07.903540	novated	2 trades to CCP	clearing
14:26:07.905118	position update	member M-0412 +1.000 BTC	positions
14:26:08.412000	reported	2 trade reports	reporting
14:26:09.131000	acked	regulator ack, 0 rejects	reporting

every event carries the order id end to end · the same record appears in the end-of-day reconciliation

One order, from entry to regulator ack.

Representative views of production tooling. Data anonymized.

What we built

Java/SpringGoPostgreSQLKafkaKubernetesGrafana

Next case

Next step

Have a hard system to build?

Tell us what it has to do. We will tell you how we would build it.