# For Creators

## No code required.

Create, own and operate your own investment pool on Dappy. Using our templating tool, you’ll be up and running in less than 5 minutes. No code required.

## Your pool, your rules.

#### Owner Fees

Pool owners set their own fees. Every time an investor enters your pool, you will earn a small fee. With a lot of investors entering your pool, these fees can really start to add up. Use the cashflow from fees to buy additional exposure and marketing for your pool.

#### Rewards Rate

Set your own revenue goals and work out how much inflow you can viably generate per day. Setting a high rewards rate (above 1.5% daily) will be deemed high-risk. Maximize your inflow by strategically monetizing investors' pooled funds. Make sure to redeposit earnings frequently to pay your investors and maintain a healthy record of growth.

#### Hedge Ratio

The hedge ratio you set determines what portion of pooled funds will remain locked in contract versus what portion of funds you will be able to access and monetize. Setting your hedge ratio high (above 75%) will give your investors high confidence that their funds are secure, but may make it more difficult to keep up with your outflow. Choosing a lower hedge ratio means you'll have access to more capital, but requires more trust from your investors.

## You are not alone.

Join a flourishing [community](https://dappy.gitbook.io/docs/protocol/links) of owners, investors, advisers and onlookers who contribute to the project by exchanging new ideas, tips and strategies. Take advantage of our shared knowledge base and open-source tools to increase your understanding and elevate your performance.


---

# 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://dappy.gitbook.io/docs/basics/for-creators.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.