> For the complete documentation index, see [llms.txt](https://city-protocol.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://city-protocol.gitbook.io/docs/tokenization-as-a-service/what-is-taas.md).

# What is TaaS

Tokenization as a Service, or TaaS, is City Protocol's capital-layer infrastructure for transforming yield sources into programmable onchain products.

It is designed for asset originators, strategy managers, neofinance platforms, and distribution partners that want to bring institutional yield assets onchain without rebuilding issuance, oracle, investor access, verification, reporting, and lifecycle infrastructure from scratch.

**TaaS is not only a token minting layer.**&#x20;

A tokenized yield product must define who can subscribe, what the token represents, how Net Asset Value (NAV) is calculated, how claims are verified, how subscriptions and redemptions are processed, and how the product can be distributed across applications and networks. TaaS packages those requirements into a reusable framework.

***

## Why TaaS

City Protocol's thesis is that onchain finance will expand beyond crypto-native yield once high-quality real-world and institutional strategies become accessible through consumer-grade rails.

The missing layer is infrastructure. Most asset managers and yield providers do not need a new frontend first. They need a compliant, verifiable, and distribution-ready way to convert an asset, fund, strategy, or vault position into an onchain product that users and integrators can understand.

**TaaS fills this gap by standardizing the tokenization workflow across six functions:**

1\. Yield asset tokenization;

2\. NAV monitoring and Oracle publication;

3\. Investor management and access control;

4\. General-purpose attestations and verification;

5\. Multichain distribution;

6\. Product lifecycle management, including subscription, redemption, and reporting.

The result is a repeatable path from offchain or strategy-managed yield to onchain access.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://city-protocol.gitbook.io/docs/tokenization-as-a-service/what-is-taas.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
