# Introduction

<figure><img src="https://1976028141-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdDlNSdIqQrkAaN1oYcEY%2Fuploads%2FfplZjrLCxRRGasaxqeoj%2Fember-x-profile-banner-1500x500.png?alt=media&#x26;token=7ce1d8a6-8bfa-41e9-aff4-2ab3a0083b5e" alt=""><figcaption></figcaption></figure>

**Ember Protocol** is a unified vault platform that tokenizes any yield or fund strategy - *crypto or real world* - across DeFi, CeFi, and Web2. It's the first Structured Vaults Product on Sui, incubated by Bluewater Labs, offering a suite of non-custodial, permissionless vaults managed by top-tier curators in Web3, running strategies to unlock the highest risk-adjusted returns for users.

* **Everything Vault Layer:** Vaultify any strategy with a single share-price model; supports both permissioned (KYC) and permissionless setups.
* **Crosschain:** Strategies run crosschain, deposits currently available on Sui (and very soon on Solana and EVM)
* **Three Layers:**

  1. **DeFi** – best-performing on-chain yield vaults and market-making strategies.
  2. **CeFi** – tokenized private credit and fund portfolios with transparent NAVs.
  3. **Web2** – yield integration for neobanks, fintechs, and asset managers.

The vision for Ember Protocol is to create a unified Liquidity Layer, designed to pull yield from several ecosystems and democratize accessibility for all Web3 users. One vault platform powering all strategies,
&#x20;one liquidity layer connecting Web2 and Web3
&#x20;and one brand driving the next wave of tokenized assets.  Just deposit and forget!&#x20;


---

# 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://learn.ember.so/ember-protocol/introduction.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.