GATEWAY

Case studies

Selected production engagements and institutional pilots, presented with clear attribution and evidence status.

Evidence from delivery

Each record separates the customer context, Gateway contribution, and available result. Pilot and placeholder evidence is labeled explicitly.

02Pilot

Global post-trade market infrastructure

23,000+ TPS on customer premises

A high-throughput blockchain deployment validated above 23,000 transactions per second, running entirely on the customer’s own premises.

Evidence23,000+ TPS
Customer anonymized
Performant blockchainRead case study
06Pilot

Latin American financial market infrastructure group

Differentiated visibility for a market operator

Organisation- and role-aware policy enforced at the JSON-RPC boundary for one of the world’s largest financial-market infrastructure groups: controlled access, attributable decisions, auditable operations.

EvidencePolicy at the RPC boundary
Customer anonymized
Open Privacy SuiteRead case study
08Pilot

Global post-trade market infrastructure

Private state with supervisory access

A privacy pilot applying deny-by-default access, purpose-bound supervisory views, and approved disclosure to post-trade workflows.

EvidenceDeny-by-default oversight
Customer anonymized
Open Privacy SuiteRead case study

Context before claims

Evidence is presented with the boundary needed to interpret it responsibly.

Named scope

What Gateway engineered, integrated, or operated is stated for each engagement.

Visible status

Production records and scoped pilots are differentiated at first glance.

Attribution boundary

Confidential customers and evidence awaiting publication remain clearly marked.

Bring the financial requirement. Define the architecture.

Start with the operating context, control boundary, and evidence your institution needs.

Book an architecture workshop