> ## Documentation Index
> Fetch the complete documentation index at: https://tetrafi.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Why TetraFi

> The mission, and the segment: settlement rails for stablecoins and tokenized real-world assets, at institutional size.

Stablecoins already move tens of trillions a year, and tokenized real-world assets are the next balance sheet arriving on-chain - yet most institutional flow in both still settles through closed, bilateral OTC relationships, coordinated over chat and trust rather than competitive pricing and reliable rails. Institutions want to move on-chain; what's missing is the core infrastructure to do it properly.

## What TetraFi Builds

Settlement rails and **modular on-chain primitives** for the institutions moving on-chain - neobanks, exchanges, fintechs, and asset managers. The first product suite delivers composable cross-chain liquidity aggregation, settlement, and execution with configurable policy enforcement. Next come [TetraFi T+0 Vaults](/vaults) and a programmable credit layer - the primitive that bridges TradFi's delayed, asynchronous settlement cycles with the instant-settlement expectations of the on-chain economy - and [Multilateral Netting](/netting), which offsets the network's obligations against each other so only the residual ever pays a settlement toll.

Think of it as the regulated settlement layer traditional finance has had for decades - built natively for on-chain assets.

## The Segment We're Built For

Most cross-chain infrastructure optimises for reach: the long tail of tokens, retail ticket sizes, anonymous counterparties. TetraFi optimises the other axis - a narrow asset set traded deep: **regulated stablecoins and tokenized real-world assets, at institutional ticket sizes, between identified counterparties.**

That means all three flows those assets generate, not just one: **secondary trading** in the token, **primary issuance** as it mints, and **redemption** back to cash - carried on a single rail rather than treating the trade as the only event worth pricing.

Narrowing is the point, not a limitation. On this asset set it buys things breadth cannot:

* **These are instruments, not tokens.** A tokenized treasury or a regulated stablecoin carries a par value, an issuer, a redemption right, and an eligibility rule. Pool pricing prices none of that; a firm quote from an identified desk does.
* **At size, pools invert.** Pool depth prices *against* you as the ticket grows - a desk holding inventory prices *for* it. That inversion is where this segment begins.
* **Primary and secondary are the same rail.** Mint, redeem, and secondary trade compose as legs in one route, so a subscription or a redemption becomes an executable path rather than a separate operational process.
* **The counterparty is a legal entity.** KYB'd, jurisdiction-filtered, and policy-gated before a request ever reaches a desk - mandatory for these assets, and beside the point for the long tail.
* **Settlement is delivery-versus-payment.** Escrowed delivery-or-refund is what settling an instrument requires; best-effort routing is not.

Breadth still has its place. The [Router](/router-api/introduction) reaches the wider token universe through DEX, bridge, and fiat sources, and sits alongside the aggregated routing most institutions already integrate - depth is the claim we make about stablecoins and tokenized assets specifically. The full asset and network picture is on [Coverage](/supported-chains).

## Cross-Chain First, One Signature

TetraFi treats cross-chain as the default, not the special case. A user or institution expresses an **intent** - what goes in, what comes out, on whichever chains - and signs once. Solvers absorb everything in between: route selection, bridge choice, liquidity sourcing, settlement. No bridge menus, no asset-hopping, no multi-step workflows. Quotes stream in around 100 ms, execution commitments land in sub-seconds, and settlement completes atomically - which is what lets capital move from any chain into any asset, vault, or strategy in one click, and back out the same way.

## The Morpho-Shaped Goal

Our long-term aim is to do for institutional execution, settlement, and liquidity what Morpho did for on-chain lending: **open, modular infrastructure that institutions control and own themselves**, while benefiting from a shared, secure, globally accessible network.

## Own the Deployment, Share the Network

Each institution runs its own TetraFi deployment - immutable contracts, no custody key, no upgrade key, governed under its own regulatory perimeter - while connecting to one shared liquidity and settlement network. Joining the network beats forking the code for two structural reasons:

* **Liquidity compounds.** Every additional LP, solver, vault, and issuer deepens the shared pool; aggregated institutional flow attracts sharper providers, and competition compresses spreads for everyone.
* **Capital gets reused.** The same solver inventory or vault capital serves payments, OTC settlement, stablecoin conversion, RWA redemptions, and treasury rebalancing - instead of idling inside isolated products.
* **Configuration is sovereignty.** Venue sets, LP rosters, jurisdiction filters, and policy pipelines are settings of *your* deployment - the network is shared, the rules are yours.

## Infrastructure, Not a Competitor

TetraFi is not built to replace banks, fintechs, asset managers, or exchanges. It is the **shared institutional infrastructure** they build proprietary products on - under their own brand and regulatory perimeter. Through one integration, an institution can assemble and distribute cross-currency stablecoin accounts, 24/7 payments and remittances, on-chain FX - and, further out, savings, credit, and tokenised investment products.

<CardGroup cols={2}>
  <Card title="How it works" icon="diagram-project" href="/how-tetrafi-works">
    The two products and the platform underneath them.
  </Card>

  <Card title="Talk to us" icon="envelope" href="/support">
    Building something institutional? Let's compare notes.
  </Card>
</CardGroup>
