> 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/introduction/welcome-to-city-protocol/neofinance-stack-overview.md).

# Neofinance Stack Overview

City Protocol is a one-stop neofinance stack for yield asset tokenization, verified vault implementation, and modular financial service integration.

The stack is organized into three layers:

* **TaaS:** Tokenization as a Service;
* **VaaS:** Vault as a Service;
* **NaaS:** Neofinance as a Service.

Together, these layers connect yield providers, vault curators, applications, developers, and users.

<figure><img src="/files/RS0mjirbr50akAkVNfOv" alt=""><figcaption></figcaption></figure>

***

## Tokenization as a Service

TaaS bridges composable onchain technology with high-quality yield sources.

It helps yield providers and strategy managers transform deal flow, private credit, trading strategies, or other yield assets into programmable products that can be accessed through City Protocol and partner platforms.

**Core TaaS modules include:**

<table><thead><tr><th width="161.671875">Module</th><th>Function</th></tr></thead><tbody><tr><td>Yield Asset Tokenization</td><td>Creates the onchain representation of a yield product or strategy.</td></tr><tr><td>NAV Monitoring Oracle</td><td>Calculates, validates, and publishes product value for subscriptions, redemptions, and reporting.</td></tr><tr><td>Investor Management</td><td>Handles eligibility, access rules, limits, and permissions.</td></tr><tr><td>General-Purpose Attestation Engine</td><td>Connects product claims to verifiable records such as reserves, collateralization, reports, and service-provider confirmations.</td></tr><tr><td>Multichain Distribution</td><td>Prepares products for distribution through City Protocol, partner apps, and supported networks.</td></tr><tr><td>Staking and Liquidity Provision</td><td>Supports product-specific liquidity, participation, or incentive design where applicable.</td></tr></tbody></table>

TaaS makes tokenized yield products easier to launch, integrate, and monitor.

***

## Vault as a Service

VaaS is the secure operating layer for vault participation.

It gives partners a standardized way to launch and scale verified vaults without rebuilding deposit contracts, accounting systems, dashboards, proof infrastructure, and redemption logic from scratch.

Core VaaS modules include:

<table><thead><tr><th width="170.00390625">Module</th><th>Function</th></tr></thead><tbody><tr><td>Pre-Audited Smart Contracts</td><td>Standardized vault contracts for deposits, shares, withdrawals, and core controls.</td></tr><tr><td>Modular Deployment</td><td>Configurable parameters for each curator, product, strategy, and investor policy.</td></tr><tr><td>Management and Verification Dashboard</td><td>Real-time data feeds, visualization, reporting, and monitoring.</td></tr><tr><td>Automation and Monitoring Engine</td><td>Accounting updates, yield accrual, alerts, and NAV reflection.</td></tr><tr><td>Subgraph-Level Indexing</td><td>Onchain indexing for deposits, subscriptions, withdrawals, redemptions, fees, yield, roles, and settlement records.</td></tr><tr><td>Security Governance Layer</td><td>Multisig governance, timelocks, NAV signer quorum, strategy whitelisting, and emergency pauses.</td></tr></tbody></table>

VaaS makes vaults more secure, transparent, and predictable for LPs, curators, and integrators.

***

## Neofinance as a Service

NaaS is the modular integration layer for neofinance products.

It allows projects, platforms, wallets, exchanges, apps, and developers to integrate financial functions through City Protocol's API/SDK stack instead of stitching together many separate providers.

NaaS modules can include:

* yield vaults;
* token swaps;
* fiat on/off-ramps;
* KYC/AML and compliance;
* lending and borrowing;
* payments and card infrastructure;
* rewards and user incentives;
* agentic payments and subaccounts.

NaaS turns the capital layer into usable product experiences. A platform can add yield, swap, payment, spending, or agent-native transaction features without building the entire backend itself.

***

## From yield source to user experience

City Protocol's stack creates a full path from institutional yield to end-user access.

{% stepper %}
{% step %}
A yield provider or strategy manager brings an asset, strategy, or deal flow.
{% endstep %}

{% step %}
TaaS tokenizes the product, configures access rules, and connects the oracle and verification infrastructure.
{% endstep %}

{% step %}
VaaS operates the vault, enforces policy, tracks NAV, monitors deployment, and handles redemption.
{% endstep %}

{% step %}
NaaS exposes the product and related financial modules through APIs and SDKs.
{% endstep %}

{% step %}
Neofinance platforms deliver the experience to users, LPs, developers, and agents.
{% endstep %}
{% endstepper %}

This is how City Protocol turns isolated yield sources into composable neofinance infrastructure.


---

# 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, and the optional `goal` query parameter:

```
GET https://city-protocol.gitbook.io/docs/introduction/welcome-to-city-protocol/neofinance-stack-overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.