> ## Documentation Index
> Fetch the complete documentation index at: https://cts-docs.cosmos.network/llms.txt
> Use this file to discover all available pages before exploring further.

# Cosmos Tokenization Suite

> Issue, settle, and move tokenized assets on institution-controlled infrastructure synchronized with existing systems.

The Cosmos Tokenization Suite (CTS) lets banks issue tokenized deposits on their
existing banking cores, and settle and move them across networks. Everything
runs on infrastructure the institution controls, synchronized with the core
banking system. Its three solutions share a common technology layer.

## Find your starting point

> [card] [For commercial banks](https://cts-docs.cosmos.network/cts-issuance/overview.md)
>
> Issue tokenized deposits on your existing core, and settle and move them
> across networks.

> [card] [For custodians](https://cts-docs.cosmos.network/digital-asset-custody/integrations.md)
>
> What CTS requires from a custody provider, and how wallets, settlement
> assets, and signing connect.

> [card] [For ledger operators](https://cts-docs.cosmos.network/cts-interop/overview.md)
>
> Connect an existing chain or platform to other DLT networks over IBC,
> without replacing it.

## Three solutions

| Solution | What it does | Who it is for |
| - | - | - |
| [Issuance](https://cts-docs.cosmos.network/cts-issuance/overview.md) | Issue, hold, and transfer tokenized deposits | Commercial banks |
| [Settlement](https://cts-docs.cosmos.network/cts-settlement/overview.md) | Operate tokenized settlement across a network of member institutions | FMIs, clearing houses, payment and messaging networks, central banks |
| [Interop](https://cts-docs.cosmos.network/cts-interop/overview.md) | Connect an existing ledger to other DLT networks over IBC | Institutions already running their own ledger |

## How it works

> [card] [Banking core integrations](https://cts-docs.cosmos.network/banking-core-integrations/overview.md)
>
> Integrations support Fiserv, Jack Henry, and custom cores. The core
> remains the record of record.

> [card] [Digital asset custody](https://cts-docs.cosmos.network/digital-asset-custody/overview.md)
>
> For assets on shared or public networks, keys remain with the custody
> provider. CTS issues signing requests and does not hold those keys.

> [card] [Digital ledger](https://cts-docs.cosmos.network/digital-ledger-support/overview.md)
>
> The digital ledger is a private EVM chain alongside the core. It runs on
> Cosmos EVM or an institution's own chain.

> [card] [Settlement](https://cts-docs.cosmos.network/settlement/settlement-options.md)
>
> Settlement uses stablecoins, tokenized deposit networks, or traditional
> rails. It supports gross or netted settlement.

> [card] [Interoperability](https://cts-docs.cosmos.network/ibc/overview.md)
>
> IBC is a messaging protocol, not a bridge. No intermediary holds the asset.

> [card] [Use cases](https://cts-docs.cosmos.network/use-cases/overview.md)
>
> Use cases include tokenized deposits, stablecoins, real world assets, and
> securities.

## Get started

**1. Understand the model**

[What is Cosmos Tokenization Suite](https://cts-docs.cosmos.network/what-is-cts/overview.md) covers the
capabilities. [Architecture](https://cts-docs.cosmos.network/what-is-cts/architecture.md) shows how the layers
fit together.

**2. Check your core**

[Core Requirements](https://cts-docs.cosmos.network/banking-core-integrations/core-requirements.md) lists the
read and write surface CTS needs. It is the fastest way to establish
whether an integration is viable.

**3. Stand up an environment**

[Getting Started](https://cts-docs.cosmos.network/what-is-cts/getting-started.md) covers configuration and the
first tokenization run.

## Talk to us

Contact [sales@cosmoslabs.io](mailto:sales@cosmoslabs.io) for an integration on a
core CTS does not yet support, a pilot, or a partnership.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.