> For the complete documentation index, see [llms.txt](https://docs.reserve.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reserve.org/core-components/yield-dtfs/deployment-guide.md).

# Deployment guide

Anyone can create a Yield DTF — permissionless & production‑ready in under 10 minutes.

This guide walks deployers through the launch process: strategic design, parameter configuration, deployment, and post‑launch best practices.

## Overview

The Reserve Yield Protocol provides a system of [factory smart contracts](https://research.csiro.au/blockchainpatterns/general-patterns/contract-structural-patterns/factory-contract/) that allows anyone to deploy their own Yield DTF instance onchain.

![](https://753544653-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEFwcfC1MMOt9iISSOBwK%2Fuploads%2Fgit-blob-848e0f4b50044610e3416a5686104b039f0f733d%2Ffactory%20sc%20light.svg?alt=media)

Creating a Yield DTF can be done either by interacting directly with the [Reserve Yield Protocol’s smart contracts](https://github.com/reserve-protocol/protocol) or any user interface built on top of them. The Reserve app provides a convenient [interface to the Yield DTF factory](https://app.reserve.org/deploy/yield-dtf), but any front‑end can access the same permissionless contracts.

## Learn more

* **Getting started** → [Designing a successful Yield DTF](/core-components/yield-dtfs/deployment-guide/designing-your-yield-dtf.md)
* **Deployment walkthrough** → [Using the Reserve app UI](/core-components/yield-dtfs/deployment-guide/yield-dtf-deployment-walkthrough.md)
* **Reference parameters** → [Advanced parameters](/core-components/yield-dtfs/deployment-guide/advanced-parameters.md)
* **Post‑launch playbook** → [Tips for DTF success & adoption](/core-components/yield-dtfs/deployment-guide/post-launch-playbook.md)


---

# 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://docs.reserve.org/core-components/yield-dtfs/deployment-guide.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.