Core Concept

How Hyperscale Works

Hyperscale is a cross-domain financial infrastructure platform that operates as an Electronic Money Institution (EMI). We provide the orchestration layer between your fintech products and the entire Saudi financial ecosystem.

The Integration Tax

Every financial product pays a hidden cost we call the Integration Tax. Building connections to banks, payment processors, KYC providers, and card issuers consumes 12-18 months of engineering time before you can even launch. The cost exceeds $500,000 in integration work alone—and that's before you've built your actual product.

Worse, once integrated, you're locked in. Switching providers means starting over. Provider outages become your outages. Every team rebuilds the same connections independently, wasting billions across the industry.

Traditional Approach

Time to launch12-18 months

Integration cost$500K+

Provider switchingRebuild

With Hyperscale

Time to launch3 weeks

Integration cost$0

Provider switchingInstant

The Control Plane

Hyperscale sits between your products and the provider ecosystem. You integrate once with our API—we handle connections to all 40+ providers, including banks, payment processors, KYC services, and card issuers.

Architecture Stack

The platform is organized into distinct layers, each with clear responsibilities. Your application calls the SuperGraph, which routes requests through domain services and the orchestration engine to the appropriate provider adapters.

SuperGraph

GraphQL federation across all providers. One query language, one schema, unified responses from any combination of banks, PSPs, and services.

Domain Services

Business logic organized by domain: Accounts, Transactions, Identity, Compliance, Billing. Each service maintains canonical entities.

Orchestration Engine

Temporal workflows for durable execution. Every multi-step operation is guaranteed to complete or gracefully fail—no inconsistent states.

Provider Adapters

Normalize provider-specific APIs to canonical formats. When providers update their APIs, we update the adapter—your code never changes.

Trust Architecture

Hyperscale operates as an Electronic Money Institution (EMI), not just a technical service provider. This means we can hold and manage virtual ledgers on behalf of partner banks, creating a trust chain from regulated infrastructure to your end users.

Partner Bank

SAMA-licensed institution that holds actual customer funds in pooled accounts. Bears regulatory risk and executes final settlement. Trusts Hyperscale through EMI licensing and audit trails.

Hyperscale EMI

Maintains virtual ledgers tracking each client's position. Orchestrates 40+ provider APIs, automates compliance, and routes transactions optimally. Operates with EMI licensing for e-money services.

Fintech Client

Your product. Operates with a sub-ledger position and full API access. Single API key for everything—no provider credentials to manage. Focus entirely on product development.

Technical Paradigm Shifts

The patterns that enable Hyperscale have been proven at planetary scale—Netflix, Stripe, Uber—but haven't been applied to financial services infrastructure in Saudi Arabia. These aren't incremental improvements; they're fundamental architectural changes.

From REST Chaos to Federated GraphQL

One query retrieves data from multiple providers. The SuperGraph federates requests across banks, KYC providers, and payment processors—returning unified responses.

Before

typescript

1// Traditional: Multiple API calls
2const customer = await api1.getCustomer(id);
3const accounts = await api2.getAccounts(id);
4const balance = await api3.getBalance(id);
5// 3 round trips, inconsistent schemas

With Hyperscale

typescript

1// Hyperscale: Single query
2const { customer } = await hyperscale.query(`
3  query {
4    customer(id: "${id}") {
5      name
6      accounts { balance }
7    }
8  }
9`);

From Vendor Chaos to Canonical Entities

64 canonical entities normalize data across 19 domains. Provider-specific schemas are abstracted away—your code never changes when providers do.

Before

typescript

1// Provider A: party.fullName
2// Provider B: customer_name
3// Provider C: subject.legalName
4// Different formats everywhere

With Hyperscale

typescript

1// Hyperscale: One schema
2const customer = {
3  id: "cus_xxx",
4  name: "Mohammed Al-Rashid",
5  nationalId: "1234567890",
6  // Same format, any provider
7};

From Fragile Retries to Durable Execution

Temporal workflows guarantee exactly-once execution. If a system crashes mid-transaction, it resumes at the exact step—no duplicates, no lost money.

Before

typescript

1// Traditional: Hope for the best
2try {
3  await bankApi.transfer(amount);
4} catch (e) {
5  // Did it go through?
6  // Should we retry?
7  // What state are we in?
8}

With Hyperscale

typescript

1// Hyperscale: Guaranteed execution
2workflow.execute('transfer', async () => {
3  await step('debit', () => source.debit(amt));
4  await step('credit', () => dest.credit(amt));
5  // Resumes exactly where it stopped
6});

From Hardcoded Logic to Smart Routing

The routing fabric knows provider capabilities, costs, and constraints. It selects the optimal provider and handles failover automatically.

Before

typescript

1// Traditional: Endless conditionals
2if (currency === 'SAR' && amount < 1000) {
3  return providerA.process(payment);
4} else if (currency === 'USD') {
5  return providerB.process(payment);
6}
7// Unmaintainable spaghetti

With Hyperscale

typescript

1// Hyperscale: Declarative routing
2fabric.route({
3  capability: 'payment_processing',
4  requirements: { currency, amount }
5});
6// Best provider selected automatically

From Batch Reconciliation to Real-Time Events

Event streaming replaces batch processing. See transactions settle in real-time, detect fraud instantly, and maintain live customer positions.

Before

typescript

1// Traditional: Daily batch jobs
2SELECT * FROM transactions
3WHERE date = CURRENT_DATE - 1
4-- Always a day behind
5-- Fraud detected too late

With Hyperscale

typescript

1// Hyperscale: Instant visibility
2eventStream.on('PaymentSettled', (event) => {
3  updateLedger(event.transactionId);
4  triggerFraudCheck(event);
5  // Real-time, sub-second
6});

Provider Ecosystem

Hyperscale connects to 40+ providers across the Saudi financial ecosystem. This includes major banks, payment processors, card networks, KYC services, and specialized verticals like travel and insurance.

Banking

SNB, Al Rajhi, D360, STC Bank

Payments

Geidea, Moyasar, Tap, HyperPay

Cards

Visa, Mastercard, mada

KYC

Nafath, SIMAH, Elm, Onfido

64 canonical entities across 19 domains normalize data from all providers. Explore entities

Continue Learning

Trust Model

Deep dive into trust layers

Credential Custody

How we secure provider keys

Provider Catalog

Browse 40+ integrations

Entity Catalog

64 canonical entities

Core Concept

How Hyperscale Works

The Integration Tax

Traditional Approach

Time to launch12-18 months

Integration cost$500K+

Provider switchingRebuild

With Hyperscale

Time to launch3 weeks

Integration cost$0

Provider switchingInstant

The Control Plane

Architecture Stack

SuperGraph

GraphQL federation across all providers. One query language, one schema, unified responses from any combination of banks, PSPs, and services.

Domain Services

Business logic organized by domain: Accounts, Transactions, Identity, Compliance, Billing. Each service maintains canonical entities.

Orchestration Engine

Temporal workflows for durable execution. Every multi-step operation is guaranteed to complete or gracefully fail—no inconsistent states.

Provider Adapters

Normalize provider-specific APIs to canonical formats. When providers update their APIs, we update the adapter—your code never changes.

Trust Architecture

Partner Bank

SAMA-licensed institution that holds actual customer funds in pooled accounts. Bears regulatory risk and executes final settlement. Trusts Hyperscale through EMI licensing and audit trails.

Hyperscale EMI

Maintains virtual ledgers tracking each client's position. Orchestrates 40+ provider APIs, automates compliance, and routes transactions optimally. Operates with EMI licensing for e-money services.

Fintech Client

Your product. Operates with a sub-ledger position and full API access. Single API key for everything—no provider credentials to manage. Focus entirely on product development.

Technical Paradigm Shifts

From REST Chaos to Federated GraphQL

One query retrieves data from multiple providers. The SuperGraph federates requests across banks, KYC providers, and payment processors—returning unified responses.

Before

typescript

1// Traditional: Multiple API calls
2const customer = await api1.getCustomer(id);
3const accounts = await api2.getAccounts(id);
4const balance = await api3.getBalance(id);
5// 3 round trips, inconsistent schemas

With Hyperscale

typescript

1// Hyperscale: Single query
2const { customer } = await hyperscale.query(`
3  query {
4    customer(id: "${id}") {
5      name
6      accounts { balance }
7    }
8  }
9`);

From Vendor Chaos to Canonical Entities

64 canonical entities normalize data across 19 domains. Provider-specific schemas are abstracted away—your code never changes when providers do.

Before

typescript

1// Provider A: party.fullName
2// Provider B: customer_name
3// Provider C: subject.legalName
4// Different formats everywhere

With Hyperscale

typescript

1// Hyperscale: One schema
2const customer = {
3  id: "cus_xxx",
4  name: "Mohammed Al-Rashid",
5  nationalId: "1234567890",
6  // Same format, any provider
7};

From Fragile Retries to Durable Execution

Temporal workflows guarantee exactly-once execution. If a system crashes mid-transaction, it resumes at the exact step—no duplicates, no lost money.

Before

typescript

1// Traditional: Hope for the best
2try {
3  await bankApi.transfer(amount);
4} catch (e) {
5  // Did it go through?
6  // Should we retry?
7  // What state are we in?
8}

With Hyperscale

typescript

1// Hyperscale: Guaranteed execution
2workflow.execute('transfer', async () => {
3  await step('debit', () => source.debit(amt));
4  await step('credit', () => dest.credit(amt));
5  // Resumes exactly where it stopped
6});

From Hardcoded Logic to Smart Routing

The routing fabric knows provider capabilities, costs, and constraints. It selects the optimal provider and handles failover automatically.

Before

typescript

1// Traditional: Endless conditionals
2if (currency === 'SAR' && amount < 1000) {
3  return providerA.process(payment);
4} else if (currency === 'USD') {
5  return providerB.process(payment);
6}
7// Unmaintainable spaghetti

With Hyperscale

typescript

1// Hyperscale: Declarative routing
2fabric.route({
3  capability: 'payment_processing',
4  requirements: { currency, amount }
5});
6// Best provider selected automatically

From Batch Reconciliation to Real-Time Events

Event streaming replaces batch processing. See transactions settle in real-time, detect fraud instantly, and maintain live customer positions.

Before

typescript

1// Traditional: Daily batch jobs
2SELECT * FROM transactions
3WHERE date = CURRENT_DATE - 1
4-- Always a day behind
5-- Fraud detected too late

With Hyperscale

typescript

1// Hyperscale: Instant visibility
2eventStream.on('PaymentSettled', (event) => {
3  updateLedger(event.transactionId);
4  triggerFraudCheck(event);
5  // Real-time, sub-second
6});

Provider Ecosystem

Banking

SNB, Al Rajhi, D360, STC Bank

Payments

Geidea, Moyasar, Tap, HyperPay

Cards

Visa, Mastercard, mada

KYC

Nafath, SIMAH, Elm, Onfido

64 canonical entities across 19 domains normalize data from all providers. Explore entities

Continue Learning

Trust Model

Deep dive into trust layers

Credential Custody

How we secure provider keys

Provider Catalog

Browse 40+ integrations

Entity Catalog

64 canonical entities