# Canopy's Tech Stack ### Overview #### **1.** [**Canopy UI**](https://app.canopyhub.xyz) The Canopy User Interface serves as the primary gateway for users to access and interact with the ecosystem. Designed for simplicity and efficiency, it allows users to deposit funds, track performance, and manage portfolios effortlessly. *** #### **2. Canopy Vaults** Canopy Vaults enable single-sided liquidity provision, leveraging top-performing protocols on the movement network**.** These vaults offer competitive yields while abstracting away the complexities of the LP process into [multi-protocol strategies](/canopys-four-layers/strategy-layer.md). *** #### **3. Automated On-Chain Liquidity Management Strategies** * Built-in ALM strategies such as **YieldIQ**, **MedianStable**, **Flip**, and **Ascend**. These strategies optimize liquidity allocation, adjust to market conditions, and maximize yields. Each strategy targets specific use cases, such as dynamic reallocation (YieldIQ), stablecoin pairing (MedianStable), pair flipping (Flip), and growth in volatile markets (Ascend). *** #### **4. AEGIS Contract** The **AEGIS Contract** autonomously manages and rebalances vaults to ensure optimal performance and liquidity allocation. Its failsafe mechanisms prevent unauthorized actions and mitigate risks, providing security and resilience to the ecosystem. *** #### **5. Reward Distribution Engine** The Reward Distribution Engine enables protocols to distribute incentives efficiently, aligning users with project goals. --- # 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.canopyhub.xyz/about-canopy/canopys-tech-stack.md?ask= ``` 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.