> For the complete documentation index, see [llms.txt](https://alembic.gitbook.io/alembic-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://alembic.gitbook.io/alembic-docs/introduction/what-is-alembic.md).

# What is Alembic?

**Alembic Finance** is a decentralized finance (DeFi) protocol designed to make advanced on-chain investment strategies accessible, transparent, and efficient for all types of crypto investors.

Built on **HyperEVM**, a next-generation EVM-compatible blockchain, Alembic combines the **speed, scalability, and low gas costs** of HyperEVM with the **security and interoperability** of the Ethereum ecosystem.

At its core, Alembic’s strategies are powered by **HyperCore,** a high-performance execution and analytics engine that manages yield optimization, portfolio rebalancing, and cross-protocol strategy execution in real time.

Together, **HyperEVM** and **HyperCore** form the foundation of Alembic’s infrastructure, delivering institutional-grade performance within a decentralized framework.

In short:

> Alembic Finance is where DeFi meets professional-grade portfolio management, powered by HyperLiquid thanks to HyperCore and deployed on HyperEVM.

#### **Key Highlights**

* **Non-custodial:** Users remain in full control of their assets at all times.
* **Transparent:** All strategies are on-chain and verifiable.
* **Optimized returns:** Smart rebalancing algorithms continuously optimize yield allocation.
* **Accessible to everyone:** A simple interface designed for both new and experienced investors.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://alembic.gitbook.io/alembic-docs/introduction/what-is-alembic.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
