What Type of SuperApp Are You Building?

This page helps you identify your SuperApp type and points you to the right integration path.

Prerequisite: If you haven't read it yet, start with Introduction: Ownera Application Orchestration Layer to understand what the Router does and why you should connect to it.

---

1. Business SuperApp

You are a Business SuperApp if:

• Users interact with your UI to trade, invest, issue, or manage assets
• You own business logic and decision-making (order routing, allocation, compliance)
• You need to execute transactions with counterparties on other platforms

Examples

How You Integrate

┌─────────────────────────────────────────────────────────────┐
│                    Your Application                         │
│                                                             │
│   ┌──────────┐    ┌──────────────┐    ┌─────────────────┐   │
│   │    UI    │◄──►│   Business   │◄──►│     Router      │   │
│   │          │    │    Logic     │    │   Integration   │   │
│   └──────────┘    └──────────────┘    └────────┬────────┘   │
│                                                │            │
└────────────────────────────────────────────────┼────────────┘
                                                 │
                                    REST (actions) & GraphQL (reads)
                                                 │
                                                 ▼
                                      ┌─────────────────┐
                                      │   Your Router   │
                                      └────────┬────────┘
                                               │
                      ┌────────────────────────┼────────────────────────┐
                      │                        │                        │
                      ▼                        ▼                        ▼
           ┌─────────────────┐      ┌─────────────────┐      ┌─────────────────┐
           │  Counterparty   │      │    Utility      │      │    Ledgers      │
           │    Routers      │      │   SuperApps     │      │    & Chains     │
           └─────────────────┘      └─────────────────┘      └─────────────────┘

Your integration module handles:

1. Identity Mapping — Your internal users/accounts → global investor profiles
2. Asset Mapping — Your instruments/products → global asset profiles
3. Action Translation — User actions in your app → intents submitted to the Router
4. State Sync — Orchestration results from Router → updates in your UI and systems

What you keep vs. what the Router does

As a Business SuperApp, you keep control of:

• Your UX and experience – screens, flows, error handling, user journeys
• Your business logic – when to show opportunities, when to initiate/approve actions
• Your own data & auth – user accounts, permissions, internal state, audit in your systems
• Your internal workflows – how events from the Router map into operational steps

The Router takes care of:

• Cross-party orchestration – coordinating workflows across counterparties and services
• Routing & connectivity – talking to other Routers and SuperApp utilities (custody, payments, ledgers, data)
• Shared positions & lifecycle – maintaining network-visible positions, events and execution plans

→ Next Steps for Business SuperApps

1. Authorization - Set up authentication
2. Hello World: Connect Your App - Build your first integration

---

2. Utility SuperApp

You are a Utility SuperApp if:

• Other applications consume your service (not end users directly)
• You provide infrastructure capabilities: custody, payments, data, connectivity
• You want to be invoked as part of multi-party orchestrated workflows

Examples

How You Integrate

┌─────────────────┐                    ┌─────────────────┐
│    Business     │                    │    Business     │
│    SuperApp A   │                    │    SuperApp B   │
└────────┬────────┘                    └────────┬────────┘
         │                                      │
         ▼                                      ▼
┌─────────────────┐                    ┌─────────────────┐
│    Router A     │◄──────────────────►│    Router B     │
└────────┬────────┘                    └─────────────────┘
         │
         │ Invokes as part of
         │ orchestration plan
         │
         ▼
┌─────────────────┐
│  Your Utility   │
│    SuperApp     │
│                 │
│ ┌─────────────┐ │
│ │  Adapter    │ │
│ │  Interface  │ │
│ └─────────────┘ │
└────────┬────────┘
         │
         ▼
┌─────────────────┐
│ Your Underlying │
│ System (ledger, │
│ payment rail,   │
│ data source)    │
└─────────────────┘

Your integration involves:

1. Implementing an Adapter Interface - The Router calls your service via a standard API contract
2. Handling Instructions - Receive and process requests (sign, transfer, hold, release, etc.)
3. Reporting Results - Return outcomes back to the Router for orchestration continuation
4. Managing Entitlements - Control which organizations can use your service

Two Integration Models

→ Next Steps for Utility SuperApps

1. Ledger Adapter Specification - For tokenization/ledger connectivity
2. Custody Adapter Specification - For custody/signing services
3. Use Case: Providing Custody Services - End-to-end example

---

3. Hybrid: Both Business and Utility

Some platforms serve both roles:

If this is you: we suggest you start with your primary use case (usually Business SuperApp), then add the other role incrementally.

---

Choosing Your Path

---

FAQ

Q: What if I just want to query data, not execute trades?
A: You're still a Business SuperApp - just a read-only one. You'll use GraphQL to query assets, positions, and portfolios without submitting intents..

Q: What about Distributed Hubs / Domain Protocols?
A: Most developers don't need to think about these. Distributed Hubs are pre-configured protocols for specific markets (e.g., repo, securities lending). If you're joining an existing market, you'll use its existing Hub. Only market operators creating new markets need to define them.

Q: Can I run my own Router?
A: Yes. Financial institutions can operate their own Router instance. Contact Ownera for details on deployment options.

---

Next Steps

1. Understand the primitives - Core Concepts: Router & Primitives
2. SuperApp Architecture - SuperApp Architecture
3. Build your first integration - Hello World: Connect Your App