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

# Introduction

> Red Potion is a multi-tenant, on-chain asset-management protocol. It gives professional fund operators the rails to run tokenized funds on-chain, and gives investors a simple way t

Red Potion is a **multi-tenant, on-chain asset-management protocol**. It gives professional fund operators the rails to run tokenized funds on-chain, and gives investors a simple way to gain exposure to those funds through a single deposit.

## Three layers

Red Potion is organized as three nested layers. Understanding them is the fastest way to understand the whole system.

**The protocol root.** One contract, the [FundManagerDeployer](/developers/contract-reference/fund-manager-deployer), is deployed and operated by the Red Potion protocol team. It holds the canonical implementation code for every contract type, creates tenants, and stores the protocol-wide fee recipient.

**The tenant.** Each fund house gets its own [FundManager](/developers/contract-reference/fund-manager) — a launchpad that can create any number of funds. A tenant controls its own funds and its own upgrade authority; tenants are isolated from one another.

**The fund.** Each fund is a self-contained **hub-and-spoke** instance: a [Fund](/developers/contract-reference/fund) hub surrounded by spokes that handle deposits, redemptions, pricing, fees, and risk, plus one or more [Strategy](/developers/contract-reference/strategy) wallets that deploy the capital.

```
Protocol root      FundManagerDeployer   (Red Potion team)
                          │  creates
Tenant layer        FundManager           (one per fund house)
                          │  creates
Fund instance       Fund + spokes + strategies
```

## What makes Red Potion different

**Batch settlement instead of continuous pricing.** Most on-chain vaults price every deposit and withdrawal instantly against a live exchange rate. Red Potion instead groups requests into **batches** and settles each batch at a single price derived from an operator-submitted NAV report. This suits funds whose true value depends on off-chain or cross-chain positions that cannot be read live on-chain, and it guarantees every participant in a batch the same execution price.

**Operator-run, guardrail-bounded.** Capital is actively managed by a fund operator, not by an autonomous strategy. To keep that power bounded, operators can only deploy capital through [Strategy](/developers/contract-reference/strategy) wallets restricted to an **allowlist of exact calls**, and every deposit and redemption is screened by a per-fund [RiskManager](/developers/contract-reference/risk-manager).

**Roles managed in one place.** Every fund and its spokes authorize privileged actions against a single access-control registry on the [Fund](/developers/contract-reference/fund). One admin surface governs the whole fund. See [Access Control & Roles](/developers/access-control-and-roles).

**Multi-chain execution.** A fund can deploy capital on chains other than the one it lives on, using a [StandaloneStrategy](/developers/contract-reference/standalone-strategy). Assets are bridged operationally and the results are reflected back into the fund's NAV through the [Oracle](/developers/contract-reference/oracle).

## Who it's for

Red Potion serves three audiences at once: **fund operators** who want to run a strategy on-chain without building infrastructure, **investors** who want managed exposure through a single tokenized position, and the **protocol operator** who onboards tenants and maintains the shared contract stack. The [next page](/overview/how-batched-fund-shares-work) explains the mechanic that ties them together — batched fund shares.