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

# What is Backyard?

Backyard is yield infrastructure for launching vaults and allocating capital.

We let any yield provider or risk curator launch a vault on Solana to attract liquidity and LPs.

LPs can build manual or auto-rebalanced strategies by merging a wide range of yield products like stablecoins, blue-chip, RWAs, and tokenized stocks.

### Problems we solve <a href="#s0" id="s0"></a>

Yield on Solana is spread across a lot of different protocols, and it's a mess to manage. In Backyard you can handle all of it in one place, and not just that: you can combine different categories of yield in a single strategy, like stablecoins, RWAs, tokenized stocks, and more.

Putting everything into one protocol is risky, so we make it easy to split your money across several.

And the best yield is usually available only to institutions. Our goal is to bring new, great yield to Solana and make it available to everyone.

The protocol is governed by a ve3,3-style economy, which means boosted APR for users and more liquidity for new vaults.

<figure><img src="https://2472987558-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FF2M1JvgzxZ8XZJajMV95%2Fuploads%2FQwurDKmQpcJxXgWsmyvG%2Fimage.png?alt=media&amp;token=7ed16702-3949-4d26-ab8b-774b28fded6a" alt=""><figcaption></figcaption></figure>


---

# 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://backyard-fi.gitbook.io/backyard-finance/what-is-backyard.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.
