Our platform runs on AWS across multiple regions. A private Direct Connect circuit carries it into Equinix LD4 and NY4, and inside those buildings a physical cross-connect runs to each liquidity provider — any provider you want. The public internet is never on the path.
A quote routed over the public internet crosses networks nobody in the trade controls. Paths change without warning, congestion is invisible until it costs you, and the tail latency that decides a fill is the part you can least predict.
Our path removes the question. AWS Direct Connect is a dedicated, private circuit from our cloud infrastructure into Equinix. A cross-connect is a physical cable between our port and the liquidity provider's, inside the same building. Both are point-to-point, with no shared transit and no routing decisions — and because we are present in LD4 and NY4, that cable can run to whichever provider you nominate.
Schematic. Gold indicates the private path: AWS Direct Connect into Equinix, then physical cross-connect to each provider. The same layout exists in LD4 (London) and NY4 (New York).
We are not a reseller with a logo on someone else's bridge. The pricing service, the risk engine and the portal are ours — which is why we can change them when a client needs something changed.
Prices arrive from each provider over the cross-connect and are normalised, monitored and distributed in real time — with freeze, jump and spread detection running on every tick, and open/closed status driven by trading sessions and market holidays.
Quotes push to the portal over a persistent connection. No polling, no refresh, no stale book.
Trade and exposure data flows through an auditable pipeline with gap detection — so the numbers in your report match the fills that produced them.
Feed handlers detect a dead session and reconnect without human intervention. Services autoscale across AWS regions, and a separate disaster-recovery site stands behind them. [UPTIME / SLA FIGURE — CONFIRM]
Role-based access, two-factor authentication, IP allow-listing and a complete audit trail on every action.
Everything runs on AWS across multiple regions with autoscaling, diverse fibre paths into Equinix, and a separate disaster-recovery site.
[FIX VERSION — CONFIRM: 4.2 / 4.4?] sessions for price and order flow. [Certification / onboarding lead time — CONFIRM]
Direct integration with your existing bridge or platform. [SUPPORTED BRIDGES / PLATFORMS — CONFIRM]
If you are already in Equinix LD4 or NY4, we meet you with a cross-connect in the same building — and if you want a specific liquidity provider on your book, we cross-connect to them too.
Send us your data centre and connectivity requirements and we'll come back with a path.
Talk to engineering