SuperApp Architecture
This guide helps you design your SuperApp deployment: where components run, who operates the Router, and how you connect to the network.
Prerequisite: Read Choose Your SuperApp Type first to determine if you're building a Business or Utility SuperApp.
Architecture at a Glance
Every SuperApp deployment involves three questions:
| Question | Options |
|---|---|
| Who runs the Router? | Your organization, your client's organization, or managed by Ownera |
| Where does your SuperApp run? | Your infrastructure, client infrastructure, or SaaS/cloud |
| How do you connect? | Single Router, multiple Routers, or hub topology |
Business SuperApp Patterns
Pattern 1: Single Institution (Internal App or Trading Venue)
You are: A team inside a financial institution, or a trading venue / market operator running your own platform.
┌─────────────────────────────────────────────────────────────────┐
│ Your Institution / Venue │
│ │
│ ┌─────────────────┐ ┌─────────────────┐ │
│ │ Your Business │◄───────►│ Your Router │ │
│ │ SuperApp │ REST/ │ │ │
│ │ │ GraphQL │ │ │
│ │ • Trading UI │ Events │ │ │
│ │ • Investor App │ └────────┬────────┘ │
│ │ • Ops Tools │ │ │
│ │ │ │ │
│ │ Can also act │ ┌─────────────┼─────────────┐ │
│ │ as an adapter │ │ │ │ │
│ └─────────────────┘ ▼ ▼ ▼ │
│ ┌──────────┐ ┌──────────┐ ┌──────────┐ │
│ │ Custody │ │ Ledger │ │ Payment │ │
│ │ Connector│ │ Connector│ │ Connector│ │
│ └────┬─────┘ └────┬─────┘ └────┬─────┘ │
│ │ │ │ │
│ ▼ ▼ ▼ │
│ ┌──────────┐ ┌──────────┐ ┌──────────┐ │
│ │ HSM │ │ Ledger │ │ Payment │ │
│ │ │ │ │ │ Rail │ │
│ └──────────┘ └──────────┘ └──────────┘ │
│ │
└──────────────────────────────────┬──────────────────────────────┘
│ FinP2P Network
┌─────────────┴─────────────┐
▼ ▼
┌────────────┐ ┌────────────┐
│ Partner / │ │ Partner / │
│Participant │ │Participant │
│ Router A │ │ Router B │
└────────────┘ └────────────┘Characteristics:
| Aspect | Details |
|---|---|
| Router operator | Your institution |
| SuperApp location | Your infrastructure (on-prem or private cloud) |
| Tenancy | Single-tenant |
| Network connectivity | Your Router ↔ Partner/Participant Routers |
| Local utilities | Use from SuperApp Store or build custom |
You build:
- Your Business SuperApp (UI + backend)
- Router integration module (REST/GraphQL client + event listener)
You configure:
- Router connection (URL, credentials)
- Investor/asset mappings
- Partner organization connections
- Integration with local Utility SuperApps (from Store or custom-built)
Utility SuperApps from the StoreYou don't need to build every adapter yourself. The SuperApp Store offers pre-built Utility SuperApps that connect your Router to specific technologies - custody platforms, ledgers, payment rails, and more. Deploy them alongside your Router and configure for your environment.
Your SuperApp as an AdapterYour Business SuperApp can also listen to Router events and act as an adapter - for example, to integrate with internal systems, trigger workflows, or bridge to proprietary infrastructure.
Utility Integration Options
Your Business SuperApp can integrate with local Utility SuperApps in two ways:
| Model | How it works | Example |
|---|---|---|
| Router-mediated | Router calls Utility as part of orchestration plan | Custody signing during settlement |
| Direct integration | Your Business SuperApp calls the Utility directly | Analytics, pricing lookups, document retrieval |
┌───────────────────────────────────────────────────────────────-──┐
│ ┌─────────────────┐ ┌─────────────────┐ │
│ │ Your Business │────────►│ Your Router │ │
│ │ SuperApp │ └────────┬────────┘ │
│ │ │ │ │
│ │ │ │ Router-mediated │
│ │ │ ▼ │
│ │ │ ┌─────────────────┐ │
│ │ │ │ Custody Connector │
│ │ │ └─────────────────┘ │
│ │ │ │
│ │ │──────────────────────────────────────┐ │
│ │ │ Direct integration ▼ │
│ └─────────────────┘ ┌───────────--───┐ │
│ │Pricing Connector │
│ └────────────--──┘ │
└────────────────────────────────────────────────────────────────-─┘Market Infrastructure Considerations
If you're operating a trading venue or market infrastructure:
| Consideration | Details |
|---|---|
| Participants | Your participants (banks, brokers) may run their own Routers and connect to yours |
| Dual role | You may also provide Utility SuperApp services (execution, clearing, settlement) |
| Onboarding | You may offer a hosted Router option for smaller participants |
Pattern 2: Multi-Client SaaS Platform
You are: An ISV or fintech offering a platform to multiple financial institutions.
┌─────────────────────────────────────────────────────────────────┐
│ Your SaaS Platform │
│ │
│ ┌─────────────────────────────────────────────────────────┐ │
│ │ Your Business SuperApp │ │
│ │ (Multi-Tenant) │ │
│ │ │ │
│ │ ┌─────────┐ ┌─────────┐ ┌─────────┐ │ │
│ │ │Tenant A │ │Tenant B │ │Tenant C │ │ │
│ │ │ Config │ │ Config │ │ Config │ │ │
│ │ └────┬────┘ └────┬────┘ └────┬────┘ │ │
│ │ │ │ │ │ │
│ └────────┼─────────────┼─────────────┼────────────────────┘ │
│ │ │ │ │
└────────────┼─────────────┼─────────────┼────────────────────────┘
│ │ │
▼ ▼ ▼
┌────────────┐ ┌────────────┐ ┌────────────┐
│ Client A │ │ Client B │ │ Client C │
│ Router │ │ Router │ │ Router │
│ │ │ │ │ │
│ (at FI A) │ │ (at FI B) │ │ (at FI C) │
└────────────┘ └────────────┘ └────────────┘Characteristics:
| Aspect | Details |
|---|---|
| Router operator | Each client (FI) runs their own Router |
| SuperApp location | Your SaaS infrastructure |
| Tenancy | Multi-tenant (logical) or multi-instance |
| Network connectivity | Your app → Multiple client Routers |
You build:
- Multi-tenant Business SuperApp
- Per-tenant Router configuration management
- Tenant isolation layer
You configure (per client):
- Client's Router URL and credentials
- Client-specific asset/investor mappings
- Enabled features and protocols
Tenancy options:
| Model | Description | When to use |
|---|---|---|
| Logical multi-tenant | Single deployment, tenant isolation in code | Most SaaS scenarios |
| Multi-instance | Separate deployment per client | High isolation requirements |
Utility SuperApp Patterns
Utility SuperApps provide services (custody, payments, ledger connectivity, data) consumed by Routers. They typically run alongside a Router - either yours or another party's.
You are: An FI running your own custody, payment, or connectivity services alongside your Business SuperApp.
┌─────────────────────────────────────────────────────────────────┐
│ Your Institution │
│ │
│ ┌─────────────────┐ ┌─────────────────┐ │
│ │ Your Business │ │ Your Router │ │
│ │ SuperApp │────────►│ │ │
│ │ │ │ │ │
│ │ • Trading UI │ │ │ │
│ │ • Investor App │ └────────┬────────┘ │
│ └─────────────────┘ │ │
│ │ │
│ ┌───────────────────┼───────────────────┐ │
│ │ │ │ │
│ ▼ ▼ ▼ │
│ ┌──────────────┐ ┌──────────────┐ ┌───────────┐ │
│ │ Your Custody │ │ Your Ledger │ │Your Payment │
│ │ Utility │ │ Adapter │ │ Utility │
│ └──────┬───────┘ └──────┬───────┘ └─────┬─────┘ │
│ │ │ │ │
│ ▼ ▼ ▼ │
│ ┌──────────────┐ ┌──────────────┐ ┌───────────┐ │
│ │ HSM │ │ Ledger │ │ Payment │ │
│ │ │ │ │ │ Rail │ │
│ └──────────────┘ └──────────────┘ └───────────┘ │
│ │
└──────────────────────────────────┬──────────────────────────────┘
│ FinP2P Network
▼
┌─────────────────┐
│ Partner Routers │
└─────────────────┘Characteristics:
| Aspect | Details |
|---|---|
| Operator | Your institution |
| Location | Your infrastructure, alongside your Router |
| Serves | Your Router only |
| Use case | Internal custody, proprietary ledger connection, internal payment rails |
Integration Models
Utility SuperApps can be invoked in two ways:
| Model | How it works | Example |
|---|---|---|
| Router-mediated | Router calls Utility as part of orchestration plan | Custody signing during settlement |
| Direct integration | Your Business SuperApp calls the Utility directly | Analytics, document retrieval, pricing lookups |
Many Utilities support both models. The "SuperApp" designation means the Utility follows ecosystem conventions and best practices - even when integrated directly by your application rather than through the Router.
┌─────────────────────────────────────────────────────────────────┐
│ Your Institution │
│ │
│ ┌─────────────────┐ ┌─────────────────┐ │
│ │ Your Business │────────►│ Your Router │ │
│ │ SuperApp │ └────────┬────────┘ │
│ │ │ │ │
│ │ │ │ Router-mediated │
│ │ │ ▼ │
│ │ │ ┌─────────────────┐ │
│ │ │ │ Custody Utility │ (signing) │
│ │ │ └─────────────────┘ │
│ │ │ │
│ │ │──────────────────────────────────────┐ │
│ │ │ Direct integration │ │
│ └─────────────────┘ ▼ │
│ ┌──────────────┐│
│ │Pricing Utility│
│ └──────────────┘│
└─────────────────────────────────────────────────────────────────┘You implement:
| Component | Specification |
|---|---|
| Ledger connectivity | Ledger Adapter API |
| Custody / signing | Custody Adapter API |
Next Steps
- Understand the primitives - Core Concepts: Router & Primitives
- Build your first integration - Hello World: Connect Your App
Updated 4 days ago