01
Choose
DLT & protocol foundation
EVM executionSovereign networksSettlement foundations
Gateway Platform
Composable infrastructure for sovereign onchain finance.
Gateway-owned technology for protocol, managed environments, interoperability, privacy and controls, financial-product infrastructure, and production operations, designed to connect with the institution’s existing core.
Institutional systemsCore · IAM · SIEM · data
Specialist providersIdentity · custody · fiat · liquidity
Inside the boundaryGateway Platform
- 01DLT & protocol foundation
- 02Managed environments
- 03Interoperability & data
- 04Privacy, identity & controls
- 05Financial-product infrastructure
- 06Production operations
DeployCloudInstitution-controlledRegionalOn-premisesHybrid
Platform thesis
Modular in adoption. Unified in operation.
Adopt the Gateway software capabilities the product needs while keeping interfaces, controls, telemetry and operational ownership coherent.
Inside the Platform boundaryGateway-owned technology
02
Operate
Managed environments
03
Connect
Interoperability & data
04
Govern
Privacy, identity & controls
Open Privacy SuitePolicyPermissionsEvidence
05
Compose
Financial-product infrastructure
Payment and asset primitivesTokenisation modulesAccount abstractionProduct policy
06
Assure
Production operations
ObservabilityChange controlIncident responseSupport
Connected through defined interfacesInstitutional systems and approved specialist providers remain outside the Platform boundary.
See Gateway Orchestration Interface architecture
The institution stays authoritative at every interface.
Gateway Platform connects to core systems through named contracts for data, identity, policy, telemetry and evidence. Specialist or regulated services remain externally owned and are coordinated through Gateway Orchestration.
01Core systems
→APIs · events · reconciliation→
Protocol & financial-product services02Identity & keys
→IAM · KMS · policy decisions→
Privacy, permissions & controls03Security & oversight
→Telemetry · evidence · escalation→
Production operationsExternal responsibilityApproved specialist providers retain their regulated roles.Coordinated through Gateway Orchestration →
Deployment models
Your jurisdiction. Your deployment model.
Cloud, institution-controlled, regional, on-premises, and hybrid patterns are scoped against the required data, key, administration, evidence, support, and exit boundaries.
Cloud
A managed environment with the production envelope and service boundary defined in the applicable agreement.
Institution-controlled
Platform software deployed into the institution’s estate with component-level operating and support boundaries.
Regional
Eligible processing, storage, keys, and administration constrained to agreed jurisdictions, subject to provider availability.
On-premises
Selected capabilities placed within an institution-controlled environment where architecture and support scope permit.
Hybrid
Institution-controlled and managed components joined through explicit interfaces, evidence, and operational ownership.
Modernise beside the core.
Keep authoritative ledgers, identity, security, reporting, and customer systems in place. Introduce new onchain capability through a controlled interface and a staged migration path.
Brownfield by design
Change one boundary without forcing wholesale replacement.
Operating responsibility
Technology ownership and institutional authority remain distinct.
Components, operations, support and service levels are documented per deployment. Product governance and specialist-provider obligations retain named owners.
Gateway
Technology delivery and operations, where contractedPlatform software, integration delivery, and the infrastructure controls, observability, incident response, support, and service levels included in the applicable agreement.
Institution
Product governance and retained obligationsCustomer relationship, asset and product policy, jurisdictional analysis, risk acceptance, regulatory obligations, and business approvals that remain with the institution.
Specialist providers
Contracted or regulated services, where applicableServices such as KYC/AML, custody, fiat access, liquidity, attestation, legal, or audit within each provider’s contracted and, where applicable, licensed or approved scope.
Define the platform boundary
Select capabilities after the operating requirements are visible.
Map the product, systems, jurisdictions, controls, interfaces, and evidence into a candidate Gateway Platform architecture.