> 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/value-proposition/onchain-product-platforms.md).

# Onchain Product Platforms

Neofinance platforms need more than a single financial feature. A modern application may want to offer yield, swaps, lending, borrowing, and rewards in one user journey. Building each module separately is slow and expensive.

City Protocol gives platforms a modular stack instead of a patchwork of one-off integrations.

**City Protocol helps platforms:**

* embed tokenized yield products and verified vaults;
* access product metadata, capacity, fees, risk labels, NAV history, verification records, and redemption status;
* integrate swaps and chain abstraction so users do not need to manage bridges or route selection manually;
* connect lending, swaps, yield, and borrowing modules through a unified stack;
* expose eligible products to different user segments based on jurisdiction, wallet status, accreditation, or partner policy;
* reduce the operational load of managing many vendors, dashboards, data formats, and settlement flows.

The benefit is faster expansion from a single-feature app into a full neofinance product. Platforms can add new financial services while relying on City Protocol for the underlying tokenization, vault, verification, and integration logic.