# Overview

Chamber is the parent brand. A few sibling brands run alongside it — same team, shared resources, shared fees and revenue. They exist as distinct products because each serves a different audience or strategy type, not because they're separate businesses.

## Sibling brands

* [**Toros Finance**](/ecosystem/toros-finance.md) — leveraged tokens and options tokens. Largest fee contributor across the group.
* [**mStable**](/ecosystem/mstable.md) — yield product, currently a single Pendle-sUSDe vault on Ethereum.
* [**Flat Money**](/ecosystem/flat-money.md) — perpetual options contract layer. Currently used internally by Toros for options strategies; no standalone end-user surface right now.

## How they relate to Chamber

Each brand is built on the Chamber vault stack — same contracts, same Guard System, same oracle infrastructure, same DAO treasury. Fees generated by any brand flow to the same Chamber DAO treasury under the same 10% split (see [DAO protocol fees](/treasury-and-protocol-economics/dao-protocol-fees.md)).

Practically: a vault on Toros is a Chamber vault with a Toros front-end on top. The audits, incident history, and onchain transparency that apply to Chamber apply to all of them.

## What lives where

| Brand         | URL                                    | Status                    |
| ------------- | -------------------------------------- | ------------------------- |
| Chamber       | [chamberfi.com](https://chamberfi.com) | Live                      |
| Toros Finance | [toros.finance](https://toros.finance) | Live                      |
| mStable       | [mstable.org](https://mstable.org)     | Live (single vault)       |
| Flat Money    | —                                      | V2 in flux; V1 deprecated |

Each product has its own docs for strategy-specific detail; this section gives the one-paragraph version and a pointer.


---

# Agent Instructions: 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://docs.chamberfi.com/ecosystem/overview.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.